News for hackers. Stuff that matters.

A comment on PipeWire and fixing the Linux Video Capture stack. Parent comment

Re:PipeWire and fixing the Linux Video Capture stack by zibzab on Sunday October 03, 2021 @04:57AM (#28735618)
What do I need to remove to get this working without any conflicts?

You mentioned qjackctl, is there a reason I must keep using that instead of having everything defaulted to PW pipe

[ Parent | on HN ]
Re:PipeWire and fixing the Linux Video Capture stack by WastingMyTime89 on Sunday October 03, 2021 @06:39AM (#28736070)
Everything uses PW pipe.

Pipewire implements the API of all the system it replaces. So you can keep using Jack routing tools while everything is actually using Pipewire.

[ Parent | on HN ]
Re:PipeWire and fixing the Linux Video Capture stack by nyanpasu64 on Sunday October 03, 2021 @05:22AM (#28735721)
Does `systemctl --user disable --now pulseaudio` help? Also you can use `enable --now` to enable and start at the same time.
[ Parent | on HN ]
Re:PipeWire and fixing the Linux Video Capture stack by alias_neo on Sunday October 03, 2021 @06:55AM (#28736156)
Don't forget to mask pulseaudio, just disabling it isn't enough.
[ Parent | on HN ]
Re:PipeWire and fixing the Linux Video Capture stack by kzrdude on Sunday October 03, 2021 @11:01AM (#28737713)
The difference seems to be:

disabled - the service is not started automatically

masked - the service can't be started at all, even explicitly requested by user or app

[ Parent | on HN ]
Re:PipeWire and fixing the Linux Video Capture stack by alias_neo on Sunday October 03, 2021 @11:34AM (#28737974)
On Ubuntu at least, I had to mask it otherwise pulseaudio was started again on reboot despite being disabled.
[ Parent | on HN ]