View Issue Details

IDProjectCategoryView StatusLast Update
0003848ardourbugspublic2020-04-19 20:15
Reporterdanboid Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
Target Version3.0-beta1 
Summary0003848: MIDI region starting at 0 first time playback problems
DescriptionCreate a MIDI track then when you create the first region you must create it exactly like so:

* Push rewind or HOME to make sure you're at 0 and enable Edit region and Draw/Edit MIDI notes
* Set snap units to Bars
* Draw a new MIDI region in your newly created track starting the first bar as near to 0 as you can manage (so that it should be starting at 0) and make it as long or short as you want
* Insert at least 5 notes of any duration at any point in the bar

When you play back a region created this way, A3 will only play the first few notes but not the rest of the region or it will miss notes or get stuck one note.. the flaw differs but a MIDI region created with its origin at 0 never plays right first time.

9124
Additional InformationIt used to be only the first note would get played in this situation so things have improved a little :)
TagsNo tags attached.

Activities

cth103

2011-03-24 12:05

administrator   ~0010404

I can't reproduce this, unfortunately.

danboid

2011-03-25 11:44

reporter   ~0010411

Just tried this again here under the official 32bit alpha 2 (aah, isn't that nice to say? ;) under AV Linux and the problem persists here. I created a region as described above with 8 notes- on first playback it played the first note, accidentally held that note hence ignoring 4 notes after it then it played the final three notes OK. Second playback was fine.

danboid

2011-04-07 15:21

reporter   ~0010504

Doesn't seem to be an issue any more in alpha4 - resolve please.

cth103

2011-04-07 21:58

administrator   ~0010510

Thanks.

system

2020-04-19 20:15

developer   ~0022447

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.

Issue History

Date Modified Username Field Change
2011-03-12 13:25 danboid New Issue
2011-03-12 16:16 cth103 cost => 0.00
2011-03-12 16:16 cth103 Target Version => 3.0-beta1
2011-03-24 12:05 cth103 Note Added: 0010404
2011-03-25 11:44 danboid Note Added: 0010411
2011-04-07 15:21 danboid Note Added: 0010504
2011-04-07 21:58 cth103 Note Added: 0010510
2011-04-07 21:58 cth103 Status new => resolved
2011-04-07 21:58 cth103 Resolution open => unable to reproduce
2011-04-07 21:58 cth103 Assigned To => cth103
2020-04-19 20:15 system Note Added: 0022447
2020-04-19 20:15 system Status resolved => closed