Nucleus+
Fortinet Firewall and managed switch
Piega Roon Ready Connect plus
4’000
Tidal keeps skipping tracks, no issues when playing Tidal directly in their webapp.
Modified title for clarity.
What if you bypassed the managed switch and just connected it to a dumb switch like a GS108 netgear? Also, you might review the networking faq and the topics on managed switches.
Hi @Renzo,
Thanks for writing in to us about this issue. I want to echo what @Rugby said above. Managed network switches aren’t really recommended for use with Roon unless you’re a networking professional. As for your firewall make sure you have whitelisted the Roon associated processes (e.g. Roon, RoonServer, RAATServer).
Let us know if this works out for you.
Thanks @Rugby and @daniel for your inputs.
I had my network professional work on the managed switch, but still experience problems when streaming (i am not being stubborn, i will try to get a normal switch in, it’s just a lot of tinkering to do). while we were at it today, I’ve noticed that the issues arises only with high quality files 192 kHz 24 bit will skip, 44 kHz 16 bit will play just fine. Still, the webplayer would also play the 192kHz files.
my connection is not the best (just a 100 Mbit Download rate and some latency too). so, the question that arises, is it the bandwith with the larger files or could the latency be an issue. I feel like there’s no sense in tinkering if the bad internet connection is causing all the problems.
any thoughts on this from your part?
thanks again for your help, much appreciated!
Renzo
Hi @Renzo ,
Does this issue happen for any other zones or just one in particular? Do you have any way to test the main Roon Server output to see if it occurs (such as HDMI output on your Nucleus)? This way the additional network traffic is bypassed and you can gauge direct speed from the Nucleus output. Testing the non-managed switch would be a good idea as well, so do let us know how this goes.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
Hi @noris
thanks for that input, it never occured to me, that the zone could be the issue, but suspected a problem at the roon server / source. rebooting the zone player did the trick. thanks for your help and sorry for bothering.