[Bug 19784] timestampOffset with multiplexed Media Segments

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

Aaron Colwell <acolwell@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Aaron Colwell <acolwell@chromium.org> ---
Changes committed.
https://dvcs.w3.org/hg/html-media/rev/d5956e93b991

Splices are resolved on a per track basis. I did not change this for muxed
content because I wanted the splicing behavior to be consistent between muxed
and demuxed content. Given the additional text added in this change, I believe
content providers can create content in such a way that they can get the output
they want without requiring special splicing behavior for muxed content.

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

Received on Tuesday, 19 February 2013 00:57:10 UTC