#237: Support for HTML5 video tag
------------------------------+---------------------------------------------
Reporter: vik | Owner: baiju
Type: enhancement | Status: assigned
Priority: minor | Milestone: 4.1 Beta
Component: EmbeddedPlayback | Keywords:
Tester: And |
------------------------------+---------------------------------------------
Description changed by anna:
Old description:
> Modern browsers are now natively supporting the embedding of video using
> the <video> tag. A number of formats are now acceptable, depending on the
> browser and OS. E.g. Firefox 3.5 only supports ogg, Safari 4 supports
> h.264 (possibly others?), Chrome supports everything (ships with ffmpeg).
> IE8 doesn't support the video tag at all, future IEs are probably
> unlikely to. Which leaves a slightly messy situation, with two
> approaches:
>
> 1) In javascript, determine the browser's video and codec capabilities,
> and write HTML pointing to the appropriate source (ogv, mp4, or fallback
> to flv)
> 2) Use the html5 'source' attribute to specify multiple possibilities,
> and let the browser decide which one it can use.
>
> In both cases, at least two video formats will be needed on the server:
> ogv and (probably) mpeg4. Transcoding will need to handle make both of
> these.
>
> Also in both cases, a fallback will be required - the easiest for users
> is the previous default standard for web video - Flash (which we already
> support with Flowplayer).
New description:
Modern browsers are now natively supporting the embedding of video using
the <video> tag.
More info on this can be found here:
http://diveintohtml5.org/video.html
VIDEO CODEC SUPPORT IN UPCOMING BROWSERS
CODECS/CONTAINER IE FIREFOX SAFARI CHROME OPERA
IPHONE ANDROID
Theora+Vorbis+Ogg · 3.5+ † 5.0+
10.5+ · ·
H.264+AAC+MP4 9.0+ · 3.0+ 5.0+ ·
3.0+ 2.0+
WebM 9.0+* 4.0+ † 6.0+
10.6+ · ‡
* Internet Explorer 9 will only support WebM “when the user has installed
a VP8 codec,” which implies that Microsoft will not be shipping the codec
themselves. SO THE USER INSTALLS A CODEC AS PER USUAL ON THE OPERATING
SYSTEM - AS PER DIVX, XVID ETC.
† Safari will play anything that QuickTime can play, but QuickTime only
comes with H.264/AAC/MP4 support pre-installed. SO THE USER WOULD HAVE TO
INSTALL PERIAN, FOR EXAMPLE. SIMILAR USER-STORY TO INSTALLING XVID SUPPORT
ON MAC OPERATING SYSTEM.
‡ Google has committed to supporting WebM “in a future release” of
Android, but there’s no firm timeline yet.
At our end we have a couple of choices:
1) In javascript, determine the browser's video and codec capabilities,
and write HTML pointing to the appropriate source (ogv, mp4, or fallback
to flv)
2) Use the html5 'source' attribute to specify multiple possibilities, and
let the browser decide which one it can use.
In both cases, at least two video formats will be needed on the server:
ogv and (probably) mpeg4. Probably now we want to also provide a WebM/vp8
file. Transcoding will need to create these.
Also in both cases, a fallback will be required - the easiest for users is
the previous default standard for web video - Flash (which we already
support with Flowplayer).
--
--
Ticket URL: <http://plumi.net/ticket/237#comment:10>
Plumi <http://plumi.org/>
Plumi - FOSS Video Sharing Platform
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
