So a while ago I posted that I had some difficulties in getting Roon to see the full audio capabilities of my HDMI connection. I wrote it up in a blog here:
So, after completing those changes, my Roon bridge correctly identified my receiver’s capabilities, up to 196k/32 bits. I’ve been running like that since November 10th. All this time my receiver (Anthem MRX 540) has been happily getting high resolution music and upsampled Internet radio.
At some point over the past week I accepted all the upgrades and this has now completely broken. The UI says it can’t detect my high res connection and only plays at 44 kHz.
I know this installation is probably bleeding edge, but if you could take my observations into account and offer me tips to restore my full bandwidth HDMI output I’d really appreciate it.
So, I stand by my blog post, but the issue I had today was not due to any Roon bridge changes. It was my fault. I recently had to move my Pi5 out of the way while I re-wired my home theater setup. When I reconnected it I ended up using the wrong HDMI port. The high resolution audio hack I provide in my blog only works on HDMI-1, but not HDMI-0.
Sorry to trouble you, but if you want to consider updating future versions of the Roon bridge so we don’t need this hack that would be great.
Best,
Erik
mjw
(Here I am with a brain the size of a planet and they ask me to pick up a piece of paper. Call that job satisfaction? I don't.)
3
I think the issue is more likely some peculiarity with your installation. Whilst Oracular uses Pipewire, ALSA is installed by default, yet you say you had to install it afterward. This is a dependency for Roon Bridge.
I’d start with:
sudo apt install --reinstall libasound2 alsa-utils --yes
sudo alsa force-reload # no need to reboot
You can check the devices using aplay -l. Incidentally, a working Roon Bridge does not need that JSON file.
Moreover, you should not be running 24.10 now as support ceased last July. Either stay with an LTS or do a distribution upgrade every six to nine months.
Thanks for circling back and for the clear follow-up — glad to hear this turned out to be the HDMI port (HDMI-1 vs HDMI-0) and that you’ve got high-res output working again.
Since the root cause is identified and resolved on your end, we’re going to go ahead and close this thread out.