Not really problems, but a complication in the keystroke equivalent usage, such as my Countour ShuttlePro in relation to program design.
The buttons are programmed with keystroke equivalents (such as <Space> for start/stop, <CTRL/R> for record, etc).
However, if your mouse focus has moved to a different window (not track data window) pressing, say, the assigned Start/Stop (=Spacebar>) button will perform that function for the active window. My favorite (NOT!!!) is inadvertently disabling EQ bands while tweaking and start/stopping.
What is needed is either dedicated control surface support, or a second set of keystroke equivalents for transport controls that *remain* whichever window is currently active.
geoff
The buttons are programmed with keystroke equivalents (such as <Space> for start/stop, <CTRL/R> for record, etc).
However, if your mouse focus has moved to a different window (not track data window) pressing, say, the assigned Start/Stop (=Spacebar>) button will perform that function for the active window. My favorite (NOT!!!) is inadvertently disabling EQ bands while tweaking and start/stopping.
What is needed is either dedicated control surface support, or a second set of keystroke equivalents for transport controls that *remain* whichever window is currently active.
geoff