Pi 4 USB to Hegel H190. No sound

Audio Gear Talk RoPieee
30

if you are still willing to troubleshoot this issue further and understand what/why it’s not working, there a few more thing you can try; but it’s recommeded that you know your way around a Linux system, so you don’t struggle on this journey

  • test RoonBridge installed on DietPi
  • test RoonBridge installed on Raspbian OS

document your journey so you can compare those two variations with your know good solution - moOde player (i assume here that you can gain shell / console access to rPI runninng moOde and collect similar details)

  • kernel version
  • audio devices (aplay -l) / alsamixer volume settings / amixer controls / amixer contents
  • your DAC’s capabilities (aplay -l -D “your DAC” -d 5 --dump-hw-params /dev/null)
  • your USB DAC’s capabilities/settings as viewed by the kernel / USB subsystem (lsusb)

if moOde player works fine, then the only logical conclusion (to me) would be that the kernel or ALSA configuration was tweaked to handle the Hegel DAC

1 Like
31

I’m so grateful that you want to help, but Linux is outside my knowledge - except to follow simple scripts! I tried to install ROONbridge on Moode and didn’t manage it….

I’ll take my time and work through what I can and keep updating the thread in case anyone else hits this problem

32

Maybe narrowing the problem down….

Advice on the Hegel Facebook group was to connect the ROON core usb to the amp - much unplugging and moving later the ROON core usb works!

This isn’t a solution (I’d need 20m of usb cable or a house rebuild) but it must be the Pi now that is the issue.

As @spockfish noted in the beginning, the amp does show as two connections, digihug usb audio usb audio and digihug usb audio usb audio #1. Both work with one connected to the ROON core and one disabled, but not when connected to the Pi4.

Next up, try a different Pi (more unplugging and crawling on the floor).

Once again, thanks to all for your interest and help.

33

Good grief - an old Pi 3b works fine, so it is the Pi4 at fault.

More work to do, but thanks to everyone here again.

34

Have I entered an alternate universe?

So the old Pi3 worked, so re-flashed (again) the card for the Pi4 and tried again….

It worked! But - now the screen doesn’t show anything other than ‘connection failure’:thinking:. Tried several resets and settings/zones seem to be ok.

@spockfish if you would be so kind, feedback is d989b442ffcf58a5

35

Have you enabled the extension in Roon?

36

Isn’t it always the obvious thing that catches you out!?

I have no idea or explanation as to what was going on over the last 3 days! I hope it wasn’t idiocy on my part.

37

I’ve had issues with my Pi4 going missing (in fact is is missing right now) but never the Pi3B’s. Not sure what the explanation is but at least in my case the Pi4 is less stable than the 3B.

38

That is interesting. I got the impression that the Pi4 connected easily after the Pi3 had initiated the conn3ction.

39

As further troubleshooting, try configuring one or more of the RoPieeeXL endpoints such as Airplay, uPNP/DLNA or Spotify to see if they work (that would take Roon out of the picture for the purpose of this test).

If Airplay worked, you could try configuring Roon to play via Airplay (I believe this is possible, but I don’t use Roon)

40

Final update - the outcome may be lost as a reply to an earlier post.

No idea why it failed to work, but it is now working ok.

Switching to an old Pi3 connected to the amp and worked fine, and after that re-flashing the Pi 4 sd card (which I had done several times already), the Pi4 connected and has worked fine since.

One of life’s mysteries…. Thanks again to all here for the advice.