This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18573 - Mention crosslapping for QoI
Summary: Mention crosslapping for QoI
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Aaron Colwell (c)
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-15 09:59 UTC by Philip Jägenstedt
Modified: 2012-08-27 08:51 UTC (History)
3 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2012-08-15 09:59:47 UTC
http://xiph.org/vorbis/doc/vorbisfile/crosslap.html

This is a quality of implementation issue, but crosslapping (not crossfading) can be used both when switching between streams that align perfectly and ones that have come overlap. A non-normative link to the vorbisfile documentation could be useful to implementors.
Comment 1 Aaron Colwell (c) 2012-08-15 16:45:17 UTC
(In reply to comment #0)
> http://xiph.org/vorbis/doc/vorbisfile/crosslap.html
> 
> This is a quality of implementation issue, but crosslapping (not crossfading)
> can be used both when switching between streams that align perfectly and ones
> that have come overlap. A non-normative link to the vorbisfile documentation
> could be useful to implementors.

Mind if I change the text to "crossfade or crosslap" since crosslapping might not be an option for non-Vorbis codecs like AAC, HE-AAC, or MP3?
Comment 2 Philip Jägenstedt 2012-08-16 08:17:53 UTC
Crosslapping is actually performed on raw PCM buffers, it isn't a codec-specific technique.

But yes, mentioning both is fine. Note that "crosslapping" has slightly better searchability than "crosslap", so if it can be phrased as such it'd be great.
Comment 3 Aaron Colwell (c) 2012-08-24 22:47:24 UTC
Changes committed.
http://dvcs.w3.org/hg/html-media/rev/ca093bbbbefb