Crash when selecting USB audio interface

lich000king · September 2, 2023 at 1:32 PM

Hi

So I have le 11.0.1 running on a pi4/8GB. When I plug in my Behringer U-phoria UMC1820 USB audio interface, the system reboots...

The u-phoria has a separate power supply and is supposed to work well on the pi (e.g.).

It seems like the device is recognised all right. it's just when I select it in the settings as audio output device that gives the crash. I see two new entries, one 'analog' and one 'spdif' when the u-phoria is connected. Selecting either gives the same result.

Code

$ uname -a
Linux LibreELEC 6.1.19 #1 SMP Sat Mar 18 20:58:05 UTC 2023 aarch64 GNU/Linux

Code

$ lsusb |grep BEHRINGER
Bus 001 Device 003: ID 1397:0503 BEHRINGER International GmbH UMC1820

Somehow these logs don't seem to reveal much, at least to me.

I also disabled bluetooth in the le settings, that didn't help.

Has anyone seen something similar? Any ideas are appreciated

petediscrete · September 2, 2023 at 2:50 PM

Have you tried alternating USB ports when plugging in the unit, USB 2/USB3. Have you confirmed the unit is actually functioning as it should. Try powering on the RPI4 first then hook up the unit.

**chewitt** · September 3, 2023 at 6:24 AM

Any difference if the device is connected before power-on/boot? (prob. not, but will ask anyway)

lich000king · September 3, 2023 at 5:31 PM

Thanks.

Quote from petediscrete

Have you tried alternating USB ports when plugging in the unit, USB 2/USB3. Have you confirmed the unit is actually functioning as it should. Try powering on the RPI4 first then hook up the unit.

So, it tried both USB2 and USB3 ports, it's the same.

When I boot from a current raspios (Release date: May 3rd 2023, System: 32-bit, Kernel version: 6.1, Debian version: 11 (bullseye)) the interface not only doens't crash but actually play audio.

Quote from chewitt

Any difference if the device is connected before power-on/boot? (prob. not, but will ask anyway)

Unfortunately not. It's exactly the same.

**Da Flex** · September 3, 2023 at 10:09 PM

Behringer UMC22 (ASIO conform) works fine here (RPi3B+). Which driver do you use at your music production OS? I bet it's not ASIO.

petediscrete · September 3, 2023 at 10:57 PM

Quote from lich000king

Thanks.

So, it tried both USB2 and USB3 ports, it's the same.
When I boot from a current raspios (Release date: May 3rd 2023, System: 32-bit, Kernel version: 6.1, Debian version: 11 (bullseye)) the interface not only doens't crash but actually play audio.
Unfortunately not. It's exactly the same.

That’s good. You’ve ruled out a faulty unit so it appears it’s down to a kernel/driver issue in LE. I’ve tried many DACs with LE and I must admit none of them have had any issues working. When you hot plug the unit what are you seeing from dmesg output.

lich000king · September 4, 2023 at 8:14 PM

Quote from Da Flex

Behringer UMC22 (ASIO conform) works fine here (RPi3B+). Which driver do you use at your music production OS? I bet it's not ASIO.

ALSA. There is no ASIO for linux, is there?

Quote from petediscrete

That’s good. You’ve ruled out a faulty unit so it appears it’s down to a kernel/driver issue in LE. I’ve tried many DACs with LE and I must admit none of them have had any issues working. When you hot plug the unit what are you seeing from dmesg output.

This is what I get:

Code

[  130.109641] usb 1-1.1: new high-speed USB device number 6 using xhci_hcd
[  130.200398] usb 1-1.1: New USB device found, idVendor=1397, idProduct=0503, bcdDevice= 1.00
[  130.200432] usb 1-1.1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[  130.200446] usb 1-1.1: Product: UMC1820
[  130.200459] usb 1-1.1: Manufacturer: BEHRINGER
[  130.200470] usb 1-1.1: SerialNumber: 2F35E9FA
[  131.144560] usbcore: registered new interface driver snd-usb-audio

I made another test, the interface seems to work in le outside of kodi:

Code

$ aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default
    Default Audio Device
sysdefault
    Default Audio Device
default:CARD=vc4hdmi0
    vc4-hdmi-0, MAI PCM i2s-hifi-0
    Default Audio Device
sysdefault:CARD=vc4hdmi0
    vc4-hdmi-0, MAI PCM i2s-hifi-0
    Default Audio Device
hdmi:CARD=vc4hdmi0,DEV=0
    vc4-hdmi-0, MAI PCM i2s-hifi-0
    HDMI Audio Output
default:CARD=vc4hdmi1
    vc4-hdmi-1, MAI PCM i2s-hifi-0
    Default Audio Device
sysdefault:CARD=vc4hdmi1
    vc4-hdmi-1, MAI PCM i2s-hifi-0
    Default Audio Device
hdmi:CARD=vc4hdmi1,DEV=0
    vc4-hdmi-1, MAI PCM i2s-hifi-0
    HDMI Audio Output
default:CARD=UMC1820
    UMC1820, USB Audio
    Default Audio Device
sysdefault:CARD=UMC1820
    UMC1820, USB Audio
    Default Audio Device
front:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    Front output / input
surround21:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    4.0 Surround output to Front and Rear speakers
surround41:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=UMC1820,DEV=0
    UMC1820, USB Audio
    IEC958 (S/PDIF) Digital Audio Output

Display More

And I can successfully play audio like this:

Code

aplay --device plughw:CARD=UMC1820,DEV=0 test.wav

What does this mean?

**Da Flex** · September 4, 2023 at 8:58 PM

Code

