Bapu

And to all the mothers who raised decent caring future fathers.

Yup, your cash is always flowing to the company that only offers subscriptions ? j/k see my signature

I've contacted both @azslow3 and moss on the Reaper forum. We'll see if either agrees they need to fix something. The biggest finger pointing I'd expect is how the DAWProject file thinks that Kontakt and Opus are FXs and not instruments. (as a programmer I'd say the issue is somewhere between ReaCWP and Project Converter). Footnote, if I create a Studio One project with Opus in it and I interrogate the DAWProject XML file it thinks it is an "instrument" (uh DUH!). The secondary finger pointing is either between ReaCWP and Project Converter or between Project Converter and Studio One. That's the FabFilter C-2 VST3 plugin being in Reaper but not Studio One. Footnote: In interrogating the DAWProject file created by Project Converter there is no entry for FabFilter. Still is ReaCWP creating it incorrectly in the .rpp (it's there and works) or is Project Converter not seeing understanding it correctly.

Here's an update based on nearly two days of experimentation with ReaCWP and Project Converter attempting to take a MIDI only CbB project to Studio One. @PavlovsCat may be interested. It required some manipulation after these steps: 1. Consolidate all MIDI tracks (not 100% sure this is necessary but a 'safety' step', Save song as well as Fabfilter C 2 VST3 settings as a preset. 10 minutes. 2. Open Reaper (with axslow3's ReacCWP plugin installed) and open Lasse's .cwp, Save a s a Reaper .rpp file. 2 minutes. 3. Open the free Project Converter (v1.2.2) and convert the sabed .rpp in step 2 to a DAWProject file. 2 minutes. 4. Open Studio One and open the DAWProject file. 3 minutes (Kontakt and Opus took some time to load). Now here is where the fun started. 4.1. Project temp was off (120, not 90) and the MIDI performed as such. So I went back to Cakewalk and saved the project in MIDI 1 format. 3 minutes. 4.2. Removed all MIDI in Studio one and replaced it with the output of the MIDI 1 saved file. 5 minutes. 4.3. Now the DAWProject file seemed to think that Kontakt and Opus were audio Fxs not instruments (that took some time to research). So, it created audio tracks with Kontakt and Opus as 'inserts'. As we know Studio One wants instruments in the Instrument Rack and then have instruments tracks feed their MIDI data to the respective instrument. The conversion did create instruments tracks with the MIDI correctly. But they had no "instrument" to pint to. Nothing played. Thiis mishap is on Instruments is either azslow3 or moss (from the Reaper Forum) issue to be solved. I'll be taking it up with them. Small issue is that although FabFilter C-2 (VST3) was in the Reaper project, and the guts of the DAWProject file creted by Project Converter knew about it, Studio one did not have Fabfiler C-2 VST 3 in it (not the VST version either). That too needs to be taken up with moss in the Reaper forum. But here's the weird part. All instances of Kontakt and Opus do a send to EW Spaces II. Spaces II is in the .rpp and DAWproject files. And it's in Studio One after opening the DAWProject file with the correct settings. Fortunately, the inserts of Kontakt and Opus (11 in all) were configured correctly. So, I simply dragged them to the instrument Rack and then pointed the instruments tracks to their correct instance of Kontakt and/or Opus. (20 is minutes or so). Then I added Fabfilter C-2 VST3 and loaded the saved preset made back in Cakewalk. (1 minute) The project plays "pretty much like the original wav file. I did not null test yet. I'd expect them to probably not null but I'd rather just trust my ears that it's good enough to start with if I were inclined to either edit/add to/remix the orchestra. Knowing what I know now, it would take about an hour or so to do similar sided projects. Hopefully azslow3 and moss can get their issues sorted out.

@cclarryprobably knows. I'm not at my Studio computer.

Why not petition @azslow3 to say we need a CWP Converter (like this Reaper one by MOSS) for CbB/Splat to DAWProject format? Someone suggested that MOSS created that in a very short time (hours or just few days). If MOSS and @azslow3 got together I would think in less than a week they could have a direct CWPtoDAWProject converter. I'd chip in $100 for the development of that.

Or as @Jim Roseberry says, maybe I only need to spend $15 for a one month usage every now and then. As it is I probably only open up CbB for real use 2 or three times a year at most.

Since I no longer record/mix/master in CbB this is no great upset to me. My only observation is that once a person was on the Cakewalk train, a version update was $49 for years and then slowly crept up to $99 (IIRC) and then the Lifetime Update hit (and flopped obvs). In today's economy they've decided that $299, $399 or even $599 for a base product and then version updates at $49/$99 is better served by everyone in at $149/year. Hats off to BandLab, I say. Will I be a full on yearly member for on and on. Maybe.

Reaper to DAWProject format (which is doable, via a free 3rd party tool) so that it can be opened in Studio One is a bit more problematic given that Reaper has the most flexible track routing options (which can mean more complex). Since a track in Reaper is anything you want it to and ypu do that without being confined to any way of identifying what type of "track" it is. There is no formal track/bus/vca/aux/fx identification. Just route what you want where you want. Heck a Reaper track can be an instrument (ala Cakewalk) with audio in it too all the while being a folder. Why you would want to do that is beyond me but it probably would be done with horrendous results. I've seen reacwp make a valiant effort to structure a Reaper project out of folder, tracks and buses and as I said, I had some pretty good results in the 20 or so projects I tested. But I use mostly audio with some occasional simple MIDI. I just never went fully into using Reaper. I found Studio One a better fit for me.

If you want to go to Reaper, there is a painless way using azslow's plugin called reacwp it works pretty good for me for Audio only projects. All you do once reacwp is installed as a Reaper plugin, is open the .cwp in Reaper and save the Reaper project to wherever. I did discover that Cakewalk Instrument tracks have a wonky result from reacwp, so a quick fix is to move the MIDI to a MIDI track and routing that MIDI to the Instrument track which is extremely helpful before opening the .cwp file in Reaper. YMMV

My thoughts from my day one on FB. Killed my personal account so people would quit bugging me. I created a "music" account that I only use for User Groups and I've all but stopped going there too.

Installed!

Not Installed! I was sure I owned the Pro Version but a review of My Account says "no way Hose-A", yet I do get an offer of $123 since I own some "other" products.

nvm

30 files done 18 to go 61.4% of size done.

Probably their site since I have 2000Mbsec service but typically get 1000Mbsec.

Started downloading 4 hours ago and I'm at 43%.

Aha! I only installed the engine. Shouldn't be too long now for the ROOM PACK. ?

MIDI to follow one day soon I suppose.

Or "free" if using a prepaid serial number. Installed!

Installed!

Ya Installed!

Installed!

I bought it after the 3rd update. Works a treat with my limited knowledge at this point.

Imagine if all your plugins were actual hardware ?