Ardour (v5.3.0) crashes upon launching certain sessions. The crashes appear to be caused by “bad plugins” as launching Ardour by navigating to its /bin folder in the terminal and running “./ardour5 -B” to bypass plugins allows it to successfully launch. This occurs on AV Linux, but also occurred on Ubuntu 16 with Ardour 4 installed. The sessions were originally recorded with Ardour4. Ardour5 still crashes when the “Safe Mode” checkbox is checked.
When running with the “-B” predicate the playback is still “messed up.” It is slow, has pops and static. Removing (deleting) all plugins does not fix the issue. The application also experiences general slowness in affected sessions: scrolling, loading, operations.
I have copied sessions affected by these issues into a new directory (say “cp -r Session1 Session2”) giving write permissions only to root. When launching outside of root, Ardour launches in “Read Only Mode.” In Read Only Mode the playback is “correct” (no pops, static, general distortion) but I of course can not save any changes.
When all plugins are deleted in a session, the session is “Saved As” and reopened the playback will be “correct.” However as soon as a plugin is added back in the playback is again “messed up.”
It seems any plugin being added causes these issues to the affected sessions. I am mostly using Guitarix LV2 plugins, all plugins are LV2. I think the issues are caused by too many regions in the sessions, or rather recording too many regions. The affected sessions have 100+ regions across several tracks as a result of me messing around for a while whilst learning Ardour. Clicking “Clean Unused Regions” in the Region List does not solve the issue.
I would like to:
- Salvage these sessions: get the audio and MIDI tracks into a new, usable session or make the affected sessions “work.”
- Learn what is causing this issue and how to avoid it in the future.