Re: [LAU] using Jack an interface to ecasound

Am 18.01.2017 um 08:19 schrieb john gibby:
> Hi Chris et al,
> Thanks so much... I thought I might be using jack incorrectly... So
> now I'm trying to use jack as explained by Chris above. Here's some
> output:
>
> gibbyj@email-addr-hidden:~/Downloads$ jackd -R -d alsa -d hw:2 -p 128 -n 2
> jackd 0.124.2
> Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben
> Hohn and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
>
> JACK compiled with System V SHM support.
> `default' server already active
> no message buffer overruns
>
> I am not sure what it means when it says 'default' server already
> active. I thought I had stopped the server with qjackctl. When I
> start it as above, and then start qjackctl, qjackctl still thinks the
> server is stopped. (Kinda wish I had jack2, seems like it has better
> admin functions.)
>
> Here's some more output; there's a jackdbus process; why is that here,
> I thought that was jack2?
>
> 4611 gibbyj 20 0 813480 76580 56480 S 0.3 1.0 2:08.47
> qjackctl
> 4413 gibbyj 20 0 223540 17504 16136 S 0.3 0.2 1:31.74
> jackdbus
> 4611 gibbyj 20 0 813480 76580 56480 S 0.3 1.0 2:08.48
> qjackctl

`default' server already active: this simply means that jackd is running
already, which is jackdbus in your process list. To control jackdbus
there is a cli program called jack_control, but possibly you cannot even
stop it (by typing "jack_control stop" in a terminal) as long as some
other process uses it.

You really should check what jack packages are installed on your system;
jack1 has no jackdbus coming with it, but if you try to start jackd via
qjackctl it says it is jack1.

There is no way to have jack1 and jack2 installed on the same system.
actually it seems really strange that jackdbus is able to run at all
under this condition, maybe others know more...

jackdbus is a variant of jackd that can communicate via dbus. Once one
jack server is running any subsequent attempt to start a second one will
fail unless you set up for non trivial and sophisticated use cases
typical users don't need.

Looking at AVLinux 2016 I see it has been built anew from ground up and
offers to include the KXStudio repositories, did you by chance install
anything from there?

To me it seems your system is somewhat messed up, you really should
check thoroughly what packages are installed. I'm an openSUSE user
though and don't have much experience with debian derived systems, so
that's about all I can say.

Reading the JACK FAQ at jackaudio.org might be a good idea (to get an
overview about how that ecosystem functions).

Cheers, Edgar

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Wed Jan 18 16:15:02 2017