subtlearts

mileskb
Just to be clear... All of my software is up/running and activated (I used command center).   Am I correct in assuming as long as it's activated already, I'm all set as long as I don't uninstall or try to move to another PC?  In other words it will continue to work on my studio PC as long as my studio PC remains my Studio PC ?  

Well that's the key question, and the answer is there isn't really an ironclad answer. For the present and immediately foreseeable future, the answer is 'yes, but...' - and it's a big but. Basically (and there are many threads here discussing it, and others likely more qualified than me to speculate) everything should be cool for a while anyway, but there is always a chance that Microsoft will make a change to Windows at some point that will break something crucial in terms of Sonar's ability to install or function. I don't know what OS you're on, or if you are in a position to cut your studio PC off from the internet or freeze it from updates, but while those are one avenue that some here have talked about, it doesn't strike me as a perfect solution for anything other than the immediate future.

 
Well, I guess that's encouraging.  I mean I'm running Sonar 2, 3, and 4 Producer Editions (mainly because they had some cool plug-ins and features that were used on projects and I don't want to re-invent the wheel if I have to revisit them.  I recall I had to do something wierd with one of them to get it to install properly, but they are all running on Windows 10 just fine.  I've always used AMD processors going back as far as I can remember and never really had latency issues that I couldn't work out easy enough.   Frankly although technically AMD chips seem to be a little slower, if it wasn't for those waits for processing or saving...  I wouldn't eat or go to the can when I was working in the studio.   I always go back to the fact that I was able to record 8 Tracks audio at once on a 486 machine back in the day.   But I digress.   

azslow3
For those who move toward Reaper.... keep your projects in CWP and till you actively used ProChannel modules (other then EQ), do not rush with exporting everything. A simper way to move projects is under investigation (by me)

Sounds promising! I would use that for sure, though I have used some PC stuff over the years but nothing I couldn't recreate pretty easily if the basic project info could be ported without heavy lifting.

Are you still planning to get your control plugin set up to work with Reaper? I'm hoping that's still in the cards too ;-)

subtlearts

azslow3
For those who move toward Reaper.... keep your projects in CWP and till you actively used ProChannel modules (other then EQ), do not rush with exporting everything. A simper way to move projects is under investigation (by me)

Sounds promising! I would use that for sure, though I have used some PC stuff over the years but nothing I couldn't recreate pretty easily if the basic project info could be ported without heavy lifting.

"Basic project info" is what I am investigating at the moment. I have already understood that even "basic" is huge to make any sense (many project parameters, almost all strip parameters,  all clip parameters, MIDI, FXes, automations... uh... endless).
 
Also note that I plan to make the result at least donationware. Related projects are not free (f.e. http://www.aatranslator.com.au/ ) while they do not cover FXes, MIDI, etc.
At the same time I like Reaper concept of "endless Demo"
 
The show stopper can be legal issues. If CWP format is not allowed to be parsed, I will be unable to publish the converter
On one side, what we produce in Sonar is in general "our". And we are free to do with it what we want (WAV, MIDI). At the end, generating output which is not restricted nor a property of someone else is the primary purpose of any DAW. CWP is not "encrypted" and so a parser should not break any locks (which is always illegal). Parsing does not involve Sonar nor any other CW programs RE (that is forbidden by EULA).
But CWP is not a public format, so there can be some complications, I am not a lawyer.
 

Are you still planning to get your control plugin set up to work with Reaper? I'm hoping that's still in the cards too ;-)

That was my primary condition when I was choosing the new DAW. But it will take (a lot of...) time.

azslow3
"Basic project info" is what I am investigating at the moment. I have already understood that even "basic" is huge to make any sense (many project parameters, almost all strip parameters,  all clip parameters, MIDI, FXes, automations... uh... endless).

 
I can imagine! Even just tracks, clips & contents, which would be kind of the minimum to be useful, would be a ton of work to reliably automate; add plugins, routing, and parameters of same, and I can imagine it being a daunting task. Not to discourage you, because it would be awesome to have working, but I can't help wondering if it's worth it? Why not just focus on the plugin port?
 

Also note that I plan to make the result at least donationware. Related projects are not free (f.e. http://www.aatranslator.com.au/ ) while they do not cover FXes, MIDI, etc.
At the same time I like Reaper concept of "endless Demo"

 
Understandable. If it works and saves me a lot of time, I'll happily support it... the Aatranslator project as far as I can see doesn't seem to read .cwp files, can only process .omf files from Sonar, which is of limited use. 
 
I imagine that Reaper's open, text-based file format is somewhat easier to deal with on a technical level? 
 

Are you still planning to get your control plugin set up to work with Reaper? I'm hoping that's still in the cards too ;-)

That was my primary condition when I was choosing the new DAW. But it will take (a lot of...) time.



Yeah I suspect it will not be simple. But again, given what I've seen of the community over there, I suspect and hope you will find more enthusiasm for your contributions. 
 

subtlearts
Not to discourage you, because it would be awesome to have working, but I can't help wondering if it's worth it? Why not just focus on the plugin port?

If I am forced to strictly follow my priority list, I should suspend everything else and continue with Sibiac. That project, unlike my other activity, can be a game changer for a lot of people (far above music community). But I am not a "company", so I am not force.
 
But there is a list of reasons to look toward the converter:
1) as many "programmers", I like challenges. The driving force is the question "is that possible?". With controllers, I have checked: yes, it is (but see below). With Sibiac I have checked: yes, it is. With the converter, till I have the first working prototype, the answer is unclear
2) "strategic" thoughts about Sonaries. Many Sonar power users still not consider Reaper as a serious alternative and look toward other DAWs. Guess what will happened in case they can download Reaper demo (without registration, 11MB download), download the converter (without registration <1MB download), click on own Sonar project and get it "as is" (or close to that) in Reaper. I mean they will be able to see how what they have already done is mirrored in Reaper. I guess that can be more convincing then watching some videos "how to do this and that" or "is this feature exists". Also when someone has 100+ real projects in Sonar and there is only one other DAW which can open them (and this DAW works on Mac,Win,Linux+Wine and probably Linux in the future!), it can be hard to choose something else.
3) in Reaper, there is one Control Surface case which is not well covered (unlike in Sonar): MIDI keyboards with extra controls. To make AZ Controller work in such case as good as in Sonar (even better), I need some modifications in Reaper. If I can present such useful add-on as CWP projects converter, I hope there is better chance Justin or John perceive my requests and questions as serious.