Talk:PipeWire

Revert edit about considering two options to launch PipeWire

Dear John3-16, This edit is being reverted because Pipewire user service is the recommended method going forward and the pipewire-launcher will be removed at some point. When a recommended method is available, listing them on par with bespoke methods will confuse new users. We can always list such methods under a heading like Custom configuration. Our installation page was a perfect example for listing a lot of options, but frustrating for new users. Thanks for you contributions to Wiki and it is highly appreciated and i hope you understand and agree with the reasoning for this revert. -Prabuanand (talk) 03:49, 22 July 2025 (UTC)

Agreed that Pipewire user service is the recommended method; and that the pipewire-launcher method is expected to be sunsetted; this was respected in my edit. The Note was preserved which stated that the second option would be deprecated. My impression is that enough readers may not stop and realize that these are mutually exclusive methods, if they implement the passages in this guide one after another in a rush.

I concur with you too that other, bespoke methods would be superfluous on the wiki; their existence was only being acknowledged in the edit's Summary. Thank you for your extensive wiki help also; please continue!

John3-16 (talk) 04:26, 22 July 2025 (UTC)

Thanks for you reply. Understood the reasoning and added the suggested changes. - Prabuanand (talk) 05:22, 22 July 2025 (UTC)

Is rtkit still recommended for Realtime scheduling?

 Done

rtkit's repository hasn't been updated since 2020-04-05 and the open issues seem to list some problems. Gentoo PipeWire#Audio Groups implies rtkit is the fallback and pipewire group is the recommeneded path. /etc/security/limits.d/25-pw-rlimits.conf (which is shipped from upstream) also seems to imply that the pipewire group is preferred. --Encode (talk) 07:48, 17 November 2025 (UTC)

Made changes to wiki section. Please feel to make necessary changes to fix any remaining inaccuracies, and to remove the Accuracy template. Thanks. -Prabuanand (talk) 10:54, 17 November 2025 (UTC)

I changed the wording slightly and removed ‘glitch-free’ because I feel that is too strong. Everything looks good. --Encode (talk) 20:13, 18 November 2025 (UTC)