Re: [Jack-Devel] jackd 0.116 won't release terminal?

PrevNext  Index
DateThu, 10 Mar 2011 15:04:47 -0500
From George Morgan <[hidden] at gmail dot com>
Tojordan <[hidden] at gmail dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-Tojordan Re: [Jack-Devel] jackd 0.116 won't release terminal?
Follow-Upjordan Re: [Jack-Devel] jackd 0.116 won't release terminal?
On Thu, Mar 10, 2011 at 2:16 PM, jordan <[hidden]> wrote:

> Hi George,
>
> > I was looking to start jackd from an init-script in Linux at system start
> > up.  I imagine this is not necessary if I enable auto-start so maybe that
> is
> > the right way to handle things.  I believe a jackdrc (or .jackdrc) is
> > required and setting an environment variable to enable auto start?
>
> Are you referring to the auto-start option in Qjackctl??? (or something
> else?)
> If you are referring to Qjackctl, i believe that only applies to if
> you start Qjackctl, and is not for auto-starting jack on boot.
> (someone can correct me, if am wrong. I dont actually use qjackctl)
>
> A)...depending on what Desktop environment you are using, you could
> just add jack as a startup application. - i know in gnome this is very
> straight forward to do;
>
> system -> preferences -> startup applications
>
> Add a startup application, name it and then put in the commandline
> that you wish to use to start jackd. ex:   jackd -r -dalsa -dhw:0
> -r44100 -p512 -n2  (or whatever)
>
> ...and your done.
>
> B)  I can also tell you how I go about starting Jackd on boot...
>
> In my case , i have multiple dedicated-systems running Jack. ie: a
> synth/sampler/looper rackmount, an multi-FX board, etc that i use for
> live-performance. ~ I use init-scripts. they first start Jack using
> the commandline with my proper settings - ie: what soundcard,
> samplerate, frames, etc (as would be found in .jackdrc) and then it
> loads each application + assigns the proper audio/midi routing to
> each. Then, i tweak the loading order (for faster startup).
>
> ...and i am done. It always loads correctly (and is fool proof!)
>
> a guide for something like this would be the "Ubuntu Studio
> Preparation" guide. found here:
>
> https://help.ubuntu.com/community/UbuntuStudioPreparation
>
> scroll to the bottom of the guide, and look for the heading "Get it
> all going". It's a simple and straight forward to setup (especially,
> if you are new to Jack & if all you want to do is start jackd on
> boot!)
>
> hope that helps,
>
> jordan
>

I am doing something similar to what was described in part B) of your answer
and actually have a script similar to the one at the end of the link you
showed.  I did have to put the sleep in there also to get things started
up.  I happened to be running this in a terminal over SSH on a server for
testing purposes.  When exited the shell and expected the terminal to close
it was kept open.  Since I had run several processes that interact with
jackd I killed them one at a time and it wasn't until I killed jackd that
the ssh session closed allowing the terminal window to close.  This is what
led me to believe that jackd had some dependency on a controlling terminal
or something.

This is what I'm referring to with respect to auto-start:

http://trac.jackaudio.org/wiki/jackdrc%285%29
http://trac.jackaudio.org/wiki/jackdrc(5)

George Morgan
PrevNext  Index

1299787510.17992_0.ltw:2,a <AANLkTinmv1Nyw3Bq=4bHQm2H0Dfb+xEpRs9JNDxYV2vy at mail dot gmail dot com>