Re: [Cellar] FFV1 Version 4

Dave Rice <dave@dericed.com> Tue, 05 January 2016 16:08 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 E7EA11A8843 for <cellar@ietfa.amsl.com>; Tue, 5 Jan 2016 08:08:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.58
X-Spam-Level: *
X-Spam-Status: No, score=1.58 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, 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 oh1Tr1T9-Kd9 for <cellar@ietfa.amsl.com>; Tue, 5 Jan 2016 08:08:21 -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 3E2AB1A8845 for <cellar@ietf.org>; Tue, 5 Jan 2016 08:08:21 -0800 (PST)
Received: from [146.96.19.240] (port=33091 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 1aGU9i-000AoT-12; Tue, 05 Jan 2016 11:08:20 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_CEB941E9-3171-4C82-B17D-A55E2A79D441"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Dave Rice <dave@dericed.com>
In-Reply-To: <CAO7v-1TCNOcqhv=JR5dMWhibD=kLyQwLztk8RG3v-rtegn7s7Q@mail.gmail.com>
Date: Tue, 05 Jan 2016 11:08:16 -0500
Message-Id: <E89E5459-836A-4FD7-BA52-6F75AFD67083@dericed.com>
References: <CAO7v-1TCNOcqhv=JR5dMWhibD=kLyQwLztk8RG3v-rtegn7s7Q@mail.gmail.com>
To: Kieran O Leary <kieran.o.leary@gmail.com>
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/r59Xjmz65MzyS1bu9nYIV7yz1i8>
Cc: cellar@ietf.org
Subject: Re: [Cellar] FFV1 Version 4
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: Tue, 05 Jan 2016 16:08:23 -0000

> On Jan 5, 2016, at 9:22 AM, Kieran O Leary <kieran.o.leary@gmail.com> wrote:
> 
> Hello,
> 
> I saw on your charter that a milestone for September 2016 is "Submit specification for FFV1 video codec version 4 to IESG (Standards Track)". https://datatracker.ietf.org/wg/cellar/charter/ <https://datatracker.ietf.org/wg/cellar/charter/>
> 
> Is there any information or roadmap available about proposed changes from version 3 to version 4? I'm asking as the added features of Version 3 were significant for moving image archives, and I'm curious to know what version 4 may look like.

This is the place to provide proposals. There has been a little discussion on FFmpeg-devel but none yet on CELLAR. IMO I'd like to consider the following for FFV1:

Increased Self-Description of Intended Decoding
- documentation of color matrix (i.e. bt.601, bt.709, etc)
- documentation of sample range (i.e. full range vs broadcast range)

Increased Self-Description of the Encoding
- storage of encoding parameters (I see this features in h264, are these called SEI messages?)

Extending Pixel Format Support
- support for Bayer pixel formats

Some Header Adjustments
- currently some values such as bit depth, display aspect ratio, and chroma subsampling are set per slice rather than per frame. Perhaps there is a reason I am not considering, but possibly some adjustment could improve the logic of the frame and slice headers.

Looking forward to discussion on this topic.

Best Regards,
Dave Rice