User talk:Psykose

From Alpine Linux
Jump to navigation Jump to search

PipeWire

Thanks for updating PipeWire article! However, after removing the two lines in my config file, as you updated, my Bluetooth headset stopped working. Adding them back fixed the issue.

    { path = "wireplumber"  args = "" }
    { path = "/usr/bin/pipewire" args = "-c pipewire-pulse.conf" }

Should we add them back?

La9 (talk) 11:00, 24 July 2022 (UTC)

those get started if you use /usr/libexec/pipewire-launcher - and don't otherwise. the two methods are either:

- use pipewire-launcher - add those lines to the config and use only `pipewire`

the issue with the latter is that if they are in the config, and then someone uses the launcher, it breaks because multiple of them get started. so, everyone is 'supposed' to use the launcher.

if you know what you're doing you can of course edit everything as you wish, but the issue with using the config is pipewire drops all its defaults if a config exists- if someone copies /usr/share/pipewire/pipewire.conf to /etc/pipewire/ 6 months ago, then adds those lines, then currently they would have missed all the new changes to the default config, because /usr/share/pipewire/pipewire.conf (with all the new changes to it) would have been ignored this whole time. i've had audio break because of that :) it's a little easier to start things via wrapper and not touch the configs, in that case.