webm - Wrapper Chrome Firefox Opera - must have the recent browser revs. Real problem - Mozilla is non-profit - goes against their charter to pay royalties. mp4 - wrapper Safari IE (the go-to standard) (recently Google said they won't support this in the future) (so where in the tool chain, someone has to pay for the license. May 2010 - Google WebM Video Standard - immediate support for Chrome and Operaĭemo of videos in containers - 6 different ones March 2009 - Safari4 adds native support. Opera browser: Anne van Kesteren - HTML5 should work like an object with special video semantics.Īllows for playback of video on a webpage without special plugins, etc. Over past 5 years, steady growth in video and need for accessibility. Q: Any particular source on take-up of HTML5? Is there a good objective source?Ī: The Definitive Guide to HTML5 Video - Silvia Pfeiffer (Amazon) & - not totally unbiased, but at least labelled opinion, just get stuff done, what works. Question of which browsers supported? See Wikipedia page on HTML5 Video: Welcome from Forrest: bottom-up kind of group - discussion-based talking about issues that people have. Through our investigation, we found that HTML5 spec isn't full baked yet, but does have huge potential and adoption will only grow with time. Want to try a quick experiment yourself? Download the free Miro video converter: Įxport to "WebM" format and use the following html code to test playback in your favorite browser.Ī huge thanks to John Foliot for presenting on the topic of html5 video.įorrest: The reason why we started investigating the use of html5 video was our desire to support video playback on the iPad. Note the ability to playback the video at 1.5x or 2x speed, and display the captions as a clickable transcript.Ĭheck out the demo and toggle between flash and html5 video: If you're viewing a video on youtube, add the following parameter to the url to force it to playback in html5: &html5=True = Here are a couple of quick tips to get your feet wet with html5 video = I don't know of any media player that can perform progressive download playback on inappropriately encoded video.Meeting notes from VMG meeting held on March 7, 2011. If it doesn't have the option, then consider using a different app. Media editing/encoding apps often have an option called something like "optimise for the web" or "enable progressive download" for video files. If it's encoded at the beginning, it can start playing immediately. If the metadata is encoded into the end of the file, which used to be a common practice, then users have to wait. Media players require metadata about the video file, sometimes called the MOOV Atom, so that they know how to play it. The most frequent reason for videos not playing before they've finished downloading is in the way the video files themselves are encoded. I think what you're referring to is progressive download: which all the popular media players (mentioned here at least) and HTML5 compliant browsers are capable of doing. It is called "videoeasy" because, well you know, "videodifficult" was taken. But they will always have the nice Moodle forums, and at least they don't have to install or write yet another plugin. I guess the drawback is that the user needs to have some knowledge of javascript and friends, if they want to alter the default behaviour. So they can alter it as per the documentation for that particular HTML5 player, to do things like add poster images, change css styles, set to preload, even add event handlers. But the templates are also editable by the user. The user can select the HTML5 player they want and use it out of the box. I have written a proof of concept filter that makes a template for each HTML5 video player. We simple parse the media link on the page as we do now, and pass that off to a set of templates for each HTML5 player we support. And relying on 3rd party plugins for the rest.Īnyway I propose a different approach, we might call a thin layer. And having to write an interface to the configurations for each slick new html5 video player is unrealistic, leading to basically pushing one. The landscape is changing very fast, and people's requirements/preferences are quite different.Īnd my own experience with Flowplayer is that the myriad of configuration options it provides is fantastic, but having to write an interface to that in Moodle inevitably leads to dumbing it down and removing options. I humbly suggest that annointing one of the many html5 video players out there as Moodle's chosen, is not the correct approach. I noted also this tracker issue about Flowplayer and handling HTML5 video. I have seen a bit of complaint about Moodle's flowplayer implementations inability to handle MP4 and people struggling to find a solution that fits them.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |