Interesting. Did you switch both MK2 devices to exclude the problem residing within the Mk2?
From tony22âs post it seems to be an interaction between the two. Thatâs consistent with my experience. Doesnât mean either one is really to blame. Weird things seem to be unavoidable in the digital realm. As my late mother-in-law would have said, âsh@t happensâ. I would note, though, that in the system that has not experienced these issues, the streamer cost a few times what the other one cost (itâs also much more massiveâno idea if that has anything to do with it).
1 Like
Doesnât help that the latitude given in the published specs for various interfaces are wide, allowing USB gadgets et al to be super cheap with super cheap chipsets in many cases.
I have (at least) 2 raspberry pi based streamers - different types, different boards, one feeds DSD no problem to my RME DAC via USB (and DSD64 via coax). The other one gets stuck with PCM/DSD transitions (although it hasnât made a horrible noise yet). Both have identical software.
So in that case it isnât the DAC, itâs the varying (and cheap) USB chipsets in the streamer and the impossibility of software designers actually testing on every possible combination.
With all these (relatively) cheap solutions based on varying chipsets with varying specs for streamers, I think it is inevitable that this kinda stuff happens.
Is anyone having this trouble with coax (dsd64) or I2S?
(I mean the problems with DSD/PCM transitions etc.) or is it only USB?
Just as a matter of interest 
Edit - I see @tony22 said something like this further up (and I liked it), and rather more eloquently
7 Likes
Hmm⌠you got five likes there so far. But I do not see any responses! I had occasional white noise issues using USB cable when switching between DSD and PCM. This was with FPGA 208. DSD to PCM seems to be the issue. When using a DDC to convert USB to I2S over HDMI, I may get a slight âthuhâ sound moving between tracks, but not so much as the pop type sound that I often get with 100% USB cable. This is using an ASRock mini-PC running Euphony Stylus. I have not had any issues when turning on embedded HQPlayer and pushing everything across as DSD256. But I have not used this much lately as have been helping with testing⌠admittedly on an unusual, non-Roon system. But that probably is the point of Ted having many testers; he is not limited by whatever equipment he has to hand.
2 Likes
Thanks
Anyone have issues on non-USB with with noise blasts I wonder?
Itâs academic to me, but this stuff interests me.
Would need to know if the Sonore paired with other, non-PSA dacs results in the same issue (and to what degree) to be able to better answer that question.
For example, if the Sonore works great with every other dac, then the problem is mk2. If the mk2 works great with every other streamer than the Sonore, then the problem is Sonore. And the entire spectrum in between those two extremesâŚ
1 Like
When I first got our BartĂłk I tried the Signature Rendu SE with it. It did not pop.
The opticalRendu with Hugo TT2 does not pop.
1 Like
Looks like the new firmware is available now.
Looks like itâs only a user interface update. No new firmware 
The documentation doesnât say anything about fixing the power disable of inputs being fixed.
@ted do you know if this has been addressed?
2 Likes
DirectStream_DAC_Mk2_v2.6.2.zip (409.5 KB)
Version 2. 6.2
Date 06/05 /2023
Description: Firmware 2.6.2 adds intelligent muting to reduce noise issues
Fixes: DAC 613 Improve muting algorithm to help with noise issues
6 Likes
Disappointed that PS Audio released UI update 2.6.2 without bundling the FPGA code upgrade.
Update did nothing for me regarding elimination of white noise that I experience with 208-antero 
1 Like
I was reading Stereophileâs recommended components, and for the Benchmark DAC, JA said he only measured in the audible spectrum.
Why is the same measurement standards not applied?
Maybe they should rename the magazine Measuremenphile, or Specificationphile. While Iâve said it before, I donât see how a reviewer in good faith can comment on a productâs low end performance with a speaker that needs to be eqâed just to get low end reach. Too many variables.
4 Likes
Unfortunately the MK2 didnât measure well in the audible spectrum so more investigation as to why was performed.
I think we all are wondering why after another two months; this is all that was accomplished.
But that is not all that has been going onâŚ
I am referring to all the features that still do not function. I would hope they are currently working on the other noise issues. This will probably be an ongoing project with all the different streamers available now.
It took a number of releases before the original DS had all of its quirks dealt with - and it had way less user configurability than the MkII. 
However, I do agree that it would be nice if this sort of thing could have a faster turnaround.
1 Like
From one of the original post on March 10:
1) Better Roon integration. Waiting on status from Roon.
2) Larger text display for both volume and format. (Is this possible?)
3) update to the display settings so:
- it can allow the user to choose a default of either giving prominence to the output / volume level, or the input name and its sample rate, so that in either setting, they are easily visible across the room; and*
- it can show the DS2âs pre-selected input names in full â At least on my unit, when using the coaxial input, the âStreamerâ input name shows up initially in large text, and then as âStreameâ in small text, together with the output / volume.*
4) better menu navigation (back to previous level especially)
5) lifting/grounding functions from remote control
6) automatically shorting/isolating unused inputs function
7) ticks and pops issues fixing. Seems to be an issue with only some streamers / setups.
8) retune or fix the SDM as Ted explained. 6 months - 1 year.
9) enable triggers.
10) enable balance from remote.
11) enable the power on/off for each input circuit.
12) enable network updates.
13) * web interface to control settings.
14) configurable i2s.
15) bit perfect test
* NOT WORKING ON.
I think out of this list only one (10 balance from remote) has been addressed and working, 11 enable the power on/off for each input circuit was fixed however stopped working in the later version. Same with 14 configurable i2s and 15 bit perfect test.
I think for most, 7 ticks and pops has been fixed.
3 Likes
Yup, I get it.
It wasnât âall that was accomplishedâ because Ted and Barry have been working non stop on it. It would be more accurate to say âitâs all thatâs been released.â
Ted released no FPGA code to a small group of testers and they came back with a few bugs so over this weekend, Tedâs working on fixing them.
I do believe weâll have something very soon.
10 Likes
Many thanks to the testers. This can be a good deal of work.
7 Likes
Hi, you mentioned balance from remote.
I havenât used the remote yet, not seeing a balance button or buttons.
Would you tell me where that is, or is it obvious and I have overlooked?