demos

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.
Loading player ...

This is an example of how to use the HTML5 video tag in a cross-browser fashion. The HTML5 <video> tag makes it possible to embed video clips in web pages much like how the <img> tag works for images. The browser itself provides the playback functionality without any need for plugins like Quicktime or Flash.

Currently, much debate is going on about which video codec(s) should be supported. Apple and Microsoft support H.264 while Google, Mozilla and Opera support both WebM (which has VP8 as video codec) and Theora.

In order for the video to playback in any of the above mentioned browsers, it suffices to add two source attributes to the video element, one referencing an MPEG-4 encoded file and one pointing to a WebM or Ogg encoded file.

This still leaves us with legacy browsers that don't support HTML5 and/or the <video> tag. The trick here is to degrade to Flash using javascript. The tag <video> would simply be ignored by these browsers.

If you only want to serve H.264 video's, you can use Flash fallback for the Google, Mozilla and Opera browsers as well.

 

The code (using jQuery) looks like this:

<div id="player">
   <video id="demo-video" poster="background.jpg" width="512" height="288" controls>
    <source src="http://demo.cdn01.rambla.be/bwcheck/bbb-1000.mp4" type="video/mp4" /> 
    <source src="http://demo.cdn01.rambla.be/bwcheck/bbb-1000.ogg" type="video/ogg" /> 
   </video>
</div>
<script type="text/javascript" src="flowplayer-3.1.4.min.js"></script>
<script type="text/javascript">
    $(document).ready(function() { 
    var v = document.createElement("video"); 
    if ( !v.play ) { // If no, use Flash.
      $("#player").css("width", 512);
      $("#player").css("height", 288);
      $("#player").css("background", "url(background.jpg) no-repeat left top");
      $f("player", 
         "flowplayer-3.1.5.swf", 
         "http://demo.cdn01.rambla.be/bwcheck/bbb-1000.mp4"
        );
    }
  });
</script>;

For more info on the HTML5 video tag, read our blog post: The HTML5 "video" tag: codec confusion and how to circumvent it

The demo below intends to show how Flash video (encoded in the Sorenson Spark video format) performs when compared to H.264 encoded media files. You will find that the image quality of the video is noticeably worse at equal bitrates compared to video files that are encoded to H.264.

This example shows video delivered as download (as opposed to streaming). Download (or progressive download as it's usually referred to) has its pro's and con's.

One advantage lies in the fact that media is delivered over http, which is unlikely to run into firewall restrictions. When (Flash) streaming your media files (using the rtmp protocol), some (mostly corporate) firewalls may block the video. Downside with downloads are higher bandwidth consumption, and slower startup (as part of the video needs to be buffered before playback can begin).

The examples below show the same video file encoded at different bitrates. When watching the video, you can select from multiple resolutions. This allows you to decide on an ideal combination of bandwidth consumption, player resolution and image quality.

Be aware however that every video file is different in terms of bitrate-quality ratio. For example, animation video and cartoons tend to perform better at lower bitrates compared to camera footage. Videos that show a lot of movement or rapid camera transitions (concerts or sports events for example) require higher bitrates to maintain a decent image quality.

Get Adobe Flash player

This page requires Flash 10.

Syndicate content