New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change of the default device not automatically detected #49
Comments
How are you changing the default card? |
Currently, by using pulseaudio's module-switch-on-connect. I think the same used to happen when I was just switching by changing the .asoundrc, but I'm not 100% sure as I now use pulseaudio making it hard to test. In case pulseaudio is unsupported, sorry for the false alarm. |
I second this issue.
|
I can confirm this issue as well. |
I can confirm this issue as well. |
Just a quick update, my workaround with restarting it to detect the switch of audio output has recently stopped to work. So, since I use pulseaudio anyway, I have switched over to using "pa-applet". It also handles volume keys and a tray icon with a volume bar plus supports switching output. |
my workaround on xfce was to switch to (http://goodies.xfce.org/projects/panel-plugins/xfce4-pulseaudio-plugin ) |
One more instance in unplugging and plugging back in USB sound card (which is the only sound card in my system).
|
I can suggest updating the device list on opening preferences dialog. Then it will be possible to change the device to newly inserted sound card without restarting volumeicon. Item for switching in context menu would also be handy |
Don't use volumeicon due to bug: Maato/volumeicon#49 Signed-off-by: schspa <schspa@gmail.com>
If the default device is changed (e.g. from built-in sound card to USB headset), Volumeicon does not change the volume on the new (current) device (the headset), but on the previous default (built-in card). It is enough to switch the device in preferences and switch it back to default to make it detect the change, but it would be very helpful if it could do this automatically.
The text was updated successfully, but these errors were encountered: