![]() 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |