You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not as easy. The hardware based device changes can be really tracked using the /dev/snd/control* device node events, but the other "virtual" devices are mostly based on the configuration files and evaluated when the application asks for them.
We have already alsactl state management daemon, so we can probably send some notifications over DBus at least for the hardware devices.
What's a good workaround for this? I've been doing what the OP said for some time: checking for udev events and then waiting 6 seconds for the device to actually be available to ALSA... but it's such a hack.
Hotplug support is mandatory in any modern system. But in ALSA there is no way to be notified by audio device changes.
I'm aware that as a hack, one could listen to udev notifications. But this is not appropriate, because:
The text was updated successfully, but these errors were encountered: