Closed minsulander closed 10 months ago
Sounds like the best bugfix would be to get a reliable USB hub ;)
Could you please share your log file so I can a look at if there is even anything reported ?
Thanks
Wrote too quickly and did not see your edit, thank you.
Yes indeed, I need a new USB hub, but it would still be nice if VectorAudio indicated that audio is not working.. could happen for other reasons, say, if my cat (if I had one) tripped on the USB cable and pulled it out without me noticing... :laughing: There might be more plausible cases.
I found a way to add that notification. Will be available in the next version
Awesome! Thanks a bunch.
I added an event for this, but to be very honest it might still crash haha, give it a try and we will see. Pulse audio does behave strangely. For example on macOs, coreaudio would automatically rerouted everything to default active devices. Let me know how it goes
Thanks for looking into this. I haven't had a chance to try out the latest version yet, but I will as soon as I can, and let you know.
Wonderful! Now I get this error dialog when I (or my USB hub) disconnect the headset:
Although... when I click OK, the dialog closes and then the whole app freezes. But this is so much better because at least I know I have a problem, and I can kill it and restart/reconnect.
Great, going to close this as "good enough", will see I'll manage to fix the freeze in the future
I'm using VectorAudio 1.4.0 on Linux (Ubuntu 22.04) with a USB headset and noticed that if you:
In that situation it would be nice if VectorAudio showed some large error banner, or disconnected automatically, or (even better) reset the audio device somehow to remedy the situtation by itself.
With all due respect that audio on Linux can be quite frustrating... :wink:
vector_audio.log
shows this when I pull the USB plug:so there should be something to hook into to trigger some error handling behavior..