You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, beats_set_marker will only add a a new grid, leading the previous grid to have an uneven number of beats. This as to address the case with varying BPM or beat/half-beat track.
Going forward, we add a new CO to allow setting a new marker, which stretches the previous grid and keep complete (that is, contain an integer of beats)
A nice to have would be to make beats_set_marker configurable to allow its behaviour to optionally copy beats_stretch's behaviour. This would allow mappings to prioritise the use of beats_set_marker, but still allow user to change the default behaviour, in case they don't use tracks with varying BPM or beat phase.
Currently,
beats_set_marker
will only add a a new grid, leading the previous grid to have an uneven number of beats. This as to address the case with varying BPM or beat/half-beat track.Going forward, we add a new CO to allow setting a new marker, which stretches the previous grid and keep complete (that is, contain an integer of beats)
A nice to have would be to make
beats_set_marker
configurable to allow its behaviour to optionally copybeats_stretch
's behaviour. This would allow mappings to prioritise the use ofbeats_set_marker
, but still allow user to change the default behaviour, in case they don't use tracks with varying BPM or beat phase.Originally discussed in #13330
The text was updated successfully, but these errors were encountered: