Kara
My feedback
15 results found
-
21 votes
This does seem indeed promising! We will be investigating and letting you know!
Kara
supported this idea
·
-
47 votes
We do have customers using touchscreens with Yodeck. We do plan to provide some better support for configuring the touchscreen.
Touchscreens are usable with Widgets and Web Page, and we plan to expand support for navigating content (move to next, previous) and add support for an on-screen keyboard and navigation buttons for the web browser.
Kara
supported this idea
·
-
57 votes
We are planning to provide trigger support within 2020.
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.
Kara
supported this idea
·
-
23 votes
This makes sense. We will add support for a second WiFi soon.
We are also provide support for WPA Enterprise.
Kara
supported this idea
·
-
6 votes
We have worked on this. First, we have removed action buttons in listings, but we might also need to remove the main navigation items that the user dos not have access too.
Kara
supported this idea
·
-
11 votes
First, keep in mind that this icon indicates that the device is overheated so it is being throttled down (lowering performance) in order to prevent the temperature from rising. This has a performance hit, but it does not affect reliability severely. So, we do not consider it a critical issue. You have “hot” devices running, and they will work fine throttled.
The device temperature is available in the “Status” tab in the Monitor details of the Yodeck portal, so it is actually available in the UI.
It does make some sense to warn the user, since the overheating can be managed so that there is no performance hit. We are planning to create a kind of message centre inside the app to provide important messages to Users, which could include some device status alerts. I am marking this suggestion as “Accepted” and we will investigate when this message center is…
Kara
supported this idea
·
-
40 votesKara
supported this idea
·
-
4 votesKara
supported this idea
·
-
13 votes
An error occurred while saving the comment -
4 votes
-
1 vote
-
38 votes
-
25 votes
-
13 votes
-
1 voteKara
shared this idea
·
There's a couple ways you could accomplish this without VNC through software or hardware.
As we have recently discovered, you could use the "HDMI extender" recommended by Yodeck's video wall documentation (Lenkeng LKV373A) for this. Connect the PC's video output to an HDMI splitter, the HDMI splitter to both the user's display and the HDMI extender, and connect the extender to your network with an ethernet cable. It will grab a multicast IP address. In Yodeck, you can then add a video stream media object, and point it to "udp://[multicast IP]". Then you'll have a live display of that PC's screen at all times from any Yodeck display, with about a one-second latency. This is definitely not the cheapest or easiest way to do it, but it will require zero intervention from your users and no software to be running on the client machine.
Alternatively, any software that can broadcast the user's screen to the local network over multicast should also work! Apparently, VLC and OBS can both do this.