Yeah. Basically: 
 
The previous behavior was:
 
Request a handshake over and over again and do nothing else until you're responded to.
 
The behavior after my modifications:
 
Immediately pretend a successful handshake happened.
Never request a handshake.
If you get a handshake request, behave as usual and handshake back. (should keep everything that worked before, working still).
 
 

First I love Sonar X3 .   That said, not having these protocols working properly with control surfaces seriously compromises the ability for SONAR based studio owners to provide a truly professional environment.  Without the ability to have a full functioning control surface like the other DAW competition, it puts SONAR out of the running for use in a professional environment that many clients expect, especially those who still prefer the hands on approach.  I can mix as well as anyone using only a mouse and manual track by track automation.  However, to get the "true studio experience", a control surface is required and many clients simply will not take you seriously if you do not have one. Multi finger mixing is a thing of beauty and even fader automation is barely supported in many CS's let alone plug-in pot movements etc.   "MIX MOVES" have always been  joyful part of mixing and to be able to capture those from a physical surface into the box is still critical to getting mixes with the human touch.  Beautiful equipment like the SSL Nucleus, Mackie Control and even higher level stuff like the SSL Matrix is just not supported or really usable anywhere near their potential.   This is a HUGE gap that it's time for SONAR to address.  I have been considering moving up my level of production and studio experience only to read and discover none of the products I would consider are barely supported if at all.   I wonder if the Tascam merger might change that as they make some awesome interfaces and control surfaces as well that also lack in true Sonar X 1,2 or 3 support.

I'm with you stxx... However priorities priorities.

My guess is they're banking on more and better touch control and people getting nice big touch screens instead of dedicated DAW control hardware. Sonar is in the front lines with that and in many ways it makes more sense to invest in that, from the developer's as well as the consumer's POV.

Their touch screen again is cool for the little guy working solo but if you have a real studio control room with u and a few bandmembers and you want to mix old school which is still very organic and is still how the big boys do it, every other daw can support that but sonar. Something like Raven which is the future of control surfaces I think still uses the protocols. Sonar to touchscreen is good for editing but the space to work with multiple set of hands and fingers just isn't there. Sonar must get this together. The protools avid sw / hw integration is just phenomenal and is a big reason sonar is the least "pro" than any of the others

I have to be sympathetic with stxx. Control surface support in SONAR needs updating!
 
In my experience, The ACT controller plug in works really nice, but only if I'm working with 8 rotors, 8 sliders, and 8 buttons. I have 24 rotors on my controller (M-Audio Keystation Pro 88), and when I setup those 24 rotors for use with the Cakewalk Generic Surface controller and ACT Plug In and use ACT learn mode to assign those rotors to the rotors of the Pro Channel EQ, SONAR doesn't remember the assignments (SONAR X1).
 
To keep having to reassign those 24 rotor controllers upon re-opening a project is a pain in the butt.
 
I really wish SONAR will become more solid in the area of control surface support, for generic control surfaces and with known control surface protocols, such as Mackie Control Universal!
 
Please, Cakewalk, help us out in this area? And I perceive this recent move to present us with the release of the Cakewalk-Control-Surface-SDK open source project, is a step in the possible improvement for control surface support. However, it may be a good idea to aim to improve control surface support through efforts made by Cakewalk and the open source project.

Cakewalk really killed it with the VS700. That was the deepest integration I've seen in a daw. Maybe we can modify the 700 plugin to work with other hardware now that it's open source. What are you looking for?

I do see your point, really, but I think as touch screens become larger, more plentiful and cheaper, the hardware control surfaces will start to dwindle. When you think about it, a hardware control surface is really another step between you and the software. It is either tailored completely to the software you use (making it nearly useless for other software and thus an even more niche market) or it is a more general controller (e.g. Mackie) which means it's sort of an abstract general purpose box of faders and knobs. Fine for adjusting your drum mix or navigation, but not really that useful for editing the sound of your VST. A true large touch screen bypasses all of that, although I admit at the cost of the loss of the feel of faders. But we lost the physical keyboards on our phones too and everybody is raving about the new iFads anyway.

I don't think we're there yet, but consider a touch screen the size of the Raven at the cost of a Mackie Control (or close). Or even a touch screen only slightly larger than the Mackie Control. Perhaps make it even easier to select what is on the touchscreen from Sonar, and I really don't think HW CS will stand a chance much longer. Or at least I would believe this to be a workflow at least on par with (and for me superior to) any hardware controller.

EDIT: I'm talking about using the touch screen as if you're setting it up as a hardware controller, so on your desk and lying nearly flat. With your main screen(s) in front like you already have. Put the console on the touch screen permanently if you like, and it is already surpassing the Raven in that you're directly controlling the software. Pretty soon you'd find yourself adjusting a whole bunch of stuff you never would with a Mackie or Raven.

I really like the idea of running a touchscreen as a dedicated console. I am concerned about viewing angle though. If I could get one that had a really nice viewing angle (because I wouldn't be looking straight at it, more of like a 45 to 60 degree angle) I might give up my Mackie Control Pro...

stxx
First I love Sonar X3 .   That said, not having these protocols working properly with control surfaces seriously compromises the ability for SONAR based studio owners to provide a truly professional environment.  Without the ability to have a full functioning control surface like the other DAW competition, it puts SONAR out of the running for use in a professional environment that many clients expect, especially those who still prefer the hands on approach.

I completely agree. This needs to be high on the priority list. For some touch screens may replace the need for a CS, but for many others there will simply be no substitute for putting fingers on a fader or knob, closing your eyes, and mixing.