Re: [Cellar] AV1 mapping Matroska

Steve Lhomme <> Wed, 27 June 2018 09:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D909F130F49 for <>; Wed, 27 Jun 2018 02:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id j96lylOWd-3h for <>; Wed, 27 Jun 2018 02:30:42 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F1E7F130F40 for <>; Wed, 27 Jun 2018 02:30:41 -0700 (PDT)
Received: by with SMTP id m16-v6so766068pls.11 for <>; Wed, 27 Jun 2018 02:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=VAbC9DnO2qFxmo7a/O1cUOa6HIl3tMGa4qvorquZXKQ=; b=Rk8WzeP2V/cYGVAcEwgmC13amRvom8GDXBZEHoFWLgQGzteaMpMHejv1h+fpm/U+h5 eEGHURncJ1n7wVBb2poCgRgrvMypOzgP4xQ4oZtCz1/NgO5MZOLzrWm7mUGf3S3vRWk9 880zmUd4397cA2UoXlXHFhMOROYvvCMWDniQR6ui2slkZk3SVe1bPlOCFY3YUosObygk 3Ema7bNKTmPEnBoWcH4QtOxXCuk5h7bVp4mpOGvTm7pjjEfY3/tYanOKvu7ZEc8UJd7M Nld8IBdm0BfxE320yWVHLPX8Wg1pYu8SU4HthLMslBW9Mtro1JDaw5J0CybLKmDP3rQM ozHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=VAbC9DnO2qFxmo7a/O1cUOa6HIl3tMGa4qvorquZXKQ=; b=a4Qc+Y9qjHiNyA4Zb3gDdpiH4DlXYRhhuZFhYDM2It01+lQCjFz5urYn4uVPhFpIKn XRdH4mrzIw4FZapYv1itebcQ/xPhrf9oVJIjkAkFrFhUBZQW481wuZvNC4/ZzmTr9x3Q vCgC4UO/SJoYeTe3k6o4poZEYKeR8pERh/kNUoTWbdtYhwnj5fJQMkQA7K72MZ90tb/t uWHUaWu69ubY+R40yg3aTjUcSEhjWhFjgIw0zuT3/3PAnd4nddsxofdOoZW+vFVHnPkw Jea7M1kEyzoXRaQ1NCc3BaziZa2D3t/gxFL1TfV4UrYnmJXx88nNSq7Iv/w3ymn+CPmD 75sQ==
X-Gm-Message-State: APt69E3iAYpexlIr2BJUtsphRQ7O7dsvjFvcjYB6dlq+Xk5rVd+1MytE UwshNIfXRUCcu8ad80eULUKhG1Z/zgn6VAb90AEb2A==
X-Google-Smtp-Source: ADUXVKJdRNZBhCaG/WSbMnkM58yJD80184M607yf4TVbSah5dbY5yDPsbZAkrj/SSlk7PZ55ECoLmMyGcXSLwvg+p6M=
X-Received: by 2002:a17:902:bd95:: with SMTP id q21-v6mr5255506pls.237.1530091841376; Wed, 27 Jun 2018 02:30:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:17af:0:0:0:0 with HTTP; Wed, 27 Jun 2018 02:30:40 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <>
From: Steve Lhomme <>
Date: Wed, 27 Jun 2018 11:30:40 +0200
Message-ID: <>
To: Codec Encoding for LossLess Archiving and Realtime transmission <>
Cc: Frank Galligan <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Cellar] AV1 mapping Matroska
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Jun 2018 09:30:44 -0000

2018-06-27 10:58 GMT+02:00 Moritz Bunkus <>rg>:
> Hey,
> I've only had time to skim over it. It's definitely understandable.
> For me the most important thing is to have the mapping in Matroska and WebM
> be identical. As the reference encoder already produces WebM files, I
> highly suggest we communicate with their developers regarding the
> mapping. I cannot find a document for AV1/WebM bindings at the moment,
> though…

Ah I didn't know that. Now I can see the code. Especially webmenc.c
with a TODO for Frank Galligan in there.

It way for some Wip In Progress code, because I have been appointed by
the powers that be at AOM to do the proper/official mapping.

At least this code doesn't write any CodecPrivate which could work,
except, as for VP9 we wouldn't know the decoding profile just from
reading the TrackEntry which is a major problem to select the proper
hardware decoder. And the MP4 mapping also integrates a kind of
CodecProvate with the Sequence Header OBU in there.

>> I will dig deeper but we may have to tweak CodecDelay to make it signed.
> You cannot change the type of an existing element. It would potentially
> break the interpretation of existing files created with the old
> semantics. Let's take the value 144, which as an unsigned EBML integer
> would be stored as 0x81 0x90. If you read that back as a signed EBML
> integer, you'd get the value -128.

Given a codec delay sounds like some time the codec needs when fed
data before it outputs data. So I have hope it matches and I did the
math wrong.

In any case I don't know if we should include the flags like MP4 does.
Because it seems very MP4 specific (and it's a draft and may go away).
Unlike the rest of their "Codec Private" it should not be fed to the
decoder (the OBUs we have can be fed as-is to the decoder).

> Kind regards,
> mosu
> _______________________________________________
> Cellar mailing list

Steve Lhomme
Matroska association Chairman