Yes some idea of what’s on the layout, what durations are configured, the machine spec, and any logs would be a good starting point. Note we’ve never supported Embedded versions of Windows as they don’t get the full .net framework load from Microsoft. I only mention it as that could be the root of the issue.
Also can you try keeping Task Manager open on top of the Player for a while to see if the black screen coincides with any particular system metric (ie high CPU loading, running out of RAM etc)
You can post up images, but you need to read a few other threads here first to gain “trust” to do so. It’s that way to prevent spammers uploading junk!
So the errors suggest the Player can’t connect to the CMS. You need to investigate why that might be. Prime candidates are missing .net framework updates (and they may not be available to you on Win 7 Embedded), poor network connection (eg wifi connection) and/or faulty cabling/hardware.
By the details of the layout, I mean a text description. So for example, two regions, the first with 2 images, durations 10 and 5 seconds and the second region with a webpage hosted on a local server, duration 90 seconds, in Open Natively mode.
They’re much the same errors as before. The first ones “remote name could not be resolved” are where there’s no connection between the player and your DNS servers. So we’re asking to resolve “server.com” and getting no response. So that’s a simple networking issue you need to investigate. The last lines suggest that then the Player could connect for a period but perhaps some packets were lost or there was some timeout. None of those should prevent a layout with some images on from continuing to play back.
Can’t find any problems with the network. It’s 4 different firestations with over 20 displays, and it’s the same problem on all locations. As said earlier, this was not a problem with Xibo 1.5 and 1.6 on same network.
After updating to 1.7.4 this morning, I have discovered a new problem. Xibo halts on one of my layout that show a html page.
If I restart xibo client, it runs normally until the specific layout. This has never been a issue before.
I have one url layout scheduled that worked fine before update. It’s a page with ongoing rescue missions. The page is live, and it’s updating every 15 sec. So the problem is that the xibo player is not loading next layout scheduled , but only repeat the same url layout
We’d need to be able to recreate it locally as it would need to be run on a development machine where we can see what’s happening.
Can you test with a different URL and see if the issue persists - my suspicion is it won’t as it hasn’t been a problem in testing here.
If so we’ll need to isolate what it is about that particular website that’s causing a problem in a way that gives us a test case we can reproduce here.
After 15 seconds the player loads another layout. I have no layouts with multiple regions, only one region for each layout. Multiple layouts, that I can schedule when I want to see, and for how long. Each layout duration is set to 10 - 15 or 20 sec.
If you set the duration to 15 seconds then it will show for 15 seconds and then move on.
Your earlier message implied that the page you’re loading automatically refreshed itself every 15 seconds. If that’s not the case then we still need to understand what it is about that particular page is preventing the player from moving to the next media item when it works OK with other URLs.
