Installed Interim 2.08. Giving it a try now.
Excellent idea. I also made reference to the interim release.
I do not want to change the beginning of the thread title (“Final version firmware”) as I am afraid people looking for the thread will not find it.
There is an interesting discussion on-going in another forum about RAM buffering in the SACD/CD player and how this makes the quality of the optical drive in the player less important (because jitter is being “eliminated” by the RAM buffering instead of in the optical drive). Evidently Esoteric are now employing a RAM buffering technique in their newer model disk spinners. The argument is, why put such an expensive optical drive like the VRDS in it if electronic/software techniques now make the (expensive) mechanical engineering marvel of the VRDS redundant?
I think PS Audio pioneered the use of RAM buffering in the player, and others since followed. Like many of their other original ideas such as after-market power cables, power regenerators etc etc.
That was also the basis of the original Digital Lens.
They are one in the same.
Does the new release sound better to anyone than the previous version (2.04)? Maybe it’s my imagination because I am so excited to have the new code but I swear in a very short listening session it sounded more spacious to me.
In any event, thanks for releasing this. 
Brodric…This is from the DMP owners manual about RAM. PSA has stepped it up a notch…
“Up until DMP’s advanced Lens technology was introduced, the internal Digital Lens found in the older PerfectWave Transport relied on an intelligent RAM buffer to isolate digital data from the mechanical optical drive and laser mechanism. Separated from the CD reading device, data accumulated in the Lens’ buffer until output through a fixed low jitter clock to the DAC.
After eight years of research and two years of development, PS engineering has been able to shorten the memory requirements and improve the timing of digital audio data. The new Lens takes advantage of advances in semiconductor architecture found in FPGAs (Field Programmable Gate Array). Using a single large scale integrated FPGA, PS chief DMP architect, Bob Stadtherr, devised a segmented structure including intelligent RAM, two-way isolated communication with the drive, and near field output latches controlled by an ultra-low jitter fixed clock.”
Absolutely no question in my setup (Audio Solaris headphone amp, Audeze LCD-X, DMP & DSD (BHK 250 is in the shop) the new code sounds better. I would love to know why and would be curious as to whether anyone else noticed a change in sound quality.
There are many reports of better sound quality on the announcement thread : https://forum.psaudio.com/t/dmp-interim-update-code/5337
FWIW up this thread I predicted better sound quality (last paragraph of https://forum.psaudio.com/t/final-version-firmware-released-1-94-december-9-2016-now-interim-2-08-march-9-2018/3498/408 )
Matt knows to run things as slow as possible (but still fast enough to get the job done) and there’s a lot less thread thrashing in the new code.
Thank you Ted. It’s harder for me to find the threads I follow since the forum changed.
As far as better sound quality from the new code, good things come to those who wait.
Since we’re supposed to be reporting bugs…
Went back to the system to play a disc that was already in the DMP, what I was playing before when I commented how much better it sounded. Disc began playing as soon as I hit PLAY but there was no sound at all. Check connections, input on DSD, etc. Nope, no sound. Hit play again, still no sound. Advanced tracks, nothing. Ejected the disc, put it back in and hit play. BINGO. Music.
I believe I read that someone else had reported this. Just wanted to report it to Matt & Paul.
Instead of ejecting the disk most of the time I can press stop, next track (maybe play) and then previous track to get to the beginning of the disk (too many steps, but much less time that ejecting and reloading.)
For me navigating with next and prev track and then pressing play has always been reliable. On the old code many other paths seemed to fail at random.
Using 2.04 I never had an instance where the disk played (you can see the track time counting up) but no sound was output. I had instances where it wouldn’t play correctly or not at all (timer stuck on 0:00), but never where it seemed to be playing fine but there is no output. I am assuming in that case it’s not outputting data for the DSD to decode. It shouldn’t be that the DSD has gone into mute.
The new search function works great. Dig around a bit and you should find all of your previously watched threads.
At the bottom left of each thread is a button. Change this to “Watching” and you will be notified of every new reply, together with a count of new replies for that thread. Here is an example.
Of course not, but this is an interim release and many bugs are expected.
No, that’s fine. The point I was making was my guess was that it wasn’t outputting any signal to the DSD rather than the DSD went into mute. I was offering up a diagnosis. 
I realize this is interim code and will still have some bugs. It seems better than 2.04 though.
Ah, sorry about that chief!
1 Like
Dear Mr Guru—yes works perfectly—stop/next track/previous track/ play—and I barely have to move my thumb so I don’t expend too much energy. Thanks!
Perfect. We all strive to keep thumb waving to a minimum.
1 Like
I think the Interim 2.08 sounds better for sure. More air, sense of space. Dead quite. The problem I seem to have with it. I have to keep messing with it to get it to play to the dac. I often have to stop it and start disc again a # of times or open tray and then re close. This only happens at the end of a disc. So if the disc ends, and I plush play again, nothing. The track is counting normal, but no sound at all. Pushing stop, or pause or next track does nothing most of the time. Switching dac inputs back and forth to another input does nothing as well. So it’s player related.
Sound great, but it’s erratic.