API for external Web Sites
It’s really simple to embed a media file into your static web page or a page generated by a CMS by using the provided API. To embed a video you need to provide an IFRAME with the wanted width and height as shown in this example:
< iframe width="400" height="300" src="http://publicSitesServer/sites/embed/CatalogName/RecordID" frameborder="0" allowfullscreen>
The player loads into that IFRAME by using all space available. The used Sites installation needs a valid configured directURLUser that has access to the given record. In addition to make things secure the record needs to be enabled for a direct Preview URL. The RecordID is either the plain id or a randomized ‘encrypted’ non-guessable value for the given id. That secret ID is stored in the sub-table as external ID for all internal formats.
The API also supports playing a specific segment. In this case the URL gets a parameter ?t=segmentID The URL can also be retrieved by clicking the little share icon in the list segment icons.
User with permission to create user comments can create a time-segment comment in Sites. Such a comment consists of a headline, a longer description text and a start time and duration for the media file. Such a comment can be used to mark specific segments of a video which might be of special interest for a consuming user. For example you could mark the interesting events in a sports game or a specific speaker talking in a longer discussion. If the logged in user has permission to create comment replies it’s possible to reply to such a time-segment comment. This gives users a possibility to provide feedback for your selected segments or the entire video.
Virtual any media file can be processed by the Attention Video Suite to provide a web-compatible streamable version. For video files there are four different quality levels offered, ranging from an MP4 with 360p resolution up to high quality MP4 with 1080p resolution. This enables you to stream to all kinds of devices, small handhelds with low bandwidth and high end devices supporting high resolution videos. When using the provided media player the end user can switch between the different quality levels on the fly. Audio files should always be converted into the two different formats MP3 and OGG which have the same quality but each of these formats is only supported by some of the available browsers and end devices. To support all browsers it’s recommended to always provide both MP3 and OGG at the same time.