Skip to content
Snippets Groups Projects
Commit 19658bd2 authored by Ralph Giles's avatar Ralph Giles
Browse files

Clarify how multistream Opus packets are packed into Ogg packets.

parent 1a7c4ceb
No related branches found
No related tags found
No related merge requests found
......@@ -154,7 +154,7 @@ However many pages it spans, the comment header packet MUST finish the page on
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 @@ The value N is specified in the ID header (see
logical Ogg bitstream.
</t>
<t>
The first N-1 Opus packets, if any, are packed using the self-delimiting
framing from Appendix&nbsp;B of <xref target="RFCOpus"/>.
The remaining Opus packet is packed using the regular, undelimited framing from
Section&nbsp;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&nbsp;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&nbsp;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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment