6 Jul
2022
6 Jul
'22
6:17 a.m.
On Tue Jul 5 22:14:01 2022 +0000, Claire wrote:
After restarting PulseAudio a bunch of times (after trying to reproduce the issue with pipewire-pulse too), it eventually ended up in a state where I got the exact same test failures. But those were reproduced on `master` too, and audio input did not work in any other application either, so while it's still possible I introduced a regression, I suspect this might just have been PulseAudio being stuck in a weird state, and might not be related to the code changes at all…
It's definitely this patch that causes a regression for me. Specifically, removal of only the second `pulse_probe_settings()` call is enough to trigger it.