I'm currently have 3 screenly[1] installations on RPis and works nice. Doesn't support channels though, which is a major drawback for DS but other than that works fine and it's open-source.
If by 'channels' you mean breaking the screen into different blocks (normally referred to as 'zones' in DS language), it is possible using HTML, but strongly discouraged. The reason is simply that the Raspberry Pi isn't powerful enough to handle that heavy workload.
Regarding the browser Screenly OSE (the Open Source version) uses, it's called UZBL[1]. It does support JavaScript, as long as it isn't too complex. For instance, animations etc won't work. Also, Flash isn't supported for obvious reasons.
This looks great, but it's a shame that the chromecast itself is hostile to personal testing or use.
If I didn't have to go through at least 4 bullet points just to get my chromecast listed on a central registry I'd be much more willing to try this out.
Interesting way to put content on screens. What's the performance like on chromecast?
I wrote a web based digital signage system ( http://www.streetsign.org.uk ) which we've used at a few conferences, and now at a couple offices around the world. The display-clients can be any web capable computer, but we're mainly using raspberry pis. They really don't have great performance, in terms of smooth transitions & scrolling text, etc. Even with the experimental collabora browser. But they're cheap.
I'd wondered about using chromecasts as clients, but wasn't sure if the built-in chrome would be up for it, and what performance would be like...
Note: beware the speaker volume for the 'takeover' button.
I've had an idea for a brick and mortar advertising network for small businesses, but its difficult to track conversion for ads in the physical world. Groupon, whats your angle?
Am aware of a high school that tried to use a Chromecast for digital signage (not this particular software) on the same network as students (woops)... needless to say the screen wasn't showing their digital signage for long! After a prankster played a few "educational" videos for the whole cafeteria, school admin panic ensued and that was the end of the Chromecast for signage plan.
(This scenario wouldn't happen of course on a network where you have 100% trust that no-one else is going to hit the Chromecast button on their browser or phone...)
Nitpick: doesnt work on Chrome on ios. Didnt test Safari, but its a pretty good idea to check mobile views before a show hn. I cant even tell if its a product page or the actual app.
I'd hoped it was a custom firmware replacement for the Chromecast, rather than an ugly hack on top of Google APIs.
I'd rather stick to the much more open solutions, like the Raspberry Pi, or for more computationally intensive signage, a small Intel NUC or Shuttle PC designed for signage.
[+] [-] NaNaN|11 years ago|reply
[+] [-] atmosx|11 years ago|reply
[1] http://www.screenlyapp.com/
[+] [-] mvip|11 years ago|reply
The creator of Screenly here.
If by 'channels' you mean breaking the screen into different blocks (normally referred to as 'zones' in DS language), it is possible using HTML, but strongly discouraged. The reason is simply that the Raspberry Pi isn't powerful enough to handle that heavy workload.
Regarding the browser Screenly OSE (the Open Source version) uses, it's called UZBL[1]. It does support JavaScript, as long as it isn't too complex. For instance, animations etc won't work. Also, Flash isn't supported for obvious reasons.
[1] http://www.uzbl.org
[+] [-] hendry|11 years ago|reply
[+] [-] alloyed|11 years ago|reply
[+] [-] deckiedan|11 years ago|reply
I wrote a web based digital signage system ( http://www.streetsign.org.uk ) which we've used at a few conferences, and now at a couple offices around the world. The display-clients can be any web capable computer, but we're mainly using raspberry pis. They really don't have great performance, in terms of smooth transitions & scrolling text, etc. Even with the experimental collabora browser. But they're cheap.
I'd wondered about using chromecasts as clients, but wasn't sure if the built-in chrome would be up for it, and what performance would be like...
[+] [-] bengali3|11 years ago|reply
I've had an idea for a brick and mortar advertising network for small businesses, but its difficult to track conversion for ads in the physical world. Groupon, whats your angle?
[+] [-] tehwebguy|11 years ago|reply
[+] [-] nebstrebor|11 years ago|reply
(This scenario wouldn't happen of course on a network where you have 100% trust that no-one else is going to hit the Chromecast button on their browser or phone...)
[+] [-] thinkingkong|11 years ago|reply
[+] [-] TD-Linux|11 years ago|reply
I'd rather stick to the much more open solutions, like the Raspberry Pi, or for more computationally intensive signage, a small Intel NUC or Shuttle PC designed for signage.
[+] [-] dbarlett|11 years ago|reply
[+] [-] gilnovi|11 years ago|reply
[+] [-] Fogest|11 years ago|reply
[+] [-] mmanfrin|11 years ago|reply
[+] [-] gilnovi|11 years ago|reply
[+] [-] samstave|11 years ago|reply
[+] [-] rodedwards|11 years ago|reply
[+] [-] unknown|11 years ago|reply
[deleted]