View Issue Details
|ID||Category||Date Submitted||Last Update|
|0006270||bugs||2015-04-21 17:32||2020-04-19 20:17|
|Fixed in Version||5.X git (version in description)|
|Summary||0006270: Inputting midi notes after tempo change results in wrong note duration|
|Description||Steps to reproduce: create a session and let the first two measures have different tempos. Create a midi region occupying these two measures. Insert a midi note in the first measure, by clicking and dragging it to last 2 beats. It'll give you a note with a 2 beats duration alright. If you do the same to the second measure, that have a different tempo, the note will have the wrong duration. It will be longer/shorter depending if the tempo is faster or slower.|
It makes no difference if snapping is on or off..
|Additional Information||I have recorded a small video showing this bug. I can upload it if someone find it useful.|
|Tags||4.0, 4.2, 4.4, Midi, tempo, tempo change|
|Users sponsoring this issue|
Total Sponsorship = US$ 5
2015-08-15 00:19: eduardomezencio (US$ 5)
||I also discovered another thing that may be just an 'extension' of this bug. If you place a midi region in a range that contains two different tempos and then split the region in two, when you place notes in the second region the notes are going to be placed in the wrong position: it will be placed ahead if the second tempo is faster than the first and behind if the second tempo is slower than the first one.|
||I just stumbled into this :( I discovered that you can work around this issue either by creating note with simple click (instead of drag - it will have length of one snap unit) or by resizing it later - editing seems to work fine.|
||There are huge changes coming to tempo/meter (primarily to allow "ramping"). Unlikely we'll look into any reports like this until that work has been incorporated into the main development branch. Just FYI.|
||Thanks for the info. Ramping surely sounds cool. Does this development happen in tempo_ramps branch? Is there any ETA?|
I just tested with version 5.4.399 on linux and cannot reproduce this issue.
Can you please confirm that this issue is now fixed. Thanks.
||Well, my computer is broken and I can't test it for now.. I'll test as soon as I can, but I'm dropping a donation right now anyways|
I've just retested this with version 5.5.480 and it still seems to work correctly, so I'm going to mark this issue as resolved.
Thanks for the donation.
||Fixed at some point in the early 5.X releases|
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-04-21 17:32||eduardomezencio||New Issue|
|2015-08-15 00:19||eduardomezencio||Sponsorship Added||eduardomezencio: US$ 5|
|2015-08-15 00:19||eduardomezencio||Sponsorship Total||0 => 5|
|2015-10-26 01:43||eduardomezencio||Note Added: 0017513|
|2015-10-26 01:48||eduardomezencio||Tag Attached: 4.0|
|2015-10-26 01:48||eduardomezencio||Tag Attached: 4.2|
|2015-10-26 01:48||eduardomezencio||Tag Attached: Midi|
|2015-10-26 01:48||eduardomezencio||Tag Attached: tempo|
|2015-10-26 01:48||eduardomezencio||Tag Attached: tempo change|
|2015-10-26 01:48||eduardomezencio||Tag Attached: 4.4|
|2016-05-06 18:44||caryoscelus||Note Added: 0018179|
|2016-05-10 22:54||paul||Note Added: 0018186|
|2016-05-11 15:40||caryoscelus||Note Added: 0018187|
|2016-11-20 01:05||timbyr||Note Added: 0018998|
|2016-11-20 01:05||timbyr||Status||new => feedback|
|2017-01-13 03:04||eduardomezencio||Note Added: 0019277|
|2017-01-13 03:04||eduardomezencio||Status||feedback => new|
|2017-01-13 23:50||timbyr||Note Added: 0019278|
|2017-01-13 23:53||timbyr||Note Added: 0019279|
|2017-01-13 23:53||timbyr||Status||new => resolved|
|2017-01-13 23:53||timbyr||Fixed in Version||=> 5.X git (version in description)|
|2017-01-13 23:53||timbyr||Resolution||open => fixed|
|2017-01-13 23:53||timbyr||Assigned To||=> timbyr|
|2020-04-19 20:17||system||Note Added: 0023440|
|2020-04-19 20:17||system||Status||resolved => closed|