Frequent playback stoppages due to "Too many failures" message (ref#E0KX08)

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Both streaming and local* *library* music are affected.

Do you encounter any playback errors with the "System Output" Zone?

· The System Output has the same problem as my other Zone.

Do you have a complex network setup?

· I don't have a mesh network, but I use *managed network switches*

Your local network might need some re-arranging to support Roon.

· None of the suggestions have helped me. I'd like to submit a support request.

Do you have an approximate timestamp of when the issue last occurred?

· 11-Jan-2025

What are the make and model of the affected audio device(s) and the connection type?

· xCORE USB audio 2

Describe the issue

I get 'Too many failures. Stopping playback'

Describe your network setup

Roon installed on a laptop, used as a desktop app. That laptop is wired to a router. A USB cable connects it to the DAC. I tried to play local files and got that message. When the same laptop uses as a remote control only, through other Roon servers, everything works well. The DAC is properly identified by Roon Setup/Audio. It doesn't show the maximum resolution etc. but with 'workaround devices that misreport capabilities' I get the same results. Roon seems to be updated.

Hi @raphy.lohev,
Thanks for reaching out to us about this issue. I think the best way to troubleshoot this is to take a look into your logs when the failure is happening. I saw that you said it happened on January 11th but we need a bit more specificity to find the event in your logs. Can you please reproduce the failure and let us know the date and time that it occurred? Once you do we can begin to inspect your logs. Thank you in advance for your cooperation!

Hi daniel,

Thanks for getting back to me.
I can reproduce it of course. Would you like me to send the log file folder (zipped)? If you would, please let me know how should I upload it.

The following ticket seems to be quite similar to what I have:

Hi @raphy.lohev,

That would be helpful. You can upload it here. When you upload please tell us what you named the file to assist in locating it. Also please let us know the date and time of the reproduction in that log set.

Hi,
I have reproduced it and uploaded the entire server logs folder as “Logs_RL_1501_09_31.zip”.
Time: 09:31, 15-Jan-2025, (Israel time).

Thank you.

Hey @raphy.lohev,

Thanks for sending those over! We were able to take a closer look into things, and see the following:

First, Roon sent a setup request to the DAC:
"request":"setup","format{"sample_type":"pcm","sample_rate":96000,"bits_per_sample":16,"channels":2,"sample_subtype":"none"

Then, we see the response from the DAC:
"RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED"

So the the DAC seems to reject the setup request, leading to a failure in playback. The issue is likely caused by a mismatch between the audio format Roon is trying to send and the formats your DAC supports:

  • The DAC doesn’t support 16-bit audio at 96kHz.
  • The original 24-bit/96kHz stream could also be unsupported, leading Roon to downconvert to 16-bit/96kHz, which still failed.

For a next step in troubleshooting, lets see about adjusting your output settings:

  • Go to Settings > Audio > Xcore > Device Setup.
  • Look for the Max Sample Rate and Max Bit Depth options. Manually set these to values that your DAC supports (e.g., 24-bit/96kHz or 16-bit/44.1kHz).

If that doesn’t help:

  1. Test out using the Sample Rate Conversion via MUSE
  2. Test out using both a different cable and port with the DAC

We’ll be on standby for your results! :+1:

Hi @benjamin
Thank you for your reply.
In Windows properties for this device (inside setup), I see that the device enables 24/44.1 sample rate. However, when I try to play 16/44.1 tracks, I get the same results.
It is Windows 11 and I got to the following screen:

MUSE did not change the situation either.

I could suspect this is a matter of device driver, but Tidal desktop application plays very well with this same configuration. That includes 24/192.
In addition, Roon server from a NUC, where Linux is installed + ROCK works well.
So, it seems like a ROON server on Windows combined maybe with Windows specific device.

Please refer to the following ticket where I think someone else reported probably the same problem:

Please let me know what you think.

Hey @raphy.lohev,

Yes, we’ve seen past issues with Xcore in the past, if you’re able to swap drivers, even temporarily, that’d be a worth while test.

We have a ticket in with development that we’ll be discussing later this week - I hope to have more information to share then. Thank you for your patience in the meantime! :pray:

Hi @benjamin ,

What other driver would you suggest?
The only driver for the xCore is the Windows11 system default.
I could not find anything else.
If you can provide a link to some other suitable driver, I would try it.

In the meantime, I tried ASIO4ALL driver. The results were as follows:

  • It did not show any errors, but there was no sound at all.
  • When I set it to ‘private zone’, it worked, but there was noise, together with the music.

So, in general, I still have no reasonable solution.

Thank you for your support.

My apologies @raphy.lohev,

We’ll need to have QA attempt to reproduce this in-house, but unfortunately, we do not have a machine with Xcore available at this time. We’ve added it to the list, but it may take some time before we’re able to get our hands on a similar system.

Would you be able to reproduce this, and share the specific date, time, and name of track attempted to play?

We’ll be monitoring for your response, thank you! :pray:

Hello @benjamin,
I played now a track, closed Roon and uploaded a zip file of the logs folder, as “RoonLogs_2025_02_08_16_54.zip”.
The track was:

It was a 24/192 track and was very noisy. Date: 08-02-2025, time: 16:54.

Thank you for your support.

Hi @raphy.lohev ,

Thanks for sending the logs over, but unfortunately these are the logs for your Roon interface, not for the Roon Server (which is where the errors would be contained). Just to confirm, you were using your “EOS” Roon Server for the attempt?

Looking over the logs for that after enabling diagnositcs, I was able to find the track played, and it looks like it was through the ASIO4ALL driver. Does the same issue happen without ASIO4ALL involved?

Looking over similar dropouts for this zone, I see it only occur when playing local content, has this issue happened when streaming content from TIDAL/Qobuz? If the issue only happens with local content, I suspect it might be related to getting the files from the storage location.

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