View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007234 | ardour | bugs | public | 2017-02-12 15:47 | 2020-04-19 20:18 |
Reporter | Lost_Highway | Assigned To | nmains | ||
Priority | immediate | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | Linux | OS | Ubuntu Studio | OS Version | 16.04 LTS |
Fixed in Version | 5.X git (version in description) | ||||
Summary | 0007234: A5.6: midi region weirdness | ||||
Description | Using Ardour 5.6 downloaded from the Ardour site, I'm experiencing a lot of weird behaviour with midi regions that didn't occur with 5.5. With snap set to grid or magnetic and the units set to beats, clicking/holding on a midi region to move it causes the region to jump a long way (maybe as many as a dozen beats) forward or backward. Trying to drag the cursor one way or the other to move a region results in the region flickering back and forth rapidly between the expected position where the cursor is and a position either many beats before or many beats after. Sometimes when dragging a region, the midi events with the region move e.g. so the notes near the beginning of the region are no longer there and later notes are near the beginning of the region. Sometimes when this happens the notes don't disappear completely but now exist outside the rectangle representing the region. I've done a few screenshots which hopefully will illustrate this. First shows the regions in place. The second shows the effect of dragging a region to the left by about seven /8 beats -- the region jumps much earlier on the timeline. The third screen shot shows another drag of the region, which has caused midi events to shift within the region, some of which have shifted outside the region box entirely. Is it only possible to upload a single file? | ||||
Tags | No tags attached. | ||||
|
|
|
I can reproduce this issue with the officical 5.6 build (linux, 64bit). Does not occur with 5.5. I've attached a simple Session that can be used to reproduce the issue. The issue seems related to the Meter change and does not occur if it is removed. |
|
|
|
thanks for the report. this should have been fixed by commit 50fc9e0d0f478. |
|
Seems to be fixed here with master@5.6.4 |
|
As there is no further negative feedback I'm marking this issue 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. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-02-12 15:47 | Lost_Highway | New Issue | |
2017-02-12 15:47 | Lost_Highway | File Added: Screenshot_3.png | |
2017-02-13 10:50 | timbyr | Note Added: 0019377 | |
2017-02-13 10:50 | timbyr | Assigned To | => nmains |
2017-02-13 10:50 | timbyr | Status | new => confirmed |
2017-02-13 10:50 | timbyr | File Added: 5.6-midi-notes-sequence.tar.xz | |
2017-02-13 13:19 | nick_m | Note Added: 0019378 | |
2017-02-13 13:25 | timbyr | Note Added: 0019379 | |
2017-02-26 09:51 | timbyr | Note Added: 0019439 | |
2017-02-26 09:51 | timbyr | Status | confirmed => resolved |
2017-02-26 09:51 | timbyr | Fixed in Version | => 5.X git (version in description) |
2017-02-26 09:51 | timbyr | Resolution | open => fixed |
2020-04-19 20:18 | system | Note Added: 0023718 | |
2020-04-19 20:18 | system | Status | resolved => closed |