- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Aug 2012 15:26:01 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18642
Steven Robertson <strobe@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |strobe@google.com
--- Comment #1 from Steven Robertson <strobe@google.com> 2012-08-21 15:26:01 UTC ---
> In addition, the byte stream specs could place the necessary requirements
> to make this situation as unlikely as possible.
It is not possible in the general case to incrementally produce a
specification-compliant byte stream which represents the result of compositing
media data from multiple independent streams into a source buffer. (For
instance, a single ISO BMFF stream cannot contain multiple 'moov' atoms, and
therefore cannot be updated with new codec descriptions or timescales on the
fly.)
As a result, implementations cannot produce a decodeable media stream by simply
tweaking incoming media segments in place. Therefore, no implementation should
be limited in its representation of timecodes by the format of the incoming
byte stream.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 21 August 2012 15:26:02 UTC