Our media delivery platform supports progressive downloads and all major streaming protocols. This way, it doesn't matter whether your videos are watched on pc, tablet, smartphone or TV-set. Moreover, with a single codebase or embedding code you can deliver your media to a multitude of devices, players and platforms.

This demo uses the fallback mechanism built into the Jeroen Wijering player, which makes the player go down a list of protocols - in the order you choose - until delivery succeeds.

1. The example below first tries to stream the video over good old RTMP (Flash streaming).
2. Failure to do so (e.g. because the Flash plugin is not installed or Flash is not supported) will result in an attempt to deliver the video to HTML5 players that support Apple HTTP Live Streaming (HLS). This will succeed on Apple devices, such as the iPhone or iPad, who do not support Flash.
3. As a last resort, the video is made available by means of progressive download to any HTML5 player. In order to make sure that all (HTML5 enabled) browsers can play the video, it is offered in three different formats (H.264, WebM and Ogg). This serves as a catch-all for pretty much all remaining platforms.

The W3C recently issued a Last Call announcement for HTML5, moving the standard one step closer to the finishing line (currently set in 2014). In the meantime, HTML5 has been gaining traction on the web with growing support by browsers and devices alike. According to a recent study by ABI Research, more than 2.1 billion mobile devices will have HTML5 browsers by 2016.

HTML5 video: H.264 and webm

An important aspect of HTML5 is the support for embedded multimedia, including video, audio, and dynamic graphics. Various HTML5 video players have emerged and the list of features is growing steadily. However, the lack of a common video codec for all browsers remains a huge problem, which is not likely to disappear in the near future. Apple (Safari) and Microsoft (IE) have committed to support the H.264 video codec, while Google (Chrome), Mozilla (Firefox) and Opera are bolstering the VP8 codec (as part of a WebM container) instead. The latter group is also supporting the Theora codec and Ogg container format, sometimes depending on the browser version. For more information concerning both formats and the surrounding issues, see this article from our State of Play series.

To avoid your HTML5 videos not playing in some browsers or on some devices, you can currently still use H.264 with a fallback to Flash. However, this solution has a number of drawbacks (e.g. lack of a unified architecture, Flash overhead on devices) and may not be future proof. Another option, which leaves your HTML5 code intact for all browsers and devices, is to encode your videos into Mp4 (H.264), WebM (VP8) and Ogg (Theora). Rambla Transcoding Service (RATS) supports these video formats and has an API that allows for a quick integration into your custom environment.

Auto-Publish BOTH FORMATS Easily

If you need a simple and transparent solution that requires no development effort, our hotfolder system may be what you're looking for. All you have to do is upload your video to your own private FTP directory (= the so-called 'hotfolder'). The hotfolder takes care of the rest:

• It encodes your video into Mp4, WebM and Ogg format (dimensions, bitrates... can be configured).
• It optimizes the encoded videos for online delivery.
• It publishes the .mp4, .webm and .ogg video's side-by-side on the Rambla CDN (you can determine the exact location by creating sub-directories inside your hotfolder).
• It provides you with a notification or report.

GETTING STARTED

Every Rambla user account has a default hotfolder which is suited for this purpose. To configure your default hotfolder for HTML5: log in to the RATS web-application and select the 'user' menu, then choose 'html5' as your default format-group. Your hotfolder is now ready to start encoding your videos into WebM and mp4 formats and publish them on the CDN. In order to use it, just upload your video files to 'ftp.enc01.rambla.be', logging in with your hotfolder credentials (= your user name followed by the "-enc" suffix and your user password).

For more information or help, see our hotfolder guide or contact us.