GitLab

Add an example of renegotiating a producer and consumer format.

Handle an EnumFormat param change on the link ports and start
the renegotiation process.

Reset our state before checking the state of the ports or else
we might still think a port has buffers while they are being
allocated.

When a caller sets a format, we do this regardless of the currently
configured format.

The caller frees the buffers after setting a new format.

Make it possible to log more info in the param debug functions

Observers check the flags to see if there is a change. The serial
can be used to toggle a change when no other flags change.

profiles2 is meant to be NULL terminated, according to its documentation
Fixes a crash in pavucontrol-qt

Always make sure passive links are prepared so we can follow them
and use them to activate nodes.

Let the jack client make passive links when the PIPEWIRE_LINK_PASSIVE
variable is set. Makes it possible to start qsynth with passive links
so that it suspends when not in use.

Check if a driver is only connected to other nodes with passive
links, if that's the case, set the driver and all followers in
IDLE.

Don't preallocate ports, do so on demand to reduce memory
usage.

This makes it easier to test PipeWire in its "as-installed" state,
for example in an OS distribution.

The .test metadata files in ${datadir}/installed-tests/${package} are
a convention taken from GNOME's installed-tests initiative, allowing a
generic test-runner like gnome-desktop-testing to discover and run tests
in an automatic way.

The installation path ${libexecdir}/installed-tests/${package} is also
a convention borrowed from GNOME's installed-tests initiative.

In addition to the automated tests, I've installed example executables
in the same place, for manual testing. They could be separated into
a different directory if desired, but they seem like they have more
similarities with the automated tests than differences: both are there
to test that PipeWire works correctly, and neither should be relied on
for production use. Some examples are installed in deeper subdirectories
to avoid name clashes.
Signed-off-by: Simon McVittie <smcv@debian.org>

This lets them be used installed or uninstalled, like pipewire itself.
Signed-off-by: Simon McVittie <smcv@debian.org>

..so that we can resize the array later.

We only need as many ports and buffer data as the maximum number
of channels, which is 64.
Fix empty output size. We're only ever going to fill this with
float samples.

Calculate the size of the buffer as the difference between the first
byte and the last byte. This takes into account the alignment.

Or else we lose the MAPPED flag and we don't unmap (not that it's
a problem because it gets unmapped when we close the fd).