If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system? I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change. #!/usr/bin/pulseaudio -nF # load-module module-jack-sink load-module module-jack-source
load-module module-native-protocol-unix load-module module-volume-restore load-module module-default-device-restore load-module module-rescue-streams load-module module-suspend-on-idle .ifexists module-gconf.so .nofail load-module module-gconf .fail .endif .ifexists module-x11-publish.so .nofail load-module module-x11-publish .fail .endif
Regards Sid.
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system?
It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change.
This allows PA-aware apps routed over jackd.
Takashi
On 26/08/09 07:25, Takashi Iwai wrote:
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system?
It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
OK.
I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change.
This allows PA-aware apps routed over jackd.
Problem is "palay xxx.wav" outputs no sound and neither does jack's example utils. Killing jackd, paplay works.
Takashi
Regards Sid.
Sid Boyce wrote:
On 26/08/09 07:25, Takashi Iwai wrote:
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system?
It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
OK.
I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change.
This allows PA-aware apps routed over jackd.
Problem is "palay xxx.wav" outputs no sound and neither does jack's
If your jackd deamon is running try : killall pulseaudio pulseaudio -nF ~/jack.pa --log-target=syslog
and if it doesn't work check messages what is wrong: cat /var/log/messages | grep pulseaudio
example utils. Killing jackd, paplay works.
when you kill jackd ( in your case, pulseaudio on top of jackd) I suppose pulseaudio connect directly to sound device so it doesn't go through the jackd if you want check which sound server is using your sound device try : fuser -v /dev/snd/*
Takashi
Regards Sid.
you could also check which "input device" is used by pulseaudio : strart pavucontrol and go to "input device" tab, you should see something like "jack source" - I suppose you started pulseaudio on top of jackd (ideal solution when you want start pulseaudio apps and jackd apps together)
On 26/08/09 08:39, Michal Seben wrote:
Sid Boyce wrote:
On 26/08/09 07:25, Takashi Iwai wrote:
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system?
It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
OK.
I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change.
This allows PA-aware apps routed over jackd.
Problem is "palay xxx.wav" outputs no sound and neither does jack's
If your jackd deamon is running try : killall pulseaudio pulseaudio -nF ~/jack.pa --log-target=syslog
and if it doesn't work check messages what is wrong: cat /var/log/messages | grep pulseaudio
example utils. Killing jackd, paplay works.
when you kill jackd ( in your case, pulseaudio on top of jackd) I suppose pulseaudio connect directly to sound device so it doesn't go through the jackd if you want check which sound server is using your sound device try : fuser -v /dev/snd/*
Takashi
Regards Sid.
you could also check which "input device" is used by pulseaudio : strart pavucontrol and go to "input device" tab, you should see something like "jack source" - I suppose you started pulseaudio on top of jackd (ideal solution when you want start pulseaudio apps and jackd apps together)
pulseaudio is always running and then I start jackd and the jack app.
From /var/log/messages:-
I don't see any reference to jack in pavucontrol. Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:03 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:10 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:45:01 slipstream gnome-keyring-daemon[1197]: couldn't connect to dbus session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed. Aug 27 15:46:49 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy <<<<======== Aug 27 15:47:12 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 4.00 ms Aug 27 15:47:30 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 8.00 ms Aug 27 15:47:32 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 16.00 ms Aug 27 15:47:42 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 26.00 ms Aug 27 15:48:20 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:02 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:49:27 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:49:41 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:52:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:52:50 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:53:32 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:53:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:54:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 16.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 46.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 36.00 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 35.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:56:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 46.00 ms Aug 27 15:59:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms # ps fax|grep jack 1553 pts/2 S+ 0:00 | _ grep jack 1253 ? Ssl 0:03 /usr/bin/jackd -d alsa -dhw:0 -r48000 -p1024 -n2 slipstream:/home/lancelot/ftp/aug09 # fuser -v /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: root 1253 F.... jackd lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC1: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC2: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/pcmC0D0c: root 1253 F...m jackd lancelot 5866 F...m pulseaudio /dev/snd/pcmC0D0p: root 1253 F...m jackd /dev/snd/pcmC1D0c: lancelot 5866 F...m pulseaudio /dev/snd/pcmC1D0p: lancelot 5866 F...m pulseaudio /dev/snd/pcmC2D0c: lancelot 5866 F...m pulseaudio
No audio however. Regards Sid.
At Sat, 29 Aug 2009 02:39:36 +0100, Sid Boyce wrote:
On 26/08/09 08:39, Michal Seben wrote:
Sid Boyce wrote:
On 26/08/09 07:25, Takashi Iwai wrote:
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system?
It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
OK.
I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change.
This allows PA-aware apps routed over jackd.
Problem is "palay xxx.wav" outputs no sound and neither does jack's
If your jackd deamon is running try : killall pulseaudio pulseaudio -nF ~/jack.pa --log-target=syslog
and if it doesn't work check messages what is wrong: cat /var/log/messages | grep pulseaudio
example utils. Killing jackd, paplay works.
when you kill jackd ( in your case, pulseaudio on top of jackd) I suppose pulseaudio connect directly to sound device so it doesn't go through the jackd if you want check which sound server is using your sound device try : fuser -v /dev/snd/*
Takashi
Regards Sid.
you could also check which "input device" is used by pulseaudio : strart pavucontrol and go to "input device" tab, you should see something like "jack source" - I suppose you started pulseaudio on top of jackd (ideal solution when you want start pulseaudio apps and jackd apps together)
pulseaudio is always running and then I start jackd and the jack app.
From /var/log/messages:-
I don't see any reference to jack in pavucontrol. Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:03 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:10 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:45:01 slipstream gnome-keyring-daemon[1197]: couldn't connect to dbus session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed. Aug 27 15:46:49 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy <<<<======== Aug 27 15:47:12 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 4.00 ms Aug 27 15:47:30 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 8.00 ms Aug 27 15:47:32 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 16.00 ms Aug 27 15:47:42 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 26.00 ms Aug 27 15:48:20 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:02 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:49:27 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:49:41 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:52:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:52:50 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:53:32 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:53:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:54:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 16.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 46.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 36.00 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 35.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:56:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 46.00 ms Aug 27 15:59:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms # ps fax|grep jack 1553 pts/2 S+ 0:00 | _ grep jack 1253 ? Ssl 0:03 /usr/bin/jackd -d alsa -dhw:0 -r48000 -p1024 -n2 slipstream:/home/lancelot/ftp/aug09 # fuser -v /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: root 1253 F.... jackd lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC1: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC2: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/pcmC0D0c: root 1253 F...m jackd lancelot 5866 F...m pulseaudio /dev/snd/pcmC0D0p: root 1253 F...m jackd /dev/snd/pcmC1D0c: lancelot 5866 F...m pulseaudio /dev/snd/pcmC1D0p: lancelot 5866 F...m pulseaudio /dev/snd/pcmC2D0c: lancelot 5866 F...m pulseaudio
No audio however.
And, do you see the jack I/O entries in pulseaudio (e.g. in pavucontrol)? If not, it means that jack module of puluseaudio doesn't work / run on your system properly.
But, the very first question is why you need jackd, and why you need pulseaudio together. When jack is running, it is a king. All others have to obey. pulseaudio has a module that serves as a jack client, and this is the config file your took from Fedora. If this config isn't given properly, of course they start a war and try to conquer with each other.
Takashi
On 29/08/09 09:25, Takashi Iwai wrote:
At Sat, 29 Aug 2009 02:39:36 +0100, Sid Boyce wrote:
On 26/08/09 08:39, Michal Seben wrote:
Sid Boyce wrote:
On 26/08/09 07:25, Takashi Iwai wrote:
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware like audacity just don't do any sound stuff, even the example jack utils don't output sound. Is my understanding that jack should not stop non-jack aware apps from using the sound system?
It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
OK.
I found an old Fedora post that recommended the following ~/jack.pa script, I enabled those modules in default.pa and restarted pulseaudio, no change.
This allows PA-aware apps routed over jackd.
Problem is "palay xxx.wav" outputs no sound and neither does jack's
If your jackd deamon is running try : killall pulseaudio pulseaudio -nF ~/jack.pa --log-target=syslog
and if it doesn't work check messages what is wrong: cat /var/log/messages | grep pulseaudio
example utils. Killing jackd, paplay works.
when you kill jackd ( in your case, pulseaudio on top of jackd) I suppose pulseaudio connect directly to sound device so it doesn't go through the jackd if you want check which sound server is using your sound device try : fuser -v /dev/snd/*
Takashi
Regards Sid.
you could also check which "input device" is used by pulseaudio : strart pavucontrol and go to "input device" tab, you should see something like "jack source" - I suppose you started pulseaudio on top of jackd (ideal solution when you want start pulseaudio apps and jackd apps together)
pulseaudio is always running and then I start jackd and the jack app.
From /var/log/messages:-
I don't see any reference to jack in pavucontrol. Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:03 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:10 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:45:01 slipstream gnome-keyring-daemon[1197]: couldn't connect to dbus session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed. Aug 27 15:46:49 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy <<<<======== Aug 27 15:47:12 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 4.00 ms Aug 27 15:47:30 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 8.00 ms Aug 27 15:47:32 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 16.00 ms Aug 27 15:47:42 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 26.00 ms Aug 27 15:48:20 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:02 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:49:27 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:49:41 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:52:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:52:50 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:53:32 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:53:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:54:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 16.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 46.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 36.00 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 35.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:56:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 46.00 ms Aug 27 15:59:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms # ps fax|grep jack 1553 pts/2 S+ 0:00 | _ grep jack 1253 ? Ssl 0:03 /usr/bin/jackd -d alsa -dhw:0 -r48000 -p1024 -n2 slipstream:/home/lancelot/ftp/aug09 # fuser -v /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: root 1253 F.... jackd lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC1: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC2: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/pcmC0D0c: root 1253 F...m jackd lancelot 5866 F...m pulseaudio /dev/snd/pcmC0D0p: root 1253 F...m jackd /dev/snd/pcmC1D0c: lancelot 5866 F...m pulseaudio /dev/snd/pcmC1D0p: lancelot 5866 F...m pulseaudio /dev/snd/pcmC2D0c: lancelot 5866 F...m pulseaudio
No audio however.
And, do you see the jack I/O entries in pulseaudio (e.g. in pavucontrol)? If not, it means that jack module of puluseaudio doesn't work / run on your system properly.
Nothing in pavucontrol with reference to jack.
But, the very first question is why you need jackd, and why you need pulseaudio together. When jack is running, it is a king. All others have to obey. pulseaudio has a module that serves as a jack client, and this is the config file your took from Fedora. If this config isn't given properly, of course they start a war and try to conquer with each other.
Takashi
The SDR application (currently not running)needs jackd, but pulseaudio seems to be an absolute openSUSE "must run" requirement. A "kill -HUP" will restart one pulseaudio daemon, a "kill -9" restarts with many along with one zombie, presumably as a result of the -9.
slipstream:/home/lancelot/ftp/aug09 # ps fax|grep pulse 5866 ? Ssl 0:50 /usr/bin/pulseaudio --start --log-target=syslog 5873 ? S 0:00 _ /usr/lib/pulse/gconf-helper 26825 pts/1 S+ 0:00 | _ grep pulse
slipstream:/home/lancelot/ftp/aug09 # kill -9 5866 slipstream:/home/lancelot/ftp/aug09 # ps fax|grep pulse 26833 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26845 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26834 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26828 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26826 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26829 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26827 ? Sl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26831 ? S 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26838 ? Rsl 0:00 | _ /usr/bin/pulseaudio --start --log-target=syslog 26857 ? Z 0:00 | _ [pulseaudio] <defunct> 26867 ? S 0:00 | _ /usr/lib/pulse/gconf-helper 26853 ? Sl 0:00 _ /usr/bin/pulseaudio --start --log-target=syslog 26870 pts/1 S+ 0:00 | _ grep pulse 26847 ? Sl 0:00 _ /usr/bin/pulseaudio --start --log-target=syslog 26830 ? Sl 0:00 _ /usr/bin/pulseaudio --start --log-target=syslog 26832 ? Sl 0:00 _ /usr/bin/pulseaudio --start --log-target=syslog 26849 ? Sl 0:00 _ /usr/bin/pulseaudio --start --log-target=syslog 26850 ? Sl 0:00 _ /usr/bin/pulseaudio --start --log-target=syslog slipstream:/home/lancelot/ftp/aug09 # Regards Sid.
At Sat, 29 Aug 2009 16:47:59 +0100, Sid Boyce wrote:
On 29/08/09 09:25, Takashi Iwai wrote:
At Sat, 29 Aug 2009 02:39:36 +0100, Sid Boyce wrote:
On 26/08/09 08:39, Michal Seben wrote:
Sid Boyce wrote:
On 26/08/09 07:25, Takashi Iwai wrote:
At Tue, 25 Aug 2009 22:47:25 +0100, Sid Boyce wrote:
> If jackd is running, all apps, including those that are jack aware like > audacity just don't do any sound stuff, even the example jack utils > don't output sound. > Is my understanding that jack should not stop non-jack aware apps from > using the sound system? > It blocks all others. Also jackd would be blocked if another is accessing the sound device. JACK requires the exclusive access usually.
OK.
> I found an old Fedora post that recommended the following ~/jack.pa > script, I enabled those modules in default.pa and restarted pulseaudio, > no change. > This allows PA-aware apps routed over jackd.
Problem is "palay xxx.wav" outputs no sound and neither does jack's
If your jackd deamon is running try : killall pulseaudio pulseaudio -nF ~/jack.pa --log-target=syslog
and if it doesn't work check messages what is wrong: cat /var/log/messages | grep pulseaudio
example utils. Killing jackd, paplay works.
when you kill jackd ( in your case, pulseaudio on top of jackd) I suppose pulseaudio connect directly to sound device so it doesn't go through the jackd if you want check which sound server is using your sound device try : fuser -v /dev/snd/*
Takashi
Regards Sid.
you could also check which "input device" is used by pulseaudio : strart pavucontrol and go to "input device" tab, you should see something like "jack source" - I suppose you started pulseaudio on top of jackd (ideal solution when you want start pulseaudio apps and jackd apps together)
pulseaudio is always running and then I start jackd and the jack app.
From /var/log/messages:-
I don't see any reference to jack in pavucontrol. Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:43:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 1.00 ms Aug 27 15:43:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:03 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 2.00 ms Aug 27 15:44:10 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:45:01 slipstream gnome-keyring-daemon[1197]: couldn't connect to dbus session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed. Aug 27 15:46:49 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy <<<<======== Aug 27 15:47:12 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 4.00 ms Aug 27 15:47:30 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 8.00 ms Aug 27 15:47:32 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 16.00 ms Aug 27 15:47:42 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 26.00 ms Aug 27 15:48:20 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:02 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:49:27 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:49:41 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 2.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:49:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 4.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:50:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:51:12 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:52:29 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:52:50 slipstream pulseaudio[5866]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy Aug 27 15:53:32 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 8.00 ms Aug 27 15:53:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 16.00 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 15.99 ms Aug 27 15:53:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:54:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 26.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 16.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 46.00 ms Aug 27 15:55:13 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 36.00 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-sink.c: Increasing wakeup watermark to 25.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 35.99 ms Aug 27 15:55:43 slipstream pulseaudio[5866]: alsa-source.c: Increasing minimal latency to 36.00 ms Aug 27 15:56:10 slipstream pulseaudio[5866]: alsa-sink.c: Increasing minimal latency to 46.00 ms Aug 27 15:59:42 slipstream pulseaudio[5866]: alsa-source.c: Increasing wakeup watermark to 15.99 ms # ps fax|grep jack 1553 pts/2 S+ 0:00 | _ grep jack 1253 ? Ssl 0:03 /usr/bin/jackd -d alsa -dhw:0 -r48000 -p1024 -n2 slipstream:/home/lancelot/ftp/aug09 # fuser -v /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: root 1253 F.... jackd lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC1: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/controlC2: lancelot 5866 F.... pulseaudio lancelot 5918 F.... kmix /dev/snd/pcmC0D0c: root 1253 F...m jackd lancelot 5866 F...m pulseaudio /dev/snd/pcmC0D0p: root 1253 F...m jackd /dev/snd/pcmC1D0c: lancelot 5866 F...m pulseaudio /dev/snd/pcmC1D0p: lancelot 5866 F...m pulseaudio /dev/snd/pcmC2D0c: lancelot 5866 F...m pulseaudio
No audio however.
And, do you see the jack I/O entries in pulseaudio (e.g. in pavucontrol)? If not, it means that jack module of puluseaudio doesn't work / run on your system properly.
Nothing in pavucontrol with reference to jack.
Then it's the problem of your system.
But, the very first question is why you need jackd, and why you need pulseaudio together. When jack is running, it is a king. All others have to obey. pulseaudio has a module that serves as a jack client, and this is the config file your took from Fedora. If this config isn't given properly, of course they start a war and try to conquer with each other.
Takashi
The SDR application (currently not running)needs jackd, but pulseaudio seems to be an absolute openSUSE "must run" requirement.
Really? Doesn't "zypper rm pulseaudio" work?
Takashi
-
Michal Seben -
Sid Boyce -
Takashi Iwai