· I am experiencing freezes or crashes
· None of the above
· Other
please refer to EB1F08
see EB1F08 I get this error message when playing through my NUC but NOT when playing ROON via my Win11PC. Is this related to the drop outs?
Good day @Harald_Hespe !
I hope you’re doing well today.
Thanks for sharing your problem here.
Could you please introduce a bit more of details regarding this problem ?
You mentioned that you experience a dropouts and the title of the thread and problem description are a little bit controversial.
Can you please clarify where do you experience dropouts and if possible under which circumstances ?
Why do you think xcore driver has something to do with it ?
Also, the screenshot you have provided, does it correlate with your problem ? Because screenshot itself is not indicating the issue withdrouputs.
Also, we’d appreciate if you could provide the time stampts (exact time and date) of when does dropout happen to you.
Thanks!
Looking forward to your reply!
Regards.
Hi @Harald_Hespe,
If you’re referring to the “Metadata Improver: Paused” notifcation, RoonServer is usually having issues resolving URLs with upstream services.
Please follow the suggested steps here and let us know if this helps:
As for the dropouts, we’ll need more information to take action on that report. Please provide the details @alex_h has requested in the post above to equip our team to investigate.
Thank you!
Hi again, I am sorry for the heading of this issue which obviously is wrong. I don’t know where it came from…
Hello @Harald_Hespe ,
Glad to hear that the DNS change helped with the metadata improver issue. As for the dropout issue, we are looking into this with our dev team. Just to confirm though, the issue happens when both the NUC and the Win 11 PC are being used as Roon Servers? Or was that message just referring to the metadata improver error?
Hi, and thanks for feed back. I get drop outs only when playing Roon through my NUC. I have not noticed any drop outs with Roon on win11 pc.
Further on, maybe not relevant but it seems the drop outs happens typically in the first hour or 1/2 hour of a listening session after powering on the system. (The NUC is on always)
Pls let me know if you need more info.
Best regards
Harald
Hi @Harald_Hespe,
If you can, please reproduce the issue and share the specific track name the next time it happens. From there, we’ll enable diagnostics for your Roon Server on your NUC to investigate further.
Thank you! 
Hi Benjamin, I started up my system at 07.30 approx and played a Bach violin Concert. (good breakfast music) at 07.59 I had two short drop outs.
Hey @Harald_Hespe,
Thanks for sharing the above timestamp! We were able to capture it and review a fresh diagnostic report around that time, and observed the following:
First we see a poor connection trace:
Warn: FTMSI-B-OE qo/F9EFF959: poor connection kbps:4830.0 (min:5307.0) This is critical. It means Roon’s file transfer manager (FTMS) measured that the available bandwidth to the Aries dropped below the minimum required for the 192 kHz stream (after DSP to 32/192).
At 24/192 FLAC → 32/192 PCM, the stream requires roughly 6–10 Mbps sustained. Your device saw 4.8 Mbps, below the threshold of 5.3 Mbps.
Then we see:
dwStatus:AllBlocksDownloaded files:0 accessTimeOut:TrueThis means Roon requested blocks of the track, but the Aries didn’t retrieve them in time, even though the track was fully downloaded.
This often means the Aries couldn’t be fed data fast enough over RAAT.
And then, we see the dropouts themselves:
11/21 06:58:20 [Local 11/21 07:58:20] Trace: [AURALiC ARIES_G1 @ 192.168.50.171:57834] [raatclient] GOT [27] {"samples":64328,"status":"Dropout"}
11/21 06:58:20 [Local 11/21 07:58:20] Trace: [AURALiC ARIES_G1 @ 192.168.50.171:57834] [raatclient] GOT [27] {"samples":96000,"status":"Dropout"}
11/21 06:58:20 [Local 11/21 07:58:20] Trace: [AURALiC ARIES_G1 @ 192.168.50.171:57834] [raatclient] GOT [27] {"samples":96000,"status":"Dropout"}
11/21 06:58:20 [Local 11/21 07:58:20] Trace: [AURALiC ARIES_G1 @ 192.168.50.171:57834] [raatclient] GOT [27] {"samples":28800,"status":"Dropout"}
11/21 06:58:25 [Local 11/21 07:58:25] Trace: [my Aries] [Enhanced 36.6x, 24/192 QOBUZ FLAC => 32/192] [100% buf] [PLAYING @ 0:42/5:15] Violin Based on the logs, the problem is between your Roon Server and the Aries, not between Roon and Qobuz.
A few next troubleshooting steps for you to try:
Let me know how the above go - thank you! 
Hi Benjamin and thanks for all the analysis!
I will come back within a few days and report if the drop outs still remains.
Best Regards
Harald
Hello @Harald_Hespe ,
Thanks for letting us know regarding the proposed testing. Yes, please let us know how it goes.
We have sometimes seen switches failing, so it is possible that this is what is occuring here. If you have no issues with WiFi, it is also suggested to try a different (unmanaged) switch to see how that behaves.
Hi Again, latest status report:
Hello @Harald_Hespe
Thanks for the update, Harald — that’s very promising news!
Since replacing the switch seems to have resolved the dropouts so far, please continue to monitor the system over the next few days.
Let us know how things behave and whether the issue stays fully resolved or if anything returns.
We’ll be here to follow up once you report back.
Hi Guys, the drop out problem is solved. I have been playing a lot >15h the last 3-4 days without any hick ups! Thanks for superb support and help to solve this issue!
Best Regards
Harald
Hello @Harald_Hespe ,
Glad to hear the new switch is working out well, this is wonderful news. I’ll go ahead and mark your thread for closure, happy listening!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.