I spent all weekend migrating my current project over to Studio One, learning how to setup Studio One and starting mixing in Studio One. The process appeared very painful at first, with some roadblocks along the way to which I had to find workarounds. I was very skeptical in that I knew that I am going to throw away 30 years of experience and knowledge on how SONAR works but realize that the time to go through this painful process is now.
I will say that at first my mind was telling me I was right in that nothing could replace Sonar or that it would take months to be able to put a project together in another DAW (learning curve). I was wrong, once I got to know my way around a bit, it became easier and more enjoyable.
My project includes about 5 instruments triggered with MIDI. Using Kontakt, BFD3 for drums and UVI. I also have live guitar and bass tracks along with live vocals (wave files).
I was able to save my Sonar project as a MIDI format 2 file and simply load it into Studio One. This method copied along the tempo map from Sonar as well. I then had to delete all the blank audio tracks that came with the MIDI file from Sonar (trying to load my audio into these tracks caused Studio One to crash). I will also say that I was using Studio One 2 in the beginning and that may have been the problem (not the latest version with its bug fixes). I was then able to load in all the wave files from the project directly from the SONAR audio folder of the project.
I also wanted to record some live track stuff so I redid the bass guitar directly in Studio One.
Now, the good news. Studio One is so much more responsive than SONAR (probably because its genesis was a few years ago and not decades ago, no legacy code). Also, the music sounds better in Studio One than it did in Sonar. It is the exact same VSTi's, MIDI tracks and audio tracks, all mixed using the same plugins that were used in SONAR. I did not use any native Studio One plugins. I have no idea why this is. A real good example of how responsive Studio One is compared to Sonar was obvious to me as soon as I imported a wave audio file into an audio track. This would take 15 to 20 seconds in SONAR and it took less than 1 second in Studio One. Also, the project in SONAR was using about 25 - 30% CPU but in S1 it was only using 15-16%.
The GUI is quite different and I will miss the track ICONS from Sonar. My eyesight isn't that good and the instrument track ICONs were a god send in Sonar. The routing is different too; the options are all there but if you insert an FX bus, you can't do a send from the FX bus to any other bus. Let's say you add an FX bus for a delay. You insert the delay but you have NO send mechanism to sent the output of the delay to the reverb bus. There are work arounds to this but just wanted to explain how the routing is different in S1 than SPLAT. But, the bottom line is that I was able to do what I wanted re creating the mix. Editing tempo maps is a bit different. S1 has the same tight integration with Melodyne as does Splat, so nothing loss in the ARA department either. For education purposes, I tried to load a SONAR plugin(Breverb) into S1 but it wouldn't let me with a message that Breverb can only run within Sonar. No biggie for me in that I don't use any Cake plugins other than Channel Tools but I am sure that S1 has a replacement tool.
Bottom line, if you are thinking about Studio One and you are a long time user of SONAR, don't worry, after a few hours of project time in S1, I actually like S1 better than Sonar (time will tell but that is my current thoughts after one weekend with S1. I think that S1 is 50% off until tomorrow, 11/27 as part of their Black Friday sale.
I already owned an earlier version of S1 and was able to upgrade to the latest (FULL) version for $99.50 directly from Prosonus web site.
Good luck to you all in finding a new DAW for your projects. I am still very disappointed and sad over the SONAR shuttering news but hey, life goes on.
I also want to thank all the kind folks on this forum who have helped me and others over the years.