# DSD256 not playing

**URL:** <https://forum.msbtechnology.com/t/dsd256-not-playing/1161>\
**Category:** Support\
**Created:** [April 12, 2026, 5:41am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161 "2026-04-12T05:41:12Z")\
**Posts on this page:** 19\
**Page:** 2

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [September 18, 2026, 8:42pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/21 "2026-09-18T20:42:21Z")

</div>

Thank you, @Dan . Much appreciated.

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).

Let’s see what @Jonathan_Gullman or @Daniel_Francis come back with.

---

<div class="post-metadata">

**Author:** ![Dan](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/dan/32/39_2.png) [@Dan](https://forum.msbtechnology.com/u/Dan)\
**Post date:** [September 18, 2026, 8:51pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/22 "2026-09-18T20:51:49Z")

</div>

Yes, Sentinel, which included a brand new Renderer… I didn’t have to move the one in my old Cascade over to it.

Glad it added some info. The clicks would worry me too.

Dan

---

<div class="post-metadata">

**Author:** ![Dan](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/dan/32/39_2.png) [@Dan](https://forum.msbtechnology.com/u/Dan)\
**Post date:** [September 18, 2026, 8:54pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/23 "2026-09-18T20:54:50Z")

</div>

Just to double check, your Renderer is connected directly to ethernet 2 on the Pink Faun?

Dan

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [September 18, 2026, 8:57pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/24 "2026-09-18T20:57:45Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [September 20, 2026, 11:50am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/25 "2026-09-20T11:50:20Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Hiind](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hiind](https://forum.msbtechnology.com/u/Hiind)\
**Post date:** [September 21, 2026, 5:42am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/26 "2026-09-21T05:42:51Z")

</div>

I,too am facing a problem! My DSD 256 is being downsampled to 128 and then strangely being converted to PCM!

 ![IMG_0008](https://canada1.discourse-cdn.com/flex003/uploads/msbtechnology/original/2X/5/5cc9f671c450ba0353d3c44293f46fa273d0ebf7.jpeg)

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [September 21, 2026, 7:08am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/27 "2026-09-21T07:08:22Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Hiind](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hiind](https://forum.msbtechnology.com/u/Hiind)\
**Post date:** [September 21, 2026, 12:26pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/28 "2026-09-21T12:26:08Z")

</div>

I think it is probably related to the update as I was not facing this problem previously and yes,it also used to play native DSD flawlessly!

---

<div class="post-metadata">

**Author:** ![Jonathan\_Gullman](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/jonathan_gullman/32/682_2.png) [@Jonathan\_Gullman](https://forum.msbtechnology.com/u/Jonathan_Gullman)\
**Post date:** [September 21, 2026, 4:26pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/29 "2026-09-21T16:26:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [September 21, 2026, 5:11pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/30 "2026-09-21T17:11:31Z")

</div>

@Jonathan_Gullman I am currently on a business trip, will probably be able to record the symptom by the middle of the week and attach to a DM to you.

---

<div class="post-metadata">

**Author:** ![Hiind](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hiind](https://forum.msbtechnology.com/u/Hiind)\
**Post date:** [September 21, 2026, 5:12pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/31 "2026-09-21T17:12:55Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Hiind](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hiind](https://forum.msbtechnology.com/u/Hiind)\
**Post date:** [September 26, 2026, 1:16am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/32 "2026-09-26T01:16:55Z")

</div>

Any clarity/information on my problem?

---

<div class="post-metadata">

**Author:** ![Jonathan\_Gullman](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/jonathan_gullman/32/682_2.png) [@Jonathan\_Gullman](https://forum.msbtechnology.com/u/Jonathan_Gullman)\
**Post date:** [October 1, 2026, 4:11pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/33 "2026-10-01T16:11:27Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Hiind](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hiind](https://forum.msbtechnology.com/u/Hiind)\
**Post date:** [October 2, 2026, 4:43am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/34 "2026-10-02T04:43:54Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Daniel\_Francis](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/daniel_francis/32/681_2.png) [@Daniel\_Francis](https://forum.msbtechnology.com/u/Daniel_Francis)\
**Post date:** [October 5, 2026, 3:48pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/35 "2026-10-05T15:48:02Z")

</div>

> [@Hiind](#):
>
> “sound” ( sorry bad pun!) reason!

Never apologise for a pun. Life needs more of them 🙂

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [October 5, 2026, 11:07pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/36 "2026-10-05T23:07:59Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Gullman](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/jonathan_gullman/32/682_2.png) [@Jonathan\_Gullman](https://forum.msbtechnology.com/u/Jonathan_Gullman)\
**Post date:** [October 9, 2026, 12:10am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/37 "2026-10-09T00:10:24Z")

</div>

Yes! We have it working and will be pushing it to the beta testers very soon.

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [October 14, 2026, 7:16pm UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/38 "2026-10-14T19:16:42Z")

</div>

@Jonathan_Gullman was so kind as to push the 3.1.6 beta4 firmware to my Network Renderer V2, and I can confirm the new firmware solves the issues I reported in this thread about playing back DSD256 files creating disturbing clicks/burst when sending them via Roon/RAAT to the renderer. And also the awkward confusion in the Roon signal path, which showed a DoP encapsulation, is gone, too, and it now looks like native hi-res DSD playback, again. Thanks to the team for the great support.

---

<div class="post-metadata">

**Author:** ![itoakio](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.msbtechnology.com/itoakio/32/485_2.png) [@itoakio](https://forum.msbtechnology.com/u/itoakio)\
**Post date:** [October 26, 2026, 8:40am UTC](https://forum.msbtechnology.com/t/dsd256-not-playing/1161/39 "2026-10-26T08:40:26Z")

</div>

My renderer just updated to 3.1.6 beta7, and DSD256 playback still works fine.

[Previous page](https://forum.msbtechnology.com/t/dsd256-not-playing/1161.md?page=1)
