View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004736 | ardour | bugs | public | 2012-02-20 23:00 | 2020-04-19 20:16 |
| Reporter | makohund | Assigned To | cth103 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0-beta3 | ||||
| Target Version | 3.0 | ||||
| Summary | 0004736: Changing existing tempo mark causes some midi regions to lose all notes | ||||
| Description | Repeatable problem with all midi notes disappearing from a particular region upon any attempt to change the tempo, or to add any new tempo markers. The notes can't be retrieved by undoing the tempo change/add, and the only way to get them back is to close the session without saving, and reopening it. I only have the one session with midi to work with, and it has this problem. I don't know if I could repeat it with another session from scratch. So maybe it is just something strange with this one session file. I think I'd deleted my .ardour and .config/ardour settings before installing beta3 on each of the two machines, but I'm not absolutely positive. Tarball of that session directory is attached. | ||||
| Additional Information | How the session was put together: ----------------------------------------------------- -Started new empty session, set tempo to 105bpm -Created one midi track -Used external keyboard to record a midi region to that track -Stretched the region out, moved some notes around, did some copy/pasting -Later on, copied the session to another machine, also with fresh beta3 install, and worked on it more there -Duplicated and forked that region multiple times -Erased notes from each new region, and shrunk the regions down to what was left -Deleted the original region, renamed the new ones to taste -The result... a few distinct parts for a song -Used step editor to add more notes to one of the new regions -Arranged the new regions into part of a song, using "duplicate" (without forking) to repeat parts Discovering the problem: ----------------------------------------------------- Pretty happy at that point. After saving for the umpteenth time, I tried changing the tempo (just the single original autocreated tempo marker at the beginning) to 107. Played it back. It started out fine, then all of a sudden went silent. Looked closer at the screen... whoah! All of the notes in one of the regions had vanished. (Happened to be the one I'd added to with the step sequencer, if that somehow matters.) And the duplicates of that region (an immediate repeat, and then again at a later point in the song) were showing tiny vertical lines where the notes should have been. Trying to select them caused them to disappear too. All of the other regions were fine... notes still there, and they still played back. Undoing the tempo change works, but doesn't bring the missing notes back. Closed the session without saving, and reopened... everything was back the way it had been when saved, with the tempo at 105. Testing: ----------------------------------------------------- Repeated attempts at changing the tempo to various bpms both higher and lower than 105 all caused note loss. Tried with snap to grid both on and off. Tried creating tempo marks at other points. Even tried adding a tempo marker of the exact same tempo right at the start of the problem region. In all cases, the notes in that region vanished, only to return after bailing on the session without saving, and reloading. Wanting to test what happens if I save it and reopen, I created a backup copy of the directory, then opened it and repeated the test. Saved it this time, then reopened. The notes are still missing after reopening. I then made a backup copy of my backup, and renamed the backup directory to match the original. When opening it, I got a message about recovering from crash. Now this is weird... if I chose to recover crash data, the midi notes would be missing from the region. If I chose to ignore crash data, the notes would be there. (Didn't expect that at all.) | ||||
| Tags | No tags attached. | ||||
|
2012-02-20 23:00
|
|
|
|
I think this because your session file is slightly corrupted due to a bug in Ardour which I think may be fixed in SVN 11984. I'd be interested to hear if you can reproduce the problem with a SVN version of Ardour after 11984. |
|
|
Closing due to lack of feedback; @markound please leave a note if you are still having problems. Thanks! |
|
|
Apologies for lack of feedback, found a workaround long ago and have since been buried in other projects. I suspect the assessment is correct. I can more easily check/verify now that RC4 is out, but until/unless I get to it, and discover otherwise... agreed. Consider it closed. Thanks! |
|
|
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 |
|---|---|---|---|
| 2012-02-20 23:00 | makohund | New Issue | |
| 2012-02-20 23:00 | makohund | File Added: 3.tar | |
| 2012-02-23 16:46 | cth103 | cost | => 0.00 |
| 2012-02-23 16:46 | cth103 | Target Version | => 3.0 beta4 |
| 2012-04-15 18:12 | cth103 | Status | new => confirmed |
| 2012-04-15 21:06 | cth103 | Note Added: 0013133 | |
| 2012-04-15 21:06 | cth103 | Status | confirmed => feedback |
| 2012-05-23 15:08 | cth103 | Target Version | 3.0 beta4 => 3.0 |
| 2012-06-14 23:38 | cth103 | Note Added: 0013541 | |
| 2012-06-14 23:38 | cth103 | Status | feedback => resolved |
| 2012-06-14 23:38 | cth103 | Resolution | open => fixed |
| 2012-06-14 23:38 | cth103 | Assigned To | => cth103 |
| 2012-06-15 01:28 | makohund | Note Added: 0013542 | |
| 2020-04-19 20:16 | system | Note Added: 0022973 | |
| 2020-04-19 20:16 | system | Status | resolved => closed |
