Since the last 1.8 update playback jumps like a damaged record!

Roon Core Machine

Networking Gear & Setup Details

Connected Audio Devices

Number of Tracks in Library

Description of Issue

Bummer! what did you do?
Since the last 1.8 update Feb. 2022 playback jump like a damaged record!!!
Was fine before the update.

Hi,

In order for Roon’s @support team to better assist you, please provide a brief description of your current setup using this link as a guide.

Make sure to describe your network configuration/topology, including any networking hardware currently in use, so they can have a clear understanding of how your devices are communicating.

Using Roon Rock installed on a NUC connected directly on (the main) Google Wifi router. I have 3 other Google Wifi points in the house, very strong network without problems. All my devices using Roon are cable connected to the routers.

Problem is happening often both on my PC and Ifi Stream. Both of which worked flawlessly before the recent update.

Is there a way to go back to the previous build?

Hey @Jean-Pierre_Deslande,

We’re terribly sorry about the issues that started coming up after the release of the latest build.

You mention that nothing has changed in your setup, but playback skips. While we don’t support downgrading (here are a few reasons why), we’d love to help sort this out.

You say you experience these playback issues on your PC (is this System Output) and your endpoint (the iFi Stream). What is the source of the music you’re trying to play?

Tidal. Mqa most likely.
Thanks

Thanks for that!

Would you please continue to help us with a few more answers?

  1. If you play directly from TIDAL to your audio system, is there any interruption in playback?
  2. Could you please play separately to each zone individually? Is playback interrupted for each and every zone?

What would be really really great, was if you could change your Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. That would tell us if the problem lies with getting the streaming information from TIDAL, or, if it’s something environmental (connection between Core and devices, bandwidth, one of the devices themselves, and so on). Please, let us know if you can give this a try :slight_smile:

1 Like

Hi beka
My network in very fast (over 600Mb/s in each direction) and all has been working flawlessly for at least a couple of month before the update. Nor planning to change anything there.

Yes things work better using Tidal Connect, but I don’t use it much.

It happens in all zones, one, the PC, uses Ifi DAC, the others have Ifi Stream (before I used Bluesound Nodes which i found less stable…), all USB connected and Ethernet cable used for Roon Core and all devices.

Happened a couple of times today, each time I saw the dreaded message: Tidal media is loading slowly. Funny, I don’t know if this is a thing, but it seem to happen mostly on very well known music (big rock bands classics, that sort of thing), but rarely with classical and jazz and less known stuff.

My network uses Google DNS.

Glitches occurring again…

Hey @Jean-Pierre_Deslande,

I want to take this to our technical team so they can take a look at what might be going on. Since they only return to work on Monday, I was wondering if you’d be able to answer a couple more questions:

  • is there any issue if you play to System Output (first, please enable it in Settings → Audio and then select it as a zone)
  • is there any change if you:

Log out of TIDAL in Roon and then quit Roon
Stop Roon Server from running in the Web UI
Find and open your RoonServer database
Navigate to RoonServer/Cache
Move the contents of the /Cache folder elsewhere, like your desktop
Try restarting Roon Server via the WebUI
Log back into TIDAL in Roon

If you could also please take a moment to explain exactly the topography of your setup, that would really help our technician (audio devices, how are they connected, what router/modem/switches, etc.).

Many thanks :pray:

Hi beka,

Did switch to System output of the PC, only thing is that MQA not fully resolved (green dot), unlike when I set the output to iFi DAC V2.

I did reinitialize the Core and Tidal and removed the cache as you instructed, system is now running.

We’ll have to see if it made a difference, that cache was sure large

Here’s my setup

Roon ROCK runs on Intel NUC Intel Core i7 (Intel NUC mini PC kit NUC7i7BNH (Intel Core i7))
8GB RAM
250 GB internal SSD
2 TB Sandisk SATA III SSD

Router: Google Wifi system (set of 4).

ROCK NUC Connected directly (Ethernet cable) to the main Google router which is connected to provider device (Bell’s Home Hub 3000), our internet service is 1Gb/s up/down unlimited.

Setup 1 (I have 2 of those connected to different amps in the house): Ifi stream (up to date firmware), connected directly (Audioquest Ethernet cable) to Google meshed component, Stream connected to DAC Topping SE90 via USB (Audioquest cable)

Setup 2:
Windows 11 PC - ICore 7 16GB RAM 500GB SSD + 2TB SSD SATA connected directly (Ethernet cable) to Google meshed component, Sound output via USB to IFi DAC V2 then RCA to Topping PA3 Amp.

Also use Roon directly on iPhone (12 Pro) and FiiO M11 Pro sometimes, not the most stable … but I’m not really concerned about that.

Thanks.

Hey @Jean-Pierre_Deslande,

I’m very grateful that you made it a priority to try the suggested steps over the weekend :pray: . We appreciate the answers and details.

You say “the system is now running” — does this apply to all of your devices, or just PC System Output?

