- From: Steven Robertson <strobe@google.com>
- Date: Tue, 24 Jul 2012 12:24:42 -0700
- To: Aaron Colwell <acolwell@google.com>
- Cc: Mark Watson <watsonm@netflix.com>, "public-html-media@w3.org" <public-html-media@w3.org>
On Tue, Jul 24, 2012 at 11:08 AM, Aaron Colwell <acolwell@google.com> wrote: > Ping. I haven't seen any responses to my last email on this thread so I'm > not sure how to proceed. > > I'm retracting my support for the push/popTimestampOffset() proposal until > someone can address concerns I mentioned. > > For now I'm proposing we just do the simplest thing that would work: > 1. Add an "attribute double timestampOffset" to SourceBuffer. > 2. The value of this attribute is added to media timestamps before the > frames are inserted into the source buffer. 0 is the default value for this > attribute since that results in unmodified timestamps. > 3. If the app tries to set this attribute while in the middle of appending a > media segment, an INVALID_STATE_ERR exception is thrown and the attribute is > not updated. If the app doesn't know whether it is in the middle of a media > segment, it can always call abort() to reset the parser state. > > Please let me know if you are ok with this simple attribute proposal or > whether you have arguments for the push/pop mechanism that I should > reconsider. Sounds good to me. Steve
Received on Tuesday, 24 July 2012 19:25:49 UTC