I just did it and it's workingstevethefiddle wrote:That's what I've been trying to get working on my virtual test machine - not the best test bed for this kind of thing - no joy so far. I'll start a new topic about it if I get it to work.bgravato wrote:it seems that there's a module to send pulseaudio output to jack...
You need to install the package pulseaudio-module-jack and then you need to manually edit some conf file to load the modules... (in my opinion this should be done by the postinst scripts on the package, or at least there should be some note about it in the README file) Anyway you can do this by adding the following lines to /etc/pulse/default.pa
Code: Select all
load-module module-jack-sink
load-module module-jack-source
Also you should start pulseaudio after jackd.
Sometimes I wish the opposite... if for some reason I need to restart jackd I'll have to close and restart the apps which create persistent ports at startup only... apps that only create/connect the ports when I hit play I don't need to restart themstevethefiddle wrote:I use jack on my desktop machine for that same reason, but find the versatility of PulseAudio indispensable on my laptop.bgravato wrote:for what I do and my needs I think jack suits me better and is more powerful...
I had trouble getting Audacity to work properly with Jack for years, but now it works great - just wish we had persistent ports rather than ones that disappear every time you click stop.
You can try to work around that using the patchbay in jack control