I’m using Xibo Cloud 1.8.9 at the moment and have it connected windows player, running on a win7 local vm (virtual box).
I have enabled Proof-of-play for the given Display but I’m unable to confirm when proof-of-play data will be synced to the CMS. I’ve read the KB on Statistic Reporting, and it sounds like proof-of-play data are sent once a layout has been completed. But in the scenario or setup that I had created, this does not appear to be the case, perhaps I have misunderstood the KB explanation. Would some one be able to advise when proof of play will be sent given my setup in the following.
One display, schedule to run 10 different/separate layouts. Each layout consist of 1-item (1-image), each layout last for 10 seconds. I’d scheduled these 10 different layouts to run for the next 10 days with the same day and time setup.
I ran the above setup from 7.30pm to about 9.30pm last night, resumed the player this morning about 7-ish, still running now. The last proof of play data I’m seeing is up to 8:30PM last night…
Can I manually trigger the proof-of-play to sync? I’ve tried manually triggering the items under TASKs, but no luck.
It could be better to contact Spring Signage directly via ticket and let us know which CMS Instance you’re using.
As for the stats, they are stored and then sent from the player, assuming that player is connected to the CMS it should be sending the stats as per the FAQ topic about it.
Assuming that I know which CMS Instance you have in mind, then there are stats from 2018-05-07 there, displays does not appear to be online now.
As for future reference for those others who may face similar issue. These are my findings, based on the current Xibo Cloud 1.8.9 CMS .
Proof-of-play data are sync along with the Collect-Interval. Thus depending on the collect-interval set for the display, it may be 5mins or 24hrs away. It was recommended that, if you have a short interval layout runs, then it may be worth having a shorter collect-interval, as this allows smaller batches of the stats file to be uploaded to the CMS, compared to a massive batch. Of course if you have longer run time layouts, then it is worth well setting the collect-interval longer.
In resolving my specific issue about the proof-of-play not updating correctly. I ended up creating a new cloud instance, everything worked like expected. Thus in the old cloud instance I must have done something stupid and caused a flow on effect.