https://bugs.kde.org/show_bug.cgi?id=432487
Niklāvs Koļesņikovs <89q1r1...@relay.firefox.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |89q1r1...@relay.firefox.com
--- Comment #6 from Niklāvs Koļesņikovs <89q1r1...@relay.firefox.com> ---
Due to some clients being bad and setting the default device at their startup
as their explicitly chosen target, which essentially breaks default device
switching later on, both PA and PW now ignore target.object value when it
matches the current default. It's annoying but there's no other way when client
software is pulling such shenanigans.
For the above reason, I don't think it's possible to implement lock to device
functionality for cases where the desired sink or source matches the current
default within the current PulseAudio API. The best solution would likely be to
work with either PipeWire or WirePlumber on a new API call that would be
restricted to privileged clients such as plasma-pa and allow an explicit
target.object override.
Alternatively it might be possible to keep the old behavior for when a client
sets its own target.object but permit a privileged client to set the value "for
realz". Doing so would permit this without modifying the existing PA API by
only changing the audio server internals.
Either way someone will need to figure out the priority of such an override
i.e. is plasma-pa higher precedence than the client making its own choice and I
don't know enough to say one way or another, since both are supposed to be user
controlled and having them mismatch would be terrible UX.
--
You are receiving this mail because:
You are watching all bug changes.
