Server running core and the network receiver are both connected via ethernet.
Number of Tracks in Library
66,000
Description of Issue
Hello,
I get cutouts in my music that are about 2 seconds long and happen frequently on each track (~5min tracks) that are played locally from a file on the same file system where the core is running to my Denon PMA-150 receiver. Oddly live streams from the roon seem to play fine with no cutouts.
I’ve also noticed a weird thing when trying to go to the next track on my list by clicking the forward button. It puts my Denon into AirPlay mode (I have no Apple devices) and I can’t get out of it by manually choosing another track on Roon or trying to play another album. I have to go to the Denon and restart it to get it to “work” with Roon again.
I’m confused - the Denon is not Roon Ready, so as far as I know, the only way for Roon to communicate with it over the network is to use Airplay.
Can you post some screenshots of Roon’s settings for the Denon (Settings > Audio, and the details of the device setup screens for the Denon connection in Roon)?
Yes it’s a somewhat old processor but the CPU usage on the machine is below 30%.
My Unifi switch is configured with VLANs. The Denon is on the IoT network. The NAS is actually on both the Main network and IoT (it has two NICs). But you could say the roon core is on the Main network since the IP it sees in the roon Settings is the IP on the Main vlan.
On that note, my Main vlan has full access to devices in the IoT land. I also have Multicast and IGMP snooping enabled on all lans. Furthermore I have a rule to allow established and related traffic states back.
Roon does however play fine on my computer and mobile phone. It could be because they are on the same network (main). Is it possible to change the IP (nic) that roon core should use or is it auto configured?
Hmmm, this is quite frustrating… Here are the things I’ve done.
Scenario A
Made a copy of my roon server directories. (rsync -rav …)
Stopped my current roon server.
Booted up a new roon server using the new directory and pointing to my second NIC on IoT Networks.
Problems
The Roon app cannot find Roon core running on a separate network (vlan) even though it has complete access to the vlan.
If I switch my network on the device running the roon app to IoT then it will find the Roon core. This is not ideal. Audio sources are all missing too. Won’t even see the speakers on itself. Is this in the server directory somewhere that can be fixed or wiped out so Roon can fix itself?
Scenario B
Move Denon into main network and fired up original roon server.
Seems to be no intermittent cutting out anymore but it’s quite annoying that this is a snowflake issue with this device.
Thoughts…
Do ya’ll know if this is only an issue with AirPlay on separate vlans? Would I have similar issues if I install roon-bridge to communicate to my Denon receiver?
(Although I still have hopes of solving the AirPlay issue without additional hardware)
Are you able to reproduce this issue when running Roon on another core not running through Docker Container? Unfortunately, our scope of support does not cover running your core on a Docker container, so our reach here won’t be very far.
Let me know if this is possible, in which case we’d be happy to help!
