Hi Olaf, >From a scalability standpoint, a player-based solution has helped our team >efficiently process specific course media requests. The Flowplayer instance >and the embed codebase are both served from a central location. This method >allows us to make revisions to the code that in turn updates all course media >delivered using the service.
Our team uses an online form to add in variables (videoURL, posterURL, height, width, Captions, Auth/No Auth, Link type:MP4, FLV, MP3). The form generates a script (or iframe) code that can be used for embed into a online course environment. The embed code detects the viewing environment and loads the appropriate plugin/media type (Flash if desktop browser or HTML5 if mobile/tablet browser). Attached is a test instance of our "player as a service" solution (I guess that is what you might call it). Again it uses Flowplayer, Video for Everybody <http://camendesign.com/code/video_for_everybody>, and custom tweaks and authentication. The first video shows how the player instance operates when authentication is not used; the second shows the prompt that the player provides when authentication is needed -- students must enter in their university ID to load the player and view the video; the third is smiler to the first but with an iframe. The first and third videos should work on iOS and Android, too (...though we are working to make the Android support better). URL: http://ccnmtl.columbia.edu/draft/briano/t_index.html /Brian On Apr 5, 2011, at 7:02 PM, Schulte Olaf A. wrote: > Hello Brian > > Neat! Can you explain a bit more around these services, their scalability > especially? An example from your course media would be nice, too. > > Regards > > Olaf A. > >> -----Ursprüngliche Nachricht----- >> Von: [email protected] [mailto:community- >> [email protected]] Im Auftrag von Brian O'Hagan >> Gesendet: Dienstag, 5. April 2011 22:24 >> An: Opencast Community >> Betreff: Re: [Opencast] The Universal Player >> >> Hi George! Thanks for re-starting this topic! >> >> Funny, I recently sent this to some on staff here at Columbia re: HTML5 >> players... >> That these players are quickly becoming what is being coined as "Player as a >> Service" offerings - video services built around single player instance that >> can >> auto-magically load Flash/HTML5 supported media, as well as mobile support. >> It's >> an intriguing service model - we offer a similar model now for course media >> using >> Flowplayer, Video for Everybody code >> <http://camendesign.com/code/video_for_everybody>, and some custom auth >> patches. >> >> http://blog.jilion.com/2010/08/31/introducing-sublimevideo-player-as-a-service >> >> http://sublimevideo.net/ >> >> http://m.vid.ly/user/ >> >> /Brian >> >> On Apr 3, 2011, at 8:40 PM, George Bray wrote: >> >> >> Fans of new developments in online video might be interested to look >> at Media Core: http://mediacore.com/ >> >> It's a social portal centered around video, with the main feature that >> their player decides video format you should get depending on the >> device used. >> >> This got me thinking about where the world is at on universal players >> and the video format wars. Brian's updated roundup is helpful: >> <http://opencast.jira.com/wiki/display/OC/HTML5+Web+Resources> >> >> But it seems there's not been much progress toward easy universality. >> Neither H.264 nor WebM/VP8 can be used in all situations, so each >> piece of content needs to be in at least 2 formats. The player needs >> to decide the best way to deliver, based on platform, browser and >> manufacturer's video religion. >> >> The "try HTML5 but fall back to Flash" approach seems to be used by >> Longtail (formerly JW Player) too. >> <http://www.longtailvideo.com/players/> >> >> Any other developments in this area recently? >> >> George >> _______________________________________________ >> Community mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/community >> >> >> To unsubscribe please email >> [email protected] >> _______________________________________________ >> >> >> > > _______________________________________________ > Community mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/community > > > To unsubscribe please email > [email protected] > _______________________________________________ > _______________________________________________ Community mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/community To unsubscribe please email [email protected] _______________________________________________
