@tedsmith
Thanks for the response
It is interesting that a compile can produce different sound
My experience with 173 vs 178 could be a side effect
Just a thought, I wish there is a place that the users can do an experimental compile and use the one that works best
Like a home brew that put on AWS, i am willing to pay for each compile
The ISE suite of Xilinx tools for FPGAs that I used for the DS uses simulated annealing to place and route. Thatâs a statistical process so each compile can have a different random number seed. A given compile is reproduceable when using the same seed. With some complicated designs you might have a farm of machines all compiling with a different random number seed and take the first one that completes successfully (or use some other selection plan.)
With the DS Mk II the Vivado tools donât use simulated annealing I have about 300 different configurations of options/goals that I can run. I usually stick with the one thatâs the fastest for normal work.
Is the reason why the upgrade method applied in the perfectwave-ds transition is not applied in the ds mk1-mk2 replacement just economical?
The cases are different, the back panels are different, the screen is different, the mounting holes are different⊠We wanted two AES inputs, didnât want a bridge, wanted an externally accessible fuse, wanted a display that wasnât noisy and didnât use switching power supplies⊠It was time to change the hardware to be closer to the other newer PS Audio offerings.
@tedsmith - this seems similar to the issue I raised about DoP vs Native DSD with our Sonore Signature Rendu SE. In Native, DSD is converted, in my case with Roon, to 352.8/24. In DoP all DSD processes correctly.
XMOS series of processors most with USB embedded. Now the DS Mk II uses ComTrue.
Yep, thatâs what I thought too.
Lately Iâve been getting burned in my tests in the new foobar2000 2.0 with the newer SACD plugin because it keeps a separate DSD/PCM configuration for each possible output selection (of which I have maybe 20.) Then when you unplug a USB cable and plug it back in it resets the configs for that input again. All manner of confusion resulted in my brain before I figured out what was going on.
Oh man! I hope thereâs a way to pin it to what you want vs having to go back in a set it each time. Especially with your Use Case.
The good news for those of us that have the Native âissueâ is that it really doesnât matter. Itâs not like DoP is a step down in SQ.
The puzzled looks I get when I say that the first thing I do with Native DSD is to convert it to DoP 
Science! What a concept.
BTW - Over 500 hours now. You should be very proud Ted, it sounds really good.
For me one of the best outcomes of the MKII is the lower noise floor. Listening at lower volumes late into the evening is pure pleasure. The first track in this recording is a great example of this on my system. It sounds so beautiful this time of night.
I have closed in on the 100-hour mark and noticed the similar USB issues last night. I wound up rebooting and the problem appeared to go away. Will monitor over the next few days.
Quick update on the beta unit I received on December 6th. After 40 hours of continuous play I had no problem switching between USB and optical (the only connections I have right now). No clicks or delays. The display reads properly. The MKII runs cool, just slightly warm to the touch. No mechanical hum can be heard even with my ear almost touching the unit. Still sounds detailed, open and smooth at this 40 hour mark.
Forgot to add that Iâm still running version 2.3.0 as it was shipped. Going to wait and see if anythingâs changes before I update to 2.3.3
Folks:
I am still running 2.3.0 and FPGA 173.beta 173 since Saturday and there is no drop out or silence. My USB connection (Curious with 5 volt supply) is not recognized by my MAC Mini although I get a green dot. In other words I get no music through the gear except from Mac internal speaker. It worked with MKI. I just noticed that the unit is running warm to the touch. Also the SQ is a mixed bag. In my opinion and my equipment and set up, the MKI has greater transparency than the MKII. I can relax and enjoy the music. The MKII is more dynamic and imaging is better, but I canât relax. I could be wrong but thatâs my take on SQ. I would like to update to 2.3.3. Where can I get the files?
Another listening session last night, Auralic streamer through USB, Qobuz and files on attached SSD. The difference between DSD MK1 and MK2 is remarkable. Soundstage is taller and much wider. Space between instruments is more well defined and decay is striking. I thought my Auralic Aries G.1 was the weak link in the system, but the gap between it and the PWT has narrowed greatly.
I have one of the first beta units and have had zero issues, and have not made any updates.
One issue I have as others have mentioned is with the manual. I am the type that will download and read the manual cover to cover waiting for the component to arrive. As much as I love the hardware, Iâve always felt the manuals were sorely lacking. For all of the PS Audio components I own and have owned, I have had to look to the forum or customer support to get answers.
MK2 is no exception. There are operational functions and settings I have learned about here that are not mentioned in the manual at all. WTF!? It seems to me a better prepared manual could save the mother ship a good deal of grief. And why not update the online PDF manual as these issues arise? Hire a manual guru for just this purpose? I know there are plenty of detail oriented folks here . . . Rant over.
MK2 has been the best component upgrade I have made to date. Thanks Ted and all at PS Audio for an amazing DAC. I have noticed my vinyl purchases have lost some priority.
The skillsets of having the technical chops and the writing skills, while not mutually exclusive, are tougher to find in one person than youâd imagine, and especially at what a company would like to pay the âmanual guru.â Itâs not uncommon for the role to get short shrift.
And the product development is always gonna get top priority. In this case, this thread is evidence that the product itself is still not quite ready for primetime, so not surprising that the manual wouldnât be either.
Have you checked Audio MIDI Setup on the Mini to ensure it is set to output to âPrimary Play Interfaceâ? If you make any changes, it often needs to be reset.
That would suggest something is not right to me, as that is the opposite of most of our experiences.
You should have an email from Aaron with 2.3.3. It is also above in the thread here somewhere. Sorry I do not have post numbers on my iPad.
Hello Aaron:
Iâve tried your suggestion. In Midi I do not see âPS Audio Outputâ. IN Tidal I do not see âPS Audio outputâ. I can only get sound from the Mac internal speaker. I also rebooted. I tried all USB ports on the Mac with same result. The screen shows a green dot for USB. Interestingly, if I disconnect the USB cable from MKII, I still get green dot. It worked with MKI. I am running: 2.3.0;FPGA 173.beta 173; USB 3.01,a605; unit # 151331. Thanks I appreciate your help.
PS I2S works, but I am no 100% on SQ. Maybe speakers need to be set up.
