#237: Support for HTML5 video tag
------------------------------+---------------------------------------------
Reporter: vik | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 4.3 Beta (Re-Design of
EM.org & Plumi)
Component: EmbeddedPlayback | Resolution:
Keywords: | Who will test this: And
------------------------------+---------------------------------------------
Changes (by anna):
* milestone: 4.2 Beta (Features - Content Sharing Focus) => 4.3 Beta
(Re-Design of EM.org & Plumi)
Old 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
>
> *** FIREFOX ***
>
> Theora+Vorbis+Ogg
> v3.5+
>
> H.264+AAC+MP4
> ??
>
> WebM
> 4.0+
>
> *** SAFARI ***
>
> Theora+Vorbis+Ogg
> †
>
> H.264+AAC+MP4
> 3.0+
>
> WebM
> †
>
> *** CHROME ***
>
> Theora+Vorbis+Ogg
> 5.0+
>
> H.264+AAC+MP4
> 5.0+
>
> WebM
> 6.0+
>
> *** OPERA ***
>
> Theora+Vorbis+Ogg
> 10.5+
>
> H.264+AAC+MP4
> NO
>
> WebM
> 10.6+
>
> *** IPHONE ***
>
> Theora+Vorbis+Ogg
> NO
>
> H.264+AAC+MP4
> 3.0+
>
> WebM
> NO
>
> *** ANDROID ***
>
> Theora+Vorbis+Ogg
> NO
>
> H.264+AAC+MP4
> 2.0+
>
> WebM
> ‡
>
> * 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).
>
> Some options for HTML5/Flash Fallback players / javascript libraries:
>
> * http://henriksjokvist.net/archive/2009/2/using-the-html5-video-tag-
> with-a-flash-fallback
> * mwembed http://www.kaltura.org/project/HTML5_Video_Player
> * Kaltura HTML5 Player
> http://www.kaltura.org/project/HTML5_Video_Media_JavaScript_Library
> * OSM Player http://www.mediafront.org/project/osmplayer
> * Projekktor http://www.projekktor.com/
New description:
to replace flowplayer - with HTML5 video player by default
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
*** FIREFOX ***
Theora+Vorbis+Ogg
v3.5+
H.264+AAC+MP4
??
WebM
4.0+
*** SAFARI ***
Theora+Vorbis+Ogg
†
H.264+AAC+MP4
3.0+
WebM
†
*** CHROME ***
Theora+Vorbis+Ogg
5.0+
H.264+AAC+MP4
5.0+
WebM
6.0+
*** OPERA ***
Theora+Vorbis+Ogg
10.5+
H.264+AAC+MP4
NO
WebM
10.6+
*** IPHONE ***
Theora+Vorbis+Ogg
NO
H.264+AAC+MP4
3.0+
WebM
NO
*** ANDROID ***
Theora+Vorbis+Ogg
NO
H.264+AAC+MP4
2.0+
WebM
‡
* 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).
Some options for HTML5/Flash Fallback players / javascript libraries:
* http://henriksjokvist.net/archive/2009/2/using-the-html5-video-tag-
with-a-flash-fallback
* mwembed http://www.kaltura.org/project/HTML5_Video_Player
* Kaltura HTML5 Player
http://www.kaltura.org/project/HTML5_Video_Media_JavaScript_Library
* OSM Player http://www.mediafront.org/project/osmplayer
* Projekktor http://www.projekktor.com/
--
Comment:
Should this be done in the milestone prior to the re-design, or can it be
done as part of the re-design?
--
Ticket URL: <http://plumi.org/ticket/237#comment:19>
Plumi <http://plumi.org/>
Plumi - FOSS Video Sharing Platform
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
