View Issue Details

IDProjectCategoryView StatusLast Update
0006098ardourbugspublic2020-04-19 20:17
Reportersvictor Assigned Todrobilla  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Summary0006098: Midi files created in 3.5.411 disappear from session upon reopen and crash Ardour on import
DescriptionRecorded some midi regions. Closed Ardour.
Upon reopening, Ardour complained about not being able to reopen the last take.

Tried to import it > Ardour crashed. Actually the mere fact of reaching the session interchange folder made it crash.

Reopened Ardour > it complained about another take it could not open. Tried to import it > Ardour crashed again when reaching interchange folder.
When I reopened Ardour, another region was missing from the session.

I could finally import some regions by copying them to another folder. But those regions showed empty (no notes). Message in log was : [INFO]: Track 1 of /home/tor/Desktop/Take28_Bass-1.mid contained no usable MIDI data

For other files, trying to import them from a different folder made Ardour crash. Interestigly even 3.5.403 crashes with those files. Kick-snare-1.mid in attachment is one of them.
TagsNo tags attached.

Activities

2014-12-30 20:30

 

2014-12-30 20:31

 

svictor

2014-12-30 22:49

reporter   ~0016182

Bug is actually in optimized download from http://nightly.ardour.org Debug version seems to work fine.

drobilla

2014-12-31 04:14

developer   ~0016183

Import/load of corrupt/truncated MIDI files, and not crashing in the import dialog if files are unloadable, fixed in 3.5-4151-g168d187

"Kick-snare-1.mid" is truncated, but Ardour now loads what's there. "Take28 Bass-1.mid" is empty.

I'm considering that the bug for this ticket, but it does not address how the files got this way in the first place. I strongly suspect that stemmed from some issues that have been fixed since. Can you reproduce creating broken files like this with the current version?

svictor

2014-12-31 13:37

reporter   ~0016189

The crash on import of corrupted files is fixed indeed. Thanks!

The problem with creating broken files is still there in optimized build (see my previous note). With that build, it’s as simple as: create a new session, add a new midi track, record some midi into it [playback to verify it’s all there], save session, close Ardour, reopen session > midi region is still there but has no events.

Couldn’t check the debug build yet (still downloading…). But I suppose that one works fine. It did yesterday anyway.

svictor

2014-12-31 14:10

reporter   ~0016190

I confirm that debug build saves the files correctly.

What happened to me in the first place was with an optimized build. The symptoms were a bit different from those which I see now in my test session. Ardour then said something in the log about not being able to recreate the region, whereas in the test session log is silent and Ardour recreates the region, but the latter is empty. I suppose the difference is due to the fact that the session I messed up in the first place was already started with a dbg build, then continued with an optimized one.
I didn’t try to reproduce that particular situation. But there is at least a problem with recording and saving midi in the optimized builds which is 100% reproduceable.

drobilla

2014-12-31 22:38

developer   ~0016191

Huh. That's weird...

drobilla

2015-01-05 20:55

developer   ~0016204

Relatively sure this is fixed in 3.5-4191-gb56905b, I can't reproduce lost MIDI data on save in an optimized build anymore.

system

2020-04-19 20:17

developer   ~0023362

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
2014-12-30 20:30 svictor New Issue
2014-12-30 20:30 svictor File Added: Kick-snare-1.mid
2014-12-30 20:31 svictor File Added: Take28_Bass-1.mid
2014-12-30 22:49 svictor Note Added: 0016182
2014-12-31 04:14 drobilla Note Added: 0016183
2014-12-31 04:14 drobilla Assigned To => drobilla
2014-12-31 04:14 drobilla Status new => resolved
2014-12-31 04:14 drobilla Resolution open => fixed
2014-12-31 13:37 svictor Note Added: 0016189
2014-12-31 14:10 svictor Note Added: 0016190
2014-12-31 22:38 drobilla Note Added: 0016191
2014-12-31 22:39 drobilla Status resolved => confirmed
2015-01-05 20:55 drobilla Note Added: 0016204
2015-01-05 20:55 drobilla Status confirmed => resolved
2020-04-19 20:17 system Note Added: 0023362
2020-04-19 20:17 system Status resolved => closed