Firstly, I also stream using a Pink Faun 2.16 ultra, like you do. So that should be a comparable setup.
My main concern is the “disruptive” clicks which may or may not pose a threat to the loudspeakers. And this started after the 3.1.5 FW update, which suggests a correlation. It might be that the clicks are not inherent to the Renderer alone, but result from the interaction between the Renderer and the DAC. And there I believe our setups differ. A Cascade in my case, and I believe you upgraded to a Sentinel.
The observation about DoP in the signal path is just what I came across once digging a little deeper. The DoP encapsulation, at least overtly displayed in Roon, is also new after the update to 3.1.5. I don’t know whether the encapsulation step was always there, it just did not show in Roon prior to the update.
As to the display on the msbtech.local page, mine looks exactly like your screenshot. Which is not surprising since DoP does not change the fact that the stream is DSD, it is just recalculated such that a PCM stream can carry the original 1 bit information, albeit in a less efficient format (the encapsulation costs bandwidth and processing power at both ends of the conversion).
That, indeed, it is not. Both devices (PF, Renderer V2) are separately connected to a Reiki SuperSwitch X. However, even if that makes a difference, that still would not explain why everything was fine with FW 3.0.5 and the clicks only appeared following the update to 3.1.5. But thank you for exploring.
One addition: I incur the same loud spikes/bursts with DSD128. Only DSD64 works such that there is either no spike or a very quiet/gentle sound prior to the start of playback.
Thank you. This problem, though, appears not to be related to the Network Renderer V2 firmware update to 3.1.5, correct?
And by the way: encapsulation as DoP does not mean the stream is converted to PCM. It only means the DSD stream is embedded in a PCM stream serving as a container for the same 1 bit data. Nonetheless, if your renderer and DAC both support native DSD this would be the cleaner path, since DoP means computing at both ends as well as more bandwidth on the connection.
There was up update last week. We will be looking into this to see what might be going on and I’ll be messaging some of you directly to figure out what is going on. If you want to join the beta program please reach out to us directly and we can get you enrolled in early releases of this issue. In the meantime, can you please email or message me a video of any clicks/pops you might have. We can tell a lot from the sound of a click/pop.
I am already enrolled in the beta program and I have no problem with clicks and pops at all! Only with the issue I mentioned.Thanks for the prompt response.
We are still working on it. The Analog DAC downsampling will be fixed with the next update. The ticks are proving to be a difficult problem to track down.
Real quick, can you go into the settings of the Analog DAC Renderer in Roon and make sure the “max DSD rate” wasn’t set lower?
Hi Jonathan, the max DSD rate is set to 128,and does not have an option to select 256! This is odd because previously it was set at 256 and played those fles,natively,perfectly.I don’t know what has changed in the Renderer software for this to happen.Thanks for your continued support of even your “legacy” products and whereas I have no doubt that your current products are better,I still love my Analog DAC and would be very reluctant to part with it without a “sound” ( sorry bad pun!) reason!
Hi @Jonathan_Gullman, are there any news regarding a Network Renderer V2 firmware fix for the bursts/clicks issue pertaining to DSD256/DSD128 playback? Thank you so much.
