Back then I had DFHS for drums, and it had both mono and stereo outs. Sonar 5 could do multi-output softsynths, but didn't handle mono correctly. Everything is in your hands, dear usersġ) does Sonar 5 support mono outputs from SoftSynth (for multi-outputs synth)? But since I do not have older Sonars, users interested in "antic" compatibility will have to cooperate a bit (providing examples and making some specific projects). The project from Glennbo does not seems like different, except 2 questions I have mentions (and in respect to features I already convert. Keep up the good work, and I look forward to upcoming improvements. Sorry, if these may have already been reported or if they are just user error!īut we're off to a great start.
REAPER VS SONAR 8.5 INSTALL
To adjust various MIDI settings, I had to install the FX ReaControlMIDI on every track, and adjust appropriately (most importantly, Bank/Program Select, and Volume). I had SONAR FX Velocity, and Frank's MIDI Humanizer.ĥ. My MIDI FX were not converted, but this is probably un-avoidable. And for Channels, I used the Routing icon in TCP, for each track.Ĥ. To change the routing for Devices, I used Reaper's Routing Matrix. This is probably unavoidable, since the (friendly) device names may not be the same between SONAR and Reaper. My tracks were not routed to any MIDI devices. My work-around was to change the TPQN to 960 in SONAR, and then re-do the conversion. I also had this set to 600 in Reaper (Preferences->Media->MIDI->Ticks per quarter note), so it was 600 in both programs. I think the reason is that in SONAR my TPQN (Ticks Per Quarter Note, as specified in Project Options->Clock) is always set to 600 (not the more usual 960, due to personal preference). The tempos (and their changes) were all correct, and I did not get any errors on the conversion. I had to move them all back to the original order. The order of tracks was completely different. This was an all-MIDI project of about 12 tracks, from SONAR (Producer 8.5), to the latest Reaper (5.70):ġ. Here are a few observations I had, when converting my first project.
The only deviation: it is written in "C" (not C++) and cross-compiled under Linux using GCC I think with its under 100kB size and zero external dependencies it fits fine into general Reaper paradigm. So from what I know, it already does "a little bit" more then any cross DAW converter I could find in the Internet (prove me wrong if you know other). * transfer FXes and SoftSynth of all supported kind (VST2(i), VST3(i), DX(i)), including plug-in presets from your original project. * create complete outline of your original project, including MIDI tracks, buses, AUX tracks and sends
This alpha (till possible bugs which I hope the community help me to spot) already can: announced project without real use, unclear when finished if at all.". But you can ask to put particular features higher in my TODO list That is a first alpha version! Far from everything is converted, some parts are converted partially on not precise. You can check yourself, the first post is updated