We’d love to know what are the symptoms of the issue right now, if any, so we can help resolve them :nerd_face:

All, but most important to me is the Ifi Stream.

Several cuts Sunday morning, ok since then.

Problems I see in the logs (Tidal issue?:

02/06 16:14:02 Trace: [D90 Chambre] [Lossless 69.8x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [100% buf] [PLAYING @ 1:46/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:07 Trace: [D90 Chambre] [Lossless 69.7x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [100% buf] [PLAYING @ 1:51/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:08 Trace: [D90 Chambre] [zoneplayer/raat] sync D90SE: realtime=4357307464708 rtt=1500us offset=-127657535us delta=686us drift=-3520us in 519.864s (-6.773ppm, -24.382ms/hr)
02/06 16:14:11 Warn: FTMSI-B ti/13EED1DD: block downloader too much time waiting for block request
02/06 16:14:12 Info: [stats] 23577mb Virtual, 1337mb Physical, 400mb Managed, 338 Handles, 99 Threads
02/06 16:14:12 Trace: [D90 Chambre] [Lossless 69.8x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [100% buf] [PLAYING @ 1:56/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:17 Trace: [D90 Chambre] [Lossless 69.8x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [100% buf] [PLAYING @ 2:01/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:21 Warn: FTMSI-B ti/13EED1DD: block downloader too much time waiting for block request
02/06 16:14:22 Trace: [D90 Chambre] [Lossless 69.8x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [100% buf] [PLAYING @ 2:06/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:25 Debug: [easyhttp] [3101] POST to https://swim.roonlabs.net/1/session/220ec320b70244bb80150e2441db6b35/ping returned after 176 ms, status code: 200
02/06 16:14:27 Info: [stats] 23577mb Virtual, 1337mb Physical, 404mb Managed, 338 Handles, 100 Threads
02/06 16:14:28 Trace: [D90 Chambre] [Lossless 69.8x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [100% buf] [PLAYING @ 2:11/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:31 Warn: FTMSI-B ti/13EED1DD: block downloader too much time waiting for block request
02/06 16:14:33 Trace: [D90 Chambre] [Lossless 69.9x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [54% buf] [PLAYING @ 2:16/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:38 Debug: [prebuffer] sleeping in read -- this isn't good
02/06 16:14:38 Trace: [D90 Chambre] [Lossless 69.9x, 24/48 MQA TIDAL FLAC => 24/48 MQA] [4% buf] [PLAYING @ 2:22/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:41 Warn: FTMSI-B ti/13EED1DD: block downloader too much time waiting for block request
02/06 16:14:42 Info: [stats] 23577mb Virtual, 1337mb Physical, 403mb Managed, 338 Handles, 100 Threads
02/06 16:14:43 Trace: [D90SE] [raatclient] GOT [73] {"samples":480,"status":"Dropout"}
02/06 16:14:43 Trace: [D90SE] [raatclient] GOT [73] {"samples":24000,"status":"Dropout"}
02/06 16:14:44 Trace: [D90SE] [raatclient] GOT [73] {"samples":24000,"status":"Dropout"}
02/06 16:14:44 Trace: [D90SE] [raatclient] GOT [73] {"samples":24000,"status":"Dropout"}
02/06 16:14:45 Trace: [D90SE] [raatclient] GOT [73] {"samples":24000,"status":"Dropout"}
02/06 16:14:45 Trace: [D90SE] [raatclient] GOT [73] {"samples":24000,"status":"Dropout"}
02/06 16:14:46 Trace: [D90SE] [raatclient] GOT [73] {"samples":24960,"status":"Dropout"}
02/06 16:14:46 Warn: [D90 Chambre] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
02/06 16:14:46 Trace: [D90 Chambre] [zoneplayer/raat] too many dropouts. stopping stream
02/06 16:14:46 Trace: [D90 Chambre] [Lossless, 24/48 MQA TIDAL FLAC => 24/48 MQA] [4% buf] [PLAYING @ 2:26/6:18] Sympathy for the Devil - The Rolling Stones
02/06 16:14:46 Trace: [D90 Chambre] [zoneplayer/raat] Endpoint D90SE State Changed: Playing => Prepared
02/06 16:14:46 Trace: [D90SE] [raatclient] SENT [75]{"request":"end_stream"}
02/06 16:14:46 Debug: [raat/tcpaudiosource] disconnecting
02/06 16:14:46 Warn: [zone D90 Chambre] Track Stopped Due to Slow Media

Hey @Jean-Pierre_Deslande,

I wanted to simply chime in to let you know that our technical team has already taken a look at the information you’ve shared and they’re still investigating. We’ll follow up as soon as we have an update :nerd_face:

Hi @Jean-Pierre_Deslande ,

Your symptoms match the issue discussed in the following thread:

Please reference that thread for any updates on this issue, thanks!

1 Like

Ok, it seems appropriate, glad to know your team is working on interface with Tidal. Thanks.

1 Like

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