Hi all those who are smarter than me (or at least know screenly better)
I used Screenly in the past (still have 1 screen running it continuously) but as I read a while back about the API call possibility in the newer Screenly, it became really interesting to me to use Screenly again for an upcoming project.
I want to hang 3 screens side by side that ‘interact’ with eachother. I want to be able to stretch a single message over the 3 screens, only to have them do their own thing afterwards. (i.e. have an image (5760x1080) cut in 3 parts, and have each of the 3 pi’s the image-part that corresponds to their location in the row of screens).
As far as I can gather from the doc’s, it is now easy to do an API call to all three screens to imediatly activate the asset in question and create the illusion of a single message.
Now I need to make that API call to each of the three screens. I have thought of 3 options for now:
- Have a seperate Pi that runs some software that does the api-calls at the intervals wanted. I must be able to alter the settings from anywhere in the world, with any device. (I was thinking domoticz with dzvents actions. p.s. I only know Screenly as taking the whole OS, but I might try to install domoticz or a better program on one of the pi’s running screenly, thus no need for a 4th pi after all)
- Have cron instructions on one of the three pies, that does the API calling. (This however is not really easy to change if you’re on the road and have only your smartphone to change the settings.)
- Have the first Pi’s screenly send a API call to the second Pi (and the second Pi to the third pi) as soon as it is about to load the asset. (Easiest and cheapest solution, but as far as I know, Screenly does not support doing an Api-call upon loading an asset)
As I am most likely not the first to use multiple screens side by side and have them synchronised on occasion, I wonder what others have done to do so.
p.s. Just thought of a fourth option. I do not yet know how to implement it exactly, but as I remember, I can call a web-page from screenly. What if I would set up a web-server on the first of the three pi’s, next to screenly. I then might have the 1st screenly having one asset that calls a web-page on the same pi, that webpage in turn would just do 3 API-calls, thus also would straight away remove its own focus as screenly now got the command to show the asset it needed to display in the first place, along with its 2 neighbours.