Tidal FLAC tracks not playing on NAD M10 v2 (ref#R9IL8Q)

What best describes your playback issue?

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

What type of Zone is affected by this problem?

· *Network Zones* are affected.

Is the affected network Zone connected with Ethernet or WiFi?

· Ethernet

Does the issue affect all file formats?

· The issue *only affects one file *format.

Which format is giving you trouble?

· FLAC

Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?

· It is connected through a different device (e.g Rasberry Pi)

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

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

· NAD M10 V2

Describe the issue

Not Playing certain Tidal FLAC tracks via Roon Ready (on M10 v2)

Describe your network setup

Asus Router (all wired)

One example album is “Passenger” by Maxence Cyrin.

Playing to different device works, just not M10 V2.

Also using AirPlay2 on M10 V2, just not via direct Roon Ready.

Hey @RoonFan,

Thanks for taking the time to write in and share your report!

To confirm, you are seeing these failures over both Airplay as well as Roon Ready?

If you haven’t yet, please safely stop Roon Server from running, and reboot both your Roon Server as well as your NAD.

Let’s also refresh your RAATServer database settings -

You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

  • Create a Backup of your current Roon database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the Roon App to generate a new RAATServer folder

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

Hi @benjamin

You’re absolutely right that my earlier statement, “Also using AirPlay2 on M10 V2, just not via direct Roon Ready,” was unclear and caused confusion. What I meant to say is:

“On the other hand, when sending the same TIDAL tracks via the AirPlay2 protocol to the M10 V2, the tracks play normally. In short, the issue occurs only when using Roon Ready direct playback.”

I appreciate you sharing the troubleshooting instructions, but I’m hesitant to proceed with a reset right away due to the extensive customizations I’ve set up, including DSP configurations. Rebuilding everything would take considerable time if something goes wrong during the reset process. Could we explore less invasive troubleshooting steps first and reserve a reset as a last resort?

Currently, this issue doesn’t affect all TIDAL FLAC tracks—just a few, such as the album I shared earlier. Since the problem is relatively contained, I’d prefer to avoid drastic measures unless necessary, especially if there’s a simpler solution available. Thank you again for your support!

As expected, the album is 88.2 kHz sample rate. It is a longstanding NAD problem.

https://community.roonlabs.com/search?q=Nad%2088.2%20order%3Alatest

AJ

1 Like

Thanks @WiWavelength for this resource.

This begs the question: how could a bug like this have persisted for so long?

Look here NAD M33 won't play 88.2KHz 24 Bit with roon?!?.
Think it offers the best workaround. Resampling of spec. sampling rates in roon :+1:t3:

2 Likes

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