From a38044e0978af97eae2607f0e774b06066f0b83b Mon Sep 17 00:00:00 2001 From: Ralph Giles <giles@mozilla.com> Date: Fri, 17 Oct 2014 15:08:11 -0700 Subject: [PATCH] oggopus: Refer to 'TOC sequence' instead of byte. This avoids confusion with the number of frames being defined by more than the first byte with code 3 packets. Patch from mark4o. --- doc/draft-ietf-codec-oggopus.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/draft-ietf-codec-oggopus.xml b/doc/draft-ietf-codec-oggopus.xml index 04ed7995e..d319bfb87 100644 --- a/doc/draft-ietf-codec-oggopus.xml +++ b/doc/draft-ietf-codec-oggopus.xml @@ -187,8 +187,8 @@ A decoder SHOULD treat any Opus packet whose duration is different from that of <t> The coding mode (SILK, Hybrid, or CELT), audio bandwidth, channel count, duration (frame size), and number of frames per packet, are indicated in the - TOC (table of contents) in the first byte of each Opus packet, as described - in Section 3.1 of <xref target="RFC6716"/>. + TOC (table of contents) sequence at the beginning of each Opus packet, as + described in Section 3.1 of <xref target="RFC6716"/>. The combination of mode, audio bandwidth, and frame size is referred to as the configuration of an Opus packet. </t> -- GitLab