[alsa-devel] Audinst HUD-mx2 covertly muting itself

Tobias Klausmann klausman-alsa at schwarzvogel.de
Thu Oct 31 17:15:17 CET 2013


On Thu, 31 Oct 2013, Clemens Ladisch wrote:
> Tobias Klausmann wrote:
> > While the device works right in principle, every time an app
> > closes the device, it mutes itself (or crash, this may be a Hw
> > problem). There is no indication of the broken state in the mixer
> > displays of alsamixer or alsamixer-gui, and amixer output does
> > not indicate any change, either (see below).
> The USB Audio Specification defines a mechanism with which a device
> could notify the PC of changes in mixer controls.  However, this device
> does not have such a mechanism, so this looks like a firmware bug.
> Does this happen for both the analog and digital outputs?

The place the device is currently at doesn't have the Hw for me
to test digital output. I will test this (and the one below) as
after next week

> > The vendor does not officially support anything but Windows
> Does it work correctly in Windows without any vendor-supplied driver?

See above.

I have gotten a temporary workaround: use the secondary PCM
device (hw:0,1) instead of the primary (hw:0,0), like this:

$ cat .asoundrc 
defaults.pcm.card 0
defaults.pcm.device 1

While this works, it's not eactly a discoverable way of doing it.
Obviously, this should go into the system-wide asoundrc so all
users benefit from it, but in this case, it works for me.

Maybe something along the lines of PCI device "quirks" would be
the right thing to do? I.e. swapping the two PCM devices from
ALSA's point of view.


More information about the Alsa-devel mailing list