We were getting some issues as per my earlier post (December). Our CMS is set to only accept HTTPS. I took this to mean that it would not work?
The Player you build with Docker should be the same. If you’re getting a 301 that suggests to me that the CMS you’re connecting to is causing a redirect (perhaps from HTTP to HTTPS). Post requests can’t follow redirects, and the player supports only HTTP connections at the moment.
For further clarification, i’m using the same CMS that we have working with the standard Windows clients.
The CMS I’m testing against answers on port 80 and 443, but Xibo handles pointing the Player to use SSL rather than the webserver doing it. To enable that, you tick the Force HTTPS option in the CMS settings and disable any redirects on the webserver.
It’s only a development preview. It won’t work for you as a proper player. It runs once, downloads a layout and plays it. If you don’t have a suitable CMS then I’d wait for later versions which will support this (although it’s unlikely to be in the next version)
I am actually just testing different platforms for a production environment. Obviously we are able to use the Windows player, but the company has a full-fledged Linux-based IT management infrastructure in place so we have high preference for Linux-based systems. Anyhow, I did end up getting the player working by running the host on the default port in Docker (eliminating the need to add port to the host argument).
Not sure if this has been reported before but video playback as a default layout will not loop the video. After the duration of the video, logs will show
[13:13:03] [debug]: [VideoHandler] End of stream
and the screen will be black indefinitely. Turning on the loop? option when editing the region in the layout does not seem to do anything either.
EDIT: Looks like one of the values for the weather widget is not working as well.
** Message: 13:16:47.838: console message: file:///path/to/xibo-player-test/resources/24.html @6: Viewport argument value “[[viewportwidth]]” for key “width” is invalid, and has been ignored.
As it stands, it will play the layout once and that’s all. It’s not supposed to do anything more at this stage.
If you’re trying to use it as a Player at this stage then it’s not ready for that. The point of us releasing it to you is so you can test specific layouts and give feedback on rendering performance. It’s not ready to be used.
If I have to run this on a T2/T3/Rpi board (that doesn’t have a GUI essentially), will it work? Although its armhf architecture and I believe that’s not supported.
But I want to give it a spin.
I’ve not tested with RHEL and don’t intend to. I think you might be missing the point of us giving these previews somewhat. It’s for you to test rendering on a known working configuration. It isn’t there for testing edge-cases at this time.
That’s not what these development preview releases are about. We have provided you a sensible means to run and test the software, and that is what you need to use.
