17 Jan
2017
17 Jan
'17
9:58 a.m.
Hi,
I'm having trouble setting up Jack to interface between my digital piano
application (pianoteq) and the ecasound audio processing app. I'm using
ecasound with Ladspa plugins to create a crossover network. Ecasound
splits the 2 pianoteq channels into six (woofer, mid & tweeter), and sends
them to my analog outputs through alsa. I have it working, with jack &
qjackctl, but the buffer size that jack is presenting to the digital piano
app is 1024, about 10x bigger than I want. I would like pianoteq and
ecasound to run synchronously with minimal latency. At first I thought I
could just call jackd -d ecasound -p 128, but of course ecasound is not
one of jack's supported backends. So I've been using the "dummy"
backend,
and using qjackctl to connect ports from pianoteq to ecasound. That works
fine, but I can't manage to configure the buffer size down to 128, even
though I start up ecasound with -i jack -b:128, and I also go to setup in
qjackctl and specify buffer size 128 for "dummy". When qjackctl brings up
the jack server, the buffer size gets overridden to 1024; I see the message
in the log. What am I doing wrong? Is Jack the wrong approach, when it is
ecasound, not jack, that writes to alsa?
Thanks very much!
John
Msi mb with i5 3ghz, AVS Linux
--
Sent from Gmail Mobile
17 Jan
17 Jan
10:23 a.m.
New subject: using Jack an interface to ecasound
Jan 17 2017, john gibby has written:
...
> When qjackctl brings up
> the jack server, the buffer size gets overridden to 1024; I see the message
> in the log. What am I doing wrong? Is Jack the wrong approach, when it is
> ecasound, not jack, that writes to alsa?
Hi John,
it appears that your soundcard is the problem. I've only started JACK on
the commandline or through a dedicated start script, not using qjackctl
or other JACK-supplied tools. But if you give a buffersize to JACK it
will honour that buffersize, if the soundcard can stand it. I haven't
seen an application before that couldn't honour JACK's buffersize,
whatever it is. Especially Ecasound can certainly go down to 64 samples.
What soundcard do you have? Have you tried starting JACK for your
soundcard on the commandline and see what happens?
jackd --timeout 4500 -R -d alsa -d hw:0 -p 128
Assuming that your soundcard is the first one (hw:0).
I have no experience with Pianoteq, but since it is meant as a realtime
app, it should make sure that its sounds are played back without delay
or with minimal delay. 128 and even 64 samples aren't that uncommon.
...
Best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
10:35 a.m.
New subject: using Jack an interface to ecasound
Sound is via ALC 1150 chipset; I don't think that's the problem. When I go
directly from pianoteq to alsa there's no problem; can use even a 64 sample
buffer. Maybe I need a little help in killing the default jack server and
starting it back (with dummy back end ) using direct jackd command line
instead of using qjackctl? Then I think it may keep my specified buffer
size. Am Linux newby, takes a little work! :)
On Jan 17, 2017 4:23 AM, "Jeanette C." <julien(a)mail.upb.de> wrote:
Jan 17 2017, john gibby has written:
...
When qjackctl brings up
it appears that your soundcard is the problem. I've only
started JACK on
the commandline or through a dedicated start script, not using qjackctl
or other JACK-supplied tools. But if you give a buffersize to JACK it
will honour that buffersize, if the soundcard can stand it. I haven't
seen an application before that couldn't honour JACK's buffersize,
whatever it is. Especially Ecasound can certainly go down to 64 samples.
What soundcard do you have? Have you tried starting JACK for your
soundcard on the commandline and see what happens?
jackd --timeout 4500 -R -d alsa -d hw:0 -p 128
Assuming that your soundcard is the first one (hw:0).
I have no experience with Pianoteq, but since it is meant as a realtime
app, it should make sure that its sounds are played back without delay
or with minimal delay. 128 and even 64 samples aren't that uncommon.
...
Best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
the jack server, the buffer size gets overridden
to 1024; I see the
message
in the log. What am I doing wrong? Is Jack the wrong approach, when it
is
ecasound, not jack, that writes to alsa?
Hi John, 
12:18 p.m.
New subject: using Jack an interface to ecasound
On 01/17/2017 04:35 AM, john gibby wrote:
Sound is via ALC 1150 chipset; I don't think
that's the problem. When
I go directly from pianoteq to alsa there's no problem; can use even a
64 sample buffer. Maybe I need a little help in killing the default
jack server and starting it back (with dummy back end ) using direct
jackd command line instead of using qjackctl? Then I think it may
keep my specified buffer size. Am Linux newby, takes a little work! :)
On Jan 17, 2017 4:23 AM, "Jeanette C." <julien(a)mail.upb.de
<mailto:julien@mail.upb.de>> wrote:
Jan 17 2017, john gibby has written:
...
When qjackctl brings up
the jack server, the buffer size gets overridden to 1024;
I see the message
in the log. What am I doing wrong? Is Jack the wrong
approach, when it is
ecasound, not jack, that writes to alsa?
Hi John,
it appears that your soundcard is the problem. I've only started
JACK on
the commandline or through a dedicated start script, not using
qjackctl
or other JACK-supplied tools. But if you give a buffersize to JACK it
will honour that buffersize, if the soundcard can stand it. I haven't
seen an application before that couldn't honour JACK's buffersize,
whatever it is. Especially Ecasound can certainly go down to 64
samples.
What soundcard do you have? Have you tried starting JACK for your
soundcard on the commandline and see what happens?
jackd --timeout 4500 -R -d alsa -d hw:0 -p 128
Assuming that your soundcard is the first one (hw:0).
I have no experience with Pianoteq, but since it is meant as a
realtime
app, it should make sure that its sounds are played back without delay
or with minimal delay. 128 and even 64 samples aren't that uncommon.
...
Best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
maybe a jackdbus thing? if you're using jack2, what does "jack_control
status" show?
if it says "started", do "jack_control stop" then try your jack
command/qjackctl.
--
www.the-temp-agency.com/lollipop-factory
12:30 p.m.
New subject: using Jack an interface to ecasound
On 01/17/2017 06:17 AM, Tweed wrote:
On 01/17/2017 04:35 AM, john gibby wrote:
Also, if you''re setting up a crossover for your monitors I would
recommend checking out Fons' excellent zita-lrx.
http://kokkinizita.linuxaudio.org/linuxaudio/downloads/
Debian (kxstudio) and Arch packages available for that.
--
www.the-temp-agency.com/lollipop-factory
Sound is via ALC 1150 chipset; I don't think
that's the problem.
When I go directly from pianoteq to alsa there's no problem; can use
even a 64 sample buffer. Maybe I need a little help in killing the
default jack server and starting it back (with dummy back end ) using
direct jackd command line instead of using qjackctl? Then I think it
may keep my specified buffer size. Am Linux newby, takes a little
work! :)
On Jan 17, 2017 4:23 AM, "Jeanette C." <julien(a)mail.upb.de
<mailto:julien@mail.upb.de>> wrote:
Jan 17 2017, john gibby has written:
...
When qjackctl brings up
the jack server, the buffer size gets overridden to 1024;
I see the message
in the log. What am I doing wrong? Is Jack the wrong
approach, when it is
ecasound, not jack, that writes to alsa?
Hi John,
it appears that your soundcard is the problem. I've only started
JACK on
the commandline or through a dedicated start script, not using
qjackctl
or other JACK-supplied tools. But if you give a buffersize to JACK it
will honour that buffersize, if the soundcard can stand it. I haven't
seen an application before that couldn't honour JACK's buffersize,
whatever it is. Especially Ecasound can certainly go down to 64
samples.
What soundcard do you have? Have you tried starting JACK for your
soundcard on the commandline and see what happens?
jackd --timeout 4500 -R -d alsa -d hw:0 -p 128
Assuming that your soundcard is the first one (hw:0).
I have no experience with Pianoteq, but since it is meant as a
realtime
app, it should make sure that its sounds are played back without
delay
or with minimal delay. 128 and even 64 samples aren't that uncommon.
...
Best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
maybe a jackdbus thing? if you're using jack2, what does
"jack_control status" show?
if it says "started", do "jack_control stop" then try your jack
command/qjackctl.
--
www.the-temp-agency.com/lollipop-factory
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user 
4:22 p.m.
New subject: using Jack an interface to ecasound
Hi,
On 17 Jan 2017, at 10:23, Jeanette C.
<julien(a)mail.uni-paderborn.de> wrote:
Jan 17 2017, john gibby has written:
wait a minute ....
assuming jack should already run, when starting qjackctl, nothing should change.
If you use QjackCtl to start jack, then take a look at the settings dialog provided by
QjackCtl. Set up the wanted frames value, then stop jack and after that start it again.
QjackCtl provides buttons to stop and start it.
Mention what version of QjackCtl you are using, unfortunately the GUI was redesigned.
Also take a look at the settings, does it start jackd or jackdbus?
What version of Jack are you using?
I suspect that it's not an issue with the audio interface, but a user error.
Regards,
Ralf
> When qjackctl brings up the jack server, the
buffer size gets overridden to 1024
it appears that your soundcard is the problem.
10:32 p.m.
New subject: using Jack an interface to ecasound
On Tue, January 17, 2017 2:58 am, john gibby wrote:
> I'm having trouble setting up Jack to
interface between my digital piano
> application (pianoteq) and the ecasound audio processing app. I'm using
> ecasound with Ladspa plugins to create a crossover network. Ecasound
> splits the 2 pianoteq channels into six (woofer, mid & tweeter), and
> sends them to my analog outputs through alsa.
That is a very odd way to use jackd. The usual way is that jackd controls
the audio interface.
How do you even configure ecasound to present a jack interface and also
connect to the ALSA hardware directly? Most software supports using
either ALSA directly or jack, but not both simultaneously.
If you want to continue to use ecasound the more typical way would be
configure jackd to control the output hardware, configure ecasound to use
jack, and then use whatever connection configuration tool you want (e.g.
qjackctl or jack_connect) to connect the output of your audio applications
to the inputs of ecasound, and the outputs of ecasound to the sound card.
As others pointed out something like zita_lrx might fit into a jack setup
more easily, but if you already have ecasound configured and ecasound can
use jack then the setup I describe above might be the easiest way to
modify what you currently have.
--
Chris Caudle
18 Jan
18 Jan
8:19 a.m.
New subject: using Jack an interface to ecasound
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
gibbyj@LinuxBVR:~/Downloads$ killall jackd
jackd: no process found
gibbyj@LinuxBVR:~/Downloads$ ps -ef |grep jackd
gibbyj 4413 1 0 Jan17 ? 00:01:31 /usr/bin/jackdbus auto
gibbyj 12590 3958 0 02:12 pts/1 00:00:00 grep jackd
gibbyj@LinuxBVR:~/Downloads$
No sound coming out yet with this new approach, I guess b/c I see 32
choices for hw:2 playback and I need to figure out which ones are the right
ones to send the output to. But I think I'm making progress...
Thanks,
John
On Tue, Jan 17, 2017 at 4:31 PM, Chris Caudle <chris(a)chriscaudle.org> wrote:
On Tue, January 17, 2017 2:58 am, john gibby wrote:
> I'm having trouble setting up Jack to
interface between my digital piano
> application (pianoteq) and the ecasound audio processing app. I'm using
> ecasound with Ladspa plugins to create a crossover network. Ecasound
> splits the 2 pianoteq channels into six (woofer, mid & tweeter), and
> sends them to my analog outputs through alsa.
That is a very odd way to use jackd. The usual way is that jackd controls
the audio interface.
How do you even configure ecasound to present a jack interface and also
connect to the ALSA hardware directly? Most software supports using
either ALSA directly or jack, but not both simultaneously.
If you want to continue to use ecasound the more typical way would be
configure jackd to control the output hardware, configure ecasound to use
jack, and then use whatever connection configuration tool you want (e.g.
qjackctl or jack_connect) to connect the output of your audio applications
to the inputs of ecasound, and the outputs of ecasound to the sound card.
As others pointed out something like zita_lrx might fit into a jack setup
more easily, but if you already have ecasound configured and ecasound can
use jack then the setup I describe above might be the easiest way to
modify what you currently have.
--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
12:49 p.m.
New subject: 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@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
5:25 p.m.
New subject: using Jack an interface to ecasound
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
7:45 p.m.
New subject: using Jack an interface to ecasound
Den 2017-01-18 kl. 17:25, skrev john gibby:
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.
You should be able to trace that from the dpkg log files in /var/log
/var/log/dpkg.log
/var/log/dpkg.log.1
/var/log/dpkg.log.2.gz
/var/log/dpkg.log.3.gz
etc
try:
grep installed /var/log/dpkg.log /var/log/dpkg.log.1 | grep jackd
or
zgrep installed /var/log/dpkg.log.[0-9].gz | grep jackd
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
<mailto:edogawa@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 <http://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
<mailto:Linux-audio-user@lists.linuxaudio.org>
http://lists.linuxaudio.org/listinfo/linux-audio-user
<http://lists.linuxaudio.org/listinfo/linux-audio-user>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
/bengan
19 Jan
19 Jan
4:10 a.m.
New subject: using Jack an interface to ecasound
I'm making progress. I believe I actually have jack2, with "legacy server
jackd" included along with it. I have successfully used the jack2 admin
commands to start/stop and configure jack, to 128 samples, n=3, my alsa
device, etc. I tried to set priority to 20 but since I can't remember my
admin password, no go on that. Pianoteq finally sees 128 buffer size
instead of 1024, and I can hear my piano on one of my speakers. Maybe if I
could set the priority down to 20, I could use 64 sample buffer. I see 8
playback channels in qjackctl, which I think is correct for my ALC1150
device. I still have some problems but am a ways down the road now...
Thanks!
But, I'm still a little unclear on what order to start things up in. For
now, I'm only worried about jack2, qjackctl and pianoteq; ecasound will
come later. If I don't start things up in the right order, it seems, I
cannot use qjackctl to make the connections (it ignores my clicks).
Suppose I set up a patchbay profile (once I manage to get the connections
made again). Is this the right order to quickly bring it all back up later:
1. run the commands that start jackdbus
2. start pianoteq
3. bring up qjackctl (will my saved profile then be activated, connecting
pianoteq to jack according to the profile connections?)
Thanks again,
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
6:16 p.m.
New subject: using Jack an interface to ecasound
On 19/01/17 03:10, john gibby wrote:
I'm making progress. I believe I actually have
jack2, with "legacy
server jackd" included along with it. I have successfully used the
jack2 admin commands to start/stop and configure jack, to 128 samples,
n=3, my alsa device, etc. I tried to set priority to 20 but since I
can't remember my admin password, no go on that. Pianoteq finally
sees 128 buffer size instead of 1024, and I can hear my piano on one
of my speakers. Maybe if I could set the priority down to 20, I could
use 64 sample buffer. I see 8 playback channels in qjackctl, which I
think is correct for my ALC1150 device. I still have some problems but
am a ways down the road now... Thanks!
But, I'm still a little unclear on what order to start things up in.
For now, I'm only worried about jack2, qjackctl and pianoteq; ecasound
will come later. If I don't start things up in the right order, it
seems, I cannot use qjackctl to make the connections (it ignores my
clicks). Suppose I set up a patchbay profile (once I manage to get
the connections made again). Is this the right order to quickly bring
it all back up later:
1. run the commands that start jackdbus
2. start pianoteq
3. bring up qjackctl (will my saved profile then be activated,
connecting pianoteq to jack according to the profile connections?)
Thanks again,
John
Hi John,
I have had still to fathom out how to get things just the way I want
them automatically.
After booting up, I start QjackCtl which seems to start Jackdbus quite
happily. I then
start and stop various things, and then configure the connections with
QjackCtl.
I had some problems when I plugged in a keyboard, as it didn't appear to
Jack, but then
I was advised to run a2j (alsa-to-jack) which makes a connection between
the keyboard and
Jack, then I can connect that to my sequencer program (home-grown.)
This list is a great asset for us. Lots of knowledgeable folks around
who are willing
to offer advice. Thanks folks!!
Bill
--
+----------------------------------------+
| Bill Purvis |
| email: bill(a)billp.org |
+----------------------------------------+
20 Jan
20 Jan
12:49 a.m.
New subject: using Jack an interface to ecasound
On Wed, January 18, 2017 9:10 pm, john gibby wrote:
I'm making progress. I believe I actually have
jack2, with "legacy server
jackd" included along with it.
I have trouble understanding what that means, jack2 is an implementation
of a jack protocol server, the original jackd is also an implementation of
a jack protocol server, they are functionally interchangeable, but you can
only have one or the other installed on your machine, not both.
Perhaps that wording means that your distribution has jack2, with both
jackd and jackdbus installed. That is OK, but as you seem to have found
out sometimes an application will automatically start jackdbus which then
limits how you have to interact with the already running server.
But, I'm still a little unclear on what order to
start things up in. For
now, I'm only worried about jack2, qjackctl and pianoteq;
My preference is to start qjackctl first. There are configuration options
to allow you to choose whether you want to start jackd or jackdbus, there
are convenient start and stop controls, the ability to save preset
combinations of jackd parameters you want to use (sample rate, latency,
audio interface, etc.), you can easily show or hid the console messages,
open a window to make connections. Basically everything you need to
interact with jack in one convenient place.
My usual process would be start qjackctl, load whichever preset I needed,
start jack, then start all the jack using applications I wanted.
--
Chris Caudle
12:59 p.m.
New subject: using Jack an interface to ecasound
OK Chris & Bill, thanks so much! As Bill said, I'm really lucky to have
access to this community.
To make a long story short on the jact1/jack2 issue, I could be wrong but I
believe, based on what I've read and observe, that my AVL system is
probably not corrupted, and is using jack2. I did searches thru install
packages and saw nothing related to jack1 that got installed by mistake.
The only jack processes I see running are qjackctl and jackdbus, and the
jack_control commands work. I'll keep alert to any signs that my system
somehow has both of them mixed up, but I don't think it does.
Last night I got it all working, basically following all the advice I've
received in this thread. I have a jack_start.sh script which uses
jack_control commands and has a patchbay profile to reconnect the objects.
I have a simple 2-way crossover at 60hz, and it works. My piano app see's
a 128 sample buffer, and I don't see any xruns. It sounds reasonably well.
BUT.....
Maybe jack does not play well with ecasound, because the below-60hz channel
seems way attenuated. Also, I seem to feel too much latency. I turned my
woofer amp up all the way, and I can hear the bass OK, but this is just not
right; turned up that high it should blow out the windows. Without the
ecasound/Richard Taylor LR crossover, it has much higher SPL for same
setting. (I learned about ecasound, and downloaded some ladspa filters,
from Richard Taylor's DSP website.) I'm pretty sure that when I tested
using just ecasound and not jack, I got plenty of volume out of my 12",
large cabinet woofers.
So darn, now I'm not sure which direction to go to most efficiently solve
this. I could start switching wires around to make sure it's not something
about my hardware, etc. But my suspicion, based on what y'all told me
above somewhere, is that ecasound and jack are not completely compatible in
some way, and I need to switch to the zitaIrc packages... Or, I could stop
using jack, study the Richard Taylor posts carefully, and see if there's a
way to connect pianoteq to ecasound without jack, like with plain Linux
pipes maybe. Thoughts??
Thanks,
John
On Thu, Jan 19, 2017 at 6:48 PM, Chris Caudle <chris(a)chriscaudle.org> wrote:
On Wed, January 18, 2017 9:10 pm, john gibby wrote:
I'm making progress. I believe I actually
have jack2, with "legacy
server
jackd" included along with it.
I have trouble understanding what that means, jack2 is an implementation
of a jack protocol server, the original jackd is also an implementation of
a jack protocol server, they are functionally interchangeable, but you can
only have one or the other installed on your machine, not both.
Perhaps that wording means that your distribution has jack2, with both
jackd and jackdbus installed. That is OK, but as you seem to have found
out sometimes an application will automatically start jackdbus which then
limits how you have to interact with the already running server.
But, I'm still a little unclear on what order
to start things up in. For
now, I'm only worried about jack2, qjackctl and pianoteq;
My preference is to start qjackctl first. There are configuration options
to allow you to choose whether you want to start jackd or jackdbus, there
are convenient start and stop controls, the ability to save preset
combinations of jackd parameters you want to use (sample rate, latency,
audio interface, etc.), you can easily show or hid the console messages,
open a window to make connections. Basically everything you need to
interact with jack in one convenient place.
My usual process would be start qjackctl, load whichever preset I needed,
start jack, then start all the jack using applications I wanted.
--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
2:07 p.m.
New subject: using Jack an interface to ecasound
On Fri, 20 Jan 2017 06:59:50 -0500, john gibby wrote:
I did searches thru install packages and saw nothing
related to jack1
that got installed by mistake.
To list all jack related packages that are installed run
mkdir /tmp/empty_dir
cd /tmp/empty_dir/
dpkg -l *jack* | grep ii
This doesn't ensure that nothing jack related is in a critical path, if
you should have installed something without a package or assuming you
did remove a package without removing all files, that were provided by a
package.
My piano app see's a 128 sample buffer [...] I seem
to feel too much
latency.
You started jack with 128 frames and periods are 2 or 3, for a sample
rate at 44.1 KHz or 48 KHz?
If so, play a note and check if the tuning at the audio output is
correct? Use an external instrument tuner or compare the audio output
with an external instrument or tuning fork.
Regards,
Ralf
2:26 p.m.
New subject: using Jack an interface to ecasound
On Friday 20 January 2017, Ralf Mardorf wrote:
To list all jack related packages that are installed
run
mkdir /tmp/empty_dir
cd /tmp/empty_dir/
dpkg -l *jack* | grep ii
for you are not saving anything, you don't need to create a new folder. Furthermore my
shell tries
to expand *jack*; you have to use the ' character (don't know its name in English)
like this:
dpkg -l '*jack*' | grep ii
Gerhard
2:50 p.m.
New subject: using Jack an interface to ecasound
On Fri, 20 Jan 2017 14:26:43 +0100, Gerhard Zintel wrote:
On Friday 20 January 2017, Ralf Mardorf wrote:
Thank you,
I'm using Arch Linux and didn't know this, but since I'm aware that
"apt" does not have a stable CLI interface, I wanted to ensure that
"dpkg -l" works. I already used "dpkg" instead of "apt",
since even not
all DEB based installs provide "apt", at least not one still supported
Ubuntu release. Running "dpkg -l *jack* | grep ii" in an empty
directory gains nothing over "dpkg -l '*jack*' | grep ii", but I
didn't
know that "dpkg -l '*jack*' | grep ii" does work. I'll try to keep
this
in mind, OTOH the transition to apt, at least for Ubuntu, already
started, so dpkg soon or later will be obsolet.
Regards,
Ralf
To list all jack related packages that are
installed run
mkdir /tmp/empty_dir
cd /tmp/empty_dir/
dpkg -l *jack* | grep ii
for you are not saving anything, you don't need to create a new
folder. Furthermore my shell tries to expand *jack*; you have to use
the ' character (don't know its name in English) like this:
dpkg -l '*jack*' | grep ii
21 Jan
21 Jan
12:41 a.m.
New subject: using Jack an interface to ecasound
Ralf, here is the output from dpkg:
i jack-capture 0.9.71-1 amd64 program
for recording soundfiles with jack
ii jackass 1:20140520-1kxstudio1 amd64
JACK-MIDI support for VST hosts
ii jackd 5 all JACK
Audio Connection Kit (default server package)
ii jackd1 2:0.124.2~20151211-2~xenial1 amd64 JACK
Audio Connection Kit (server and example clients)
ii jackd1-firewire 2:0.124.2~20151211-2~xenial1 amd64 JACK
Audio Connection Kit (FFADO backend)
ii jackutils-script 0.0.1avlinux6-1 all Simple
Start and Stop Scripts to Utilize With QJackctl and Launch a2jmidid and
aloop-daemon - Custom AV Linux Package
ii libjack-dev 2:0.124.2~20151211-2~xenial1 amd64 JACK
Audio Connection Kit (development files)
ii libjack0:amd64 2:0.124.2~20151211-2~xenial1 amd64 JACK
Audio Connection Kit (libraries)
ii libjack0:i386 2:0.124.2~20151211-2~xenial1 i386 JACK
Audio Connection Kit (libraries)
ii qjackctl 2:0.4.1-1kxstudio2 amd64 User
interface for controlling the JACK sound server
ii screencapjack-script 0.1.2avlinux8-1 all A very
basic screen capture script using ffmpeg and jack-capture, the script is
installed to /usr/local/bin and can edited with a text editor. Custom AV
Linux Package
I am using buffer size 128, N=3, 48000hz. When I use N=2, all I hear is
some clicking. I don't currently have an external instrument or tuning
fork. I think the latency problem may be due to the above - seems I
installed things from kxstudio that I didn't realize. I'm not sure why I
can't use an even smaller buffer size; I guess pianoteq is too cpu
intensive.
When I take jack out of the equation and play an mp3 file thru ecasound and
the 2-way crossover, it works correctly and sounds good.
By the way, I'm embarrassed to admit that I really have forgotten my admin
password, so I think I need to re-install AVL. That would get me back to
the correct baseline for Jack in AVL. But then I would have to decide
whether to re-install ecasound - which might have been what corrupted jack
for me?? Or, to forget ecasound and use zita-Irc.
Thanks,
John
On Fri, Jan 20, 2017 at 8:07 AM, Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
wrote:
On Fri, 20 Jan 2017 06:59:50 -0500, john gibby wrote:
I did searches thru install packages and saw
nothing related to jack1
that got installed by mistake.
To list all jack related packages that are installed run
mkdir /tmp/empty_dir
cd /tmp/empty_dir/
dpkg -l *jack* | grep ii
This doesn't ensure that nothing jack related is in a critical path, if
you should have installed something without a package or assuming you
did remove a package without removing all files, that were provided by a
package.
My piano app see's a 128 sample buffer [...] I
seem to feel too much
latency.
You started jack with 128 frames and periods are 2 or 3, for a sample
rate at 44.1 KHz or 48 KHz?
If so, play a note and check if the tuning at the audio output is
correct? Use an external instrument tuner or compare the audio output
with an external instrument or tuning fork.
Regards,
Ralf
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
1:04 a.m.
New subject: using Jack an interface to ecasound
On 21/01/17 10:41, john gibby wrote:
By the way, I'm embarrassed to admit that I really have forgotten my
admin password, so I think I need to re-install AVL.
You don't need to reinstall to reset your root password -
https://wiki.archlinux.org/index.php/Reset_root_password
7:10 a.m.
New subject: using Jack an interface to ecasound
On Sat, 21 Jan 2017 00:41:23 +0100, john gibby <johnalan.gibby(a)gmail.com>
wrote:
Ralf, here is the output from dpkg:
Audio Connection Kit (default server package)
ii jackd1 2:0.124.2~20151211-2~xenial1 amd64 JACK
ii libjack-dev 2:0.124.2~20151211-2~xenial1 amd64 JACK
Audio Connection Kit (development files)
Now we _know_ you are using jack1 and _not_ jack2.
Did you compile software?
I am using buffer size 128, N=3, 48000hz.
This shouldn't cause too much latency.
By the way, I'm embarrassed to admit that I really
have forgotten my
admin password
Boot a live media. Since modern Linux usually use systemd, you not
necessarily need to chroot, alternatively you could use a systemd-nspawn
container.
Mount the root partition of the install, replace /dev/sda1 by the correct
partition:
# mkdir /mnt/linux
# mount /dev/sda1 /mnt/linux
# systemd-nspawn -qD /mnt/linux
# passwd root
or
# passwd username
if you don't use a root account, but sudo only, if so replace "username"
by the name of the first user (UID 1000).
Push Ctrl+D to leave the container.
Regards,
Ralf
8:26 a.m.
New subject: using Jack an interface to ecasound
I booted my LiveCD and saw that the dpkg output there is just the same as
for my regular system (on solid-state drive). I'm glad to know that I have
jack1 and not jack2, though I'm still not really sure I understand
completely, since the jack process I get is named jackdbus. For now, I
stopped using the jack_control shell script and am just using qjackctl to
bring jack up, and still, the process name is jackdbus. I thought jackdbus
was jack2...
Also, after considering your input on my password situation, I finally
realized that in Linux there's not a separate admin user name, and I
started the root terminal and was able to remember/specify the correct root
password. So that problem is solved.
The most interesting thing is my mistaken idea that the low-pass filter was
attenuating a lot. I think I have been misunderstanding the frequency
content of those low notes on a piano. I was thinking for example the low
A is a more or less pure 27.5hz, but now I think I see, duh, there are lots
of resonances that you hear, that are higher frequencies. My 60hz low
pass filter gets rid of those and sends them to the mid/high speaker, so
all that is left for the big woofer is the lowest frequency content. That
is a kind of strange sound; divorced from its resonances, the piano key
sounds weird, and probably due to my woofers needing equalization below
50hz or so, it's not as loud. Have I got this right??
If so, I'm thinking, everything is actually working correctly!! Next
challenge: to figure out how to add some equalization via ecasound (or
other way you guys might suggest) to get good response out of my woofers,
all the way down into the 20-30hz range. That should finally make my piano
sound more like a real grand piano, I think.
Thanks!!
John
On Sat, Jan 21, 2017 at 1:10 AM, Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
wrote:
On Sat, 21 Jan 2017 00:41:23 +0100, john gibby
<johnalan.gibby(a)gmail.com wrote:
This shouldn't cause too much latency.
By the way, I'm embarrassed to admit that I really have forgotten my admin
> password
Boot a live media. Since modern Linux usually use systemd, you not
necessarily need to chroot, alternatively you could use a systemd-nspawn
container.
Mount the root partition of the install, replace /dev/sda1 by the correct
partition:
# mkdir /mnt/linux
# mount /dev/sda1 /mnt/linux
# systemd-nspawn -qD /mnt/linux
# passwd root
or
# passwd username
if you don't use a root account, but sudo only, if so replace "username"
by the name of the first user (UID 1000).
Push Ctrl+D to leave the container.
Regards,
Ralf
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
Ralf, here is the output from dpkg:
Audio Connection Kit (default server package)
ii jackd1 2:0.124.2~20151211-2~xenial1 amd64 JACK
ii libjack-dev 2:0.124.2~20151211-2~xenial1 amd64 JACK
Audio Connection Kit (development files)
Now we _know_ you are using jack1 and _not_ jack2.
Did you compile software?
I am using buffer size 128, N=3, 48000hz.
10:44 a.m.
New subject: using Jack an interface to ecasound
Hi John,
Am 21.01.2017 um 08:26 schrieb john gibby:
I booted my LiveCD and saw that the dpkg output there
is just the same
as for my regular system (on solid-state drive). I'm glad to know
that I have jack1 and not jack2, though I'm still not really sure I
understand completely, since the jack process I get is named
jackdbus. For now, I stopped using the jack_control shell script and
am just using qjackctl to bring jack up, and still, the process name
is jackdbus. I thought jackdbus was jack2...
As this has become more and more of a mystery, I have investigated a
little more. reading the AVLinux user manual, particularly the section
on software management, I was able to locate where the jackd packages
come from, and that is in fact the kxstudio repos. once I found that out
I was able to inspect the build logs for the jack package here:
https://launchpadlibrarian.net/229691222/buildlog_ubuntu-xenial-amd64.jack-…
and it turns out that it has the jackdbus patch applied.
So this part of the mystery is resolved, and your system seems to be in
good shape.
I have to apologize for adding to confusion and leading you on the wrong
track, just remember I'm not familiar with AV Linux (have looked at it
several times in the past 15 years but never regularly used it...) and
this 2016 version is significantly different from previous ones in that
it incorporates the kxstudio repos as a core part, which i didn't
realize at first. I'm really sorry for that.
As for your crossover filter network, I've never tried to do such a thig
in software, so I have to pass that on to more knwledgable folks...
Cheers, Edgar
11:16 a.m.
New subject: using Jack an interface to ecasound
On Sat, 21 Jan 2017 10:44:37 +0100, edogawa wrote:
it turns out that it has the jackdbus patch applied.
Hi,
that might explain the reason for the epoch of the package. It at least
underpins my claim, that "everything unwanted and impossible, becomes
possible, when running a Debian based Linux", especially when using
third party repositories.
Regards,
Ralf
1:29 p.m.
New subject: using Jack an interface to ecasound
On 21/01/17 21:16, Ralf Mardorf wrote:
On Sat, 21 Jan 2017 10:44:37 +0100, edogawa wrote:
I'm pretty sure you could patch jack in an Arch based
distro if you
wished to.
it turns out that it has the jackdbus patch
applied.
Hi,
that might explain the reason for the epoch of the package. It at least
underpins my claim, that "everything unwanted and impossible, becomes
possible, when running a Debian based Linux", especially when using
third party repositories.
8:43 p.m.
New subject: using Jack an interface to ecasound
On Sat, 21 Jan 2017 23:29:29 +1100, Roger wrote:
I'm pretty sure you could patch jack in an Arch
based distro if you
wished to.
Hi,
nothing would be easier than doing this, since Arch comes with a
FreeBSD alike build system, fortunately it would allow to easily change
the name to something like "jack1-dbus", too ;). My point is, that users
get confused, if distros patch software in very unusual ways, by still
using the common package names and even more bad is, that we try to
help each other, but we waste a lot of time with being confused. So no,
you unlikely will find such unthoughtful packaging by an Arch Linux
repository. Regarding this jack1 example you even will not run into
this issue, when using official Debian or Ubuntu repositories, it's
just another "special" distro problem. IMO those distros gain nothing,
they only cause problems for users.
Regards,
Ralf
11:03 a.m.
New subject: using Jack an interface to ecasound
On Sat, 21 Jan 2017 02:26:34 -0500, john gibby wrote:
I'm still not really sure I understand completely,
since the jack
process I get is named jackdbus
Hi,
everything unwanted and impossible, becomes possible, when running a
Debian based Linux. That's why I prefer Arch Linux over Debian and
Ubuntu, but Arch Linux requires some knowledge you seem not to have at
the moment, so stay with your distro. What output do you get, if you run
the following commands?
$ pgrep -a jack
$ jackd -V | head -1
$ jackdbus
$ ls -hl /usr/bin/jackd* /usr/local/bin/jackd* /opt/jack*
$ cat /etc/os-release
For an Ubuntu install the output here is
[weremouse@moonstudio ~]$ pgrep -a jack
1769 qjackctl
1775 /usr/bin/jackd -dalsa -dhw:HDSPMx579bcc -r48000 -p256 -n2
[weremouse@moonstudio ~]$ jackd -V | head -1
jackdmp 1.9.11
[weremouse@moonstudio ~]$ jackdbus
jackdbus should be auto-executed by D-Bus message bus daemon.
If you want to run it manually anyway, specify "auto" as only parameter
[weremouse@moonstudio ~]$ ls -hl /usr/bin/jackd* /usr/local/bin/jackd* /opt/jack*
ls: cannot access '/usr/local/bin/jackd*': No such file or directory
ls: cannot access '/opt/jack*': No such file or directory
-rwxr-xr-x 1 root root 31K Oct 29 2015 /usr/bin/jackd
-rwxr-xr-x 1 root root 100K Oct 29 2015 /usr/bin/jackdbus
[weremouse@moonstudio ~]$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Regards,
Ralf
18 Jan
18 Jan
2:46 a.m.
New subject: using Jack an interface to ecasound
john gibby wrote:
> Hi,
> I'm having trouble setting up Jack to interface between my digital piano
> application (pianoteq) and the ecasound audio processing app. I'm using
> ecasound with Ladspa plugins to create a crossover network. Ecasound
> splits the 2 pianoteq channels into six (woofer, mid & tweeter), and sends
> them to my analog outputs through alsa. I have it working, with jack &
> qjackctl, but the buffer size that jack is presenting to the digital piano
> app is 1024, about 10x bigger than I want. I would like pianoteq and
> ecasound to run synchronously with minimal latency. At first I thought I
> could just call jackd -d ecasound -p 128, but of course ecasound is not
> one of jack's supported backends. So I've been using the "dummy"
backend,
> and using qjackctl to connect ports from pianoteq to ecasound. That works
> fine, but I can't manage to configure the buffer size down to 128, even
> though I start up ecasound with -i jack -b:128
FWIW, from 'man ecasound':
Note that when any JACK input/outputs are used, the buffer
size setting is overridden and set to period/buffer size
reported by JACK server (e.g. jackd’s ’-p’ option). It is
not possible to turn off this behaviour.
> , and I also go to setup in
> qjackctl and specify buffer size 128 for "dummy". When qjackctl brings
up
> the jack server, the buffer size gets overridden to 1024; I see the message
> in the log. What am I doing wrong? Is Jack the wrong approach, when it is
> ecasound, not jack, that writes to alsa?
Ecasound can connect to both ALSA and JACK devices. I've
used that option in a setup using two soundcards. It is
more common that jackd manages the soundcard. Do you have
any reason not to do so?
HTH,
Joel
Thanks very
much!
John
Msi mb with i5 3ghz, AVS Linux
--
Sent from Gmail Mobile _______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Joel Roth
8:26 a.m.
New subject: using Jack an interface to ecasound
Thanks Joel, sorry, I sent a response before seeing your message. I have
no reason not to configure ecasound to use jack for both input and output,
and am now trying to get it to work that way. I'm trying to bypass qjackctl
and use the jackd command directly, so I can get -p 128. I still do not
understand why I see the message in qjackctl output, that my choice of 128
samples is being overridden to 1024. Please see my other email for some
output I'm seeing...
Thanks again!!
John
On Tue, Jan 17, 2017 at 8:45 PM, Joel Roth <joelz(a)pobox.com> wrote:
john gibby wrote:
> Hi,
> I'm having trouble setting up Jack to interface between my digital
piano
> application (pianoteq) and the ecasound
audio processing app. I'm
using
> ecasound with Ladspa plugins to create a
crossover network. Ecasound
> splits the 2 pianoteq channels into six (woofer, mid & tweeter), and
sends
> them to my analog outputs through alsa. I
have it working, with jack &
> qjackctl, but the buffer size that jack is presenting to the digital
piano
> app is 1024, about 10x bigger than I want.
I would like pianoteq and
> ecasound to run synchronously with minimal latency. At first I
thought I
> could just call jackd -d ecasound -p 128,
but of course ecasound is
not
> one of jack's supported backends. So
I've been using the "dummy"
backend,
> and using qjackctl to connect ports from
pianoteq to ecasound. That
works
> fine, but I can't manage to configure
the buffer size down to 128, even
> though I start up ecasound with -i jack -b:128
FWIW, from 'man ecasound':
Note that when any JACK input/outputs are used, the buffer
size setting is overridden and set to period/buffer size
reported by JACK server (e.g. jackd’s ’-p’ option). It is
not possible to turn off this behaviour.
> , and I also go to setup in
> qjackctl and specify buffer size 128 for "dummy". When qjackctl
brings up
> the jack server, the buffer size gets
overridden to 1024; I see the
message
> in the log. What am I doing wrong? Is Jack
the wrong approach, when
it is
> ecasound, not jack, that writes to alsa?
Ecasound can connect to both ALSA and JACK devices. I've
used that option in a setup using two soundcards. It is
more common that jackd manages the soundcard. Do you have
any reason not to do so?
HTH,
Joel
Thanks
very much!
John
Msi mb with i5 3ghz, AVS Linux
--
Sent from Gmail Mobile _______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Joel Roth
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
2865
days inactive
2869
days old
linux-audio-user@lists.linuxaudio.org
28 comments
11 participants
participants (11)
-
Bengt Gördén -
Bill Purvis -
Chris Caudle -
edogawa -
Gerhard Zintel -
Jeanette C. -
Joel Roth -
john gibby -
Ralf Mardorf -
Roger -
Tweed