I also use these test files to verify the i2s input is configured correctly. I made these track a couple years ago.
1 Like
I am on the hunt for either a VAC Signature II or a VTL TL-6.5 Series II Signature preamp.
I like having tubes in the Pre. Itās nice to shape the sound with a simple swap.
1 Like
My observations with firmware 2.5.0 so far is that de-emphasis when set to ON works properly but it does not auto-detect it when using a PWT like it did with the mk 1. This is not as much an issue with the ability to manually turn it on but it would be nice if the auto function worked as intended. This is a non issue with the PST as it does the function and always fowards a deemphasised signal when the disk requires it. I also see that you stll cannot control the balance via the remote like the mk 1 did. It is nice to see more features working now like the abitity to turn off unused inputs but wished it did so for all inputs like aes and coax too. The DAC sounds even more open and transparent and yet I know the fpga changes were more about controlling extraneous noise. In spite of that knowledge my ears are telling me different.
4 Likes
Updating the DSD Mk2 firmware from 2.3.6 / 198 to the new version 2.5.0 / 208 went well - I also used the max volume/fixed volume trick.
For the I2S connection, streaming from my Antipodes, I now also see the sample rate; this is listed as fix 564 in the release notes.
However I note the following:
- The AES/EBU XLR connection doesnāt seem to work: there is no longer any sound with this connection, the display indicates DUAL XLR with a red bullet preceded by -/-, i.e. no sample rate.
- It doesnāt differ whether I use the XLR cable with input XLR1 or XLR2.
- Toggling the XLR button on the remote does not make a difference either.
- With the previous DSD Mk2 firmware the AES/EBU XLR connection gave good sound, including sample rate and green bullet in the display.
Is there a trick to properly select XLR 1 or 2 with the new firmware installed?
Hi Ted,
Thanks for the good work. I got my firmware to 2.5.0, no probs, using a USB drive. Could I have done this FW update via the ethernet cable?
On the DAC mk2 menu, my FPGA Load shows nothing. Is this correct, pls?
TIA!
Update over the net is expected in the next UI release. Itās a big work item and they ran out of time on this release.
3 Likes
Wow a 46 lb and $18k preamp. Nice Absolute Sound review! Nice upgrade.
1 Like
Hello Audio Experts!
Can anyone answer the below, pls?
I believe that means it does not see the usb drive. Load drive in back, put in standby, then do the power cycle from the switch in the back of the unit off and then on. That loads the UI instanlty and then reboots. After that you should be able to nav to the FPGA menu and see the new one.
There used to be an enable Dual AES setting, but we disabled Dual AES for this release. Perhaps doing a Factory Reset will clear your Dual AES setting and then things will work well. Otherwise you might contact PS Audio support.
3 Likes
Yes! After doing the Factory Reset as you suggested, display indication for the XLR input changed from 6: DUAL XLR to 6: XLR 1 and the XLR connection now works well, with display also indicating sample rate and the green bullet.
Thank you!
1 Like
Iām looking at this issue with the settings being screwed up. There are various settings that are stored to persistent EEPROM across boots. The mapping for that changed from 2.3.6 to 2.5.0, and there is code that detects that copies the correct values across. It sounds like on some units (or all?), that isnāt happening properly. I did test this here, but it was early in the dev cycle and itās looking like something dropped in that is making it either not do the settings upgrade or doing it wrong. Iāll look into it today. Sorry for the inconvenience everyone!
3 Likes
This wasnāt intentional, in fact the opposite. The SW should have done this all for you. Sorry this happened, it was something I actually put a lot of time in to make sure it happened corrrectly and it was working at one point in the test cycle. Going back now to figure out whatās going on.
5 Likes
Weāve had people testing here that feel the same about the sound quality. Both the PST and DMP handle deemphasis themselves. Do you have the PWT hooked up via I2S?
For the balance control on the remote, that may be an artifact of the way the common code was developed a few years ago. One of the remotes we had had a problem where, if you hit the volume up/ down, there was a tendency to accidentally hit the balance left/ right (due to the design of the remote). So balance control was removed from the common code for those remotes and the DSDMK2 may have picked that up. Itās not a problem on the PW remote, so Iāll check that out and see if I can get it addressed in a future release. Thanks for the input!
2 Likes
For people who havenāt updated yet, Iām looking into getting the settings issue fixed today. If I can figure it out, Iāll release a 2.5.1 ASAP. If thereās no rush, feel free to hold off on the update, having this fixed should definitely make it go smoother.
On the other hand, if you donāt want to wait, just be aware you may need to go back through settings and update them to what you want. In particular, the Max Volume is apparently being set to 0, so the unit always come up at volume 0.
6 Likes
I get what u mean about change in sound quality
2 Likes
Barry,
Thank you for all your hard work. I donāt mean to sound ungrateful. Yes the PWT is connected to the DAC via i2s. Resetting the volume and other settings was not a big deal. The funny thing it did was name i2s 1 as Server. That threw me a curve as my usb was labled server. Also the volume set to 1 maximum made me think the firmware had caused some kind of problem. I do appreciate the additions of names to the list. I like seeing PST and PWT when I go to select an input much better than SACD and CD. I had defaulted to i2s 1 and i2s 2 as they used to be the best fit. The only lift options that did not carry through were shell and shield. When I tried the balance from the remote I first hit volume for DAC than the balance as I always did with the mk 1.
1 Like
Iām now forgettingā¦
Using USB only, do I lift the USB ground and ground the other, unused inputs? Or do I ground the USB and lift the others?
And is it āFeed a cold, starve a feverā, or the other way around?
Syslexia Ducks.
6 Likes
It can depend on your system. But often grounding everything but the current input is a good choice. Perhaps the second most common good configuration is grounding everything.
āSyslexia Ducks.ā took me a minute 
11 Likes
This is the same thing I had happen on both 2.3.5 and 2.5 updates. I had to remove the usb drive after running the firmware update, power cycle and put the usb drive back in for the FPGA choices to show up in the load window.
1 Like