PipeWire
0.3.59
|
The filter-chain allows you to create an arbitrary processing graph from LADSPA, LV2 and builtin filters.
This filter can be made into a virtual sink/source or between any 2 nodes in the graph.
The filter chain is built with 2 streams, a capture stream providing the input to the filter chain and a playback stream sending out the filtered stream to the next nodes in the graph.
Because both ends of the filter-chain are built with streams, the session manager can manage the configuration and connection with the sinks and sources automatically.
node.description
: a human readable name for the filter chainfilter.graph = []
: a description of the filter graph to run, see belowcapture.props = {}
: properties to be passed to the input streamplayback.props = {}
: properties to be passed to the output streamThe general structure of the graph description is as follows:
Nodes describe the processing filters in the graph. Use a tool like lv2ls or listplugins to get a list of available plugins, labels and the port names.
type
is one of ladspa
, lv2
or builtin
name
is the name for this node, you might need this later to refer to this node and its ports when setting controls or making links.plugin
is the type specific plugin name..so
to find the shared object with that name in the LADSPA plugin path.label
is the type specific filter inside the plugin.config
contains a filter specific configuration section. The convolver plugin needs this.control
contains the initial values for the control ports of the filter.Links can be made between ports of nodes. The portname
is given as <node_name>:<port_name>
.
You can tee the output of filters to multiple other filters. You need to use a mixer if you want the output of multiple filters to go into one filter input port.
links can be omited when the graph has just 1 filter.
These are the entry and exit ports into the graph definition. Their number defines the number of channels used by the filter-chain.
The <portname>
can be null
when a channel is to be ignored.
Each input/output in the graph can only be linked to one filter input/output. You need to use the copy builtin filter if the stream signal needs to be routed to multiple filters. You need to use the mixer builtin plugin if multiple graph outputs need to go to one output stream.
inputs and outputs can be omitted, in which case the filter-chain will use all inputs from the first filter and all outputs from the last filter node. The graph will then be duplicated as many times to match the number of input/output channels of the streams.
There are some useful builtin filters available. You select them with the label of the filter node.
Use the mixer
plugin if you have multiple input signals that need to be mixed together.
The mixer plugin has up to 8 input ports labeled "In 1" to "In 8" and each with a gain control labeled "Gain 1" to "Gain 8". There is an output port labeled "Out". Unused input ports will be ignoded and not cause overhead.
Use the copy
plugin if you need to copy a stream input signal to multiple filters.
It has one input port "In" and one output port "Out".
Biquads can be used to do all kinds of filtering. They are also used when creating equalizers.
All biquad filters have an input port "In" and an output port "Out". They have a "Freq", "Q" and "Gain" control. Their meaning depends on the particular biquad that is used. The following labels can be used:
bq_lowpass
a lowpass filter.bq_highpass
a highpass filter.bq_bandpass
a bandpass filter.bq_lowshelf
a low shelf filter.bq_highshelf
a high shelf filter.bq_peaking
a peaking filter.bq_notch
a notch filter.bq_allpass
an allpass filter.The convolver can be used to apply an impulse response to a signal. It is usually used for reverbs or virtual surround. The convolver is implemented with a fast FFT implementation.
The convolver has an input port "In" and an output port "Out". It requires a config section in the node declaration in this format:
blocksize
specifies the size of the blocks to use in the FFT. It is a value between 64 and 256. When not specified, this value is computed automatically from the number of samples in the file.tailsize
specifies the size of the tail blocks to use in the FFT.gain
the overall gain to apply to the IR file.delay
The extra delay (in samples) to add to the IR.filename
The IR to load or create. Possible values are:/hilbert
creates a hilbert function that can be used to phase shift the signal by +/-90 degrees. The length
will be used as the number of coefficients./dirac
creates a Dirac function that can be used as gain.offset
The sample offset in the file as the start of the IR.length
The number of samples to use as the IR.channel
The channel to use from the file as the IR.The delay can be used to delay a signal in time.
The delay has an input port "In" and an output port "Out". It also has a "Delay (s)" control port. It requires a config section in the node declaration in this format:
max-delay
the maximum delay in seconds. The "Delay (s)" parameter will be clamped to this value.Options with well-known behavior. Most options can be added to the global configuration or the individual streams:
Stream only properties:
This example uses the rnnoise LADSPA plugin to create a new virtual source.
This example uses the ladpsa surround encoder to encode a 5.1 signal to a stereo Dolby Surround signal.