Yes we could make this an effect, but I actually wouldn't sacrifice one or even two effect slots for this feature.
IMO it would be better to have those functions available
1) as separate effects: a) brake/softStart b) spinBack
2) as optional GUI buttons with parameters set in Prefs:
a) brake/softStart* b) spinBack
3) for controllers so that users can map it individually
*can share one effect/button as only one or the other can be active
> IMO shift + cue is better used for jumping to the beginning of the track
> and stopping (start_stop Control), and this is how I've designed the
> CueButton in Components.
Can users override this default behaviour without having to mess with components itself? IMO that should be possible as components more complex that a midi mapping, and it affects all mappings that rely on components.
Yes we could make this an effect, but I actually wouldn't sacrifice one or even two effect slots for this feature.
IMO it would be better to have those functions available
1) as separate effects: a) brake/softStart b) spinBack
2) as optional GUI buttons with parameters set in Prefs:
a) brake/softStart* b) spinBack
3) for controllers so that users can map it individually
*can share one effect/button as only one or the other can be active
> IMO shift + cue is better used for jumping to the beginning of the track
> and stopping (start_stop Control), and this is how I've designed the
> CueButton in Components.
Can users override this default behaviour without having to mess with components itself? IMO that should be possible as components more complex that a midi mapping, and it affects all mappings that rely on components.