Open luni3359 opened 2 years ago
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 thus not implemented. I'm not sure if the additional code complexity is worth handling this corner case.
One use case is the use of bluetooth headset which gets disconnected when loading/reloading noisetorch (meaning we cannot use noisetorch with a bluetooth microphone)
I did not look into using bluetooth headsets with noisetorch yet. Though as I imagine the feature of updating the headphone/smartphone lists when new devices are registered, one would still be required to "reload noisetorch" to activate the device. At least on pulseaudio. With pipewire we should be able to avoid it, afaict.
Problem: When the GUI is loaded NoiseTorch displays all devices it found at the time it opened, but newly added devices don't change the list.
What to expect: The list is updated when there's new devices loaded or they're removed.
Notes: I don't particularly need this but I thought that if NoiseTorch did this automatically it would offer a better user experience.