Mailinglist Archive: opensuse-factory (949 mails)
| < Previous | Next > |
Re: [opensuse-factory] jack and sound
- From: Takashi Iwai <tiwai@xxxxxxx>
- Date: Sat, 29 Aug 2009 10:25:21 +0200
- Message-id: <s5hprafkowe.wl%tiwai@xxxxxxx>
At Sat, 29 Aug 2009 02:39:36 +0100,
Sid Boyce wrote:
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
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Sid Boyce wrote:
On 26/08/09 08:39, Michal Seben wrote:
Sid Boyce wrote:pulseaudio is always running and then I start jackd and the jack app.
On 26/08/09 07:25, Takashi Iwai wrote:If your jackd deamon is running
At Tue, 25 Aug 2009 22:47:25 +0100,OK.
Sid Boyce wrote:
If jackd is running, all apps, including those that are jack aware likeIt blocks all others. Also jackd would be blocked if another is
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?
accessing the sound device. JACK requires the exclusive access
usually.
Problem is "palay xxx.wav" outputs no sound and neither does jack'sI found an old Fedora post that recommended the following ~/jack.paThis allows PA-aware apps routed over jackd.
script, I enabled those modules in default.pa and restarted pulseaudio,
no change.
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
when you kill jackd ( in your case, pulseaudio on top of jackd) I
example utils. Killing jackd, paplay works.
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/*
you could also check which "input device" is used by pulseaudio :Takashi
Regards
Sid.
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)
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
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |