on GITHUB https://github.com/Cakewa...lk-Control-Surface-SDK i have found open sources for some Cakewalk surfaces:
ACTMidiController, MackieControl, VS100, VS700

Everyone with C++ knowlege can use this framework to build her own control surface plugins for SONAR

i think this information should be made more public to MIDI hardware controller manufacturers

That's why you found it. Cakewalk put the SDK in the public domain a good while ago. Cakewalk have clearly chosen the path of supporting development for touch control rather than hardware controllers.thats the reason why they released the SDK into the public domain.

there's been little change to the initial touch support since x1... however, some useful folks have already picked up the SDK ball and are running with it, see this thread: http://forum.cakewalk.com/You-can-integrate-your-Control-Surface-with-SONAR-as-deep-as-you-want-m3125708.aspx

Aszlow3 has been doing really good old work with the SDK. Seems to really know his stuff.

Cakewalk put SDK in the public domain long before they have made the first touch enabled version (before the first touch screen was made). The last UPDATE of this SDK, together with VS/MCU source code, was moved from CW site to github not so long time ago.
 
Manufacturers are aware and was using the SDK. But most of them (I guess after counting the number of customers) are no longer doing that. The latest example is Naktar. They have made a plug-in for Impakt, but then they have written nothing for Panorama. Novation still use it in Automap.
 
And not that it was not explained OP in his previous thread...

azslow3
Cakewalk put SDK in the public domain long before they have made the first touch enabled version (before the first touch screen was made). The last UPDATE of this SDK, together with VS/MCU source code, was moved from CW site to github not so long time ago.
 
Manufacturers are aware and was using the SDK. But most of them (I guess after counting the number of customers) are no longer doing that. The latest example is Naktar. They have made a plug-in for Impakt, but then they have written nothing for Panorama. Novation still use it in Automap.
 
And not that it was not explained OP in his previous thread...

Congratulate, you have done a great job with your "AZ Controller" MIDI controller config Plug-in
Now i have tested your "AZ Controller" and i would ask, why is this "AZ Controller" plugin not part of Cakewalk package?
With "AZ Controller" i can configure now my MIDI hardware after a first settling-in period almost easily.
 

That is an option I was talking about from the beginning.
 
AZ Controller is not in Cakewalk package because I am just a user, I am not working for Cakewalk.
 
As you can see I am also preparing ready to use preset for this plug-in, in case someone has no time/background to configure it the way he/she wants, but has time to test the result and report what is not working (since I do not have any of these devices). That is why I have asked which particular device you have and what you are missing in its functionality. I can try to help then.
 
The plug-in has like 90% of what SDK provides, the rest 10% I simply do not need myself nor was asked to implement. At the same time, there are many features which do not exist in other plug-ins. If something can be done and is requested, I normally just code it.
 
There are many bugs in SDK and Sonar which are Control Surface related. There are some parts from Sonar which are not covered by SDK at all (Matrix for example). And CW does nothing in that direction since years. At the same time, what exist and work has sufficient power to cover above average needs.
 
Note that AZ Controller has no strict device <-> preset relation. So every new feature coded is available to use with any device.
 
From what I know, there are (successful) attempts to convince Launchkey/pad illuminate pads according to user preferences. The same for MCU (not really)compatible devices. So, apart from some "proprietary" protocols (made by manufacturers to be incompatible on purpose) it is possible to work with modern surfaces in Sonar. Other question who really want spend time for that. At the moment, CW, Manufacturers and ... users show close to no interest.
 

azslow3
That is an option I was talking about from the beginning.
 
AZ Controller is not in Cakewalk package because I am just a user, I am not working for Cakewalk.
 
As you can see I am also preparing ready to use preset for this plug-in, in case someone has no time/background to configure it the way he/she wants, but has time to test the result and report what is not working (since I do not have any of these devices). That is why I have asked which particular device you have and what you are missing in its functionality. I can try to help then.
 
The plug-in has like 90% of what SDK provides, the rest 10% I simply do not need myself nor was asked to implement. At the same time, there are many features which do not exist in other plug-ins. If something can be done and is requested, I normally just code it.
 
There are many bugs in SDK and Sonar which are Control Surface related. There are some parts from Sonar which are not covered by SDK at all (Matrix for example). And CW does nothing in that direction since years. At the same time, what exist and work has sufficient power to cover above average needs.
 
Note that AZ Controller has no strict device <-> preset relation. So every new feature coded is available to use with any device.
 
From what I know, there are (successful) attempts to convince Launchkey/pad illuminate pads according to user preferences. The same for MCU (not really)compatible devices. So, apart from some "proprietary" protocols (made by manufacturers to be incompatible on purpose) it is possible to work with modern surfaces in Sonar. Other question who really want spend time for that. At the moment, CW, Manufacturers and ... users show close to no interest.

if i would have'nt post here, i newer would know anything about AZ Controller and i think most HW developers and CW users have the same problem. It's time to make it more public, maybe a reference on CW MIDI controller support documentation or online documentation and you could also use KVR Forum to present your AZ Controller.
I think here on this CW forum are mostly CW users and no HW developers...

I have created AZ Controller presets for:
M-AUDIO Oxygen 61 3rd gen
NOVATION Impulse 61 DAW-Mode
iCON iControls
these presets could also be used as template for unsupported HW MIDI Controller and only MIDI Commands must be reassigned on Hardware Tab.
 
presets can be downloaded on:
http://www.azslow.com/index.php/topic,171.0.html