Just a quickie with the following improvements:
This last one should improve your situation @James_Fitzell : it should no longer hang.
Thanks!
Hello Harry
thank you for this quick update.
After updating it just says Device not found. I did send feedback: 853e91b14b0a3f37
After a reboot and some retrys: 24d2f0a43b1f69ac
yeah… there is improvement, but still no green light.
I need to figure out what the difference is between your setup and mine. I’ll create another build with some more information.
Are you willing to do some more testing to figure this out?
Thanks
In the earlier beta I had the above “not found” error if the hdmi device was off (in my case a Denon amp)
Yeah, but that’s not the case here. The device is there, my changes to the Roon config have made it in, but somehow it still doesn’t see the device.
Please don’t use the beta channel for generic questions.
yes of course. My small hope is, that i can use the HDMI implementation for multichannel audio purposes. The receiver itself is Roon Ready, but only stereo. I use ropieee at the moment for a second set of speakers at this receiver, so its no problem to test.
RoPieee 2026.05 (3907) [BETA]
Hardware: Raspberry Pi 4 Model B Rev 1.4; 4GB RAM, 16GB disk
Network: wired ethernet
Audio: USB DAC (TEAC) — Roon RAAT, AirPlay2, Spotify Connect, Squeezelite
Display: no
Remote: Flirc — Roon RAAT only
tested convenience switching between all four services, repeatedly
Roon does not recognize the HDMI. Switched the HDMI outputs on the P4, no change. Receiver Marantz AV8802A.
Roon Audio screen
Feedback here ebb36c37a7cea1dc
Regards
Was the receiver on at the time? I’ve had the same result with a Denon (like Marantz) while the receiver is off.
Same thing here with an Onkyo RZ730 latest firmware.
Yes, and I checked that the HDMI port was correctly configured and active.
Yes, have mine on and no change. Maybe Roon does not read the HDMI status signal correctly.
Works through a Win 11 Wasapi without a problem
Yeah as mentioned: with Roon there’s something still not working as expected. Spend the weekend figuring this one out, and I think I might have solved it…
So preparing a next beta build that addresses this.
