Talk:Pipewire

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 02:24, 27 July 2024 (UTC)
:: Your reply ~~~~

Example config

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

Instead of:

FILE /etc/pipewire/pipewire.conf

#
# 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)
#
exec /usr/bin/pipewire-pulse

Mine looks like:

FILE /etc/pipewire/pipewire.conf

exec = {
    ## <program-name> = { [args = "<arguments>"] }
    #
    # 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)? — The preceding unsigned comment was added by Gemiller (talk • contribs)

-- The config format change between 0.3.18 and 0.3.20. Also options for systemd and other are provided

Naib (talk) 12:03, 7 February 2021 (UTC)