On Wed, Mar 11, 2015, at 04:50 PM, Randell Jesup wrote: > On 3/10/2015 5:50 AM, Robert O'Callahan wrote: > > On Tue, Mar 10, 2015 at 8:29 PM, Randell Jesup <[email protected] > > Looking again at my original message, use-case class #1 can be handled > > by labeling dead-time video/audio as such. Can someone go on record as > > saying classes #2 and #3 aren't worth worrying about? > > Paul? Are there alternatives for #2? I don't think there's any > alternative to #3. Being able to build NLE editors for video would be > cool (and feed into the Foxeye stuff I imagine). But not mandatory.
For audio and #2, you can use the AudioWorkerNode or other Web Audio API things. For video, I don't know, we would need some kind of Web Video API, which would be a better fit anyways. Nobody implements #3 (last I check, admittedly a while ago), and my understanding is that authors don't think it's at the right level of abstraction: you either want to do something much more complicated, and go with custom code (for audio, of course, again there is no Web Video API yet, although I've seen people do crazy stuff with canvas/glcontext), or something simple that works just fine (calling play and pause at the same time, looping over multiple HTMLMediaElement). Paul. _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
