Track Pausing Causes Playback Delays and Skipping (ref#G738D6)

What’s happening?

· I am experiencing freezes or crashes

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

When I pause a track even for a few seconds and then press play, or drag the time bar a bit, one of three things will occur: Either it takes up to a minute to resume playing, stays frozen until I restart Roon, or it shows the “Tidal (or Qobuz) loading slowly…” message and skips to the next track. Rebooting the core doesn’t help.
Thanks for any assistance.

Describe your network setup

Bell 3000 modem. Core: Intel NUC NUC7i3BNH on ethernet running ROCK. Roon version 2.0 (build 1496). Running Roon on Mac OS 13.7.2.

What’s happening?

· I am experiencing freezes or crashes

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

When I pause a track even for a few seconds and then press play, or drag the time bar a bit, one of three things will occur: Either it takes up to a minute to resume playing, stays frozen until I restart Roon, or it shows the “Tidal (or Qobuz) loading slowly…” message and skips to the next track. Rebooting the core doesn’t help.

Describe your network setup

Bell 3000 modem. Core: Intel NUC NUC7i3BNH on ethernet running ROCK. Roon version 2.0 (build 1496). Running Roon on Mac OS 13.7.2.

Hi @Seymour_Stern,

Thank you for your post. I’ve merged your two threads together, since they appear to refer to the same symptom. We’ve activated diagnostics for your RoonServer instance to examine these failures events more closely.

We see RoonServer establish an initial connection to Tidal and begin to download the content to RoonServer’s buffer cache. However, requests to streaming servers almost immediately begin to time out - furthermore, RoonServer reports that samples are dropping out in the stream from Tidal, and it begins to re-request these missing samples. In some cases, the missing samples never arrive in time, forcing Roon to tear down playback. This occurs more frequently when the cache doesn’t have a large amount of data stored, like after scrubbing the playbar, rapidly skipping tracks, or pausing/resuming.

To troubleshoot this efficiently, we’ll need to know the network pathway between ROCK and the internet, including any WiFi-reliant components like access points or mesh nodes. I recommend changing the assigned DNS server in your router to Cloudflare (1.1.1.1) or QuadNine (9.9.9.9), to verify that the Tidal API addresses are resolving reliably.

Do you have any additional routers or managed switches other than the Bell 3000?

We’ll keep an eye out for your response. Thanks!

Connor, thanks for setting up this direct support thread.

I have no additional routers or managed switches other than the Bell 3000.

I changed the assigned DNS server in my routerto Cloudflare (Primary 1.1.1.1; Secondary 1.0.0.1; Host: mynetwork,monreseau,home). This appears to have solved the problem.

However, perhaps unrelated or not to the above, when I access Roon after leaving it open on the Mac for a few hours, the queue disappears for an extended time, and it could take up to a few minutes for the currently playing track to appear. Sometimes the track list and track don’t appear and I need to restart Roon. When I do, I often get a ‘Searching for Roon server’ message (even though I’m in the same room as the router), and it takes another minute or two to connect.

Any suggestions?

Thanks for your support with these issues.

Hey @Seymour_Stern,

Glad to hear changing the DNS helped!

We’d be happy to take a closer look, but in order to do so, we’ll need a more specific date, time, and if possible, name of track playing. From there, we’ll enable diagnostic mode for your ROCK/Mac and take a closer look.

We’ll be monitoring this thread for your reply. Thanks! :+1:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.