Phisolator

[PeterSt]

Anthony, yes and of course.
I had it only once yesterday, but with the notice that this is not a tick but a soft scratch. This is only annoying for that it indicates that something is not 100% right. For me it is extra annoying because I will survive but can't "sell" it to a customer ike that.

As an USB error experience expert (haha) I also learned that the "ticks" as such come from sinlgle errors only. This really feels like this : there *has* to be a tick of soe sort, and its energy is or all in that one error, or the same energy is spread over the 100 errors in one go. Now it has become a soft scratch.

The errors with showing the coverart are well known, and it is only that I never could figure out for real what causes them, except for that I only last month saw/sorted out that a million times (seriously) more things need to happen for showing the coverart than what happens during normal playback. So it is some kind of cpu bandwidth problem, or access to the memory perhaps (the largest part of what all happens is registry access, but which is in RAM with the RAM OS Disk (I assume you use that).

By now I am also positive that the Processor Core Appointment setting makes a difference. So for example (and then with the PhisolatorS) the 3-5 setting causes significant more error than the 3-4 setting. Sadly the latter does not sound good at all. But maybe you can experiment with the Wallpaper tick regarding this - if it helps it is always good bagage for further thinking.

Btw, the size of the Coverart Image file should also matter; 500K really is sufficient for a "best" picture of normal size, but 20MB exist just the same. And each pixel must be dealt with ...

Peter