Linux Player - Technology Preview 0.4-alpha


#1

Today we're making available another preview of the forthcoming Player for Linux.

This new version supports downloading and processing the schedule from the CMS and is for the first time long-running, so it will switch between layouts as dictated by the CMS schedule. Overlay and command schedules are not supported.


This is a companion discussion topic for the original entry at https://blog.xibo.org.uk/linux-player-technology-preview-0-4-alpha/

#3

Very nice to hear you’re making progress on this guys!
I am getting this error thought after layout has been dowloaded
“Player failed to start: /resources/2.xlf(470): unexpected end of data”


#4

Hello all !

Thank you to share this work with us.

Two questions :

  • Is it normal to see the 0.4 is not displaying fullscreen ?
  • For now all the video files are crashing the OS, is there something to install to make it work more fluently ? VLC installation seems to not change anything.

Chrs


#5

At the moment it’s setup to run in a Window.

What’s the message you get when it crashes with your videos please?

What OS and platform are you running on? What’s the output of snap list xibo-player-test


#6

OS :
Ubuntu 18.04.1 LTS 4.15.0-45-generic
CMS : 1.8.11
Snap List :
xibo-player-test 0.4-alpha 50 beta stivius
Hardware :
VMs, Intel Nuc, Intel Stick, Assembled PC with Nvidia Graphic card : strictly same symptoms

On the 0.3.3 version, the video files have been very slowly played.
On the 0.4-alpha :
[15:34:27.128] [debug]: Collection started 140252168513280
[15:34:27.782] [debug]: Display is active and ready to start.
[15:34:27.782] [debug]: Collection interval updated. Old: 5, New: 60
[15:34:28.856] [debug]: 20 files and 0 resources to download 140252168513280
[15:34:30.363] [debug]: [xibo-dataset-render.js] Downloaded
[15:34:30.605] [debug]: [12.otf] Downloaded
[15:34:30.932] [debug]: [jquery-cycle-2.1.6.min.js] Downloaded
[15:34:30.946] [debug]: [flipclock.min.js] Downloaded
[15:34:31.111] [debug]: [compatibility.js] Downloaded
[15:34:31.309] [debug]: [xibo-text-render.js] Downloaded
[15:34:31.411] [debug]: [xibo-image-render.js] Downloaded
[15:34:31.525] [debug]: [8.otf] Downloaded
[15:34:31.673] [debug]: [9.otf] Downloaded
[15:34:31.712] [debug]: [xibo-webpage-render.js] Downloaded
[15:34:31.740] [debug]: [xibo-layout-scaler.js] Downloaded
[15:34:32.136] [debug]: [11.ttf] Downloaded
[15:34:32.323] [debug]: [jquery.marquee.min.js] Downloaded
[15:34:32.324] [debug]: [4.xlf] Downloaded
[15:34:32.681] [debug]: [10.ttf] Downloaded
[15:34:33.741] [debug]: [jquery-1.11.1.min.js] Downloaded
[15:34:33.977] [debug]: [moment.js] Downloaded
[15:34:35.905] [debug]: [pdf.js] Downloaded
[15:34:46.223] [debug]: [pdf.worker.js] Downloaded
[15:35:09.924] [debug]: [19.mp4] Downloaded
[15:35:09.925] [debug]: Files downloaded
[15:35:09.925] [debug]: Resources downloaded
[15:35:09.925] [debug]: Received collection result
[15:35:09.925] [debug]: Log level updated

(player:7165): GStreamer-CRITICAL **: 15:35:09.983: gst_tag_list_get_scope: assertion ‘GST_IS_TAG_LIST (list)’ failed

(player:7165): GStreamer-CRITICAL **: 15:35:09.983: gst_tag_list_insert: assertion ‘GST_IS_TAG_LIST (into)’ failed
[15:35:10.159] [error]: Player failed to start: Not valid path


#7

You’re definitely not trying to run it as root with sudo?


#8

Has the layout been downloaded if you look in 2.xlf? If not, check your SENDFILE_MODE setting in the CMS. It must be Apache or Nginx - and the webserver configured for that appropriately - for this version to work with your CMS.

0.5 will have support for CMS instances that use the legacy download mode.


#9

I am not using sudo

I have not made any modification on the cms (docker) but I will check those points.
What it makes me think there is a video files issue is that when the layout provides only pictures or any web contents (pages, texts or else), everything is downloaded and playing correctly.

I’ll be back to you.
tx


#10

If you’re using Docker with Xibo 1.8.12 CMS then you don’t need to make any modification - it’s already correctly setup for you.

I’m not seeing the same crash here with the nvidia binary drivers, and others have managed to run on Intel hardware without issue.

Please try the upcoming 0.5 which I know has a fix for one video related issue. If it’s no better, then we may need some more detailed information from you so we can replicate it.


#11

Ok.

Is there a way to test again the 0.3.3 version ?


#12

I don’t believe so no. With snaps you can’t pin to a specific version, only a specific channel.


#13

0.5 is returning this :
[10:37:55.696] [debug]: Collection started
player: /usr/local/include/boost/optional/optional.hpp:1215: boost::optional::pointer_type boost::optional::operator->() [with T = Url; boost::optional::pointer_type = Url*]: Assertion `this->is_initialized()’ failed.
Aborted (core dumped)


#14

0.5 hasn’t been released so there’s nothing to test at the moment. You should be using the beta channel snap package only please.


#15

Hi, we managed to install the player but it doesn’t seem to work. When trying to start the player

installed with channel beta the error is as follows:

Session finished with error [HTTP]: Host not found (authorative).

The player never becomes visible to the CMS. While using channel edge the error is like

this:

Player failed to start: /home/user/xibo/resources/43.xlf(10): unexpected end of data.

With the channel edge we’re able to authorize the display, but it crashes while it is

starting to play its scheduled content. Here are the contents of 43.xlf:

<!DOCTYPE html>

<html><head>

<title>301 Moved Permanently</title>

</head><body>

<h1>Moved Permanently</h1>

<p>The docment has moved <a href="https://oursite.com/xmds.php?

file=IlEvDvVEr4dRWr2ntjvhifIRf8xDiZMJ&amp;type=L&amp;itemId=43">here</a>.</p>

<hr>

<address>Apache/2.4.18 (Ubuntu) Server at oursite.com Port 80</address>

</body></html>

I assume that the player is expecting layouts, but only receives this error message,

and as a consequence it crashes? What could be the error in these two cases? Any suggestions for a

solution?