• SONAR
  • Marker Key Binding not working - *SOLVED* (p.2)
2017/01/12 03:30:42
lapasoa
Well done reberclark. It seems that your workaround is working fine.
2017/01/12 04:30:16
azslow3
There are several threads with the same issue. So:
* "Insert marker" command is not working at the moment. Not as a key binding, not from Control Surfaces. Cakewalk is aware and we all hope that is fixed in the next update.
* "M" key INTERNAL binding to "Insert marker" is still working. So as long as it is not reassigned manually, it does the job.
2017/01/12 09:36:41
THambrecht
This is all is not working here. "M" does not insert a marker.
In my preference "M" is bound to the "global move tool".
Even if I unbind this shortcut "M" is again bound to the global move tool when I restart Sonar.
I have testet to exclude and include the shortcuts from the lenses, I have saved a lense with the unbounded "M" shortcut. Nothing helps. After a restart and several tests "M" is always bounded to the "global move tool".
And we have this problem on 3 computers. And it is not possible to bind any shorcut to insert a marker.
 
2017/01/12 10:29:40
azslow3
It can be localization dependent...
 
Also if you are skilled in Windows, please search for
Kx004D03
in windows registry, is it there? With which value?. NOTE: If you do not understand what I mean, PLEASE DO NOT try to search for it!
2017/01/12 11:55:51
THambrecht
Thank you.
"Kx004D03" solved the problem. Now "M" is working on all computers.
 
2017/01/12 12:24:23
gmp
azslow3
It can be localization dependent...
 
Also if you are skilled in Windows, please search for
Kx004D03
in windows registry, is it there? With which value?. NOTE: If you do not understand what I mean, PLEASE DO NOT try to search for it!




I'm amazed that this fixed the problem. Can you explain what localization dependent means? And what happened in this case with 3 computers?
2017/01/12 12:57:49
azslow3
gmp
azslow3
It can be localization dependent...
 
Also if you are skilled in Windows, please search for
Kx004D03
in windows registry, is it there? With which value?. NOTE: If you do not understand what I mean, PLEASE DO NOT try to search for it!




I'm amazed that this fixed the problem. Can you explain what localization dependent means? And what happened in this case with 3 computers?


Since the problem was solved by Kx004D03 (I understand that such explanation can sound confusing ), localizations was not the problem. Sonar comes in several languages, many things are called differently, so can affect the key bindings as well (f.e. German Y is not at the same place as in English).
 
Sonar is saving key bindings in Windows registry. Kx004D03 is the key binding for M. So manually cleaning such entry is the hard way to unbind it, in case Sonar for some reason can not do that itself.
2017/01/12 18:21:13
THambrecht
Deleting the key "Kx004D03" in the registry solved the problem. Now the "M" key is working for inserting markers on all our computers. Before this change in the registry the "M" key was nailed to the global move tool. Within Sonar this keybinding could not be deleted or changed.
This is nevertheless mysterious because we use Sonar in English, although we are in Germany.
And is nevertheless not possible to assign any other keybinding for insert marker. Before update Nov 2016 we used F11.
 
2017/01/13 00:33:56
gmp
azslow3
gmp
azslow3
It can be localization dependent...
 
Also if you are skilled in Windows, please search for
Kx004D03
in windows registry, is it there? With which value?. NOTE: If you do not understand what I mean, PLEASE DO NOT try to search for it!




I'm amazed that this fixed the problem. Can you explain what localization dependent means? And what happened in this case with 3 computers?


Since the problem was solved by Kx004D03 (I understand that such explanation can sound confusing ), localizations was not the problem. Sonar comes in several languages, many things are called differently, so can affect the key bindings as well (f.e. German Y is not at the same place as in English).
 
Sonar is saving key bindings in Windows registry. Kx004D03 is the key binding for M. So manually cleaning such entry is the hard way to unbind it, in case Sonar for some reason can not do that itself.




I'm still amazed you knew how to fix this. Do you work for Cakewalk? In my registry there is no mention of Kx004D03. How did you know that key was associated with the M? My hats off to you, man. My guess is him living in Germany had something to do with this, even though he speaks English.
2017/01/13 07:24:57
azslow3
gmp
I'm still amazed you knew how to fix this. Do you work for Cakewalk? In my registry there is no mention of Kx004D03. How did you know that key was associated with the M? My hats off to you, man. My guess is him living in Germany had something to do with this, even though he speaks English.

Some people hear and know how to find and cut a bad resonance from snare in song.
I  know how to find where and in which from a program saves key bindings.
No rocket science involved, just some experience and background. And this forum is the communication platform which allows us to help each other
 
A program saves settings into files or into the registry. If you change some particular option, f.e. bind M, and then compare what was changed in the files and registry, you find how the option is saved. Unlike copy protection, software is normally does not try to "hide" or "crypt" that.
 
PS. I am also living in Germany. I am using English Sonar, under Russian localization of Windows and German keyboard layout.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account