8 Aug
2014
8 Aug
'14
8:11 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
selecting a different interface in qjackctl has no effect. i can't
use the external soundcard, because jack stays always with the
internal one.
any ideas what causes this symptom?
i am running pulse on top of jack like this:
http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
m
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlPlEr0ACgkQ3EB7kzgMM6IMsgCfXLjIAxmgzISXQeGRpF9QMoef
c0AAn3Hm+OvgLZtTWH/sKCSBhWTZpVrt
=PX5E
-----END PGP SIGNATURE-----
8 Aug
8 Aug
9:23 p.m.
New subject: [Bulk] jack: interface selection has no effect
On Sat, 2014-08-09 at 03:11 +0900, Max wrote:
selecting a different interface in qjackctl has no
effect.
You should post the messages.
On the left side, below QjackCtl's "Start" button, there's the
"Messages" button. Click it, select the "Messages" tab, click inside
the
window, push Ctrl+A (select all), then Ctrl+C (copy), click into your
Thunderbird's editor window and push Ctrl+V (paste).
Regards,
Ralf
9 Aug
9 Aug
2:04 a.m.
New subject: [Bulk] jack: interface selection has no effect
On August 9, 2014 03:11:09 AM Max wrote:
selecting a different interface in qjackctl has no
effect. i can't
use the external soundcard, because jack stays always with the
internal one.
any ideas what causes this symptom?
i am running pulse on top of jack like this:
http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
m
I have found that when you set it up that way, you'll find that
nothing you change in QJackCtl has any effect.
You must manually edit the file /home/.jackdrc
and then restart pulse (or reboot).
But I've never quite understood how to properly restart pulse,
it always seems to lead to a messy situation needing a reboot.
You'll see that changes in QJackCtl do not appear in .jackdrc -
pulse seems to override it.
I don't quite understood why this is so.
Seems pulse uses internal jack server or something?
Even if you attempt to 'stop' jack from QJackCtl, it doesn't -
pulse just keeps on running its jack server.
Simply restart QJackCtl and you'll see Jack is actually still running
and has not stopped at all.
Can someone explain why, and how to properly restart pulse after
editing the .jackdrc file, or if there's an easier way to allow
QJackCtl to truly alter the settings?
Thanks!
Tim.
8:58 p.m.
On Sat, 9 Aug 2014, Max wrote:
selecting a different interface in qjackctl has no
effect. i can't
use the external soundcard, because jack stays always with the
internal one.
any ideas what causes this symptom?
i am running pulse on top of jack like this:
http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
That is the hardest way to do it. qjackctl expects (as installed) to use
jackdbus. If you wish to use qjackctl with jackd you have to turn dbus off
in the qjackctl settings. However, if jackd is started externally and not
from qjackctl you will still not be able to stop jackd.
The only reason to do things this way is that you are using jackd1, if you
are using jackd2, and you have dbus running in the session anyway, then
run jackdbus. If you wish to run it from the command line use jack_control
start. If you start it with qjackctl first with the settings you want,
that will be enough, other wise you will have to learn how to set
parameters with jack_control. There is no man page so try jack_control
--help
--
Len Ovens
www.ovenwerks.net
11 Aug
11 Aug
2:10 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/10/2014 03:53 AM, Len Ovens wrote:
On Sat, 9 Aug 2014, Max wrote:
> selecting a different interface in qjackctl has no effect. i
> can't use the external soundcard, because jack stays always with
> the internal one. any ideas what causes this symptom?
>
> i am running pulse on top of jack like this:
> http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
Len, thanks for trying to help me out - appreciated. But I am more
confused than before.
That is the hardest way to do it.
to do what?
qjackctl expects (as installed) to use jackdbus.
i have no jackdbus package in my apt sources available, what's that?
If you wish to use qjackctl with jackd you have to
turn dbus off in
the qjackctl settings. However, if jackd is started externally and
not from qjackctl you will still not be able to stop jackd.
with dbus turned on or off I have the same symptoms: that changes in
jackctl have no effect.
The only reason to do things this way is that you are
using jackd1,
if you are using jackd2,
jack2 is running
and you have dbus running in the session anyway, then
run
jackdbus.
$ 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
$ jackdbus auto
?
If you wish to run it from the command line use
jack_control start.
If you start it with qjackctl first with the settings you want,
that will be enough, other wise you will have to learn how to set
parameters with jack_control. There is no man page so try
jack_control --help
I wish that the settings in jackctl will have effect.
m.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlPoCe4ACgkQ3EB7kzgMM6I34QCfeqdpIIoQXgkBgsVC4LxN9O9V
Y34AniR3NbXfQ5qrA1i6cUk+mvqPLcD9
=uG4G
-----END PGP SIGNATURE-----
9:46 p.m.
On Mon, 11 Aug 2014, Max wrote:
It is a part of jackd2. Normally if you have jackd2 you also have
jackdbus.
Then, if you use qjackctl to start jack first thing in the session before
you run anything else or start jackd through a script. Then whatever
device you have set up should get picked up by jackdbus. If you run
something that needs jack first, chances are it will start jackd for you
and once it is running, qjackctl has no control over it and can not stop
and restart it. My personal feeling is that debian/ubuntu etc. should
package jackd2 and jackdbus seperate so jackd is not available in a
jackdbus system to cause problems. A script that takes the same
commandline as jackd and then calls jack_control with the right parameters
could be included instead.
Using jackdbus, and installing pulseaudio-module-jack, should besides
installing module-jack-sink and module-jack-source also install
module-jackdbus-detect which will auto-load the other two modules for you
when jackdbus is detected as running.
Personally, I have a script like:
----------autojack----------8<---------
#! /bin/bash
# start jack and midi
DELAY=1
DRIVER=alsa
DEV=hw:0
RATE=48000
FRAME=2048
PERIOD=2
#sleep $DELAY
jack_control ds $DRIVER dps device $DEV dps rate $RATE dps period $FRAME \
dps nperiods $PERIOD start
sleep $DELAY
a2jmidid -e &
sleep $DELAY
sleep $DELAY
pulseaudio -k
----------------------------8<------------------
The last line restarts pulseaudio because upstart seems to think it has to
start pulse first :P And I don't want my system too far off stock because
I try to help those with a stock system. This gets started by:
~/.config/autostart/AutoJack.desktop
But I could have put it in /etc/xdg/autostart for system wide use.
---------AutoJack.desktop-------8<--------------
[Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=AutoJack
Comment=Jackdbus starter
Exec=autojack
StartupNotify=false
Terminal=false
Hidden=false
-------------------------------8<---------------
jack_lsp shows:
system:capture_1
system:capture_2
... (the rest of my system listing skipped)
system:playback_9
system:playback_10
PulseAudio JACK Sink:front-left
PulseAudio JACK Sink:front-right
PulseAudio JACK Source:front-left
PulseAudio JACK Source:front-right
a2j:Midi Through [14] (capture): Midi Through Port-0
a2j:Midi Through [14] (playback): Midi Through Port-0
a2j:Ensoniq AudioPCI [16] (capture): ES1370
a2j:Ensoniq AudioPCI [16] (playback): ES1370
qjackctl is configured for the same card and start settings, the options
tab has Execute script on startup: pulseaudio -k and Execute script after
startup: a2jmidid -e &, but really I never use qjackctl to start and stop
jackd as it runs from session start to stop. I use qjackctl for the
patchbay (connections) and logging. In the Misc. tab I have qjackctl set
for Enable D-Bus interface and I have Stop JACK audio server on
application exit unchecked so that stopping qjackctl does not stop
jackdbus.
I use this project:
http://www.ovenwerks.net/software/index.html
To control jack latency on the fly and to disconnect pulseaudio if I think
it might interfere with what I am doing. It also sets the CPU governor and
allows me to stop cron so there is no sudden net/disk activity in the
middle of a take.
On 08/10/2014 03:53 AM, Len Ovens wrote:
Pulse on jack.
On Sat, 9 Aug 2014, Max wrote:
> selecting a different interface in qjackctl has no effect. i
> can't use the external soundcard, because jack stays always with
> the internal one. any ideas what causes this symptom?
>
> i am running pulse on top of jack like this:
> http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
Len, thanks for trying to help me out - appreciated. But I am more
confused than before.
That is the hardest way to do it.
to do what? qjackctl
expects (as installed) to use jackdbus.
i have no jackdbus package in my apt sources available, what's that? From pavucontrol, on the Configuration tab, I set any
audio card profiles
to "Off". I probably should just set pulse not to use
the alsa-sink/sourse
modules, but so far I have been too lazy to do so.
In my opinion this is the proper way to get jack and pulse to play nice.
If one is using jackd1 Then everything changes because it is not dbus
controlable (at least out of the box, I hear there is a patch)
Then the link you have above can be used and qjackctl can have the D-Bus
interface turned off. However, there is more work to turn the pulse-jack
bridge off and on on the fly as there are two modules to (un)load. Also,
jackd has to be started with qjackctl if you wish to use that as the
controler. Unless you want to add:
Execute script on Shutdown: killall -9 jackd
To your qjackctl setup.
I can not recommend jackd2 or jackd1 as one being better than the other. I
think there are situations where one or the other shines. However, in the
case where pulse and dbus are already in use, I would choose jackdbus as
the most compatible version of jack to use. I do not know if jackd can
safely be removed/-x/renamed or not when using jackdbus... that is
something I should experiment with though :)
--
Len Ovens
www.ovenwerks.net
12 Aug
12 Aug
4:34 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/12/2014 04:41 AM, Len Ovens wrote:
On Mon, 11 Aug 2014, Max wrote:
Would you suggest that your method is better and should be the
canonical way to do pulse on jack? If so, shall we write up an
alternative WalkThrough on the jackoudio wiki that helps people
setting that up?
Is that software you use (wrote?) something you want to share? It
looks very useful.
m.
On 08/10/2014 03:53 AM, Len Ovens wrote:
Pulse on jack. On Sat, 9 Aug 2014, Max wrote:
> selecting a different interface in qjackctl has no effect.
> i can't use the external soundcard, because jack stays always
> with the internal one. any ideas what causes this symptom?
>
> i am running pulse on top of jack like this:
> http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
Len, thanks for trying to help me out - appreciated. But I am
more confused than before.
That is the hardest way to do it.
to do what? -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlPpfSwACgkQ3EB7kzgMM6Lz8ACeLmpoVz9WLSVmEm5jJI83HvUH
wLsAn1NLHwwB2uiXPZHne7ZH9/+zIwXH
=Bs1s
-----END PGP SIGNATURE-----
4:57 a.m.
On Tue, 12 Aug 2014, Max wrote:
On 08/12/2014 04:41 AM, Len Ovens wrote:
I certainly think using jackdbus when dbus is present is the better way,
Not so sure (yet) if my exact setup is best. It has only been in use for a
few months. It is also not quite finished. I need to package it at least
for debian which I am reasonably familiar with and perhaps the old tar
ball method too. I have not done a good look at the depends yet :) and
would like to add a config gui for autojack. It is written in pyqt and
shell script.
On Mon, 11 Aug 2014, Max wrote:
Would you suggest that your method is better and should be the
canonical way to do pulse on jack? If so, shall we write up an
alternative WalkThrough on the jackoudio wiki that helps people
setting that up? On 08/10/2014 03:53 AM, Len Ovens wrote:
Pulse on jack. On Sat, 9 Aug 2014, Max wrote:
> selecting a different interface in qjackctl has no effect.
> i can't use the external soundcard, because jack stays always
> with the internal one. any ideas what causes this symptom?
>
> i am running pulse on top of jack like this:
> http://trac.jackaudio.org/wiki/WalkThrough/User/PulseOnJack
Len, thanks for trying to help me out - appreciated. But I am
more confused than before.
That is the hardest way to do it.
to do what? Is that software you use (wrote?) something you want
to share? It
looks very useful.
In due time. I thought vacation would give me some time to finish it out
so it was distributable.... alas, I have not had any time to myself, but
camping was fun too :)
--
Len Ovens
www.ovenwerks.net
18 Aug
18 Aug
7:03 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I figured it out.
purge qjackctl
install Cadence from the kxstudio repository.
That qjackctl is oblivious about that is has actually no control over
jack any more puzzles me. I will not miss it.
On 08/12/2014 11:52 AM, Len Ovens wrote:
On Tue, 12 Aug 2014, Max wrote:
> On 08/12/2014 04:41 AM, Len Ovens wrote:
>> On Mon, 11 Aug 2014, Max wrote:
>>> On 08/10/2014 03:53 AM, Len Ovens wrote:
>>>> On Sat, 9 Aug 2014, Max wrote:
>>>>
>>>>> selecting a different interface in qjackctl has no
>>>>> effect. i can't use the external soundcard, because jack
>>>>> stays always with the internal one. any ideas what causes
>>>>> this symptom?
>>>>>
>>>>> i am running pulse on top of jack like this:
-----BEGIN PGP
SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlPxiSQACgkQ3EB7kzgMM6JIaACfYYkXj/PtqXF3ggcvCRVM7zXL
PysAnRNHvUYDKkAkxiyLyJhebXBuEfSa
=3Hnl
-----END PGP SIGNATURE-----
8:57 a.m.
On Mon, 18 Aug 2014, Max wrote:
I figured it out.
purge qjackctl
install Cadence from the kxstudio repository.
That qjackctl is oblivious about that is has actually no control over
jack any more puzzles me. I will not miss it.
I found that chmod -x jackd worked better. The debian/ubuntu jackd2
package is broken: it ships both jackd and jackdbus in the same package.
The package should be split.
--
Len Ovens
www.ovenwerks.net
3795
days inactive
3805
days old
linux-audio-user@lists.linuxaudio.org
9 comments
4 participants
participants (4)
-
Len Ovens -
Max -
Ralf Mardorf -
Tim E. Real