This, unfortunately, will not necesarily resolve the problem. As Paul explains, some systems will block downloading the unzipped files, the problem PS Audio is trying to avoid by zipping the files.
I suspect part of the problem with installing updates is assuming all end users have knowledge of how to unzip a file, what this means, what a root directory is, etc.
I ibelieve a good deal of the confusion could be amiliorated with a detailed basic step-by-step set of instructions.
We also tend to forget that computers do only exactly what we tell them, not necessarily what we want. They are stupid and will not fix anything on their own.
I think the problem in this particular case is that PSA tried to âmake it easierâ by also incorporating into the Zip a subdirectory and files that are intended to automate the process. Too confusing. There should have been one Zip file for doing it the old fashioned way (image.bin, fpga_xx.bin - boom youâre done) and a different Zip for those wishing to go the easier automated route. Combining it all into one and then suggesting âgo see a video to figure it outâ was probably a factor in this case.
From an unrepentant landline user: knowing how to extract from an archive is still a basic skill that most computer users should have. I agree that PSA made it more confusing by putting a zip within a zip. I have just confirmed that Mac OS Sonoma does use a zip icon for a .bin file, which is confusing to say the least.
@aaronm : I completely agree with the comments above about providing better documentation (and do mention that Mac icon thing!). I am also curious whether your team knows why the USB port in the DS Mk2 is so sensitive to larger flash drives. This, it seems to me, is something that has gone on for a long time and should have been addressed in the (relatively) recent update to the DS DAC. A lot of problems reported here would not occur if users could employ any flash drive they have around â and that is something that should be happening in 2024!
I continue to be surprised that there is issue with respect to USBâs. I use a 64 gig USB with many folders on it with various firmware systems files, etc. The only limitation is formating USBs over 32GB (smaller USBs are already properly formatted).
I simply put the relevant set of upgrade files on the root directory and everything works fine. I have used other USBs of various sizes as well. I have never had a problem with installation on any PS Audio product.
Its a shame this thread is more about SW load issues versus the real merits of the latest release. That should be the news. I still can believe what I am hearing in noise performance and how live this sounds and its ability to produce bettered holographic images voice and instruments with clarity. Easily the best tweak ever by Ted.
Elk, Iâm happy for you. Apparently, there are to many exceptions that distract is from the Great content that was handed to us.
So, do know that this really is an issue where it shouldnât be in this magnitude.
Like Magister mentions, the usb port is too sensitive. I consider myself savvy enough to get the right files in the right way on the right drive. Nevertheless, I have 5 sticks of under 32 GB formated at FAT32 in the same manner and only one works in upgrading to a new PSA mountain top. Everything else they do great. So, (in my case) itâs not about those thumb drives.
Considering the upgrade in SQ, one could argue thatâs not a mountain too high to climb. On the other hand, weâre talking consumer products here. The process should be fail proof for the layman.
Now the hard question: should PSA first invest in OTA upgrading or in the next mountain top upgrade?
Indeed. Iâve been around PSA products a long time, so I know that if a particular flash drive (or, in olden days, SD card) doesnât work, I just try another one. But newer folks probably donât know that, leading to a great deal of frustration â after all, I can use any flash drive in my computer and there is never an issue.
I found my problem with the Sky Blue update! I forgot to send the updates to the USB drive! A person from PS Audio pointed that out, so I finally updated the new software. I am listening to âNightfallâ by John Taylor and Charlie Haden, and I am impressed with the whales!
Though doing my best to keep the 44-gallon drum of worms tightly sealed, itâs worth mentioning that in the early years before there was much interoperability at all between Mac and PC platforms â before the WWW even â the standard format for a compressed file archive on the Macintosh platform was a âMacBinaryâ file and when stored on non-Mac filesystems it used a â.binâ extension. (Mac filesystems didnât need, or even use, filename extensions at that time.)
So for historical reasons, itâs legit for the filesystem browser on a Mac (called âFinderâ) to use an archive icon for â.binâ files. Itâs just mildly inconvenient that developers on other platforms decided to also use â.binâ to designate binary data files that are just being passed around via regular computers in order to be installed on other digital devices which will actually know what to do with their contents.
After a series of experiments that didnât work (including three different jump drives) I noticed that the files I put on jump drives contain zero bytes, even though the names are correct and everything looks normal. I spend a couple days wrestling with this issue, and finally resorted to purchasing a loaded USB from PSAudio, which will arrive in a few days. In the meantime, thanks to everyone for their excellent suggestions and advise.
Getting the files loaded by PS Audio is a great thing, I have done that many times these last years. And then youâll have a âdriveâ that will be great for loading your own files onto in the future.
Hi everyone! I successfully updated the firmware and FPGA.
There is indeed a clear improvement in the sound⌠but a background noise appeared (similar to listening to vinyl and the needle passing through). Situation that did not occur with the previous version.
Initially after updating the FPGA, I had the same phenomena occurring when playing DSD files. Shutting-of the MK-2 for ~60 seconds solved the issue. No recurrence thus far.
