I have an Analog DAC with a V2 renderer module that used to play DSD256 files flawlessly.However,today when I tried playing some files it refused to do so,literally skipping over them and “reporting too many errors” (Roon).It plays DSD64 flawlessly.(Haven’t tried 128).
Any reason for this sudden change?
We can confirm this problem and are working on it now. Once fixed, your DAC should just update automatically.
I truly appreciate the level of support even to an older model! Kudos and thank you!
Just a quick update. We have it working and the new firmware should roll out in a few days via the automatic firmware update. Thanks for finding this bug for us!
This is a firmware update for the Renderer V2 module you are talking about here? That’s the only component, that I know of, that updates automatically. This occurs at power on?
Are there any other updates (Premier DAC+DD) expected soon?
Correct, he is referring to the Renderer update. We do however have a big dac firmware update coming this thursday, so stay tuned for some news there 
All 
s
T-minus 45 minutes…
Here you go:
https://forum.msbtechnology.com/t/renderer-update-qobuz-connect-is-here-and-its-fantastic
Hi guys,
As of now,my renderer hasn’t yet updated.
Could you message me your DAC serial number?
Sorry, the fix for 256 DSD for the Analog DAC will be rolled out in 3.0.4. It’s in beta testing now.
Thank you!
Just a question,though. My renderer shows a firmware version of 2.0.Should it not have automatically updated to 3.0.3 (even if DSD 256 doesn’t play) or will it now automatically update to 3.0.4 when that is released?
Actually in the image you transmitted the firware is version 3.0.3… it is the version of the hardware which is 2.0… 
Apologies! My mistake!
Since updating the Network Renderer V2‘s firmware to 3.1.5, there seems to be, again, an issue with DSD256 playback.
In my case I stream files via Roon/RAAT.
Firstly, whenever I start a DSD256 playback, the DAC (in my case a Cascade) produces c. 2 loud clicks which is annoying and gives me a fright about my loudspeakers.
Secondly, in Roon, it is now shown that the signal path is to the Renderer and then encapsulation in DoP v1.0. Which was not the case prior to the update. With FW 3.0.5 it was just shown as DSD straight to the analog output.
Can you please fix this @Jonathan_Gullman ? Thanks.
Just to give you another data point. I’m running 3.1.5, and Roon RAAT to Renderer without clicks and the music sounds right. Source is internal disk in Pink Faun.
Display says 256x DSD
If you browse to msbtech.local and open the audio page you can get another source of info about what is playing.
Dan