2023-02-16 18:11:52.194 T:1375     info <general>:     Device 1
2023-02-16 18:11:52.194 T:1375     info <general>:         m_deviceName      : @:CARD=UMC1820,DEV=0
2023-02-16 18:11:52.194 T:1375     info <general>:         m_displayName     : UMC1820
2023-02-16 18:11:52.194 T:1375     info <general>:         m_displayNameExtra: Analog
2023-02-16 18:11:52.194 T:1375     info <general>:         m_deviceType      : AE_DEVTYPE_PCM
2023-02-16 18:11:52.194 T:1375     info <general>:         m_channels        : NULL
2023-02-16 18:11:52.194 T:1375     info <general>:         m_sampleRates     : 48000
2023-02-16 18:11:52.194 T:1375     info <general>:         m_dataFormats     : AE_FMT_S24NE3
2023-02-16 18:11:52.194 T:1375     info <general>:         m_streamTypes     : No passthrough capabilities
2023-02-16 18:11:52.194 T:1375     info <general>:     Device 2
2023-02-16 18:11:52.194 T:1375     info <general>:         m_deviceName      : iec958:CARD=UMC1820,DEV=0
2023-02-16 18:11:52.194 T:1375     info <general>:         m_displayName     : UMC1820
2023-02-16 18:11:52.194 T:1375     info <general>:         m_displayNameExtra: S/PDIF
2023-02-16 18:11:52.194 T:1375     info <general>:         m_deviceType      : AE_DEVTYPE_IEC958
2023-02-16 18:11:52.194 T:1375     info <general>:         m_channels        : NULL
2023-02-16 18:11:52.194 T:1375     info <general>:         m_sampleRates     : 44100,48000,88200,96000
2023-02-16 18:11:52.195 T:1375     info <general>:         m_dataFormats     : AE_FMT_RAW,AE_FMT_S24NE3
2023-02-16 18:11:52.195 T:1375     info <general>:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512

Display More

Channels are "NULL" for both output options. I think the "aplay" creates two stereo channels, but Kodi tries to use the channels, provided by the audio interface.

"Device 2" has passthrough capabilities. Please try the passthrough option in LE's audio settings.

lich000king · September 5, 2023 at 8:28 PM

Hi again

Indeed, when the interface is plugged in, I can activate passthrough, and the 'spdif' device is automatically selected as passthrough device (and it's the only one available in the passthrough dropdown).

However when I now select said spdif device as audio output, I get again a reboot.

Or would it be enough to only activate passthrough, without choosing a different output device?

Meanwhile, I also installed le 11.0.3 on a different SD and tested with that, just to be sure. The issue persists, unfortunately... (the only difference being that I now got a boot loop instead of just a reboot)

**Da Flex** · September 6, 2023 at 12:03 AM

Current theory: The driver was loaded OK, but you need JACK to configure ins and outs of the audio interface.

Ardour has JACK, because it's made for musicians, LE doesn't. UMC1820 configuration for JACK: Click!

Sorry, we don't support JACK.

lich000king · September 6, 2023 at 6:11 AM

Quote from Da Flex

Current theory: The driver was loaded OK, but you need JACK to configure ins and outs of the audio interface.
Ardour has JACK, because it's made for musicians, LE doesn't. UMC1820 configuration for JACK: Click!
Sorry, we don't support JACK.

Hm, why would I need JACK if the thing works fine in ALSA?

**Da Flex** · September 6, 2023 at 2:14 PM

Quote from lich000king

Hm, why would I need JACK if the thing works fine in ALSA?

The audio interface provides a ton of ins and out, without any standard, how to route them to a speaker system. I guess that's why the ALSA driver only provides an API for JACK. JACK is the expert for connection management.

"aplay" makes an assumption about connections, and that worked. Kodi wants to do it right, and asks the driver for input channels. The answer is NULL (see post #8), because JACK should answer instead.

My Behringer UMC22 has two ins, and two outs. In that case stereo routing is obvious, and that works for Kodi.

lich000king · September 6, 2023 at 2:43 PM

Quote from Da Flex

The audio interface provides a ton of ins and out, without any standard, how to route them to a speaker system. I guess that's why the ALSA driver only provides an API for JACK. JACK is the expert for connection management.
"aplay" makes an assumption about connections, and that worked. Kodi wants to do it right, and asks the driver for input channels. The answer is NULL (see post #8), because JACK should answer instead.
My Behringer UMC22 has two ins, and two outs. In that case stereo routing is obvious, and that works for Kodi.

I see. Would it be possible to write some config file for kodi so it will recognise the correct input channels, like an asoundrc file?
That sounds easier to me than trying to build le with jack support.
Also, even if the device does not fully report the channels available, it seems a bit extreme to me for le to reboot. Shouldn't there be at least an warning or something?

**Da Flex** · September 6, 2023 at 3:12 PM

No idea, and nobody will do this for you. Easiest workaround: Install Raspberry Pi OS, and autostart Kodi on it. So you'll get JACK.

lich000king · September 6, 2023 at 3:24 PM

Quote from Da Flex

No idea, and nobody will do this for you. Easiest workaround: Install Raspberry Pi OS, and autostart Kodi on it. So you'll get JACK.

I'll try doing it myself. I like le much more than raspios
Maybe somebody can give me some hints, though, that would be great.

**Da Flex** · September 6, 2023 at 3:28 PM

If you want to build your own LE, open a new thread at Development section. We also have basic Wiki instructions.

lich000king · September 6, 2023 at 3:53 PM

Thanks

**chewitt** · September 6, 2023 at 4:32 PM

Can you share the output of "amixer controls | paste" and "amixer contents | paste" ? .. You might need to --help and tweak the commands so they show the output against the USB device instead of the host system audio device.