Add new comment

Your question's not idiotic at all.

I don't use those actions in their current state. Why? The current Rewind and Forward actions are uncontrolled. There's no idea of exactly where they will end up when the user stops pressing the action/keystroke/mouse-click. The user will still have to fine-tune the position of the PB cursor anyway.

Your idea is, in my opinion, the best option. When playback is not running, the user can, with keystroke actions, regulate and define where the PB cursor will be positioned, in a controlled and user friendly workflow. When playback is running, then the actions can conform to the current continuous behavior.

There's an addition to this. When the user is writing midi for multiple tracks, and there are intended unison or chordal parts of several instruments playing together, a controlled PB cursor provides an immediate and obvious visual cue across multiple clip editors, to complement the aural cue from listening. The user can write chords and unison parts quickly, knowing which bar he or she is on, then quickly audition to iron out any errors, or alternatives.

An ideal compromise.

p.s. One more thing. If the user presses the new action once and releases it, then the PB cursor moves by one grid unit and stops. If the user holds the keystroke down, then the cursor goes from grid unit to grid unit, until the user releases the keystroke. So he or she doesn't have to press a gazillion keystrokes to move some distance from where he or she is in the canvas. This is how it works in other daws, and is something most users would be familiar with.