.TH "libpipewire-modules" 7 "1.6.7" "PipeWire" \" -*- nroff -*-
.ad l
.nh
.SH NAME
libpipewire-modules \- PipeWire modules

.PP
.SH "DESCRIPTION"
.PP

.PP
A PipeWire module is effectively a PipeWire client running inside \fRpipewire(1)\fP which can host multiple modules\&. Usually modules are loaded when they are listed in the configuration files\&. For example the default configuration file loads several modules: 
.PP
.nf
context\&.modules = [
    \&.\&.\&.
    # The native communication protocol\&.
    {   name = libpipewire-module-protocol-native }

    # The profile module\&. Allows application to access profiler
    # and performance data\&. It provides an interface that is used
    # by pw-top and pw-profiler\&.
    {   name = libpipewire-module-profiler }

    # Allows applications to create metadata objects\&. It creates
    # a factory for Metadata objects\&.
    {   name = libpipewire-module-metadata }

    # Creates a factory for making devices that run in the
    # context of the PipeWire server\&.
    {   name = libpipewire-module-spa-device-factory }
    \&.\&.\&.
]

.fi
.PP

.PP
.SH "KNOWN MODULES"
.PP

.PP
.PD 0
.IP "\(bu" 2
\fBlibpipewire-module-access(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-adapter(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-avb(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-client-device(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-client-node(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-combine-stream(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-echo-cancel(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-example-filter(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-example-sink(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-example-source(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-fallback-sink(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-ffado-driver(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-filter-chain(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-jack-tunnel(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-jackdbus-detect(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-link-factory(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-loopback(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-metadata(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-netjack2-driver(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-netjack2-manager(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-parametric-equalizer(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-pipe-tunnel(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-portal(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-profiler(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-protocol-native(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-protocol-pulse(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-protocol-simple(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-pulse-tunnel(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-rt(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-raop-discover(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-raop-sink(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-rtp-sap(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-rtp-session(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-rtp-source(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-rtp-sink(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-spa-node(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-spa-node-factory(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-spa-device(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-spa-device-factory(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-snapcast-discover(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-vban-recv(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-vban-send(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-session-manager(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-zeroconf-discover(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-roc-source(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-roc-sink(7)\fP
.IP "\(bu" 2
\fBlibpipewire-module-x11-bell(7)\fP
.PP

.PP
.SH "AUTHORS"
.PP

.PP
The PipeWire Developers <https://gitlab.freedesktop.org/pipewire/pipewire/issues>; PipeWire is available from <https://pipewire.org>

.PP
.SH "SEE ALSO"
.PP

.PP
\fBpipewire(1)\fP, \fBpipewire\&.conf(5)\fP 

