Got it Craig -  I had to zap ALL key bindings as the nudge status changed with each 'area'  drop down menu.  Working as expected now.  Thanks for that.  Now to just reassign my custom keys:) 

I am on M1. I just checked my reassignment, and they remained assigned (I assigned them with the NumLock enabled). Cycled the NumLock and still assigned.
 
But... I found something even nuttier and more concerning. Num 2 and Num 8 are not assigned to anything, yet when I hit Num 2/Num 8 it took the selected clip (track 1), and moved in up/down tracks. Track 2 is a comped track (only one take lane), and as the clip from Track 1 "passed through" Track 2, it obliterated the take (first replaced, then nothing left)... that is with the take expanded.
 
Closed/Reopened project (no save)... Track 2 take lanes collapsed... moving this clip added a new take each time it "passed through" but did not harm the existing take. As soon as I expanded lanes, the moved clip again replaced/obliterated the only take with data on Track 2 (take 1), even after I had just created 8 new "blank takes" with the lanes collapsed.
 
So there is an issue with the NumLock key... I do not have Num2 or Num8 assigned, yet SONAR is acting like the NumLock is off for "certain instances." I am actually more concerned by the take lane behavior as I have never seen this before.

mettelus
I am on M1. I just checked my reassignment, and they remained assigned (I assigned them with the NumLock enabled). Cycled the NumLock and still assigned.
 
But... I found something even nuttier and more concerning. Num 2 and Num 8 are not assigned to anything, yet when I hit Num 2/Num 8 it took the selected clip (track 1), and moved in up/down tracks. Track 2 is a comped track (only one take lane), and as the clip from Track 1 "passed through" Track 2, it obliterated the take (first replaced, then nothing left)... that is with the take expanded.
 
Closed/Reopened project (no save)... Track 2 take lanes collapsed... moving this clip added a new take each time it "passed through" but did not harm the existing take. As soon as I expanded lanes, the moved clip again replaced/obliterated the only take with data on Track 2 (take 1), even after I had just created 8 new "blank takes" with the lanes collapsed.
 
So there is an issue with the NumLock key... I do not have Num2 or Num8 assigned, yet SONAR is acting like the NumLock is off for "certain instances." I am actually more concerned by the take lane behavior as I have never seen this before.

Thanks Mettelus - have since got it sorted.
With regards 2 and 8, as Scook describes above if they are not assigned to anything custom they will default to nudge up/Nudge down. Could that explain what you are seeing?
 
EDIT : Sorry, my bad. No they aren't.

I had this problem as well on Sonar Platinum Manchester, and fixed it in January 2016.  I deleted my keyboard shortcuts file (which was probably from 8.5) and imported a clean default keyboard shortcuts file and re-added my custom bindings (I only had about 15, so this approach was suitable for me).  Now all of the 9 nudge bindings appear as if they aren't assigned, but they all work as they should.  It seemed like the keyboard shortcuts file got corrupted at some point, and recreating it solved the problem.

shawker
I had this problem as well on Sonar Platinum Manchester, and fixed it in January 2016.  I deleted my keyboard shortcuts file (which was probably from 8.5) and imported a clean default keyboard shortcuts file and re-added my custom bindings (I only had about 15, so this approach was suitable for me).  Now all of the 9 nudge bindings appear as if they aren't assigned, but they all work as they should.  It seemed like the keyboard shortcuts file got corrupted at some point, and recreating it solved the problem.

I think this might have been my problem too shawker. I don't quite know the vintage of my shortcuts file but it is certainly very old!

I just imported SONAR Default Key Assignments.kbn from the Keyboard Shortcuts menu and added my custom bindings back in and all was well. 

mettelus
But... I found something even nuttier and more concerning. Num 2 and Num 8 are not assigned to anything, yet when I hit Num 2/Num 8 it took the selected clip (track 1), and moved in up/down tracks.

That's the default behaviour (and shows as such in Preferences).  From the Help :
 
Table 59.  
Nudge    Shortcut
Left 1    NumPad 1
Right 1   NumPad 3
Left 2    NumPad 4
Right 2   NumPad 6
Left 3     NumPad 7
Right 3   NumPad 9
Up         NumPad 8
Down    NumPad 2


 
 

Thanks for the confirmation. I assumed that might be the case but was more concerned with the "take lane wiping" while using them. It seems the Num2/Num8 are mimicking "shift-drag" behavior, which is fine, but I am not sure the behavior of creating a new lane when collapsed, but overwriting lanes when open is intended. This may already have a bug report against it, but not investigated.
 
Steps for this, move clip with Num2/Num8 across tracks with collapsed take lanes. It inserts a take each time. If you have lanes expanded when doing so, it replaces the data in take lane 1 (even though 2 is empty, and 3 could be created).
 

Paul P

mettelus
But... I found something even nuttier and more concerning. Num 2 and Num 8 are not assigned to anything, yet when I hit Num 2/Num 8 it took the selected clip (track 1), and moved in up/down tracks.

That's the default behaviour (and shows as such in Preferences).  From the Help :
 
Table 59.  
Nudge    Shortcut
Left 1    NumPad 1
Right 1   NumPad 3
Left 2    NumPad 4
Right 2   NumPad 6
Left 3     NumPad 7
Right 3   NumPad 9
Up         NumPad 8
Down    NumPad 2


 
 

Thanks Paul.  I thought this was the case Paul,  but after posting checked the preferences and discovered it wasn't.  I have just realised that this changes when you open a project then check the preferences. 

tenfoot
I thought this was the case Paul,  but after posting checked the preferences and discovered it wasn't.  I have just realised that this changes when you open a project then check the preferences. 

Man, talk about subtleties.  I've never checked preferences without a project of some sort being open so I just had to try this out.  And you're right.  Opening Sonar, but not a project, Preferences shows the keys unbound.  What does this mean ?