Hi DanBW, thanks for your reply.
Our Xibo player clients are currently on Windows 10 1909 (10.0.18363). The Xibo player is indeed v2.257.2. I will downgrade the existing player to R203 to see if it helps.
The observation about HDMI might be misleading in that the player hardware itself is pretty much different on every display. I have 6 displays total now that were added over the years:
- One NUC connected via HDMI to an HDTV,
- 1 laptop connected via HDMI to and HDTV,
- 1 tablet connected via mini-HDMI to a monitor,
- 1 mini-PC connected via VGA to an HDTV,
- 2 desktops connected via VGA-over-Ethernet to 3 plasma HDTVs (one player’s output is mirrored to a second screen by an Extron device).
So far, the issue has only been observed on the mini-PC and the 2 desktops, all of which use VGA connections. Thus, I do not know if the digital connection on the other displays plays a role in avoiding some sort of EDID issues or not, which is why I brought it up. However, I am not even sure EDID info from the attached display plays a role at all because Windows is properly displaying and scaled, only the Xibo player is shifted from time to time. All the above computers are typically shut off at 10PM nightly and powered on at 7AM daily, but some nights, they are powered on from 11PM to 4AM for maintenance tasks. The attached displays are shutdown from 11pm until 7am, so some nights, the computer is on without the attached display being on, which plays into the next paragraph.
I am also unable to replicate the issue because some days, everything will look fantastic, and the next, it will be shifted and might take a couple reboots before going back to full screen. Afterwards, I could reboot multiple times and it display properly each time. I have tried starting the Xibo player with the attached display off, then turning it on; turning off the display with the player already running, waiting a bit, then turning the display back on; and completely unplugging the external display, powering the player, then plugging the display into the player after a few minutes, but none of it seems to trigger the issue. My thought was that perhaps the maintenance on some nights running the PC without the attached display being powered on might be causing this, but I cannot find evidence to that. Also, the old Xibo v1.x player ran on the exact same hardware and Windows 10 version without any issues.
As far as the event viewer goes, I cannot find anything in the Applications or the System log, just the usual stuff. Except for Windows 10 Education and the Xibo Player, the only other software installed on those players is the OEM-drivers and SCCM agent with Endpoint Protection (mandated by our system office), again same setup that the v1.x player ran fine on.
I will go ahead and downgrade the player on the 3 devices that the issue has been reported on and see if that helps. Please let me know if there is anything else you would like me to look at.