Talk:Pipewire

My stock Gentoo /etc/pipewire/pipewire.conf does not look like the one in here.

Instead of:

``` exec /usr/bin/pipewire-pulse ```
 * 1) You can optionally start the pulseaudio-server here as well
 * 2) but it better to start it as a systemd service.
 * 3) It can be interesting to start another daemon here that listens
 * 4) on another address with the -a option (eg. -a tcp:4713)
 * 1) on another address with the -a option (eg. -a tcp:4713)

Mine looks like: ``` exec = { ##  = { [args = " "] } #   # Execute the given program with arguments. #   # Start the session manager. Run the session manager with -h for # options. #   # The bluetooth module is disabled by default because it causes # conflicts with PulseAudio. If you disable PulseAudio or don't   # load its bluetooth module, you can enable it here with -e bluez5 #   "/usr/bin/pipewire-media-session" = { args = ""} #   # You can optionally start the pulseaudio-server here as well # but it better to start it as a systemd service. # It can be interesting to start another daemon here that listens # on another address with the -a option (eg. -a tcp:4713) #   #"/usr/bin/pipewire-pulse" = { "#args" = "-a tcp:4713" } } ```

Since most Gentoo installs avoid systemd(umb), why does it suggest using systemd(umber)?