[Ardour-Users] Adding tracks or busses disconnects Ardour from JACK

Q lists at quirq.ukfsn.org
Sun Oct 9 08:54:51 PDT 2011

Hi Harry

Thanks for this.

I checked the Timeout, it was set to 2000. I expect it's probably 
inherited this from my previous set-up (I keep the same /home partition 
when I do a fresh install). I increased it to 5000 and it didn't make 
any difference.

When it disconnects, it's the very moment that I click to make a change 
in Ardour that the connections to Jack go. There doesn't seem to be any 
delay, like you sometimes get with misbehaving software being slow and 
then Jack kicks it out after the timeout period.

Thanks again,


On 09/10/11 15:04, Harry van Haaren wrote:
> Hey Q,
> Perhaps check the "Timeout" in the QJackCtl Setup, the lower that is the
> faster JACK will kick a client... so increasing that should solve the
> problem.
> Note in my experience setting this to anything > 1000ms will freak out
> FFADO, as we have an XRun that can last a second and then my AudioFire
> makes JACK stop... or something. 500ms is what I usually have loaded,
> for debugging programs you'll want to set it high..
> HTH! -Harry
> On Sun, Oct 9, 2011 at 11:18 AM, Q <lists at quirq.ukfsn.org
> <mailto:lists at quirq.ukfsn.org>> wrote:
>     Hi everyone
>     I've recently upgraded my system from Ubuntu Studio 9.10 to a fresh
>     install of Xubuntu 11.04 (with the Studio packages installed). I'm
>     currently running the stock Xubuntu kernel.
>     On the new system I've installed Ardour 2.8.12 using the installer
>     from the Ardour website. I was using an older, but still fairly
>     recent 2.8 series IIRC, version under UbuStu. I'm now running Jack
>     0.120.1.
>     Here's the problem. Whenever I try adding a track or bus Ardour
>     usually, but not always, gets disconnected from Jack. This also
>     occurs when trying to remove tracks or busses, or when changing the
>     connections on existing tracks and busses to re-route stuff.
>     This isn't isolated to a single session and these were both very
>     light sessions with single-digit CPU loads.
>     Is this an Ardour problem, a Jack problem or an OS problem? As you
>     can see, there are quite a few new variables.
>     Any idea of what the cause of the problem might be and how to
>     resolve it?
>     Thanks in advance
>     Q

More information about the Ardour-Users mailing list