Strange keybinding bug

Author
Razorwit
Max Output Level: -66 dBFS
  • Total Posts : 1235
  • Joined: 2003/11/05 18:39:32
  • Location: SLC, UT
  • Status: offline
2012/09/22 18:17:01 (permalink)

Strange keybinding bug

I see a few keybinding bug reports and I'm also seeing a strange one. Wondering if someone could verify.

Here's how I get it:
1. open a new project and make sure the multi-dock is docked in the main window with the track view. At this point the "N" key should correctly toggle the snap function.
2. Undock (float) all views so nothing is docked in the track view. Everything should be floating at this point.
3. click the track view.
4. at this point, for me, the "N" key does nothing. The snap settings don't change when hitting "N"
5. Click any of the floating windows so it has focus. Now the "N" key works again to toggle snap.


With everything floating the "N" key doesn't work when TV is selected, but it does when a floating window is selected.

Anyone verify?
Dean


EDIT - updated
post edited by Razorwit - 2012/09/23 13:22:00

Intel Core i7; 32GB RAM; Win10 Pro x64;RME HDSPe MADI FX; Orion 32 and Lynx Aurora 16; Mics and other stuff...
#1

6 Replies Related Threads

    Bill Jackson [Cakewalk]
    Administrator
    • Total Posts : 519
    • Joined: 2007/07/11 16:44:27
    • Location: Boston, MA
    • Status: offline
    Re:Strange keybinding bug 2012/09/22 18:31:28 (permalink)
    Can't reproduce here...  Can you double-check your keybindings and Make sure N isn't bound to anything different for each of the views?

    Bill Jackson
    Product Manager
    Cakewalk

    #2
    Razorwit
    Max Output Level: -66 dBFS
    • Total Posts : 1235
    • Joined: 2003/11/05 18:39:32
    • Location: SLC, UT
    • Status: offline
    Re:Strange keybinding bug 2012/09/22 21:22:04 (permalink)
    Hi Bill,
    Thanks for the response. Yep, I checked my keybindings and "N" is mapped to "Snap To Grid On/Off" in the Global bindings and in track view bindings.

    The funny thing is that it's doing it for some other keybindings as well. For example, I have "cntrl-R" bound to "set loop times to match selection" and it displays exactly the same behavior. 

    Just a random thought, but when you tried to repro it were you using a multi monitor setup?

    Dean

    Intel Core i7; 32GB RAM; Win10 Pro x64;RME HDSPe MADI FX; Orion 32 and Lynx Aurora 16; Mics and other stuff...
    #3
    Bill Jackson [Cakewalk]
    Administrator
    • Total Posts : 519
    • Joined: 2007/07/11 16:44:27
    • Location: Boston, MA
    • Status: offline
    Re:Strange keybinding bug 2012/09/22 21:27:09 (permalink)
    I didn't.  And I don't have access right now.  Try exporting your current keybinding (so you don't lose them) and zap all.  See if it's still reproducible after that.

    Bill Jackson
    Product Manager
    Cakewalk

    #4
    Razorwit
    Max Output Level: -66 dBFS
    • Total Posts : 1235
    • Joined: 2003/11/05 18:39:32
    • Location: SLC, UT
    • Status: offline
    Re:Strange keybinding bug 2012/09/22 21:55:29 (permalink)
    Hi Bill,
    Thanks again for working with me on this. Just did a zap all and the symptom persists. Just for kicks, I then did a zap all and then manually did a keybinding for "N" to turn snap on and off. Even with that as the only keybinding the symptom persists. 

    Tried it in X1 and it works fine. It's very strange....

    Dean


    EDIT:
    Just a quick update. I've uninistalled and re-installed and it's still happening. One more thing, it only happens when nothing is docked in the TV. So if the inspector is docked it works fine. If the multi-dock is docked in the TV it works fine. But if everything is floating I see the strange keyboard shortcut behavior. The really funny thing is that it changes with screensets. So if I have a screenset with nothing docked I get the symptoms. If I have a screenset with either the multidock or the inspector docked things work fine.


    post edited by Razorwit - 2012/09/23 12:45:31

    Intel Core i7; 32GB RAM; Win10 Pro x64;RME HDSPe MADI FX; Orion 32 and Lynx Aurora 16; Mics and other stuff...
    #5
    Razorwit
    Max Output Level: -66 dBFS
    • Total Posts : 1235
    • Joined: 2003/11/05 18:39:32
    • Location: SLC, UT
    • Status: offline
    Re:Strange keybinding bug 2012/09/23 13:22:58 (permalink)
    Polite bump. Can anyone out in Sonar X2 user land check this?

    Dean

    Intel Core i7; 32GB RAM; Win10 Pro x64;RME HDSPe MADI FX; Orion 32 and Lynx Aurora 16; Mics and other stuff...
    #6
    musicroom
    Max Output Level: -51 dBFS
    • Total Posts : 2421
    • Joined: 2004/04/26 22:31:02
    • Status: offline
    Re:Strange keybinding bug 2012/09/23 14:28:28 (permalink)
    I ran into this the other night as well. I started to post something about it, but forgot to...

    I did the steps you did as well - I bound N to center the selection (which I thought was the default anyway). Still did not work like it does in X1??




     
    Dave
    Songs
    ___________________________________
    Desktop: Platinum / RME Multiface II / Purrfect Audio DAW  I7-3770 / 16 GB RAM / Win 10 Pro / Remote Laptop i7 6500U / 12GB RAM /  RME Babyface



     
     
    #7
    Jump to:
    © 2025 APG vNext Commercial Version 5.1