Hello @spockfish - Roon recommended I get you involved. They have supposedly eliminated anything from the Roon Core side of things being the cause of my issue by looking at their logs on my system.
And they also suggested I generate a unique identifier in the RoPieee web interface - here it is:
09e01e475d826ea9
The issue is a previously very stable zone now intermittently drops music momentarily. This just occurred at approximately one minute into listening to the Foghat song “Slow Ride” from “Foghat Live.” The zone in question is not grouped when this error occurs, although it happens when it’s grouped, too. The problem occurs randomly and cannot be purposely repeated, but it typically occurs within an hour of beginning a listening a session.
The Roon Endpoint is a Raspberry Pi 4 running RoPieee; audio for this zone is output via S/PDIF coax from a HiFi Berry Digi + HAT to a Project Head Box S2 Digital DAC/headphone amp.
My network is all new. Top-line TPLink Router, connected to a new TrendNet 16 port gigabit Ethernet switch, to which all of the Roon components in my system are connected via Ethernet. Every single Ethernet cable is new.
I am really at a loss here: I have had Roon for years and this is something I’ve not seen before, and that includes many running RoPieee as its OS.
Your unit takes a long time to get on the internet when firing up. Way too long. That usually points to network issues (why is your router so slow in responding to DHCP requests?). Next to that I also saw some warning coming from the Hifiberry HAT. Not sure if it’s critical, but it should not do that…
I suggest you first try to eliminate the network… have you tried resetting your router? And is everything in the router ‘as default as possible’ or are their changes made to the configuration?
And check if the HAT is properly connected as well. Do you by any means have a USB DAC lying around? With that you can eliminate the HAT as potential source of the problem…
Thanks much for this. In response: Baffled at the network issue you suggest - the router (TPLink BE3600) is brand-new and the only changes I made is to use 8.8.8.8 and 1.1.1.1 as DNS, everything else is default. This problem existed before and after I replaced my router (and all network cabling), and it’s been reset since, so that doesn’t fix it. There is a new 20 foot Ethernet cable connecting my router to the switch to which the Endpoint in question is connected.
The HAT is definitely pressed firmly onto the Pi. I do have a USB DAC, but using it with the same gear would require using it via WiFi (strong signal) vs. Ethernet. Is that your recommendation?