Can you upload the .ardour session file (not the whole session folder) somewhere, and Iāll have a look at fixing it.
Itāll either involve removing the regions āRYTHM GUITAR 2-6ā or fixing their length (due to an odd bug in early Ardour 8 some regions can be longer than the actual source)
Thanks for the advice, I followed it but to no avail. I get the same notification that the session did not load because of an invalid or corrupted session state.
I couldnāt think of where to upload the .ardour session file in question, but it is just 7.4 MB, how about I send it attached to an email? You could contact me via the email address given here, provided you have an account:
I copied the files in the wastebasket and pasted them in a new folder within the session folder. When I started the session again I included the path to that folder in the search for the missing files.
I was afraid I could possibly mess it up even more if I did that. Plus, in the meantime, I had generated new audio files, since I had continued recording, and there might have been different files with the same names. Is that actually possible in a case like that?
I put the files in question back in interchange/SessionName/audiofiles today but nothing changed, I still get the same message when I start the session.
Now, to take matters further let me quote John Lennon and say āHelp me to help myselfā.
I have three vital questions:
Is there a log file where incidents like this are documented?
If something like this happens again, where in the .ardour session XML file do I have to look and
what is to be done?
Iām running Ardour 8.11, should I upgrade to newest version to prevent something like this from
happening again? Since Robin Gareus mentioned a bug in early Ardour 8 releases.
Hello,
Okay, so I re-read all that youāve writtenā¦
Did you send the xml file to Robin?
Out of my own curiosity, I might be able to help.
(Iāll send you an email now, from jklookā¦)
A log file on your machine you mean? Not sure. But I would guess no.
Itās complicated, and depends on the specific situation. Fixing this xml will probably require targeted, manual editing/adjustment of certain lines of code. Anyone solving this will have to go off of the specific error messages your getting. Speaking of that, downloading and installing a debug-build of Ardour might(?) be of use to you for further diagnosis: https://nightly.ardour.org/ -Might give a more verbose list of reasons for not opening, not sure.
The latest version of ardour does something similar, but it corrects the length error in the XML file so you get all your original regions back as well.
If this is true, then thatās great!
I did not have access to this guyās full project. -Just the .ardour file.
If I wouldāve had access to the full project I would have simply tried opening it first, yes. haha
I suppose I could test that behavior now by purposefully messing with one of my region lengths in an xml of a test project⦠Hmm⦠Iāll try this soon.
95% saved of what I was afraid could be lost isnāt lame at all, dear boy. Fortunately those were the audio files I was about to discard anyway because I didnāt like the guitar tone. Strrrike!