a session i created with ardour 3.4.x will not open with the newest version.
i do not think it is a bug, because i do not get a crash log or anything. the loading process just halts on a speciic track or bus and does not continue. it says something like track/bus xyz loaded but the routine does not continue.
is this a common issue and
is there a way to look up dependencies or to modify the session files so ardour loads it correctly?
when the session is loaded from a running instance the editor shows and all the graphs show too.
navigation works, but playing sound does not work.
jack shows this after loading within ardour
http://pastebin.com/CPLfrWF1
jack shows this when loading directly from the session file without ardour running beforehand
http://pastebin.com/CamsfVVY
in both cases the whole machine freezes up after a short time.
does someone have an idea of what is going on? is more information needed?
btw. saving and loading sessions created from the current same ardour version work
this i got from dbg
http://pastebin.com/7ztUxZUv
http://imagebin.org/285823
At [Thread 0xacbffb70 (LWP 3667) exited] my fan sped up and I waited about 3min. from there nothing happened.
I tried the core dump method, but when I enter the according line in the root terminal I get
root@toby:/home/tobias# unilimit -c unlimited
bash: unilimit: command not found
btw. where should this “core” file appear? where should I look?
sry, the core dump command was my typo. still, the freeze at the mentioned line blocks all further debugging processes.
how ever i still haven’t figured out where the core file is… 
your backtrace is fine but you didn’t keep scrolling through it. we need the entire thing (which will be several pages long). the core file will typically be in the same directory that you ran ./ardbg from.
this dbg was from within ardour after loading a session that worked.
http://pastebin.com/bi9hUNyc
the second was started from the session file from the setup gui.
http://pastebin.com/mPgQ8vWX
note: gdb did not promt after this stage (http://imagebin.org/285823), so i pressed something random (ctrl+c) which triggered some interrupt, which then led to a promt. i marked it in the dbg output… hope i did not mess anything up by doing this…
hopefully this will do for now. a core dump is not being created.
You’ve got a bug in a Calf plugin. It needs to be manually removed from the session or renamed/removed on your disks before the session will load. I can’t tell you which plugin, but it is a Calf plugin that is performing initialization of its FFT computation state.
ok, that makes sense. currently i’m using a different repository for the calf plugins.
when trying to load a similar session freezing aswell, the log actually displays: [ERROR]:Found a reference to a plugin (“http://calf.sourceforge.net/pligins/StereoTools”) that is unknown Perhaps it was removed or moved since it was last used.
would it make sense, or be possible for ardour to just ignore, or quit plugins that do not load properly? if so, i would gladly submit my first feature request.
for the time being, is there an easy way or some sort of documentation to remove plugins manually from a session?
as always, your advice and support is much appreciated.