[SOLVED Again] Behringer UMC404HD - ch 3, 4 silent

[andreaskagedal]

I have a problem that input channels 3 and 4 on my Behringer UMC404HD have gone silent.

Does anyone have any idea what is wrong and how I can fix it? Or know where I should ask this question?

I am pretty sure it did work initially. And it works fine under Windows 10, so I know it is not a hardware fault.

When I connect the box and start QJackCtl I can see all four channels, and I can connect them to wherever I want, for instance Ardour. And if I connect a microphone to ch 1 or 2, I see meters move and I can record sound etc.

But if I connect the microphone to ch 3 or 4, the meters do not move, and no sound is recorded etc. I also tried to connect Ardour directly via alsa. Same problem.

When I connect I can see the following messages in /var/log/syslog:

Code: Select all

Jan 18 21:58:04 jojoba kernel: [48923.663788] usb 3-4: new high-speed USB device number 7 using xhci_hcd
Jan 18 21:58:04 jojoba kernel: [48923.790392] usb 3-4: New USB device found, idVendor=1397, idProduct=0509
Jan 18 21:58:04 jojoba kernel: [48923.790397] usb 3-4: New USB device strings: Mfr=1, Product=3, SerialNumber=0
Jan 18 21:58:04 jojoba kernel: [48923.790399] usb 3-4: Product: UMC404HD 192k
Jan 18 21:58:04 jojoba kernel: [48923.790401] usb 3-4: Manufacturer: BEHRINGER
Jan 18 21:58:05 jojoba mtp-probe: checking bus 3, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
Jan 18 21:58:05 jojoba mtp-probe: bus: 3, device: 7 was not an MTP device
Jan 18 21:58:05 jojoba systemd-udevd[2286]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.
Jan 18 21:58:05 jojoba upowerd[2016]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1
Jan 18 21:58:06 jojoba upowerd[2016]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2
Jan 18 21:58:06 jojoba upowerd[2016]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.3
Jan 18 21:58:06 jojoba upowerd[2016]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4
Jan 18 21:58:06 jojoba upowerd[2016]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
Jan 18 21:58:06 jojoba upowerd[2016]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4
Jan 18 21:58:06 jojoba gsd-media-keys[24529]: Unable to get default source
Jan 18 21:58:09 jojoba colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1

[andreaskagedal]

OK, I figured it out.

It turns out ch 3/4 were 'muted' in alsamixer.

I did not know you could mute microphones in alsamixer. I had actually started alsamixer previously, as part of searching for the problem. And I saw this "stereo microphone" setting, with the levels all pulled down. I raised the levels but nothing happened. Still no sound. So I assumed this was not were the problem was. This time, when I started alsamixer again, I realized that raising the levels was not enough. I also as a separate action had to unmute the mic. A wonderful feeling when the meter started to move as I spoke into the mic.

I don't know how this mic became muted in the first place. I think I once started alsamixer before, and possibly I accidentally touched the "M" key to mute it. Is there a way to mute input-channels/mics without starting the alsamixer application?

[bluzee]

Not that I am aware of.

[LAM]

ALSA:

Code: Select all

amixer set Capture toggle

PULSEAUDIO:

Code: Select all

pactl set-source-mute 1 toggle

You may need to adapt these commands to you capture device.

[andreaskagedal]

As it turns out, not really solved.
Next time I start my computer and connect the interface, I see in alsamixer that the "Mic Rear", i.e. channel 3 and 4 are muted again:

alsamixer_capture.png (44.26 KiB) Viewed 1289 times

And this time I am not able to unmute it anymore. It did work once, thus my post above. But now, nothing happens when I press "M". also nothing happens when I press "M" on the "Mic Front" mic which otherwise works fine.

I have no clue how to fix this.

[andreaskagedal]

OK. so now I have solved it again

I had to read up on amixer commands and without understanding everything i managed to figure out that I could run the following command to enable all mics.

First to find the "Controls and content":

Code: Select all

amixer -c 2 contents

Then, after locating the "Mic Capture Switch" in the printout from the above command, this is how I set the capture state to "on" for all four channels:

Code: Select all

amixer -c 2 cset numid=8,iface=MIXER,name='Mic Capture Switch' on,on,on,on

I still don't understand why it did not work to enable/unmute the mics using alsamixer and the "M" key, but now it works which is most importan. I also don't know yet if I will have to do this everytime I reconnect the interface, or everytime i restart the computer, or if it will stay this way now. Time will tell.

[andreaskagedal]

I realize I might be the only one interested in this but since I started the thread I might as well continue, in case someone has the same problem in the future.

I also own and sometimes use a Behringer UMC202HD which, as the name suggests, only supports two input channels. Today I had the 202 plugged when I started the computer, and then replaced it with the 404, and saw the same problem appear again (input channels 3 and 4 silent). Even after restarting the computer with the 404 plugged in. The above/below amixer command solved it, as before.

Code: Select all

amixer -c 2 cset numid=8,iface=MIXER,name='Mic Capture Switch' on,on,on,on

[bluzee]

Most distros will have some sort of alsa or sound service that runs to save your mixer settings at shutdown and then to restore these at start up. Might have to check into your system and see if there is an issue with this.