Described here ---> http://forum.cakewalk.com/FindPost/3125708
 
It would be great if this was incorporated in Sonar so we don't have to worry about what happens if azslow3 gets bored with it, or having a change made on the Cake side that blows it up.
 

if the developer gets bored, he can always check the source back into some open source repository ...
yet, code without the main developer usually is dead code ...
just my 50 ct.
 
why worry about the future, it's all open anyway ;-)

Q:  Why worry about the future?
 
A:  I consider the future because experience tells me it's wise to do so.

It would be great if Cakewalk did that but considering it was Cakewalk that released the SDK as open source I hardly think they would take it back now. They didn't want to develop CS software to start with.

While SDK is open source, my code is not. You are using proprietary code without guarantied support all the time (think of old devices). And so I do not see a problem there.
 
But it will be nice in case CW fix CS related bugs on Sonar side. I hope in case we will ask after every new Sonar update, that has some chance to happened. I believe most nasty bugs (ACT mapping and preset saving) are easy to fix.