Wireplumber Master

Edit Package wireplumber
https://gitlab.freedesktop.org/pipewire/wireplumber

Wireplumber 0.5.0 has been released! I'll keep this package updated for the time being, but I may kill it and roll stock from there on. Time will tell...

This build is from the head of the 'Master' branch of WirePlumber, currently version 0.4.8x, soon to be released as 0.5.x. This uses a new config file format, based on pipewire's format, and is not backwards-compatible with stock wireplumber, but has many improvements and additions.

WirePlumber is a modular session / policy manager for PipeWire and a GObject-based high-level library that wraps PipeWire's API, providing convenience for writing the daemon's modules as well as external tools for managing PipeWire.

Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000745 745 Bytes
_service:obs_scm:_servicedata 0000000253 253 Bytes
_service:obs_scm:wireplumber-0.5.2+git20240422.b302ebd.obscpio 0002773516 2.65 MB
_service:obs_scm:wireplumber.changes 0000000718 718 Bytes
_service:obs_scm:wireplumber.obsinfo 0000000120 120 Bytes
wireplumber.changes 0000000000 0 Bytes
wireplumber.spec 0000008292 8.1 KB
Latest Revision
pallas wept's avatar pallas wept (pallaswept) committed (revision 61)
trigger service run
Comments 4

pallas wept's avatar

Currently running a commit short, as there were issues with the latest commit set. Will bring it back up to the full latest branch when it's all sorted.


pallas wept's avatar

Back on the full Next branch as patches have been submitted. There are still some peculiarities with automatic filter linking, but it respects object.target now, so is back to being suitable as a 'daily driver'.


pallas wept's avatar

Added the wireplumber-doc package ready for the new additions once they're all functional and we're back up to the latest Next branch, because there are new features that aren't documented elsewhere. Still using the old commit of the last working version, just for the short term.


pallas wept's avatar

Heads up! Rule syntax changed a couple of weeks ago, so that WP matches PW more accurately. So rules now look like this: { matches = [ { match = "thing" } ] actions = { update-props = { some.prop = foobar } } } Note the 'actions' wrapping the 'update-props'. So your rules will need re-writing.

openSUSE Build Service is sponsored by