- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Aug 2012 22:23:31 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18587
Aaron Colwell <acolwell@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|adrianba@microsoft.com |acolwell@chromium.org
--- Comment #1 from Aaron Colwell <acolwell@chromium.org> 2012-08-17 22:23:31 UTC ---
(In reply to comment #0)
> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#dom-duration
>
> 4. Remove all media data that is beyond the new duration from all SourceBuffer
> objects in sourceBuffers.
>
> It's not clear to which granularity this should be done. Should any segments
> which extend beyond the new duration be removed, or should enough data be
> "removed" so that playback stops exactly at the new duration. I say "removed"
> because this is actually a case of attaching metadata to the stream to stop
> playing at a certain point, since a perfect cut can only be achieved after
> decoding.
>
> Fulfilling this requirement well would make the implementation more
> complicated, so there would have to be strong use cases for it.
The initial intent was to simply remove anything that spans the duration or
goes beyond it. I think this could be a quality of implementation issue with
respect to whether a full frame is dropped and silence is inserted or whether a
frame that spans the new duration is simply truncated.
How about I add a step after step 4 along these lines
"5. If the new duration occurs in the middle of an audio frame, the UA may drop
this frame and insert enough silence to achieve the desired duration or it may
keep the frame and truncate it to the desired duration."
--
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 Friday, 17 August 2012 22:23:32 UTC