Yeah, I've been with CW/Sonar for a while. I'm sure the marker could be probably re-mapped to the F11 key - I just haven't looked.
 
I've been working on older projects, so most of my marks are already establish. After that, I mainly use markings on the fly when I hear some sort of error/issue that I may want to come back and address later. When F11 quit working, it became very frustrating to hit stop on the transport, right click and insert a marking. First world problems, eh? lol.

GMGM
Yeah, I've been with CW/Sonar for a while. I'm sure the marker could be probably re-mapped to the F11 key - I just haven't looked.
 
I've been working on older projects, so most of my marks are already establish. After that, I mainly use markings on the fly when I hear some sort of error/issue that I may want to come back and address later. When F11 quit working, it became very frustrating to hit stop on the transport, right click and insert a marking. First world problems, eh? lol.

 
Actually right now the default key for inserting the marker is M. So you can hit M on the fly just like F11. You don't' need to stop. If it doesn't work, go to keyboard Shortcuts and make sure M isn't assigned to any other key. If it's unassigned it defaults to insert marker. Because of this bug, there's no way you can bind F11 to insert marker. I'll be really surprised if it's not fixed with 2017.01 - lot's of complaints.
 

gmp
 
Actually right now the default key for inserting the marker is M. So you can hit M on the fly just like F11. You don't' need to stop. If it doesn't work, go to keyboard Shortcuts and make sure M isn't assigned to any other key. If it's unassigned it defaults to insert marker. Because of this bug, there's no way you can bind F11 to insert marker. I'll be really surprised if it's not fixed with 2017.01 - lot's of complaints.
 

 
Yeah, I found the M binding - and it works on the fly. I just don't like it. F11 is what my hand goes for, and I don't need to look at the QWERTY keyboard to find it. I tend to prefer all my key-bindings on those function keys (in my opinion, this is why function keys exist in the first place). 

GMGM

gamp
 
Actually right now the default key for inserting the marker is M. So you can hit M on the fly just like F11. You don't' need to stop. If it doesn't work, go to keyboard Shortcuts and make sure M isn't assigned to any other key. If it's unassigned it defaults to insert marker. Because of this bug, there's no way you can bind F11 to insert marker. I'll be really surprised if it's not fixed with 2017.01 - lot's of complaints.
 

 
Yeah, I found the M binding - and it works on the fly. I just don't like it. F11 is what my hand goes for, and I don't need to look at the QWERTY keyboard to find it. I tend to prefer all my key-bindings on those function keys (in my opinion, this is why function keys exist in the first place). 

I feel exactly the sam way as you about the function keys and you may want to revert back to 2016.10 or 2016.09 where it was working right. I know this is a bug, but a lot of us have been using this software for a long time and it's important for Cakewalk to let us continue to work as we prefer, especially when they change things on purpose. At least in this instance we'll get the F11 back.

^ I actually wonder if this might possibly be related to cross-coding for SonarMAC. Apple seems to be ditching the function keys (giving users a "touch strip" as a smokescreen to hide the fact that they still don't have a touchscreen). Other mac lines are sure to follow...
 
Not that we will ever know, however, because Cakewalk appears to be covering their tracks and pretending that they never mentioned anything SonarMac in the first place. lol.

Ctrl+F6 and Ctrl+Shift+F6 never worked in Sonar!
 
I've reassigned the old ones - Ctrl+ F9 and F10
 
Another crazy thing is that I can't assign < and > as keystrokes. (German Keyboard)
For Sonar they are not recognized...
 
Bassman.
 

Do we know if Cakewalk is aware of this bug?

gmp

Blades
Ok so I'm just kidding here, but...
 
Based on your post, I would guess that you might be hitting the wrong keys or something is wrong with your keyboard! :) :) :)

Try and move the synth rack to the upper right docked. Very likely you'll then have this problem too.
 
You mentioned something may be wrong with the keyboard, well you may be more right than you realize. Some are reporting problems with the localization issue. An English guy in Germany had some problems like this and found out it's because the German keyboard has some differences. Once he turned off the localization it fixed his problem.
 
I opened a song today that the F key and Delete key worked fine on. I couldn't figure out why, but now I know it's very likely the synth rack. Man this is really weird.

I think his point was that your initial post is missing about 100 letters...

I had the "delete" key issue today. Moving the Synth Rack to the bottom of the Browser window fixed it. I had the "insert marker" issue as well and moving the Synth Rack to the bottom of the Browser fixed it too. I did note that this only happens on older files, in my case. If I start with a template that has the Synth Rack on the top in the Browser everything works just fine.

cyberzip
Do we know if Cakewalk is aware of this bug?

Yes, there are several related posts, especially one about the Delete key not working. In those posts Cakewalk does reply and said it's a high priority. Unfortunately it first came up during 2016.11, which had this huge debacle with run time errors and plugins like CA-2A crashing. They needed to get that one fixed first and from what I can tell that's resolved. So I'd be really surprised if this wasn't fixed in the 2017.01 update.