SuperG
 you are the one who want's to sell onto some DAW - so you do the work to make sure *your* HW product looks good!
 

Yeah totally, but when you're Solid State Logic who make some of the finest consoles available that work with Live, Cubase, Protools, Logic, Studio One, Reaper (I'm forgetting a couple here, let's say every major daws), and then you come to Sonar's makers and have a "spectacular unresponsiveness" from them (an SSL staff member really said that, I will find the quote if necessary), you probably say to your clients "well, if you want to use our products, maybe you should stick to Protools, or any other daw than Sonar".
 
And they will! When you have a multi hundred thousand bucks studio (or even my modest couple K$ one), you want your clients to see SSL-like names. And when you buy ssl gear that complies to the mcu protocol, you expect it to integrate without drama with your daw.
 
That seem to mean that Cakewalk have a different approach, the only daw which is windows only, the only daw that don't care about Solid State Logic which hardware is found in EVERY major studios.
 
I would not compare Sonar to Windows in Seth exemple, but more to Linux, at least regarding control surfaces. Linux is the less supported os cause cause they think "if they want something to work, they just have to hack their way there". Well many people decide to use Windows or OSX cause everything is ready to use.
 
Maybe times were hard with the Roland and the X serie legacy and they had no time for SSL but I still think that a little something could be done.
 
I have a $5K SSL Nucleus that literally make Sonar crash. SSL + iPMidi + the current MCU/XT = total mess/eventual crash when the project is getting larger.
 
I NEED to use another daw to use my Nucleus, or disable it completely when using Sonar, that's a REALLY bad surprise. Imagine if I bought a $100k SSL AWS. Sonar would be forever in the garbage and I would spread the word to those who ask which daw to choose.
 
Don't you think?

Dyonight
 
Yeah totally, but when you're Solid State Logic who make some of the finest consoles available that work with Live, Cubase, Protools, Logic, Studio One, Reaper (I'm forgetting a couple here, let's say every major daws)

Here's the complete list, which includes SONAR. I'm just passing along info from SSL's web site, don't shoot the messenger.
 
What DAW software is compatible with Nucleus?
The Nucleus can be used with DAW software that conforms to the MCU or HUI control surface protocols. This includes SSL Soundscape, Steinberg Cubase and Nuendo, Cakewalk Sonar, Logic and others.
 
The mapping of physical Nucleus controls to DAW software functions is determined by the selected 'profile'.  Nucleus comes with default profiles for the following DAWs:

• Logic
• ProTools 
• Cubase
• Nuendo
• Live!
• Studio One
• Sonar
• Soundscape
• Reason
• Samplitude
• Digtial Performer

thanks Craig.... I see the article was updated the 17/11/2014... maybe there's hope...
 
But still, I need to verify I have a Sonar profile on my Nucleus memory card, it's up-to-date and there's no mention of it in the release note

Dyonight

SuperG
 you are the one who want's to sell onto some DAW - so you do the work to make sure *your* HW product looks good!

Yeah totally, but when you're Solid State Logic who make some of the finest consoles available that work with Live, Cubase, Protools, Logic, Studio One, Reaper (I'm forgetting a couple here, let's say every major daws), and then you come to Sonar's makers and have a "spectacular unresponsiveness" from them (an SSL staff member really said that, I will find the quote if necessary), you probably say to your clients "well, if you want to use our products, maybe you should stick to Protools, or any other daw than Sonar".

What do you think SSL Nucleus is (apart from the audio interface)? It is very simple peace of hardware, less complex then 16 mouses for $5 each. It can send/receive several MIDI "Note pressed", "Pitch band changed" and "Control changed". It can do NOTHING more than that, for any DAW. From the DAW perspective, it is equivalent to 3x $30 Korg Nano devices.
 
Mackie has made a "standard" long time ago. MCU is ALSO just a very simple device when you look from the computer side. But they have managed to establish quite "smart" software driver in many DAWs (SONAR inclusive) which make you "believe" the device itself is smart. And so they can sell the devices for >$1k.
 
Now lets look at SSL: they have done NOTHING on the software side, they just reuse what Mackie has established. They sell the device for $5k which is just MCU+XT IMITATION. And when something goes wrong, they blame DAW Mackie driver for be "incompatible". And you trust them.
 
But why you can trust what I am writing? Because that is relatively easy to prove! Download Mackie Logic Control documentation (free in Internet) which describe COMPLETE Mackie protocol. Download SONAR Mackie plug-in source, which is also freely available (thanks to CW!). And compare the protocol to implement with the implementation. I bet in case you find some inconsistency, CW will fix it. I went throw the whole source to make a preset for my plug-in and I have not found such inconsistency.
 
So, what exactly is wrong in that plug-in from SSL perspective? Why they do not want spend time to modify MCU plug-in (MIT license, so no legal issues) and make it work for Nucleus? Till SSL answer these questions, there is no reason to accuse CW in "spectacular unresponsiveness" but a good reason to accuse SSL in an attempt to fool users.

Any update on nucleus and sonar integration ?
If some avid control ..artist or s3 have also infos .... Tired of the vs 700 ...