In Windows 10 (or at least in build 10074) things have been changed with priorities and "time slicing" (which task is allowed to run when and for how long). This means that we run into something which we actually have seen before, but wasn't all that profound ... now it is :
With the wrong Processor Appointment Scheme no Coverart Wallpaper is going to show. Well, it does - after the (f)act - at pressing Stop.
This all is related to the general load of the Operating System as well and what is easily possible in Minimized OS does not work at all in Normal OS. An example of this is the combination of Q4 and Q5 both set to 1 and now try to ever see a Wallpaper; It won't work. Set either to other than 1, and it is fine.
This is how there's a check for that built in. Thus the combination of Q4=1 and Q5=1 and being in Normal OS, is not allowed.
In Minimized OS we have this example :
All now works fine as usual, except for that the Processor Core Scheme has to be 1-3 or 3-5. Curiously 2-3 does not work. Curiously ? what we derive from it is that the two main threads in order both have to run in the main core of a hyperthreaded pair (1-2 is a pair, 3-4 is a pair, etc.).
We did NOT build in a protection against this, because this is now about MinOS and the very best SQ anyway, and when you really want the very best you might decide to not use the Coverart Wallpaper to begin with. Meaning : If you think SQ is way better with Scheme 1-2 (No Wallpaper will show with Q3,4 = 1,1) compared to 3-5 (Wallpaper will show with Q3,4 = 1,1) then we are not going to prevent you from that.
We do in Normal OS because that's toying anyway, and it is highly confusing that you switch on the Wallpaper by all the (inexperienced
) power you have in you, but see nothing appearing of it because of some unlucky combination.
