[Bug 18642] Handle timestamp overflow in append(data)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18642

Adrian Bateman [MSFT] <adrianba@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|adrianba@microsoft.com      |acolwell@chromium.org

--- Comment #10 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
Issues identified here:
1. The text needs to be reworked so people don't think that the bytestream is
being rewritten in place.
2. Timestamp rollover behavior needs to be clarified. I believe the concensus
was that rollover within a media segment must be handled, but it is up to the
application to handle it across media segments via timestampOffset.
3. Conversion from bytestream timestamp to presentation timestamp double needs
clarification.

Next Action: Reorganize append() algorithm into several sub-algorithms so that
there are logical places to put the clarifications mentioned above. Several
open issues require this.

Assigned to Aaron.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.