Content

From SpinetiX Support Wiki

Jump to: navigation, search

Introduction

The term content refers to all the resources that are connected and presented together on an HMP in order to create a digital signage presentation. A resource can be a SVG animation (Layout, Playlist, widget), a multimedia file, an image etc. (see supported file types below); not all file types are supported by the HMP though. These resources can be stored on the local storage or retrieved from a content server.

The content for HMP can be managed using Elementi , built-in player web interface / Fusion or other third party applications. The content can be pushed onto the HMP local storage or on a content server and retrieved by the HMP from there. The HMP will then render and output that content to be displayed by a screen or projector.

The settings related to content can be configured from Control Center on

File types

Supported files types

The Hyper Media Player can parse and execute the code inside SVG / SMIL / JS files, and decode images (JPEG, PNG, GIF, SVG) and multimedia resources like: video, audio and streaming medias.

Data from RSS feeds, text files, CSV spreadsheets, ICS calendars can easily be displayed on the screen using data-driven widgets. Other text-based files (like XML, JSON, HTML, ASP, JSP etc.), can also be used, however some additional formatting might be required to display that information on the screen.

Content from web pages can also be displayed in certain conditions - see the Web content page for more details.

Unsupported files types

Except for the files types mentioned above, the rest can be considered as unsupported, either because they are proprietary formats, require too much resources, or are simply not suited for digital signage applications. Some common examples of such file types are: Flash, PDF, Databases, Word documents, PowerPoint presentations etc.

Some of these unsupported file types can be converted into a supported type of content, as images or videos for instance, and then used with the HMP - more details can be found on the following pages:

Management

The content can be managed (created, updated etc.) using:


The content can then be delivered on the HMP using the following methods:

Method Description Requirements Advantages
Content push The content is directly pushed on the HMP storage, using Elementi, the player web interface, Fusion etc.
  • Direct network access to the HMP
  • No server needed
  • Network access needed only during the update
Content pull The content is first uploaded on a content server and then retrieved by the HMP from the server using different methods (in a scheduled manner or "live").
  • Direct network access to HMP not required
  • Compatible with firewalls and NAT
  • Automatic content update according to a schedule or on-demand
  • Network used only during updates
Plug & play USB drive The content is first copied on a USB drive (which is then plugged into the USB port of the HMP) and played by the HMP directly from the USB drive .
  • No network access required
  • Larger storage space for the content
  • FAT file system can be used with most PCs


Note Note:
The different methods described above can be combined between them if required. For instance, the media content can be locally managed using the player web interface, yet have an Elementi project that is retrieved from a web server using Pull Mode.

HMP content interface

The HMP features a WebDAV-enabled HTTP server running on TCP port 81 (http://HMP_address:81/), providing access to the content stored on the HMP.

  • For HMP350/HMP300, by default, the access to the content interface is protected by the admin password; Additional users can be created using the User Management page.
  • For HMP200/HMP130, by default, the access to the content interface is not protected, and anybody can list or push content onto the HMP; if protection is needed, the access to the content interface can be secured by setting a password for the content user.
  • This interface is replicated on the main interface of the HMP under /content path (i.e. http://HMP_address/content/).

Accessing the content on the HMP

The content stored on the HMP can be accessed by:

This page was last modified on 18 November 2016, at 19:09. This page has been accessed 11,243 times.