[codec] R128 tags, per-file or per-stream?

Ron <ron@debian.org> Sun, 31 August 2014 16:22 UTC

Return-Path: <ron@debian.org>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CBA1A03F6 for <codec@ietfa.amsl.com>; Sun, 31 Aug 2014 09:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yITO4XzWjnP8 for <codec@ietfa.amsl.com>; Sun, 31 Aug 2014 09:21:58 -0700 (PDT)
Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id B35421A03D1 for <codec@ietf.org>; Sun, 31 Aug 2014 09:21:57 -0700 (PDT)
Received: from ppp121-45-54-132.lns20.adl2.internode.on.net (HELO mailservice.shelbyville.oz) ([121.45.54.132]) by ipmail06.adl6.internode.on.net with ESMTP; 01 Sep 2014 01:51:57 +0930
Received: from localhost (localhost [127.0.0.1]) by mailservice.shelbyville.oz (Postfix) with ESMTP id 2D3C1FFF35 for <codec@ietf.org>; Mon, 1 Sep 2014 01:51:56 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at mailservice.shelbyville.oz
Received: from mailservice.shelbyville.oz ([127.0.0.1]) by localhost (mailservice.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dtXQcb-RtBHo for <codec@ietf.org>; Mon, 1 Sep 2014 01:51:55 +0930 (CST)
Received: from hex.shelbyville.oz (hex.shelbyville.oz [192.168.1.6]) by mailservice.shelbyville.oz (Postfix) with ESMTPS id A7DFCFFD7E for <codec@ietf.org>; Mon, 1 Sep 2014 01:51:55 +0930 (CST)
Received: by hex.shelbyville.oz (Postfix, from userid 1000) id 92F5380470; Mon, 1 Sep 2014 01:51:55 +0930 (CST)
Date: Mon, 1 Sep 2014 01:51:55 +0930
From: Ron <ron@debian.org>
To: codec@ietf.org
Message-ID: <20140831162155.GI326@hex.shelbyville.oz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/codec/EJ90Huw_t61DssiYKRWIuem0y8M
Subject: [codec] R128 tags, per-file or per-stream?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec/>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Aug 2014 16:22:00 -0000

In Section 5.2.1 we currently say:

 "An Ogg Opus file MUST NOT have more than one of each tag"

I think that should instead say:

 "An Ogg Opus stream MUST NOT have more than one of each tag"


Since in Section 10 we say:

 "An "Ogg Opus file" consists of one or more sequentially
  multiplexed segments, each containing exactly one Ogg
  Opus stream."

And it doesn't make any sense to me that a file containing multiple
streams should not have these tags apply individually to each stream
(should they have them).


The above change would be consistent with our use of "Ogg Opus stream"
almost everywhere that talks about the mapping, and with "Ogg Opus file"
only where we talk about (possibly) combining streams, mime-types and
filename extensions.

Does anyone have any reason to think we need to say something different
to that here?  I'm assuming the current text was a 'typo', but I don't
know offhand if someone actually intended it to mean something other
than that.

  Ron