More issues with "invalid or corrupt session state" (Ardour 8.10)

Installation & Configuration Linux
#1

Similar issue to what I had few weeks ago, but this time the session was first created using Ardour 8.7 so it can’t be same timecode conversion issues.

I created a project with certain samples and few days later when I tried to open it again I was met with the same error message that certain region/sources are causing problems:

Session "/home/kinari/Music/ardour/201 (Mohabbat) (snapshot 201)" did not load successfully:
Cannot initialize session/engine: Invalid or corrupt session state. 

---ERROR: Could not set session state from XML
ERROR: Session: failed to load active playlists
ERROR: Session: cannot create Playlist from XML description.
ERROR: Playlist: cannot create region from XML
ERROR: Session: cannot create Region from XML description. Can not load state for region '[SAINT6] Aggressive 808.67'
ERROR: Session: cannot create Region from XML description. Can not load state for region '[SAINT6] Aggressive 808.60'

Same as last time, I deleted all the problematic parts from sources, regions, and playlists. (See the project file marked “zombie” in dropbox folder below.) But now Ardour consistently crashes when I try to open the modified session, without even displaying any error messages. Other sessions are loading normally, just this one is not.

See project XML files and tarball of whole session folder here in dropbox. Running Ardour 8.10 on Linux Mint 22 (Xfce). I first encountered the above issues in 8.7 and it persists after updating to 8.10. Thanks in advance for helping!

#2

It is the same problem that we still do not have a recipe for:

Region [SAINT6] Aggressive 808.17 has length a125440000@a3888640000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.31 has length a125440000@a3888640000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.53 has length a125440000@a51054080000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.60 has length a125440000@a3888640000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.67 has length a125440000@a7902720000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.24 has length a125440000@a26969600000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.38 has length a125440000@a30983680000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.46 has length a125440000@a47040000000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.74 has length a125440000@a51054080000 which is longer than its (first?) source's length of a125438040
Region [SAINT6] Aggressive 808.81 has length a125440000@a55068160000 which is longer than its (first?) source's length of a125438040

A one-line change to the code allows the session to load, but it is not clear that it’s a good idea.

1 Like
#3

Why isn’t it good idea, does it affect the rest of session somehow? Let me know if there’s another thread I can refer to here, and/or anything I can do in future to avoid this issue…

And otherwise does this mean that the session is irrecoverable? That’s the only session file I have for it and I really need access to the demo… :sweat_smile: