View Issue Details
|ID||Category||Date Submitted||Last Update|
|0007773||bugs||2019-07-14 15:22||2019-07-19 21:26|
|Platform||Windows 10||OS||Windows||OS Version||10|
|Fixed in Version|
|Summary||0007773: Midi track range not saved with .ardour file|
|Description||When you close, save and reopen an Ardour file, it should look the same, including the visible range for MIDI tracks. However this is not the case.|
|Steps To Reproduce||1. Create a new file|
2. Record a MIDI track, preferably one with a wide range of notes
4. Expand the track height
3. Enter Internal Edit Mode
4. Close Ardour
5. Choose Save when prompted
6. Reopen your Ardour session
|Additional Information||Expected behavior: The MIDI track should show the full range of notes (like it did when you closed the file), and the track height should be the same.|
Actual behavior: The MIDI track goes back to the default view and height before you recorded.
I encounter this bug almost everyday. I think being in Internal Edit Mode when you close might be the key to reproducing.
|Tags||No tags attached.|
The note-range issue should be fixed since 6.0-pre0-2059-g53c677e08f
The issue was that the note-range-min/max was only saved when manually changing the visible range (using mouse drag/drop of the MIDI scroomer).
Automatic changes (record, rec-stop) or fit to range were not saved.
||I cannot reproduce the issue that the track-height does not get saved/restored.|
||x42, is it just on 6.0 that you can't reproduce the loss of custom track-height? I tried the steps listed above four times (using 5.12), and can reproduce every time.|
||Super fast fix for the note-range bug! Thank you for working on that.|