- From: <bugzilla@jessica.w3.org>
- Date: Tue, 23 Apr 2013 20:46:54 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20901 --- Comment #3 from Michael Thornburgh <mthornbu@adobe.com> --- both of the current "AbortMode"s are useful, and required for appending discontinuous media broken into separate files, for example separated video and audio. one would use "continuation" with one sequence (say, video) to establish what the new timestamps are, and use "timestampOffset" with the other sequence(s) (say, audio) after discovering what the timestampOffset is from the first sequence, to keep all sequences synchronized by their timestamps. without this capability and just the equivalent of "continuation", the separate sequences could go out of sync if they don't start all at exactly the same timestamp (which might easily be the case for separated video and audio tracks). how about keeping the current AbortMode optional parameter for abort(), but allow out-of-order appends without calling abort for all media containers which can reasonably accommodate this, and for situations where you want the discontinuity behavior for formats like ISO BMFF? it might only be necessary for MPEG-2 TS. the behavior for abort() when called with no parameters should have been the same as before the AbortMode parameter was added. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 23 April 2013 20:46:55 UTC