Sonar Platinum [2016.11] No Longer Adds Marker with Tranzport

Ugh!
 
Just got done a mobile recording session.
 
I discovered (with great dismay) that, with the 2016.11 version of Sonar, my Tranzport can no longer "Add Marker".  What a bummer!  I hate having to run back to the keyboard between takes to add a marker now.  I don't like that at all.
 
Anyone else see this?
 
Thanks,
Paul

It´s not only the marker button that doesn´t work on the tranzport, but also the REC button. MUTE and SOLO work as expected, but REC doesn´t. When I clik REC on the selected channel in SPLAT the red led lights up on my tranzport. Very strange...

"Project | Insert Marker" does not work for me as well, as Control Surface Command nor as a custom keybinding (they are always working/not working together). "M" is working (also when sent from CS).
 
REC I can not confirm at the moment. For a while I had problems with Rec and Mute on Instrument tracks. But somehow I can not reproduce that (or forgot how to reproduce).

"M" is also not working for us on several computers.
We have no chance to insert a marker with a shortcut.
The 2016.12 update didn't fixed this.

THambrecht
For us it's also not possible to asign a keybinding to insert a marker.
It's also not possible to insert a marker with the Behringer X-Touch.
This is since the Nov. Update.

I can confirm that insert marker is not working with X-Touch since update.
 
 

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!

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

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

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

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.