services/pipewire: consider device volume step when sending updates

Previously a hardcoded 0.0001 offset was used to determine if a volume
change was significant enough to send to a device, however some
devices have a much more granular step size, which caused future
volume updates to be blocked.

This change replaces the hardcoded offset with the volumeStep device
route property which should be large enough for the device to work with.

Fixes #279
This commit is contained in:
outfoxxed 2025-10-01 00:29:45 -07:00
parent f5ca8453c0
commit 522d126d1b
No known key found for this signature in database
GPG key ID: 4C88A185FB89301E
3 changed files with 39 additions and 23 deletions

View file

@ -4,6 +4,7 @@
## Bug Fixes
- Fixed volumes getting stuck on change for pipewire devices with few volume steps.
- Fixed a crash when running out of disk space to write log files.
- Fixed a rare crash when disconnecting a monitor.
- Fixed build issues preventing cross compilation from working.