Inspector bug .. "Key field"

Author
williamcopper
Max Output Level: -68 dBFS
  • Total Posts : 1120
  • Joined: 2014/11/03 09:22:03
  • Location: Virginia, USA
  • Status: offline
2015/04/15 03:51:19 (permalink)

Inspector bug .. "Key field"

I posted this awhile ago, got no notice.   But in reading the Reference Guide, the documentation says one thing and the program, Sonar Plat, does another thing:
 
Page 1370: "In the Track Inspector, force Sonar to play the trumpet track a whole step lower by entering -2 (negative 2) in the Key+ field and pressing ENTER".
 
Try it for yourself.   If you are not accustomed to sonar's current wild state, you'll be shuddering for half an hour.
 
Of course the REAL design flaw is the choice of number keys as adamantine choices for screen sets. 
 
 
#1

9 Replies Related Threads

    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 11:09:41 (permalink)
    williamcopper
    I posted this awhile ago, got no notice.   But in reading the Reference Guide, the documentation says one thing and the program, Sonar Plat, does another thing:
     
    Page 1370: "In the Track Inspector, force Sonar to play the trumpet track a whole step lower by entering -2 (negative 2) in the Key+ field and pressing ENTER".
     
    Try it for yourself.   If you are not accustomed to sonar's current wild state, you'll be shuddering for half an hour.
     
    Of course the REAL design flaw is the choice of number keys as adamantine choices for screen sets. 
     
     


    I'm not sure what you are saying. I use the transpose key field all the time in the Inspector and don't have a problem with it. I do use the mouse wheel or pointer to go up an octave or down an octave.
     
    You may wish to try and use the number keys on the keypad with numlock. 

    Best
    John
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 11:19:18 (permalink)
    Maybe the Ref. Guide doesn't make clear that you need to double-click the field or focus it and hit Enter first to enable editing the value... otherwise your numeric keys will change screensets by default.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #3
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 11:34:35 (permalink)
    Can't be done.   Unless I have somehow upset a configuration preference or something, you CAN NOT enter a value into the field.   And of course, you think you have placed your cursor in the field, start typing numbers, and the screensets go wild.  
     
    As to using it, yes I have to use it all the time, but drawing the little slider for a french horn, for instance, exactly 7 half steps down, takes an annoying degree of focus and precision mousing to get the right number. 
    #4
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 11:43:55 (permalink)
    Bring the field in focus by clicking on it
    Hit ENTER to open up the spinbox
    Use the typewriter key numbers to enter the value
    Hit Enter to save the value
     
    The numeric keypad + and - will also adjust the value whether the spinbox is open or not as long as the field has focus. So too, the mouse wheel and SHIFT+wheel.
     
    The numbers on the numeric keypad are the screenset shortcuts.
    #5
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 11:47:36 (permalink)
    Hitting Enter works for me. Also with the field focused you can use +/- keys to increment/decrement by half-steps or square brackets, [ ], to inc/dec by octaves.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #6
    SquireBum
    Max Output Level: -84 dBFS
    • Total Posts : 347
    • Joined: 2013/06/26 13:23:55
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 12:16:52 (permalink)
    Clicking the field and pressing Enter works for me, as noted by others.
     
    Some research on earlier versions shows that the "Key+" field widget changed between Sonar X1 and Sonar X2.  In X1 the field was identical in appearance and function to the "Time +" field and the text box and spinner could be exposed by double clicking on the field.  In X2 and later, the field widget gained a slider and now requires pressing Enter to open the text box with spinner.
     
    Agree that the documentation should more clearly explain how to use the field due to the widget change.

    Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
    Windows 10 x64
    AMD Phenom II X4 955 3.20 GHz
    8 GB Ram
    Nvidia GeForce 9500 GT
    Echo Gina 3G
    #7
    SquireBum
    Max Output Level: -84 dBFS
    • Total Posts : 347
    • Joined: 2013/06/26 13:23:55
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 13:01:15 (permalink)
    williamcopper
    Of course the REAL design flaw is the choice of number keys as adamantine choices for screen sets. 

     
    Sonar is quite flexible when it comes to keyboard shortcuts.  Suggest binding the number keys to another function, such as Note duration (1=Whole Note, 2=Half Note, etc.) followed by binding Shift+number to the View | Screenset functions.

    Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
    Windows 10 x64
    AMD Phenom II X4 955 3.20 GHz
    8 GB Ram
    Nvidia GeForce 9500 GT
    Echo Gina 3G
    #8
    John
    Forum Host
    • Total Posts : 30467
    • Joined: 2003/11/06 11:53:17
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/15 14:08:47 (permalink)
    I found a neat way to enter values into the Key+ widget use the plus or minus key of the key pad. Each press will change it one value. You can use a mouse click to center it. The wheel to change value or the pointer to drag the value slider to a value. In other words there are a ton of way to enter data into this widget.  The OP is right about entering data with the number keys that doesn't work. 

    Best
    John
    #9
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: Inspector bug .. "Key field" 2015/04/19 18:42:17 (permalink)
    Thanks to all.  I had gotten used to double-click being exactly the same as click-enter; never tried click-enter, but that does work for numeric input.   One more little thing to remember, but it works, and that's great.
    #10
    Jump to:
    © 2025 APG vNext Commercial Version 5.1