- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Aug 2012 15:19:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18571
Aaron Colwell <acolwell@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acolwell@chromium.org
--- Comment #1 from Aaron Colwell <acolwell@chromium.org> 2012-08-15 15:19:22 UTC ---
(In reply to comment #0)
> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#source-buffer-media-segment-constraints
>
> "Gaps between media segments that are smaller than the audio frame size are
> allowed and should be rendered as silence. Such gaps should not be reflected by
> buffered.
> Note: This is intended to simplify switching between audio streams where the
> frame boundaries don't always line up across encodings (e.g. Vorbis)."
>
> To quote http://xiph.org/vorbis/doc/vorbisfile/crosslap.html
>
> "Vorbis introduces no extra samples at the beginning or end of a stream, nor
> does it remove any samples."
>
> Given this, it's not clear why gaps are allowed.
Vorbis encodes at different bitrates do not guarentee that the exact same frame
durations will be picked at each instant in the timeline. Higher bitrate
encodes may opt to use a short window where the lower bitrate picked a long
one. This means that the frame boundries in the two encodes won't always line
up if you splice them at an arbitrary point. This is why support for gaps is
needed.
--
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 Wednesday, 15 August 2012 15:19:26 UTC