A couple of related notes. While it is possible that the problem has finally been resolved, it was never apparent in the experience of all users, only (I would estimate) a relatively small percentage. So the fact that some users of the newest version have yet to encounter any problem, while encouraging, is far from being definitive.
Secondly, as I have mentioned previously, it would be odd for Denafrips to have found a (likely hardware) fix for the issue, yet make no mention of the fact if it was installed in this new version. Why would they not proudly – and loudly – announce a successful resolution?
The only reason that I can think of would be because it would alert unaware customers to the fact that the previous generations were vulnerable to the problem, and Denafrips does not want to engage in any expensive recall action.
One other interesting note. As I have also mentioned previously, Denafrips chose to basically ignore the fact that they advertised at least some of their previous DACs as having NOS capability, when that was false. Much like the skipping issue, I believe that the company ran an internal cost benefit analysis, and decided to gamble that most owners would either remain ignorant of the false advertising, or would not care much, as any sound differences were likely very small.
I mention the above because this appears in the marketing for the Pontus 12th:
Pontus II 12th is a true NOS DAC.
Now, that is obviously good news for those who have purchased, or will in the future purchase one of these units. But I would argue that it also confirms precisely what I have described, namely that the previous versions were not "true" NOS capable.
That the company was willing to falsely advertise at least some of its products, even after they were publicly exposed as not being NOS capable, is in my view very damning, and that behavior would give me pause in purchasing products from Denafrips in the future.