Pulseaudio configuration
Loads the zeroconf publish code that will publish tunnel sources and sinks on the network through zeroconf.-dump-conf Load the daemon configuration file nf (see below), parse remaining configuration options on the command line and dump the resulting daemonĬonfiguration, in a format that is compatible with nf. Use: pactl load-module module-zeroconf-publish
Loads the zeroconf discover code that will create tunnel sources and sinks for all published devices.
Use: pactl load-module module-zeroconf-discover The remote server needs to be listening on tcp with the module-native-protocol-tcp module-zeroconf-discover Capturing audio from the source will capture the audio from the remote PulseAudio/PipeWire server at. Use: pactl load-module module-tunnel-source server=tcp: The remote server needs to be listening on tcp with the module-native-protocol-tcp module-tunnel-source Playing audio on the sink will play the audio on the remote PulseAudio/PipeWire server at. Use: pactl load-module module-tunnel-sink server=tcp: Applications such a simple protocol player can play these streams. Connected clients receive a stream of raw samples. This loads a new server listening on the given port and IP for new connections. Use: pactl load-module module-simple-protocol-tcp record=true] You can also load a sink that will forward all audio to this remote server with: pactl load-module module-tunnel-sink server=tcp: module-simple-protocol-tcp To kill all connections and stop the server. You can unload the module by id or name: pactl unload-module module-native-protocol-tcp Fill with the IP address of the host running the server and with the port. You can then use PULSE_SERVER=tcp: pactl info This loads a new server listening on the given port and IP. Use: pactl load-module module-native-protocol-tcp The only module that is not yet implemented is the RTP network streaming module (but the ROC module is an alternative). The PipeWire PulseAudio server has fairly complete network support.
#Pulseaudio configuration how to#
Please refer to the migrating guide for more information about the supported modules and how to migrate. The PulseAudio compatible server is implemented by the libpipewire-module-protocol-pulse module, which should be loaded by the config file in the context.modules section: Server Configuration context.modules =. You can copy and edit the file to /etc/pipewire/ or ~/.config/pipewire/nf. The pipewire-pulse module has a configuration file template located in /usr/share/pipewire/nf. We refer to PulseAudio Migration for more information for how to use the replacement PulseAudio server. We recommend the following tools: ToolĬommand line introspection of PulseAudio server and configuration The pipewire-pulse server implements a sample cache that is currently not otherwise available in PipeWireĪlmost all of the native PulseAudio tools should continue to work. Check the session manager configuration guide. It allows clients linked to the PulseAudio client library to talk directly to pipewire-pulse, which then creates streams to PipeWire.Īll of the policy and device configuration is still managed by the session manager.