2 weeks.
Ok I’ll update the post.
TY
Daniel via Xibo Community <noreply@xibo.org.uk> escreveu no dia segunda, 10/05/2021 à(s) 11:37:
1 Like
That’s great, thank you Miguel_Ferreira. This will be very helpful for the community, I appreciate your help with this 
Many Thanks.
Hi,
I did some tests last week but I can’t understand what’s going on.
The players are doing well on some days and on other days they are not adjusted.
It is completely random and I cannot understand why.
In 2 players I did a completely new installation of windows and xibo player and in these 2 players everything is OK.(and changed hdd to ssd)
Maybe it will do the same with the other players.
Hi , same issue randomly on windows players with classic hard drive no SSD (old intel NUC min pc 4Go RAM), I thought it was because of the charging latency of the xibo client (latest 2R257-2) on old device. Juste put on start up menu a ping command ping www.google.fr -n 10, to loose time ;-), this seems working since but …esoteric solution …
Hope will help
Hi,
I made some changes that seem to have worked.
I removed the Xibo Player from the windows startup and created a scheduled task to start the Xibo Player with a 1 minute delay.
I tested it on a player and it seems to be OK.
I will be watching in the coming days if the problem is resolved in this way.
Hi Frederic_Horcholle and Miguel_Ferreira.
Thank you both for your updates on the issue. I am still unable to replicate this issue on multiple PCs, one with an SSD, the other uses a standard HDD.
I can see Frederic commented on the other post about this issue, thank you for that. On that post I suggested the user tries following the steps in the guide below. There was a version of the player some time ago that had an issue which would cause it to use an incorrect display setting and resolution stored in the registry on occasion. Could you both take a look at the following guide and confirm if this helps to resolve the issue?
Many Thanks.
Hi Dan, this issue is very hard to replicate. My windows players reboot each day once, this problem appears only with old NUC Mini PC with standard HDD, very strange… I don’t think the cause is the resolution. Since I put ping www.google.fr -n 10 at startup, the problem seems to have vanished. Maybe we have to wait the result if the one minute delay made by Miguel on his player.
See you
I also had this problem on a previous version (r252.5) and which disappeared without doing anything just after 2 or 3 restart the screen was well adjusted
[image]
Thank you for the update frederic_Horcholle and malix. I have informed the developers that this issue is being reported by some users, so they are aware that this is occurring.
Many Thanks.
This is a follow up message regarding this issue. I have informed the developers about this, they have also asked if a User experiencing this issue can set a Top, Left, Width and Height for the player and see if the issue persists? Below are instructions how to do that:
- Go to the
Displaysmenu in your CMS. - Click the button at the end of the entry for your player and choose
Editfrom the menu. - When the Edit Display window opens, go to the
Profile Settingstab and set thetop, left width and heightsettings for your player. - Save to confirm.
Once you have set the player size, please wait for the player to connect to your CMS and receive those new settings. Once they have been received, please restart the player.
Many Thanks.
Hi Dan,
in our player we already tried this approach, without success. The issue persists even when manually set the screen size and position
thanks for your attention
Thank you Gianzanti, that’s very helpful. I will inform the developers and continue to try to replicate this issue.
Can you confirm if you have also tried following the steps in the below post?
I also wondered if you could check the Display settings on your Windows machine and confirm:
- The scale setting. This should be set to 100%
- The display resolution.
Many Thanks.
Hi again!!
I’m sure that the scale setting is 100% (because someone in the past asked me to check that, and this is part of the install process) and the display resolution is configured according to the display attached to the player. He have players configured as 1366x768, 1280x720 and 1920x1080, and all resolutions presents the issue.
The registry settings I don’t have right now, but already asked support to get it. As soon as I get these info I’ll let you know.
As we don’t know yet the reason of this issue and as noticed in another thread about the same issue someone talking about the content type, just to let you know, always we have some kind of HTML content playing when the issue occurs. Could be a local html file or an embedded html or an url.
thanks in advance,
Thanks Gianzanti, that’s really helpful! I’ll make a note and wait to hear about the registry settings.
Many Thanks.
Hello @DanBW,
I work along Mr. Gianzanti, and actually I have a notebook that is running Xibo 2.5.7 and is one of the PCs that do have this issue. Of course its screen can´t be dettached - and most of the times it will start playing the content with the aforementioned offset.
I checked the registry keys and hand typed them just to be sure - but the problem persists. In this specific case, I am ruling out the disconnection of the display as being the cause as it happens when I first start the notebook in the morning (or restart it during the day).
Also, we have a custom Player properties in place (0, 0 , 1366, 768 - the actual resoluton of the display) but the problem persists.
I will try to uninstall it and give version 300 a try and let you know if the notebook behaves differently.
Best regards,
Norberto
Hi Norbies,
Thank you very much for the information you have provided, this is very helpful. These are very good points you have mentioned. I will also wait to hear if you encounter the same issue with the 300 player.
I noticed in your message you mentioned "it happens when I first start the notebook in the morning (or restart it during the day)". This is something that is being investigated at the moment, I wondered if you might be able to test this theory by adding a startup delay for your installed apps?
Below is a link to another thread where this issue is being discussed, could you follow the instructions in my latest post and see if the issue still occurs when you set a 60 second delay?
This issue is very difficult to replicate and so far I have had no luck seeing this on my test players. If yourself or any other members of the community are able to confirm if this reduces the instances of this issue occurring that would be very helpful.
Many Thanks.
Hello @DanBW
Sorry for the delayed update, but we were working on this issue, and trying to assemble all solutions and tips provided in the forum (thanks for mentioning the other posts).
So far we identified the following in our affected PC (which is a Acer Aspire A3 notebook with a i507200 CPU, 4Gb of RAM, Windows 10 Single Language 64bit 2004 build 1083, Feat. Experience pack 120.2212.3530.0, Intel HD Graphics 620 with driver ver 26.20.100.7261 1366x768 @ 60Hz , Xibo Player 2.257.2)
To start, we´ve setup a Player configuration to comply with the recommended resolution of the notebook display: 1366x768 pixels. We have even tried -1, -1, 1370, 770, with the same (undesired) results
Then we´ve updated the Intel Graphics HD 620 adapter using the manufacturer latest release. Again, no luck.
Test 1: Increase the startup delay to 60 seconds in Windows registry as suggested in the post (HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize)
Result: inconsistent. The Xibo Player window will sometimes display in the wrong position - in the first initialization in the morning, or if I restart the notebook (either manually or sending a command from Xibo CMS)
Test 2: Disable the startup of the Xibo Client.exe in Windows Startup - and created a Scheduled Task: delay of 60 seconds, after any user logon.
Result: achieved a better result (approx. 9 out of 10), but the Xibo Window icon will be active in the Windows´ Task Bar until I actively click the mouse.
Test 3: Still running the scheduled task, I´ve setup an AutoIt macro to left click a random spot in the screen so the task bar will lose focus and hide itself.
Result: almost perfect, but sometimes the taskbar would be displayed (or the Xibo window was displayed in the wrong position). So I followed another tip from the forum: I moved the taskbar to the side, and set it not to be locked. This simple hack apparently made this issue with the taskbar disappear.
Test 4: Install Xibo Player version 300.5 from scratch
Result: none of the solutions worked. The window was displayed in the wrong position more than 70% of the notebook hot and cold starts. So I uninstalled, removed all the Xibo folders and entries in the registry, and reinstalled version 2.257.2
Test 5: re-enable the Xibo Player in the Window Startup and disable the scheduled task.
Result: so far, we have a good score - the windows position seems to be holding up well in the last 10 reboots, but we are not confident that this will sustain, according to our test 1 above.
In all tests, if the Xibo Player process is killed (or closed), and then the Watchdog relaunches it, the window will always be displayed fullscreen, as intended.
So far, the combination of these tweaks seems to be the best (but not definitive) solution so far:
- have a Player configuration in Xibo CMS to explicitly declare the resolution of the screen/windows
- use the registry modification to delay the startup to 60 seconds
- use a scheduled task to delay 1 minute the launch of Xibo Player.exe, after any user logged on
- move the taskbar to another position than bottom, and unlock it (but still having it to auto hide), so it will not be displayed with the Xibo Player icon active
Is there a way that we could confirm where, how and when the Xibo Player process will retrieve the information from the display driver / settings / registry while starting? Or could it be a Intel driver issue, more specifically related to the 620 model?
Thank you so far, @DanBW for your attention - but this is a big issue to our client, who is considering moving to another platform because of this issue - the end user is a big company, and is not ok with having the Xibo Player window closed when the offset occurs.
Best regards,
Norberto
1 Like
Hi Norbies. Thank you very much for the tests you have performed and for passing this information on. I will inform the development team about your test results so they can look into what changes can be made to resolve this issue. Thank you also for the information about the version 3 player, this is also helpful.
If any other users experiencing this issue have also tried the startup delay and have had different experiences to the tests above, please post your findings.
Many Thanks.
Hi,
Delaying the start of the application didn’t work.
I changed another player from HDD to SDD and it is ok now and I don’t have this problem on all players where I changed to SSD.
p.s. Player V3
Hi Miguel_Ferreira. Thank you for also trying the startup delay and confirming that this has not resolved your issue but that changing from a HDD to an SSD has. This is also helpful information for the developers and I will inform them about this as well.
Many Thanks.