Update doc/ from master branch. tutorial: fix s16 scale and add some docs doc: add 'Configuration' page doc: disable deprecated list doc: fix some doxygen warnings doc: put new pulse modules to right place doc: filter some constructs that confuse doxygen doc: Fix typo 'statis' -> 'static' doc: include pipewire-pulse modules explanations also on man page doc: add pw-v4l2.1 and spa-*.1 doc: add pw-reserve.1 doc: internals/access: update documentation vs current state
2.1 KiB
\page page_config Configuration
One of the design goals of PipeWire is to be able to closely control and configure all aspects of the processing graph.
A fully configured PipeWire setup runs various pieces, each with their configuration options and files:
-
pipewire: The PipeWire main daemon that runs and coordinates the processing.
-
pipewire-pulse: The PipeWire PulseAudio replacement server. It also configures the properties of the PulseAudio clients connecting to it.
-
wireplumber: Most configuration of devices is performed by the session manager. It typically loads ALSA and other devices and configures the profiles, port volumes and more. The session manager also configures new clients and links them to the targets, as configured in the session manager policy.
-
PipeWire clients: Each native PipeWire client also loads a configuration file. Emulated JACK client also have separate configuration.
Configuration Settings
Configuration of daemons:
- PipeWire daemon configuration
- WirePlumber daemon configuration
- PipeWire PulseAudio daemon configuration
Configuration of devices:
Configuration for client applications, either connecting via the native PipeWire interface, or the emulated ALSA, JACK, or PulseAudio interfaces: