Oh yeah, a SONAR bus can either be a sub-mix of tracks, or it could be a sub-mix of other buses , or it could be a combination of both of those things.
 
Just my $.02USD.

emwhy
For those of you who aren't familiar enough with Reaper, unlike Sonar you can set-up effects on the track folder that effect all the tracks in that folder, you can even have sub folders in those folders and use effects on them. Can't do that in Sonar.

Sorry, but both statements are not accurate. In reaper there are no "Folders", but Tracks can be "Buses" (while you can never see that in Reaper itself, the option in RPP files is called "ISBUS"). These "Buses" can be folders.
So effectively, an effect on Reaper folder is the same as an effect on Sonar bus. It effect the sum of signals routed to it.
So the only thing Sonar can not is "draw" buses as folders. Since that is possible in Reaper, b12 does it.
 
Note that in ReaCWP generated projects, these Folder-Buses are folders and buses separately. I mean by default, when "Master send" is allowed in Reaper, the track output is the folder (really it is impossible to select track output other way, like Sonar people usually do... took me a good half an hour to understand when I have launched Reaper for the first time). To allow move tracks as user want, without loosing the output (the behavior in Sonar), I explicitly disable "Master send" and add original Sonar output as a send. I ALSO put the track under original Outputs as in folder. Grr... Probably no-one can follow what I mean, sorry
 

Just tested on my work PC and I see totally what and how you're doing things Alexi. Using a track folder for the entire project and calling it Master and then any subgroups/busses/submixes are also in track

So, that "Master", subgroops, etc. are you original buses (or AUX tracks, if you have some). Not something I create on my will.
 

 Only downside is my work projects are very simplistic vs. music projects and we use the 32 bit version of Sonar whereas they are allowing us to test only the 64 bit version of Reaper, so it doesn't find my 32 bit dx stuff like Sonitus and it won't load my Nomad stuff because those are locked to Sonar. Will test at home more tonight

Who does not allow you to test 32bit Reaper? For moving from 32bit Sonar, that is most natural way.
 

Just Another Bloke
How will the plug know if a SONAR bus is a sub-mix or a common FX?
Also, how will a send on a bus (to another bus) be handled? And/or multiple bus sends to a "common FX" bus?

Press "Alt+R" in Reaper, and you will understand that
Also note that in Reaper "MIDI" is a part of the send. So you will see "sends" from MIDI track to Synth track. Also for MIDI  I disable Master send.
 
So, one more time. While I try to create "Reaper natural project tree", I keep complete routing as independent from position in the tree. Moving buses/tracks around, folding/unfolding them, etc. will NOT change the routing (sound). In default Reaper settings, moving tracks in the tree CHANGE the routing (sound). So watch out if you add new tracks, they will behave as Reaper default, NOT as strips from converted project!
 

Glad to see that there is good progress being made.  And also that the copyright / intellectual property lawyers have dropped off 
 
I am pretty sure that we now fall under international maritime salvage laws.

Who does not allow you to test 32bit Reaper? For moving from 32bit Sonar, that is most natural way.
 
Our IT dept. made that call. At the time I didn't think it would possible to do what we are now testing so we agreed to go 64 bit. This was over 3 weeks ago.I would need to go back and ask them permission to install the 32 bit version. Our company is very strict about what we can run on our workstations. Even with demos.
 
 

I'm less likely to add new tracks to a converted RPP from SONAR. For me this about moving all old projects in SONAR to my new DAW of choice (as it stands Reaper is that choice today) in the event that SONAR simply will not work any more. The beauty of this plugin for Reaper is that SONAR could stop working completely but I can still "extract" my old projects to resurrect for a remix if necessary.
 
As far as new projects I intend to do it the Reaper way.
 

emwhy
Who does not allow you to test 32bit Reaper? For moving from 32bit Sonar, that is most natural way.
 
Our IT dept. made that call. At the time I didn't think it would possible to do what we are now testing so we agreed to go 64 bit. This was over 3 weeks ago.I would need to go back and ask them permission to install the 32 bit version. Our company is very strict about what we can run on our workstations. Even with demos.

Make sense (I mean your IT dept. rules).
 
For the toping of moving plugins, I have 2 ideas:
1) "convert" presets for some particular plug-ins into presets for some other plug-ins. F.e. ProChannel EQ -> ReaEQ. That way I can "recover" at least some ProChannel modules.
2) (world domination) make general way to click on some plug-in as "Replace with...", the way all settings from original plug-in are automatically applied to the new one.
But both are long term, with undefined future.
 
I have updated the documentation. Comments can be interesting to read for everyone: http://www.azslow.com/index.php/topic,406.msg2433.html#msg2433
 

Just Another Bloke
For me this about moving all old projects in SONAR to my new DAW of choice (as it stands Reaper is that choice today) in the event that SONAR simply will not work any more.

As I repeat several times, that was the origin for the project: cover "in the event" case for long term Sonar users.
 

azslow3
 

Just Another Bloke
For me this about moving all old projects in SONAR to my new DAW of choice (as it stands Reaper is that choice today) in the event that SONAR simply will not work any more.

 
As I repeat several times, that was the origin for the project: cover "in the event" case for long term Sonar users.
 

Yes, it would be foolish to think that after conversion I could just export the project and the Reaper .wav would null to the SONAR .wav.
 
However, it would/will be nice to have a fairly stable/level starting point, which you are getting closer to with each version Alexy. 

OK in the home studio where everything is in 64 bit land I can report the following:
 
vst 3s will load but won't remember presets, that I expected anyway per Alexi
 
All vst 2s load, synths, effects and remember presets (nice work!!)
Dx effects and synths and and remember presets, however Sonitus compressor causes hang/crash, that was also expected per Alexi so no big deal.
 
Big projects with either frozen tracks, or track folders still don't load properly, but the one I tested was quite big over 63 tracks.
 
Routing seems to be ok with subgroups and even effects sends loaded OK.
 
 
 

b14 is uploaded
The routing should be complete (till possible bugs):
 
- sidechain plug-ins support (DX will not work, but VST, f.e. CA-2A, theoretically should)
- multiple outputs from Synth, including mono/stereo (I must admit I have not tested all cases yet)
- Synth in FXBin / FX in Synth Rack (technologically the same case, so a plug-in with MIDI input enabled) should be handled correctly (no longer duplicated in the Synth Rack).
 
But still no levels/pans for anything. Sorry, I am a bit slow
 

emwhy
vst 3s will load but won't remember presets, that I expected anyway per Alexi

should work better with vst3. At least it does on my dev. system (not many VST3 there).
 

however Sonitus compressor causes hang/crash, that was also expected per Alexi so no big deal.

Once we release the converter, and in case that get some "resonance" on Cockos forum, we can write Reaper developers to have a look at DXes with side-chains (and DXi with multi-outputs, like TTS-1).
 

Big projects with either frozen tracks, or track folders still don't load properly, but the one I tested was quite big over 63 tracks.

Frozen is not yet processed. As explained early, folders are not going to be converted. But I have mentioned, we can discuss that.
 

Nice.