So I spend days rerouting cables, redirecting traffic, tweaking my network this way and that. I was able to reproduce my Roon hiccups here and there. What worked on a fast platform, like triggering a Roon reboot with the Senec box, did not work on a slow system - there Roon would reboot with or without that Senec box. Simply connecting my Roon Ethernet trunkline to the guest subnet worked one day and not the other. Moving that trunkline from my fully ocupied 16 port switch directly to a Fritzbox seemed to help a bit.
I looked at the diagnostics of my Fritzbox. It shows that everything is fine - but then I got frightened the work I put into the network over years: 10 meshed access points (big house and garage/garden), 100+ WiFi switches and WLAN thingies, 20 LAN thingies, 30 U-Dect devices all linked to mater and then to Alexa. Well, yes.
I deleted old connections, removed Roon’s port access (no ARC then) and prioritized the main Roon endpoint, a Nad 778 and renamed it.
I have been listening to Roon for 3 hours now and everything is working. Or may be it was all a glitch by the fibre company changing something and pulling my leg all the time. Or Roon‘s network streamshaping had a bad week.
I am afraid the problem will reappear. It would be great to know if the logs say anything. Would a dedicated Linux box help?
Well, that was interesting. No support from Roon for me, except for trivial stuff. Sure, I bought a licence and use my own hardware - why bother? And I get it: Streaming music that Roon has no rights to and preventing the user from saving it creates such an overhead that you “need a perfect network”. I can now go two ways: use Bluos instead of Roon and organise the music in Qobuz or get a Roon Linux box. Maybe that will buy me some support? Or sells me completely to an overcomplicated system where nobody seems to know his stuff operating on a shoestring.
Hey @Joachim_Strobel,
Thanks for your patience! Please note that while we don’t believe the issue is related to your network setup, commercial-grade networks unfortunately fall outside the scope of Roon’s technical support.
That said, we were able to take a close look at a fresh diagnostic report from your Roon Server, and saw repeated crashes right around the time Roon attempts to identify and connect to Type=wasapi Name=HD Audio Driver for Display Audio
.
More specifically: Error: [14] [RAAT::System Output] [output/wasapi] [2- HD Audio Driver for Display Audio] Failed to activate IAudioClient HRESULT=0x88890004
Would you be able to temporarily disable and remove this driver, and see if your issue persists?
If rebooting does still occur, it may be good to review any potential windows event viewer logs for additional details. Here’s more info on this:
- Press Win + R and type eventvwr.msc
- Press
OK
– this should openEvent Viewer
window - From the left sidebar go to Windows Logs > Application
- Right click on the
Application
subsection and pickFilter Current Log...
from the context menu
- On the
Filter
tab for theLogged
section pick a parameterLast 30 days
and pressOK
- Right click on the Application subsection again and pick
Save filtered log file as..
from the context menu - Enter the log file name, for e.g.
Roon_USERNAME
, and pressSave
- Upload the Event Viewer logs here and let us know once you’ve done so:
https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external
Thank you!
Benjamin,
You bring up a valid point that I did not write: While troubleshooting I used the local audio output from my PC. That happened to be the hdmi port feeding into a loudspeaker free monitor. I created Roon crashes, but looking back they seem to have been created by that internal audio output. So I probably solved my problem early by rerouting some Ethernet stuff but failed to see it as I observed crashes using internal audio believing that that would be more robust than streaming to the NAD. I can not recreate all and am happy that things work now.
Another issue has been that my appleTV and my Nad T778 had the same name on my net („Wohnzimmer“, Apple TVs default name in Germany) while of course having different IP addresses. But I am not sure if that did cause trouble or it only seemed that way.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.