On Sun, May 24, 2009 at 1:18 AM, Lennart Poettering <lennart at poettering.net>wrote: > On Sun, 24.05.09 00:57, rosea grammostola (rosea.grammostola at gmail.com) > wrote: > > > Ok so not running both at the same time. But how do you stop pulseaudio > from > > running and restart it after you used JACK? > > Newer PA and JACK versions cooperate in this way > automatically. If you fire up JACK PA will go out of the way for that > device. And after JACK is done PA takes the device back. JACK is king > and PA will comply. > > In older versions you can use a tool like "pasuspender". It will > suspend PA's access to the audio devices temporarily as long as child > process is running. If you make that child process JACK you have a > neat way to make JACK and PA not fight for device access. > > A more brutal way is to stop PA with "pulseaudio -k" before you run > JACK and then start PA with "pulseaudio -D" afterwards. But that > probably won't work that nicely since PA is configured to autospawn in > most cases these days -- which you can disable however by editing > client.conf. > > Ok I start qjackctl or jackd with pasuspender qjackctl BTW in Debian you have the package: pulseaudio-module-jack http://packages.debian.org/nl/lenny/pulseaudio-module-jack What is the aim of that package and how to use it (Ubuntu doesn t seems to have that package)? \r -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20090525/fb3cc86a/attachment.htm>
