18 Jan
2017
18 Jan
'17
5:25 p.m.
Thanks, Edgar. The only thing I am sure I've installed, since starting
with AVL 2016 a few weeks ago, is ecasound. Maybe jack1 came in with
that... on maybe jack2 did. I don't really know which one AVL2016 comes
with. I am tempted to save the few files I've created since installing
AVL2016, and just re-install it. I'm a Linux newbie and I don't know how
to check the packages, though I would like to learn more. And I seem to
have forgotten the admin user/pwd I specified, darn it. A re-install might
be good.
Also, I'm tempted to switch to zita-lrx instead of ecasound, in the process
of this reboot. I've gotten pretty familiar with ecasound and it seems
pretty nice as far as I can tell, but if zita-lrx is newer, better and
offers more functionality, maybe it's time to switch.
Does anyone know if AVL2016 comes with the old jack, or jack2? Since
qjackctl calls jackd, maybe AVL2016 comes with plain jack. I would prefer
to use jack2, but not if it will cause me a lot of trouble that I can't
handle as a newbie...
Thanks,
John
On Wed, Jan 18, 2017 at 6:49 AM, edogawa <edogawa(a)aon.at> wrote:
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@LinuxBVR:~/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(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user