It does not happen on our other three terminal types that are using different GPUs. I would normally lean to say it's potentially a software issue being that the browser upgrade seemed to have made some improvement however, as previously noted this only occurs on the UHD 620 iGPU. We've also tried upgrading Electron to 21.3 to get a newer Chromium backend, and that seemed to help in some cases but hasn't fully resolved the issue. We've tried using the latest drivers and it has not made a difference. It seems to be specific to the CPU that has the UHD 620 iGPU. Using the same software, we do not have this issue on other Intel CPUs using other iGPUs. However, if the primary screen is left on something static that is not redrawing, then as noted above, once a new video starts in the player on the secondary screen, the primary screen will blank and will not recover until something causes it to redraw. Another workaround is using Windows Task Manager set to "Always on Top" - so that the process performance data is constantly causing the screen to redraw. On some screens we added a clock, since that constantly updates. Jeff noted that touching does this - because there's a small animation that plays when you touch the screen. We can workaround this issue by having something on the primary screen "update" to redraw the screen. Thus it seems that the framebuffer, or whatever storage is used to get the screen contents, is still valid - however, the actual hardware screen displays blank. If we use a "print screen" or VNC viewer, the contents that should be displayed are captured correctly. What we find is any time the video player changes to a different video, the primary physical screen will go blank. The video player runs through a playlist of different videos, generally using MP4 content. There is a web-based UI on the primary screen (running in Electron) and then a separate renderer in that same Electron process that plays the video content on the secondary screen. We have two physical screens on the Posiflex 6015 terminal. The issue occurs when using the built-in HTML5 video player in the browser. To add some additional technical detail to the issue:Īs noted the application is in Electron 21.3 which uses a Chromium based browser.
0 Comments
Leave a Reply. |