wireplumber-0.5.0

[Douglas R. Reno]

This is a prerelease, see ​https://gitlab.freedesktop.org/pipewire/wireplumber/-/commit/4c82e59163841bdf6b626bc37f74394620d29239

[Bruce Dubbs]

WirePlumber 0.5.0

Changes:

• Bumped the minimum required version of PipeWire to 1.0.2, because we make use of the 'api.bluez5.internal' property of the BlueZ monitor

• Improved the naming of Bluetooth nodes when the auto-switching loopback node is present

• Updated the documentation on "settings", the Bluetooth monitor, the Access configuration, the file search locations and added a document on how to modify the configuration file

Fixes:

• Fixed checking for available routes when selecting the default node

• Fixed an issue that was causing an infinite loop storing routes in the state file

• Fixed the interpretation of boolean values in the alsa monitor rules

• Fixes a Lua crash when we have 2 smart filters, one with a target and one without

• Fixed an issue where the default nodes would not be updated when the currently selected default node became unavailable

• Fixed an issue that would cause the Props (volume, mute, etc) of loopbacks and other filter nodes to not be restored at startup

• Fixed how some constants were represented in the gobject-introspection file, mostly by converting them from defines to enums

• Fixed an issue using WirePlumber headers in other projects due to redefinition of G_LOG_DOMAIN

WirePlumber 0.4.90

This is the first release candidate (RC1) of WirePlumber 0.5.0.

Highlights:

• The configuration system has been changed back to load files from the WirePlumber configuration directories, such as /etc/wireplumber and $XDG_CONFIG_HOME/wireplumber, unlike in the pre-releases. This was done because issues were observed with installations that use a different prefix for pipewire and wireplumber. If you had a wireplumber.conf file in /etc/pipewire or $XDG_CONFIG_HOME/pipewire, you should move it to /etc/wireplumber or $XDG_CONFIG_HOME/wireplumber respectively

• The internal base directories lookup system now also respects the XDG_CONFIG_DIRS and XDG_DATA_DIRS environment variables, and their default values as per the XDG spec, so it is possible to install configuration files also in places like /etc/xdg/wireplumber and override system-wide data paths

• wpctl now has a settings subcommand to show, change and delete settings at runtime. This comes with changes in the WpSettings system to validate settings using a schema that is defined in the configuration file. The schema is also exported on a metadata object, so it is available to any client that wants to expose WirePlumber settings

• The WpConf API has changed to not be a singleton and support opening arbitrary config files. The main config file now needs to be opened prior to creating a WpCore and passed to the core using a property. The core uses that without letting the underlying pw_context open and read the default client.conf. The core also closes the WpConf after all components are loaded, which means all the config loading is done early at startup. Finally, WpConf loads all sections lazily, keeping the underlying files memory mapped until it is closed and merging them on demand

[Bruce Dubbs]

Fixed at commit 25c324ecad.