lawl

You're right, this is an issue, and I've thought about this. > I don't particularly need this This is the conclusion i ended at too :) So far I have...

Hmm, can you show me a log of pipewire-pulse? `journalctl -b $(which pipewire-pulse)` should work. As for the misspelling, yes, there's lots of things misspellt in debugging output, just never...

Also, is this reproducible? Or does it usually work but just got borked this time?

Thanks. Does restarting `pipewire-pulse` (and maybe `pipewire`) make it work again? as for the librnnoise, that should be unrelated. are you starting it on the commandline and maybe killing it...

Oh, right, the CLI doesn't clean it up, sorry i was thinking GUI for some reason. I'll create an issue for that, but definitely unrelated. As for your other issue,...

Thanks everyone, I need a way to reliably reproduce this. Please refrain from "me too" comments and just add a thumbs up to the top post.

Thanks! At this point i'm pretty sure this is a pipewire issue. Could someone with an affected system open an issue with pipewire? All operations noisetorch does should be ephemeral,...

I see, can you try not making it the default device? This causes some issues on PA too. Or is it still configured as default?

I was able to reproduce the issue (partially, did not try rebooting, but i can confirm it breaks when you select it as default). Likely requires a patch in pipewire,...

@machitgarha because it's not a bug. if someone else wants to look into it more before i get to it. Try exposing a way to set `PW_KEY_NODE_DONT_RECONNECT` via the pulse-native...