From b30b2ba21e511f61b718cdd321a21360ffe9dad8 Mon Sep 17 00:00:00 2001 From: Ralph Giles <giles@mozilla.com> Date: Fri, 17 Jan 2014 15:22:57 -0800 Subject: [PATCH] Try to clarify frame packing. Marko was concerned that RFC 6716 section 3.2.1 narrowly describes zero-length DTX frames _only_ for code 2 and 3 packets, and therefore wanted this sentence to state clearly that code 0 and 1 can be used with zero-byte frames as well. I've tried to do that. --- doc/draft-ietf-codec-oggopus.xml | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/doc/draft-ietf-codec-oggopus.xml b/doc/draft-ietf-codec-oggopus.xml index 898cbecbf..42fb6ece6 100644 --- a/doc/draft-ietf-codec-oggopus.xml +++ b/doc/draft-ietf-codec-oggopus.xml @@ -264,6 +264,16 @@ The actual length of each missing Opus frame inside the packet is zero bytes, as defined in Section 3.2.1 of <xref target="RFC6716"/>. </t> +<t> +Zero-byte frames MAY be packed into packets using any of codes 0, 1, + 2, or 3. +When successive frames have the same configuration, the higher code packings + reduce overhead. +Likewise, if the TOC configuration matches, the muxer MAY further combine the + empty frames with previous or subsequent non-zero-length frames (using + code 2 or VBR code 3). +</t> + <t> <xref target="RFC6716"/> does not impose any requirements on the PLC, but this section outlines choices that are expected to have a positive influence on @@ -325,13 +335,6 @@ Since medium-band audio is only supported in the SILK modes, wideband frames will be able to preserve all of the available audio bandwidth. </t> -<t> -Matching synthetic TOC byte(s) MAY be packed into packets using any of - codes 0, 1, 2, or 3. -If the TOC configuration matches, the muxer MAY further combine the empty - frames with previous or subsequent non-zero-length frames (using code 2 - or VBR code 3). -</t> </section> <section anchor="preskip" title="Pre-skip"> -- GitLab