Nudge works fine when going through menus, refuses to bind to keys, no matter what keys they are.

Before you start talking about "did you make sure numlock was on, did you bind the function to a key" and all of that, I have been using Sonar/Cakewalk since PA days, I know how to bind keys, and have been doing these kinds of things with the software for years.  This feels like a bug and I am hoping someone has found a workaround.

 
Has this happened since the last update ?
 
See :  http://forum.cakewalk.com/Solved-The-nudge-doesnt-seem-to-work-since-the-M1-update-m3373584.aspx
 

Multiple reports coming in on this. Sounds like this explains all the others.
So a new bug.

Is simple to verify the keybindings, but something that did strike me odd is that the Num Pad keys "register" as the number row keys (screensets) when in the assignment window and the listbox below the "Locate Key" button has focus. I honestly have never noticed this before today, so not sure if that behavior is related to this issue or not (also commented on that thread about this). "Locate Key" works, but hitting NumPad 1 alone does not.
 
To the OP, I was able to rebind them using "Locate Key" on NumPad 1, and "Nudge" Since they were all in view at that point I did the binding with the mouse only.

I use my # 7 - 9 number keys for fastforward / reverse.
ive bound them to make life easier in scrolling the timeline left and right.
I can remember if these were binded to the nudge or not.

I can reproduce this simpleM -  nudge definitely not functioning on the numeric keypad,  even after manual binding under preferences. I am on the N update.  Could be that Sonar is not recognising the numlock key state? 

mettelus
Is simple to verify the keybindings, but something that did strike me odd is that the Num Pad keys "register" as the number row keys (screensets) when in the assignment window and the listbox below the "Locate Key" button has focus. I honestly have never noticed this before today, so not sure if that behavior is related to this issue or not (also commented on that thread about this). "Locate Key" works, but hitting NumPad 1 alone does not.
 
To the OP, I was able to rebind them using "Locate Key" on NumPad 1, and "Nudge" Since they were all in view at that point I did the binding with the mouse only.

Hi mettelus.  I tried this and they show as bound but do not function.  Did you bind them with the numlock key on or off? If I turn numlock off they will bind and function -  but that is to the wrong keys. 

Interesting, I just tried to confirm so I could alert the Bakers. However it's working as expected with Newburyport. I wonder if the issue is that I don't use keyboard bindings for this, I just accept the default and have never bound nudge to the keyboard...I assume I didn't need to, because it worked.
 
When I looked at Preferences, they show as not bound. Perhaps SONAR automatically binds these, and senses some sort of conflict if you go in there and attempt to bind them yourself?
 
Maybe someone could try an experiment: If you have them bound, zap any existing nudge bindings, then try again and see if it works.

Hi Craig.  Thanks for chiming in.  I zapped all of the bindings for nudge and still no change. Weird
 
They show the default 'assigned' to nudge' without the user binding indicator but do not function. 

Anderton
When I looked at Preferences, they show as not bound. Perhaps SONAR automatically binds these, and senses some sort of conflict if you go in there and attempt to bind them yourself?

Yes, by default 1,3,4,6,7 and 9 are bound to the nudge functions. When I tested them in Newburyport earlier today, they worked in a new project on a selected audio and MIDI clips. The locate key function in the keybindings preference screen will show the bindings when a project is loaded.