Oohdesk CMS has developed several types of players:
Windows. An application installed on a computer running Windows OS versions 7/8/10. Installation instructions can be found in the Wiki.
Android. An application installed on devices (TV box, tablet, phone, TV) running Android OS starting from version 4.4. Versions 5.1 and above are recommended. Version 4.4 does not support screenshots. Installation instructions are available in the Wiki.
Samsung SSSP 2/3. Application for professional panels. Installation instructions can be found in the Wiki.
LG WebOS 2/3. Application for professional panels. Installation instructions are available in the Wiki.
Hardware player Oohdesk CMS model-3. Delivery time from 1 to 4 weeks (large batches). Player specifications can be obtained via this link 
Player for single-board microcomputers Raspberry PI 3. The Oohdesk CMS player for Raspberry has functional limitations: images and HTML are currently not planned to be supported. However, most other functions are supported.
Where to download players?
Player distributions can be downloaded in the Settings -> Distributions section.
Where to buy hardware players?
Our hardware players can be purchased from our distributors:
- Profdisplay company
- ELITTECH company
- QUARTA company
Comparison table of features and limitations:
| Hardware player | WINDOWS | ANDROID | SSP3, TIZEN (SSP4) | WebOS 2,3 | |
|---|---|---|---|---|---|
| Offline operation (content is cached in the player’s memory and does not require a constant internet connection) | + | + | + | + | + |
| Seamless content playback (frame-by-frame) | + | + | + | + Works for Tizen. On SSSP3, seamless playback works only for panel firmware versions below 1037. | + |
| Support for touch and interactivity. Collection of data on taps and form filling, sending to the server. | + | + Additionally, it is possible to configure the app to minimize on screen touch. Commands to minimize/restore the player can be sent via the player's API. | + | ||
| Support for an independent audio track (separate audio control). Audio clips can play sequentially or in random order. | + | + | + | - | - |
| Support for random video playback order. | + | + | + | - | - |
| Support for device power on/off scheduling. | - | - | - | + Turns off together with the player. Power-on is controlled by the internal screen timer. | + The player continues to run. Only the display panel (matrix) turns off. |
| Remote reboot of the application/device by command (manual reboot via web interface) | Yes, the device reboots. | Yes, the application restarts. It can also be restarted separately.Windows. | Yes, it is possible to restart only the application. | ||
| The device cannot be rebooted. | Yes, the entire panel is rebooted. | Yes, the entire panel is rebooted. | |||
| Automatically reboot the device on a schedule | + | + | - | + | + |
| Broadcast statistics | + | + | + | + | + |
| Screen zoning | + | + | + | + Main content plays full screen | + Main content plays full screen |
| Support for HTML content (web pages, CSS, JS; executed locally, cached in player memory) | + | + | + | + | + |
| Support html URL (external web pages) | + | + | + | + | + |
| Image support (jpg, png) | + | + | + | + | + |
| Video support (mp4 only, h.264 codec) | + | + | + | + | + |
| VAST content support | + | + | + | + | + |
| Integration with Yandex | + | + | + | + | + |
| ITPV content support (m3u8, Dash, HLS, RTMP) | + | - | + | - | - |
| Support for Oohdesk CMS applications (as widgets or in full screen mode) | + | + | + | +/- | |
| Partially supported (aviatablo) Due to the fact that the panels have an outdated browser, the layout of applications may not be displayed correctly. JS too. | +/- Partially supported (aviatablo) Due to the fact that the panels have an outdated browser, the application layout may not be displayed correctly. JS too | ||||
| Working with data streams and rendering the received values in locally stored HTML content. The data stream and feeds come from the Oohdesk CMS server. More details: External data integration | + | + | + | + | |
| Working with data streams and rendering the received values in locally stored HTML content. The player itself takes the data and feeds without the participation of the Oohdesk CMS server. More details: External data integration | |||||
| + | + | + | + | + | |
| Support for PUSH server and integration with emergency notification systems. More details: external trigger | + | + | + | + | + |
| Possibility of screen zoning | + | + | + | + | + |
| Content Broadcast Statistics | + | + | + | + | + |
| No external static IP address required (works through NAT) | + | + | + | + | + |
| Reloading interrupted content download to the broadcast point | + | + | + | + | + |
| Getting screenshots | + | + | + Only starting with Android 5. On versions earlier, the request to receive is ignored. | + | + |
| Email notifications to specified recipients when errors occur at broadcast points | + | + | + | + | + |
| Possibility of monitoring broadcast points to control their status: Network connection; Content download progress | + | + | + | + | + |
| System for analyzing the quality of communication at broadcast points (graph) | + | + | + | + | + |
| Synchronous operation (frame-by-frame) in video wall mode. | - | + Synchronization by the first frame of each video. Dynamic master formation. In case of master loss, automatic assignment of a new master. | - | - | - |
| Configurable timers for automatic player/panel reboot. | + | + | - | + | + |
| Watchdog. A service that monitors the player's operation. In case of abnormal situations, watchdog restarts the player. | + software | + software | + software | + software and hardware | + software and hardware |
| Automatic cleaning of memory from unused content | + | + | + | + | + |
| Possibility of remote updating of the player software without the need for technical personnel to be present at the player/panel installation locations. | + | + | - The update is downloaded to the device, but manual confirmation of software installation is required | + | + |