The steps work well and are necessary. Why associate them with fast forward and backward?
They should have their own keyboard shortcuts.
In fact, in the midi editor you already have one step (forward).
You just have to add another one backwards and that also appears in the sequencer.
They do not need a button graphical interface:
There are workflows where the keyboard is not feasible (when you record with real instruments that occupy your hands and get space between you and the keyboard). In those cases the mouse is more portable and only takes up one hand, and that allows you to work. To record, just beat snap. and move with the mouse.
Steps are useful in editing tasks (where there are no obstacles to access the keyboard), not recording.
The fast-forward and fast-backward buttons work as they do now, except for the stop, which should stop any action in progress.
The steps work well and are necessary. Why associate them with fast forward and backward?
They should have their own keyboard shortcuts.
In fact, in the midi editor you already have one step (forward).
You just have to add another one backwards and that also appears in the sequencer.
They do not need a button graphical interface:
There are workflows where the keyboard is not feasible (when you record with real instruments that occupy your hands and get space between you and the keyboard). In those cases the mouse is more portable and only takes up one hand, and that allows you to work. To record, just beat snap. and move with the mouse.
Steps are useful in editing tasks (where there are no obstacles to access the keyboard), not recording.
The fast-forward and fast-backward buttons work as they do now, except for the stop, which should stop any action in progress.