Also I think specifying the duration could get complicated. It should display for the amount of time in "Default Duration" or the duration of the video asset.
Just found this after posting something similar. This would be great at the bars because we'll get beer commercials that we display in between house slides but we don't necessarily want to show them every single playlist loop. I was thinking there could be an "Asset Frequency" and maybe its just an integer that displays that asset every X loops through the playlist.
We are planning to provide trigger support within 2019.
We are now in the process of restructuring our rendering engine in order to allow several features to be implemented. One of these features is triggers. We are planning to initially support UDP, TCP/HTTP, GPIO events, and then support keyboard/mouse events.
[Draft Specs follow:] Triggers will be available as a different menu item, in order to manage, set them up, test them, and so on. After setting them up, Users will be able to use them in Playlists, e.g. to skip a Media (or Subplaylist) entry, jump to specific Media (or Subplaylist) entry, and so on.
Agree with Mike for remote triggering of events. Perfect example... For our bars we currently have a pi setup that is triggered via a web request to duck the audio in the bar, play the Blackhawks horn and then trigger a Wemo switch to turn on a bunch of red goal lights. It would be cool to integrate the signage somehow to make it flash the words GOAL or something like that. Think cheesy animations that you see at bowling alleys when you get a strike. :) Customers love that stuff!
We supported x86 until Jan 2017. Adoption was really, really low, since a) we provide the Player for free to direct customers, and b) using the Raspberry Pi saves you so much on electricity, recovering the cost of the RPi within a couple of years.
We are planning to develop soon an HTML5-based player, so this could be easily wrapped to work on x86 hardware.
Stay tuned for updates.
HTML 5 player sounds awesome!
Supporting ICS files/URLs natively on Yodeck (and not being displayed from an online service through a Web Page) has been coming up in requests. This requires a new Widget and some serious development.
We are growing the team, and new team members coming on board will start working on new Widgets, with focus on the main social widgets and this calendar widget. These two are the most requested features so far.
This is great news! Thrilled to hear this feature is coming and even more excited to hear Yodeck team is growing! Congratulations!
I wanted to expand on my last comment... We've been using the third party plugin in WordPress along with another plugin that formats it for the screen from a competing digital signage company that shall remain nameless. I wanted to report that having put it in production for awhile it absolutely sucks. This is something that would absolutely be a great feature to include natively or via a widget if possible.
I'm out of votes right now but this would be a very welcome feature. Right now the way we do this is through WordPress and a third party plugin that formats the calendar. It's not pretty. Ideally it would be great to pull this directly from Google Calendar and have it display. Can you guys please post your script as an example? Thanks!
This makes sense. We will add support for a second WiFi soon.
We are also provide support for WPA Enterprise.
We do plan to provide a Yodeck Player app for Android. As you may understand, this requires a lot of effort. So, it might take several months until it gets completed. We target the end of 2017 for a first version, but it may well be 2018 until it gets released.
I recently saw that NEC has a TV that supports the CM3. Maybe this is a path for integration?
Yes, we do plan to have a Widget marketplace. :-) It is great that you are interested in this, hope we have more Partners and people coming in and voting for this one!
Out of votes but yeah I would love to see this as well. I think the widgets are a powerful feature and it would be very helpful to collaborate and share with others.
We plan to provide for more complex notifications settings. This will include mobile app notifications (not sure if it is going to be Pushover or our own app), custom email notifications, even SMS notifications.
A native app would be great but that's going to take time. SMS is a PIA and cumbersome and it has an incurred cost. Having everything all neatly organized in Pushover (or a Yodeck app) would make for a much cleaner experience because then you can individually clear alerts (or all alerts) essentially using it as a checklist for what to investigate. Don't forget to make this reseller friendly (we need to know what's going on at customer sites!)
Although it sounds interesting, this feature needs refinement.
In the new version to be released this week, we do have a text Widget. You could add this text Widget to all Shows on top of all other content. You would set it to transparent background and do not type anything. Then, when ever you wanted to sent a message, you would edit the Widget, type the message, and push to all devices. But would this suffice as an “emergency broadcast”?
If you are interested in this feature, please leave more comments and discuss further.
What would be cool is if there was some sort of HTTP API that you could remotely trigger a show to temporarily override the currently playing show. For example, at our bar customers, we have sound effects boards configured so that when there is a hockey game score, they press a button and it triggers a sound effect (horn and 20sec of music) and while that sound is playing we turn a red dome light on via a WeMo switch. When the song is done playing it sends an off command to the WeMo switch. What would be cool is to have a predefined show with a video in it that had some sort of animation that said "GOAL!!!" or something like that and have it triggered at the same time during song play then return to scheduled show when the "off" command is sent. This would probably be best to have an HTTP API running on the media player itself with a static assigned IP that could be called locally.