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)?
· Connected directly to my RoonServer machine
Does the device show up at all in Roon Settings -> Audio?
· Yes, it shows up there, but it isn't Enabled
Does the "Enable" button unlock the Zone?
· I can Enable the Zone, but the Zone disappears
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
Do you have an approximate timestamp of when the issue last occurred?
· Has been happening for weeks, I don't think this ever worked.
What are the make and model of the affected audio device(s) and the connection type?
· Linn Klimax DSM/2 with Katalyst DACs and/or Exakt
Describe the issue
Roon thinks my Linn DSM/2 is a Linn DSM/3 so sends DSD directly since it thinks my DSM has an Organik DAC, however it only has a Katalyst DAC and hence requires DSD to be translated.
I have attached an image of the Signal Path from my Roon Server to my Linn Klimax DSM/2. Note the icon for my Linn Streamer illustrates a Linn Klimax DSM/3 which does handle DSD natively.
Thank you for the screenshot — this is very helpful.
We`ve been in touch with Linn regarding the behavior you’re seeing. Based on their feedback, your Klimax DSM/2 should support native DSD playback, but there is one important exception:
If your system includes Exakt speakers, DSD is not supported over the Exakt link. In that case, the expected behavior is that DSD must be transcoded to PCM on the Roon Core before being sent to the DSM.
To confirm where things stand on your system, Linn has asked us to gather a bit more detail from the device itself. The easiest way to do this is to generate a diagnostic report directly from your Linn system:
Please do this just after attempting to play a DSD track that fails:
Open either the Linn app on iOS/Android or
the Manage Systems web interface.
Use the Report to Linn feature to send the device logs.
Once that’s done, please let us know here — Linn will review the report to determine whether this is a system setup issue or something else that needs deeper investigation.
Thanks again for your patience while we work through this with you.
So my Linn DSM/2 is using the Exakt Link to Linn 530 speakers, since DSD is not supported over Exakt Link, Roon needs to determine from the DSM if it is using Exakt or not.
I used the “Report to Linn” option, which created a Linn Ticket 36861.
note: this was not an issue when I previously used an Exakt only Linn DSM, the translation from DSD to PCM was performed correctly by Roon.
DSD playback over Exakt Links is not possible. You would need to configure your Roon core to output PCM audio.
So I think there needs to be a method for Roon to discover if the DSM is using Exakt and then convert DSD to PCM. It needs to perform that further qualification. I don’t know if the Linn DSM has an API that can confirm the Exakt outputs are in use.
We’ll make sure to pass your feedback along to our product and development teams — automatic detection of Exakt usage and applying the correct DSD → PCM behavior. If you have a moment, we’d also encourage you to post this in our Feedback > Feature Suggestions section so we can better understand how many other users would benefit from this and prioritize it accordingly.
In the meantime, if you’d like, we can help you configure Roon to convert DSD to PCM for this setup so playback behaves as expected.
Just let us know and we’ll walk you through the steps.
That seems to work, I disabled “Enable native DSD processing” in MUSE and that did the trick (see screenshot). Is this the recommended configuration going forward?
