Hey Mark, (I'm biased in that I think we in opencast should have all of these requirements as well as all of fluids and we should just offer a stellar open source video playback control that all projects can use. A one codebase supertool.)
> And while I'm giving out links, the preliminary list of requirements > for our video player is here: > > https://wiki.dlib.indiana.edu/display/VarVideo/Video+players > > Which should begin to answer Rüdiger's question. >From your list: "Closed captions (us43)" Supporting a standard closed captioning format is important for interoperability and tie in with other services. I think the Osnabruck team has comments on this. "Adjustable playback speed (US 56 - is this possible with streaming?)" It's available in silverlight streaming, fwiw (WMV). "Adaptive streaming - the player can change video quality (when switching to fullscreen or connection slows down)" I didn't see fullscreen capabilities in your requirements. Also, one killer feature of the MH player right now is that it allows you to have multiple videos shown at once *in sync*. Huge feature that I haven't seen in any other video player, especially useful in a world of widescreen monitors where you might want to show multiple tracks or angles. Don't know how useful it would be for variations. I also don't see anything here about accessibility controls, which was an issue for us in MH. Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
