firstly, it is fantastic that we have new fresh release.
i tried yesterday:
when i tried to play a song composed in 8.12, i got this error and ardour crashed.
Ardour9 terminated by signal SIGSEGV (Address boundary error)
just to quick check, i re-installed 9, get same error, then, returned to 8.12 works fine.
Does it work if you create a new session and tracks and plugins?
Chances there’s some plugin in the old session that doesn’t play nicely with Ardour 9.
You can also try starting Ardour from the command line and add the --disable-plugins flag, to see whether the session works in that case or not.
i did not try with new session, i can try as soon as possible.
even it works (or disabled plugins), it is not good enough since there will be lots of composed songs bits and pieces from previous versions (for me i do not have much. i am just self thrasher ). in that case all needs to be transformed to new release which can cause friction i guess.
well, please do not get me wrong, i am just trying to be helpful. this is just my opinion anyway.
Disabling all plugins lets you determine whether the segfault is due to something else in the session or if it is indeed one of the plugins that’s misbehaving.
If it is a plugin problem you should write down all the plugins you’re using in that session and then add them one after another to a new session, until you get a segfault there.
Then remove that plugin from the original session.
Sto avendo anch’io alcuni problemi, plugin che funzionavano con la 8, crashano male la 9 e sto provando sia la versione ufficiale, sia la build openSUSE. Sospetto i plugin Kpp_ (tubeamp, distruction…)
i understand the logic. yes, you are right. i will try when i find a little time to try. until than, this is some king of bug we have to deal with. you know, if it happens once, i will happen again.
best.
edit:
maybe we can try to add some kind of self diagnosis mechanism to identify the problem automatically for example 9.0.1 release.