Re: [Cellar] Colour Format proposal

Dave Rice <dave@dericed.com> Thu, 07 January 2016 18:14 UTC

Return-Path: <dave@dericed.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1111A916A for <cellar@ietfa.amsl.com>; Thu, 7 Jan 2016 10:14:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
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 Zrz9HCNcwsix for <cellar@ietfa.amsl.com>; Thu, 7 Jan 2016 10:14:04 -0800 (PST)
Received: from s172.web-hosting.com (s172.web-hosting.com [68.65.122.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D965B1A916D for <cellar@ietf.org>; Thu, 7 Jan 2016 10:14:04 -0800 (PST)
Received: from [146.96.19.240] (port=26795 helo=[10.10.202.53]) by server172.web-hosting.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from <dave@dericed.com>) id 1aHF4U-003YeE-Vd; Thu, 07 Jan 2016 13:14:04 -0500
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Dave Rice <dave@dericed.com>
In-Reply-To: <568EAA16.4000505@mediaarea.net>
Date: Thu, 07 Jan 2016 13:14:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E158FB09-D686-4A74-88B7-D46698DF746C@dericed.com>
References: <CAJGH+UuSn8O04HR1=L+b1=ouwgPd=n+xYFQZmTXqs8buZ-Wdrg@mail.gmail.com> <568C3CA0.8040300@mediaarea.net> <568EA9BD.3030606@das-werkstatt.com> <568EAA16.4000505@mediaarea.net>
To: Jerome Martinez <jerome@mediaarea.net>
X-Mailer: Apple Mail (2.1990.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <http://mailarchive.ietf.org/arch/msg/cellar/kgYuGQdiBtbvEOwZYjmGaAj9yQ0>
Cc: cellar@ietf.org
Subject: Re: [Cellar] Colour Format proposal
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2016 18:14:06 -0000

> On Jan 7, 2016, at 1:10 PM, Jerome Martinez <jerome@mediaarea.net> wrote:
> 
> Le 07/01/2016 19:09, Peter B. a écrit :
>> On 01/05/2016 10:58 PM, Jerome Martinez wrote:
>>>> Element Name: ColourRange
>>>> Level:        5
>>>> ID:           [55][A4]
>>>> Mandatory:    ma
>>>> Multiple:     -
>>>> Default:      1
>>>> Type:         u
>>>> Description:  (0: Unspecified, 1: Defined by
>>>> ColourMatrix/TransferFunction,
>>>>               2: Full range)
>>> I don't understand the 1 value.
>>> in at least AVC and HEVC, range is orthogonal to
>>> ColourMatrix/TransferFunction.
>>> I propose 0: unspecified 1: Broadcast range 1: Full range
>>> and Default:0
>> Just for the sake of completeness, I think you have a small typo:
>> You proposed:
>> 
>> // ------------------
>> 0: default
>> 1: broadcast range
>> 1: full range
>> // ------------------
>> 
>> 
>> I guess you meant "2" for "full range", as it was before?
> 
> Oops :).
> 
> // ------------------
> 0: unspecified
> 1: broadcast range
> 2: full range
> // ------------------
> 
> and default is 0.

Perhaps a statement is needed on when the value is applicable. For instance is 'broadcast range' with a JPEG2000-RCT encoding valid?

I suggest adding a citation to explain how 'broadcast range' and 'full range' are defined.
Dave