mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-12-29 11:08:40 -05:00
9b9ce21b1d
The hardware controls we track for volume and mute state can change as part of enabling or disabling the UCM device. This then triggers a re-sync of our state with the hardware controls, which can e.g. set our volume to an unwanted value as the result of enabling the device, or set a hardware control to a wrong value based on our volume while disabling the device. So these UCM-triggered changes to enable/disable the device will at best show up on user interfaces and cause confusion, but maybe even will push the hardware into an unexpected state. The volume and mute state we set from user interfaces only make sense when the devices are enabled. They should not be kept in sync with hardware for inactive UCM devices [1]. Skip the callbacks for reading and changing volume and mute state if the UCM device is disabled. This way, the volume/mute controls for sinks/sources are essentially detached from the hardware controls until the UCM device is re-enabled. [1] https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/772#note_1872757 Link: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/772 Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| include | ||
| plugins | ||
| tests | ||
| tools | ||
| meson.build | ||