After adding an event to a screen (XMR running) the Infoscreen shows “files to download” for a long time even though the player already plays the media.
Collect interval: 1 hour
After adding an event to a screen (XMR running) the Infoscreen shows “files to download” for a long time even though the player already plays the media.
Collect interval: 1 hour
I can’t recreate this issue locally, I assume all files have (100%) and are in the player library and are also correctly displayed?
What’s the player status in CMS?
Display -> Manage : The status for all media shows completely
Yes it is …
Now it’s gone.
It seems as if it went away after 1 hour.
Collect interval: is 1 hour
It’s rather strange, on player window it should be updated as it downloads new files, I’d be less surprised if in the CMS -> manage would show some files as not yet downloaded.
New trial
files to download : 6
Media in the Layout: Tide1, Tide2 … Tide5
You can check the CMS with the known data.
Problem seems solved. It only happens when client and CMS are on the same computer.
interesting, I actually did my test with that configuration, although in docker environment.
Both Client and CMS on Windows Server 2008. There also the screenshots do not work.
If request screenshot does not work, then that would imply problem with XMR configuration.
What do have set in public and private XMR addresses in CMS settings / display profile?
For external Clients:
Settings / Display:
XMR Private: tcp://localhost:51001
XMR Public: tcp://xxx.xxx.xx.242:9505
Firewall portwarding to: 192.168.2.233:9505
Internal Client
is in its own display profile : tcp://192.168.2.233:9505
I think this will overwrite the global Settings / Display: tcp://xxx.xxx.xx.242:9505
Config.json:
{
“listenOn”: “tcp://127.0.0.1:51001”,
“pubOn”: [“tcp://192.168.2.233:9505”],
“debug”: true
}
I believe that private should be:
tcp://xmr:50001
Could you try changing that?
and Public should be the DNS name or IP address that you access the CMS at (as the Player sees it)
tcp://name:9505
so that’s probably correct.
Have now tried all possible variants. Screenshots do not work anyway. Is however no problem because the combination CMS and client on a computer only for test purposes.
Current configuration:
{
“listenOn”: “tcp://127.0.0.1:50001”,
“pubOn”: [“tcp://192.168.2.233:9505”],
“debug”: true
}
Settings Display
XMR Private : tcp://localhost:50001
XMR Public : tcp://xxxxxxx.com:9505
Displayprofil Internal Client
XMR Public Address : tcp://192.168.2.233:9505