I’ve been scanning the forums for awhile now, and I haven’t found a solution to my issue yet.
I have a layout with a .jpg background, but I’m still have the issue with transparency behind the text on one windows client (lenovo stick). I’m using version 1.7.6 on server and client. I have a second windows client set up on my laptop that works fine. Both are the same version, both have had the registry keys edited to enable IE11. Both running Windows 10. Both using the same settings profile and same settings per display.
I took a look at the html files used to represent the text in the Xibo libraries, and I can confirm that on the working machine, the background image has been clipped and lined up to view properly, while the background image is not on the other.
Also, I have a weather widget I’ve been trying to add to my layout that works fine in preview on both chrome and ie11, but when loading in the player, has a neverending loading ring.
Is the background image missing from the Player library on the non-working machine? Or just not referenced in the HTML at all?
I can’t help with why your widget doesn’t load, but it’s very likely cross-origin policy preventing a local file:// resource from accessing something online. Xibo 1.8 uses a local webserver to avoid these issues in the majority of cases, and comes with built-in weather widgets.
I thought I may have figured it out, not realizing I was using a 720p display and had the background set as 1080p in the layout, but fixing that issue didn’t quite fix it. the bg is referenced in the html holding the region though
Yet if you open that file in Internet Explorer, the background image isn’t shown?
If that’s the case, then since Xibo is using IE to render that, I don’t think it’s an issue with Xibo itself, but more some issue with Internet Explorer.
It would be worth ensuring you have all the up to date Windows updates, the latest graphics drivers from the chip manufacturer (not from Lenovo), and doing a full reset on the settings for IE incase there’s some extension or similar interfering.
Reset IE to default settings, no luck yet. Updating windows and then I’ll update the graphics drivers and let you know. It couldn’t be a problem with memory or maybe a required IE plugin that’s missing could it?
As you’ve probably worked out, the windows player doesn’t support any sort of web transparency, which means that to show a background image we have to create a copy at the correct size and then position that as the CSS background of each widget - positioned to line up with the main background underneath.
The background images is created and positioned based on the detected screen size, in your case 1280x720.
I wonder if we are seeing some disconnection between the size detected by Xibo and the size windows thinks - in windows 10 their is an option for screen DPI in the windows graphics settings - can you make sure that is set to 100%?
I checked all of the settings and everything seems like it should be fine. I tried setting the same player up to a different 1080p screen, set the background back to 1080 and tested it and still nothing…I’m thinking it may be some strange hardware issue. I’ve ordered new hardware to test everything out with. so we’ll see how that goes. I’m still willing to test things out if there are any other suggestions
Assuming most of this is just a matter of me trying to schedule the same default layout (I guess I thought it would force it to refresh the layout on the player), but that Preparelayout unable to set background seems like a clue
You could try clearing out your local library of everything except the hardwarekey and config.xml file, this would force the player to recreate all of its cached resources from scratch.
I’ve no idea if having a ' in your username could be causing an issue - do you use the same user on your working displays?
Would you imagine that it was definitely the ’ in the username? Created a new user on the computer minus the apostrophe and everything works perfectly.
Way too much time wasted on such a menial fix. Glad it’s all figured out though. Thank you for all of the help! Hopefully this will help you out if someone else has a similar issue
