5 Jul
2022
5 Jul
'22
8:34 p.m.
On Tue Jul 5 20:24:29 2022 +0000, Claire wrote:
Hm, I can't replicate that, and I'm not sure what could be causing this… it is perhaps possible that the PulseAudio context/main loop/connection itself could have some lingering state between `pulse_probe_settings` calls that would make the order in which devices are probed matter?
Though the order of calls to `pulse_probe_settings` wouldn't actually change either…