Fix the case of jump-to-next-Subdivision
This commit is contained in:
parent
22bc091c37
commit
6941d0b74d
@ -3808,9 +3808,14 @@ TempoMap::round_to_quarter_note_subdivision (framepos_t fr, int sub_num, RoundMo
|
|||||||
ticks += ticks_one_subdivisions_worth - mod;
|
ticks += ticks_one_subdivisions_worth - mod;
|
||||||
}
|
}
|
||||||
|
|
||||||
if (ticks >= BBT_Time::ticks_per_beat) {
|
//NOTE: this code intentionally limits the rounding so we don't advance to the next beat.
|
||||||
ticks -= BBT_Time::ticks_per_beat;
|
// For the purposes of "jump-to-next-subdivision", we DO want to advance to the next beat.
|
||||||
}
|
// And since the "prev" direction DOES move beats, I assume this code is unintended.
|
||||||
|
// But I'm keeping it around, until we determine there are no terrible consequences.
|
||||||
|
// if (ticks >= BBT_Time::ticks_per_beat) {
|
||||||
|
// ticks -= BBT_Time::ticks_per_beat;
|
||||||
|
// }
|
||||||
|
|
||||||
} else if (dir < 0) {
|
} else if (dir < 0) {
|
||||||
|
|
||||||
/* round to previous (or same iff dir == RoundDownMaybe) */
|
/* round to previous (or same iff dir == RoundDownMaybe) */
|
||||||
|
Loading…
Reference in New Issue
Block a user