I have a Tranzport, a Mackie MCU Control & a VS-100, and none of them are working properly now.
 
The Tranzport is the worst off. I can't add markers as others have reported. Worse though, it simply does not link to tracks any more. There is no display when selecting a track, and while the transport controls of rec, mute & solo still work, they stay on even when switching to a track when not enabled.
 
The Mackie simply doesn't work at all. I can turn in on with no problems, but as soon as SONAR is loaded, it starts going haywire. There is a click sound, then all the lights and LED displays start flickering, as if there was some sort of power surge.
 
The VS-100 works with the exception of the markers as others reported. Hope this gets fixed soon!

It's all related. External controllers such as the Tranzport work by emulating keypresses, effectively acting as a ghost user pressing keys on your keyboard. If any keyboard bindings get broken, no external controllers will be able to trigger them.
 
The good news is that this bug is likely the result of a simple typo, and easily fixed by CW.
 
The bad news is that they've got more pressing issues to deal with right now with the Windows thread problem.
 
In the meantime, markers do still work, they're just less convenient to insert. My workaround is to keep the Marker View open and click the + button to insert new markers.

just installed 2016.12 and tried this with the VS-700 only to realize that this also applies for the VS-700 i.e. while keyboard shortcut "M" still works, the dedicated "marker" button on the VS-700 does not create a marker. apparently the MIDI message which the button triggers is no longer mapped properly to adding a new marker in Sonar.
 
I could work around by adding a MIDI translator to link the VS-700 MIDI message to the keyboard shortcut "M" ... however, this only works when Sonar is the application which got the focus ... so I'd much appreciate this being fixed again soon

I had to reassign my foot switch function (punch in/record) after a recent upgrade.  The defaults are listed in Sonar, don't remember exactly where off hand as Sonar is not running at this moment.  Resetting what I wanted mine to do was what was needed.

Same here...the VS-700 marker does not work, but i dont expect them to fix it since "WE" are no longer supported.

keneds
Same here...the VS-700 marker does not work, but i dont expect them to fix it since "WE" are no longer supported.

The topic is discussed in several threads, so:
a) that is not VS-700 specific, it is for all surfaces, custom key bindings and some international users
b) Cakewalk is aware and is going to fix that: http://forum.cakewalk.com/FindPost/3533113
 

I updated to 2016.12 and the "add marker" on my tranzport ..... does not add any marker.
 
Instead .... it is like to press ENTER where the focus is set (if the focus is on ARM track, it arm and disarm the track, for example...).
 
Anyway it seems that this problem will be fixed soon.
 
Regards,
 
Giorgio

keneds
Same here...the VS-700 marker does not work, but i dont expect them to fix it since "WE" are no longer supported.

BOME MIDI translator PRO - the way to fix these things ... and extend control surfaces beyond their factory supplied functionality. Not free but a great tool whenever you need to manipulate MIDI in real time.

Rob[atSound-Rehab]

keneds
Same here...the VS-700 marker does not work, but i dont expect them to fix it since "WE" are no longer supported.

BOME MIDI translator PRO - the way to fix these things ... and extend control surfaces beyond their factory supplied functionality. Not free but a great tool whenever you need to manipulate MIDI in real time.

While for MIDI processing BOME is the way to go, for extending control surfaces in Sonar I think my solution is better (and cost nothing). For example assigning "M" to some control is not far away from "Quick start" tutorial. For those who is going to try, in case you insert AZ Controller after VS-700, set "Block all channel messages" and "Block sysex" in the Options tab.

Hi All - I have the exact same problem the insert marker does not work with Sonar Platinum 22.12.0 build 12. The "M" key shortcut does work, but you can not assign any key binding to Project | Insert Marker.  This renders both my Tranzport and Tascam FW1884 control surface unable to insert a marker.  When you bind "M" to Project | Insert Marker the "M" shortcut stops working as well. Hopefully we will get a fix for this soon.