[Cellar] define FFV1 in Matroska

Dave Rice <dave@dericed.com> Sat, 04 February 2017 15:59 UTC

Return-Path: <dave@dericed.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27F3A129B27 for <cellar@ietfa.amsl.com>; Sat, 4 Feb 2017 07:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.652
X-Spam-Level:
X-Spam-Status: No, score=0.652 tagged_above=-999 required=5 tests=[SPF_NEUTRAL=0.652] autolearn=no autolearn_force=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 85ydUXjgHJnM for <cellar@ietfa.amsl.com>; Sat, 4 Feb 2017 07:59:38 -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 E93E6129B9F for <cellar@ietf.org>; Sat, 4 Feb 2017 07:59:37 -0800 (PST)
Received: from cpe-104-162-86-103.nyc.res.rr.com ([104.162.86.103]:48293 helo=[10.0.1.12]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from <dave@dericed.com>) id 1ca2kS-0035hr-DA for cellar@ietf.org; Sat, 04 Feb 2017 10:59:37 -0500
From: Dave Rice <dave@dericed.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Message-Id: <C2797F49-CF5B-44F2-A017-E721319C6FB4@dericed.com>
Date: Sat, 04 Feb 2017 11:00:52 -0500
To: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
X-Mailer: Apple Mail (2.3226)
X-OutGoing-Spam-Status: No, score=-2.9
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: <https://mailarchive.ietf.org/arch/msg/cellar/Kir-8JdOl6DTZFPrxy4XM-iRP7Q>
Subject: [Cellar] define FFV1 in Matroska
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 04 Feb 2017 15:59:39 -0000

Hi cellar,

I submitted this pull request to define an FFV1 Codec Mapping for Matroska, https://github.com/Matroska-Org/matroska-specification/pull/94. Currently all FFV1 in Matroska uses the V_MS/VFW/FOURCC Mapping. In addition to what is listed below I think the V_MS/VFW/FOURCC definition may need to be extended to say that when V_MS/VFW/FOURCC is used for FFV1, and the FFV1 is version 3 or greater, then the BITMAPINFOHEADER MUST have the Configuration Record as Private Data.

Comments? Is it advantageous to define this when V_MS/VFW/FOURCC is already the practice?

Here is the text of the proposed Codec Mapping:

### V_FFV1

Codec ID: V_FFV1

Codec Name: FF Video Codec 1

Description: FFV1 is a lossless intra-frame video encoding format designed to efficiently compress video data in a variety of pixel formats. Compared to uncompressed video, FFV1 offers storage compression, frame fixity, and self-description, which makes FFV1 useful as a preservation or intermediate video format. [Draft FFV1 Specification](https://datatracker.ietf.org/doc/draft-niedermayer-cellar-ffv1/)

Initialisation: For FFV1 versions 2 or less, `Private Data` SHOULD NOT be written. For FFV1 version 3 and greater, the `Private Data` MUST contain the FFV1 Configuration Record structure, as defined in https://tools.ietf.org/html/draft-niedermayer-cellar-ffv1-01#section-4.1, and no other data.

Dave Rice