Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The recommended way to go is to encode your video 3 times:</p> <p>h264, vorbis and webm ... then put them as sources into the html5 tag in this order (because some devices only look at the 1ŝt one) and if all fails fall back to flash.</p> <p>I don't like that solution because i have 3 video files to encode and to store.</p> <p>So i approached it the other way round to use flash if possible and switch to html5 as a Fallback. I prefer that solution as well as flash playback seems to be more reliable. Well it consumes more computing power so for HD videos you could debate but well.</p> <p>So i ended up with the following table how stuff should be used:</p> <p>IE: Flash (v9 will ship with html5/h264 support as well but flash is cool) Firefox: Flash (only theora/vorbis supported for now) Safari: Flash if possible, else HTML5 / h264 supported in versions 3.0+ Chrome: Flash, if flash not aviailable (unlikely) h264/html support in versions 5.0+ Opera: Flash (no support for h264 yet. Opera mobile... will not work. Html5 only with open formats.) Iphone: HTML5 / h264 (3.0+) Android: HTML5 / h264 (2.0+) </p> <p>The only thing to watch out is that Android doesn't use flash because the mobile phone will not have the performance for smooth playback, but it supports it in versions 2.2 ... Still working on that.</p> <p>So what do we need now?</p> <p>Reliable Flash detection and JS. If no JS is available we can display. the html5 tag or the flash player .. i think flash player is better.</p> <p>The only cases where Theora / Webm would be important are Firefox and Opera. But they should support flash which supports h264 scince version 9.something.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload