View Issue Details
|ID||Category||Date Submitted||Last Update|
|0006680||bugs||2015-11-19 11:54||2020-04-19 20:17|
|Platform||Linux||OS||Arch Linux||OS Version||Current|
|Fixed in Version||5.X git (version in description)|
|Summary||0006680: End point of MIDI regions changes when tempo is altered.|
|Description||The grid is redrawn when tempo changes and this affects the duration of MIDI regions, creating gaps or overlaps depending on whether the tempo is raised or lowered.|
|Steps To Reproduce||Create any MIDI region (let's say a four-bar bassline) and copy / paste it so there are several contiguous copies of this region, then lower the master tempo by 10 BPM or so. Observe that the end point of the region has been clipped back and any notes within that region are either cut or do not sound.|
Raise the tempo by 10 BPM or so and the regions are now padded out and overlapping, messing up the timeline.
|Tags||No tags attached.|
|Users sponsoring this issue|
Total Sponsorship = US$ 10
2016-04-27 19:36: killermike (US$ 10)
adour_tempo.png (261,305 bytes)
adour_tempo.png (261,305 bytes)
||I am having this problem with 4.7 too. It's a shame because lowering the tempo to half speed to play in a part is one of my favourite techniques when composing MIDI tunes.|
||This seems to be fixed in 5.3. In a sequence that was made at 140BPM, I was able to change the tempo to 120BPM without overlapping regions. However, it looks like the loop markers and other markers are still not moved correctly.|
I can also confirm this issue is no longer present in 5.3
For the loop and other markers to move as you expect you need to "glue" them to BBT time from the Locations window.
If you think this issue is fixed please change status to resolved.
||this should have been fixed by commit d0580ecfbc|
well actually the second part of the bug (range markers not moving)
should have been fixed by d0580ecfbc.
you may now right-click the range marker and select "Glue to bars and beats"
to make the ranges move with a tempo change.
||The issues mentioned in this report should were included in the 5.X release series, the last being mentioned was included in the 5.6 release. Marking as resolved.|
Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.
|2015-11-19 11:54||Modeler||New Issue|
|2015-11-19 11:54||Modeler||File Added: adour_tempo.png|
|2016-04-27 19:36||killermike||Note Added: 0018161|
|2016-04-27 19:36||killermike||Sponsorship Added||killermike: US$ 10|
|2016-04-27 19:36||killermike||Sponsorship Total||0 => 10|
|2016-09-08 08:43||killermike||Note Added: 0018571|
|2016-09-09 02:36||timbyr||Note Added: 0018573|
|2016-12-28 14:58||nick_m||Note Added: 0019225|
|2016-12-28 15:03||nick_m||Note Added: 0019226|
|2017-03-06 00:27||timbyr||Note Added: 0019491|
|2017-03-06 00:27||timbyr||Status||new => resolved|
|2017-03-06 00:27||timbyr||Fixed in Version||=> 5.X git (version in description)|
|2017-03-06 00:27||timbyr||Resolution||open => fixed|
|2017-03-06 00:27||timbyr||Assigned To||=> timbyr|
|2020-04-19 20:17||system||Note Added: 0023562|
|2020-04-19 20:17||system||Status||resolved => closed|