XXHighEnd

OSD no longer shows during unattended play, just get black screen with mouse pointer. Previously it worked OK, problem started when I tried some different Q settings Q3/4/5 1/1/1 but going back to previous Q settings does not bring QSD back to life. Problem has persisted through several reboots. Log file attached.

Colin - huh ?

I didn't look in the log file yet as I wouldn't know what to look for but maybe merely because I must know under what "condition" the log file was made.
Never mind for this moment, please.

Obviously you checked whether the OSD Text is set to be shown ? (this is a separate setting).

Did you previously receive Wallpaper Coverart ?
(hence has that also disappeared ?)
I am not sure : can't it be that "Don't do anything with Coverart" is active ? (and that this wasn't active previously, plus that I take it that this can matter, which I don't really know atm)

I'm a bit stumped at this moment, but I feel (sense) it can happen. No idea how though.
W10, right ?

Peter

hi peter

OSD text is active
I did previously receive coverart but now I don't
don't do anything with coverart is inactive

W10074 minimized

Colin

Colin,

Can it be so that your SFS is way low ? What is it ?

Peter

I rebooted to normal OS & OSD worked.
Rebooted to min OS & OSD still works.
So problem solved.

Colin, beautiful.

Strange though. All I know is that the Coverart and all can stay away some times for quite long (as in more than a track long) W10 quirck).

If it happens again, just tell about it. Ok ?

Regards,
Peter

I tried again Q settings Q3/4/5 1/1/1 and no OSD so this is the cause. It still played though & sound quality was good. Other setting as by profile.

Colin

Hi Colin,

I still like to be persistent in thinking that the too low SFS is the real cause. Of course it is the combination, but when I set my SFS to 0.8 or lower, I can bearly "pull" the OSD screen (which comprises of Coverart, OSD Text and XXOSK).
And true, without the 1/1/1 setting you mention, it will be less of a problem (or none - I did not test).

This *IS* W10 related; so what's flawlessly in W8 (since 2.xx) is difficult in W10 for sure.

In the end we can expect that the Processor Core Appointment setting is related *and* that it is processor related. Processor speed can be related, but I don't think it really is.

Also let's keep in mind that when things are really critical, a reboot is a first thing to help. So don't fall in that pitpall, because it's not the intention to reboot each hour (you are allowed to of course, but ...).

If you like, try a few things and let me know. But don't do it for me (and notice that personal me wouldn't go without the 1/1/1).

Regards,
Peter