- Better fix for (bsc#1223916) that basically turns the main
  profile into the (to be in 0.5.3) video-only profile unless
  wireplumber-audio is installed which now turns the main profile
  into exactly upstream's main profile.

• Files Changed
• Browse Source

- Add patch from upstream to fix a json log issue:
  * 0001-lua-json-fix-error-ouput.patch
- Add patch from upstream to add a method to merge json containers:
  * 0002-lua-json-add-method-to-merge-json-containers.patch
- Add patch from upstream to fix merging a particular case
  of configuration options:
  * 0003-json-utils-fix-overriding-of-non-container-values-when.patch
- Fix wireplumber not starting successfully when audio support is
  not enabled since the main profile now requires it. The best
  option would be to use a video-only profile but it's too late
  to change the way wireplumber is started in SLE/Leap, so the
  solution just makes audio/bluetooth optional for now
  (bsc#1223916)
  * split-config-file.py

• Files Changed
• Browse Source

- Update to version 0.5.2:
  * Highlights:
    - Added support for loading configuration files other than the
      default wireplumber.conf within Lua scripts (!629)
    - Added support for loading single-section configuration files,
      without fragments (!629)
    - Updated the node.software-dsp script to be able to load
      filter-chain graphs from external configuration files, which
      is needed for Asahi Linux audio DSP configuration (!629)
  * Fixes:
    - Fixed destroying camera nodes when the camera device is
      removed (#627, !631)
    - Fixed an issue with Bluetooth BAP device set naming (!632)
    - Fixed an issue caused by the pipewire event loop not being
      "entered" as expected (!634, #638)
    - A false positive warning about no modules being loaded is
      now suppressed when using libpipewire >= 1.0.5 (#620)
    - Default nodes can now be selected using priority.driver when
      priority.session is not set (#642)
  * Changes:
    - The library version is now generated following pipewire's
      versioning scheme: libwireplumber-0.5.so.0.5.2 becomes
      libwireplumber-0.5.so.0.0502.0 (!633)
- Remove patches from upstream that are already in 0.5.2:
  * 0001-core-set-context.modules.allow-empty-to-silence-warning-in.patch
  * 0002-monitor-utils-clear-cam-data-after-creating-nodes.patch
  * 0003-monitors_bluez-fix-BAP-device-set-node-naming.patch

• Files Changed
• Browse Source

- Add patch from upstream to silence a warning on pipewire
  (since 1.0.5):
  * 0001-core-set-context.modules.allow-empty-to-silence-warning-in.patch
- Add patch from upstream to fix a dangling reference to a device:
  * 0002-monitor-utils-clear-cam-data-after-creating-nodes.patch
- Add patch from upstream to fix BAP node naming:
  * 0003-monitors_bluez-fix-BAP-device-set-node-naming.patch

• Files Changed
• Browse Source

- Update to version 0.5.1:
  * Highlights:
    - Added a guide documenting how to migrate configuration from
      0.4 to 0.5, also available online at:
      https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/migration.html
      If you are packaging WirePlumber for a distribution, please
      consider informing users about this. Installing the
      wireplumber-doc subpackage, this file can be read by running:
      xdg-open /usr/share/doc/wireplumber/html/daemon/configuration/migration.html
  * Fixes:
    - Fixed an odd issue where microphones would stop being usable
      when a Bluetooth headset was connected in the HSP/HFP profile
      (#598, !620)
    - Fixed an issue where it was not possible to store the
      volume/mute state of system notifications (#604)
    - Fixed a rare crash that could occur when a node was destroyed
      while the 'select-target' event was still being processed
      (!621)
    - Fixed deleting all the persistent settings via
      wpctl --delete (!622)
    - Fixed using Bluetooth autoswitch with A2DP profiles that have
      an input route (!624)
    - Fixed sending an error to clients when linking fails due to a
      format mismatch (!625)
  * Additions:
    - Added a check that prints a verbose warning when old-style
      0.4.x Lua configuration files are found in the system. (#611)
    - The "policy-dsp" script, used in Asahi Linux to provide a
      software DSP for Apple Sillicon devices, has now been ported
      to 0.5 properly and documented (#619, !627)

• Files Changed
• Browse Source

- Add patch from upstream to fix all input sources only working
  when bluetooth profile is set to HSF/HFP, which was a regression
  in 0.5.0 (glfo#pipewire/wireplumber#598):
  * 0001-filter-utils-fix-handling-of-targetless-smart-filters.patch

• Files Changed
• Browse Source

- Avoid %if %{pkg_vcmp gcc < 8}, instead replicate the condition
  from the BuildRequires section.

• Files Changed
• Browse Source

- Update to version 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 (!613)
    - Improved the naming of Bluetooth nodes when the
      auto-switching loopback node is present (!614)
    - 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
      (#595, !616)
  * Fixes:
    - Fixed checking for available routes when selecting the
      default node (!609)
    - Fixed an issue that was causing an infinite loop storing
      routes in the state file (!610)
    - Fixed the interpretation of boolean values in the alsa
      monitor rules (#586, !611)
    - Fixes a Lua crash when we have 2 smart filters, one with a
      target and one without (!612)
    - Fixed an issue where the default nodes would not be updated
      when the currently selected default node became unavailable
      (#588, !615)
    - Fixed an issue that would cause the Props (volume, mute, etc)
      of loopbacks and other filter nodes to not be restored at
      startup (#577, !617)
    - Fixed how some constants were represented in the
      gobject-introspection file, mostly by converting them from
      defines to enums (#540, #591)
    - Fixed an issue using WirePlumber headers in other projects

• Files Changed
• Browse Source

- Update to version 0.4.90+git25.95cfa9e:
  * wpctl: fix settings --help listing
  * docs: conf_file: small updates
  * docs: installing: update dependency versions
  * si-linkables: do not fully reset when the underlying proxy is
    destroyed
  * registry: move to a separate file and decouple it from the
    object manager
  * log: docs: document the log topic definition macros
  * monitors/bluez: add 'internal' prefix to internal bluez node
    names.
  * monitor/bluez: set node.name property when creating combine
    stream
  * meson: bump min pipewire version to 1.0.2
  * scripts: fix regression in state-routes.lua when marking routes
    as 'active'
  * scripts: improve linking logs
  * monitors: use parseBool for boolean properties in rules 
  * config: add {device|node}.disable
  * object-interest: make WP_INTEREST_MATCH_ALL part of the enum 
  * proxy: make the FEATURES_MINIMAL and FEATURES_ALL constants
    part of the enum 
  * log: fix WP_LOG_LEVEL_TRACE value in the g-i bindings 
  * base-dirs: wrap flag groups in parenthesis 
  * log.h: define G_LOG_DOMAIN only if
    WP_USE_LOCAL_LOG_TOPIC_IN_G_LOG is defined 
  * meson: make sure the boolean options have boolean values 
  * meson: move the common CFLAGS to project-wide scope
  * scripts: make sure target is not nil when iterating filters
    with matching targets

• Files Changed
• Browse Source

- Revert that last change. Obsoletes shouldn't be used for that.

• Files Changed
• Browse Source

- Obsolete libwireplumber-0_4-0 from libwireplumber-0_5-0

• Files Changed
• Browse Source

- Add patch from upstream to fix a typo a lua script:
  * 0001-scripts-fix-typo-in-rescan-virtual-links.lua.patch

• Files Changed
• Browse Source

- Update to version 0.4.90 (0.5.0 RC1)
  * 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 (!601)
    - 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
      (!601)
    - 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 (!599, !600)
    - 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

• Files Changed
• Browse Source

- Add patch from upstream to remove the "clear-persistent"
  sub-command and add a "settings" sub-command:
  * 0001-wpctl-add-settings-subcomand-to-show_-delete-or-change.patch

- Update to version 0.4.82 (0.5.0 pre-release 2)
  * Highlights:
    - Bluetooth auto-switching is now implemented with a virtual
      source node. When an application links to it, the actual
      device switches to the HSP/HFP profile to provide the real
      audio stream. This is a more robust solution that works with
      more applications and is more user-friendly than the previous
      application whitelist approach
    - Added support for dynamic log level changes via the PipeWire
      settings metadata. Also added support for log level patterns
      in the configuration file
    - The "persistent" (i.e. stored) settings approach has changed
      to use two different metadata objects: sm-settings and
      persistent-sm-settings. Changes in the former are applied in
      the current session but not stored, while changes in the
      latter are stored and restored at startup. Some work was also
      done to expose a wpctl interface to read and change these
      settings, but more is underway
    - Several WirePlumber-specific node properties that used to be
      called target.* have been renamed to node.* to match the
      PipeWire convention of node.dont-reconnect. These are also
      now fully documented
  * Other changes:
    - Many documentation updates
    - Added support for SNAP container permissions
    - Fixed multiple issues related to restoring the Route

• Files Changed
• Browse Source

- Add patch to only enable bluetooth when audio support is enabled
  by installing wireplumber-audio (bsc#1219411):
  * fix-bsc1219411.patch

• Files Changed
• Browse Source

- Update to version 0.4.17.

• Files Changed
• Browse Source

- Update to version 0.4.16:
  * Additions:
    - Added a new "sm-objects" script that allows loading objects
      on demand via metadata entries that describe the object to
      load; this can be used to load pipewire modules, such as
      filters or network sources/sinks, on demand
    - Added a mechanism to override device profile priorities in
      the configuration, mainly as a way to re-prioritize Bluetooth
      codecs, but this also can be used for other devices
    - Added a mechanism in the endpoints policy to allow connecting
      filters between a certain endpoint's virtual sink and the
      device sink; this is specifically intended to allow plugging
      a filter-chain to act as equalizer on the Multimedia endpoint
    - Added wp_core_get_own_bound_id() method in WpCore
  * Changes:
    - PipeWire 0.3.68 is now required
    - policy-dsp now has the ability to hide hardware nodes behind
      the DSP sink to prevent hardware misuse or damage
    - JSON parsing in Lua now allows keys inside objects to be
      without quotes
    - Added optional argument in the Lua JSON parse() method to
      limit recursions, making it possible to partially parse a
      JSON object
    - It is now possible to pass nil in Lua object constructors
      that expect an optional properties object; previously,
      omitting the argument was the only way to skip the properties
    - The endpoints policy now marks the endpoint nodes as
      "passive" instead of marking their links, adjusting for the
      behavior change in PipeWire 0.3.68
    - Removed the "passive" property from si-standard-link, since

• Files Changed
• Browse Source

fix typo
  behaved/configured clients:

• Files Changed
• Browse Source

- Add patch from upstream that fixes too many matches for property
  interest:
  * 0001-object-manager-reduce-the-amount-of-globals-that-initially.patch
- Add patch from upstream that fixes an odd failure of a test after
  applying the previous patch:
  * 0002-object-manager-use-an-idle-callback-to-expose-tmp-globals.patch
- Add patch from upstream that adds ability to hide parent nodes,
  which is useful to prevent hardware misuse or damage by poorly
  behaves/configured clients:
  * 0001-policy-dsp-add-ability-to-hide-parent-nodes.patch

• Files Changed
• Browse Source

- Update to version 0.4.15:
  * Additions:
    - A new "DSP policy" module has been added; its purpose is to
      automatically load a filter-chain when a certain hardware
      device is present, so that audio always goes through this
      software DSP before reaching the device. This is mainly to
      support Apple M1/M2 devices, which require a software DSP
      to be always present
    - WpImplModule now supports loading module arguments directly
      from a SPA-JSON config file; this is mainly to support DSP
      configuration for Apple M1/M2 and will likely be reworked
      for 0.5
    - Added support for automatically combining Bluetooth LE Audio
      device sets (e.g. pairs of earbuds) (!500)
    - Added command line options in wpctl to display device/node
      names and nicknames instead of descriptions
    - Added zsh completions file for wpctl
    - The device profile selection policy now respects the
      device.profile property if it is set on the device; this is
      useful to hand-pick a profile based on static configuration
      rules (alsa_monitor.rules)
  * Changes/Fixes:
    - Linking policy now sends an error to the client before
      destroying the node, if it determines that the node cannot be
      linked to any target; this fixes error reporting on the
      client side
    - Fixed a crash in suspend-node that could happen when
      destroying virtual sinks that were loaded from another
      process such as pw-loopback
    - Virtual machine default period size has been bumped to 1024

• Files Changed
• Browse Source