ref: 19658bd2f71db54c8b50dc95b295add3cc962bd4
parent: 1a7c4ceb8518ab8e01e23675deb8d6c814745063
author: Ralph Giles <giles@mozilla.com>
date: Mon Jul 16 08:34:04 EDT 2012
Clarify how multistream Opus packets are packed into Ogg packets.
--- a/doc/draft-terriberry-oggopus.xml
+++ b/doc/draft-terriberry-oggopus.xml
@@ -154,7 +154,7 @@
which it completes.
</t>
<t>
-All subsequent pages are audio data pages, and the packets they contain are
+All subsequent pages are audio data pages, and the Ogg packets they contain are
audio data packets.
Each audio data packet contains one Opus packet for each of N different
streams, where N is typically one for mono or stereo, but may be greater than
@@ -164,10 +164,12 @@
logical Ogg bitstream.
</t>
<t>
-The first N-1 Opus packets, if any, are packed using the self-delimiting
- framing from Appendix B of <xref target="RFCOpus"/>.
-The remaining Opus packet is packed using the regular, undelimited framing from
- Section 3 of <xref target="RFCOpus"/>.
+The first N-1 Opus packets, if any, are packed one after another in sequence
+ into the Ogg packet, using the self-delimiting framing from Appendix B
+ of <xref target="RFCOpus"/>.
+The remaining Opus packet is packed at the end of the audio data packet
+ using the regular, undelimited framing from Section 3 of
+ <xref target="RFCOpus"/>.
All of the Opus packets in a single Ogg packet MUST be constrained to have the
same duration.
A decoder SHOULD treat any Opus packet whose duration is different from that of