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) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org