[Cellar] Mapping of MOV clean aperture values to Matroska

Kieran O Leary <kieran.o.leary@gmail.com> Fri, 23 November 2018 09:56 UTC

Return-Path: <kieran.o.leary@gmail.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 DFE73130E0F for <cellar@ietfa.amsl.com>; Fri, 23 Nov 2018 01:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ClpQsTCaBk2Z for <cellar@ietfa.amsl.com>; Fri, 23 Nov 2018 01:56:50 -0800 (PST)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36FCF130DFC for <cellar@ietf.org>; Fri, 23 Nov 2018 01:56:50 -0800 (PST)
Received: by mail-wm1-x32d.google.com with SMTP id r11-v6so11272522wmb.2 for <cellar@ietf.org>; Fri, 23 Nov 2018 01:56:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=He5EUxHgjPRI5+TZZ531s5h7ilihnUY/3t0kncLyxl4=; b=TgO07OsTXJNFBV7mOWBQsz3/nWOh9V3K/0dQSHudwphPJZqdEQNc8qJGCTTNk0wCf6 CbofBqZn6fqymgP7BOTjCX0xlTk3HgALPqnhWB2lxglXDlGwfONSzQzpdQjh1ZsgNome y8R9PBFnIaNAD77DAWCoqjWU7xfMZkU8lPG/C+q/EttO3M8rxmdfNi9dnMDTatdYz886 oWIxyXVNNc8BEteX51ya9gTpkA2o67IltFafbbSzNklNQi+nY7y7t66w5yo9kmQPthl5 0U090GFNoSiK+TOEs+hwJNRMrBaAFuO2LP9LE3gtKMdfd70EJwKDzUtxASwuTqkync45 QqMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=He5EUxHgjPRI5+TZZ531s5h7ilihnUY/3t0kncLyxl4=; b=NSwS/sDJQ7La57uDQ6mGbK6hJwOc/L8G6aJtcLHBflkSDfrbbrjb6YtW8VXDcNLaAa cpDLEH0ss+5HwVaqPuWaUiDBeX6O5Kg3arDyEC/eXcpGaZjNoRHlCiEfvDrVtuDrfmEN 6T+h2t3lAznZYfzNEHJY4sPzLrf/Pb6+7QAb/WODFi0kdK0CniHmt6TKHm9w22dpJHhY KpfZIeMKBko1GS0jdCX1gHfGW8BSvw7FLDid4cHwXyuwDDhaj6JMw5y44S2h/yDctALv KNbRh7biDb5Ek40icrEV4FNF8dklO+YaZthxCQQ9ZSAbjMjW6DTcUMFrWcc3iPfVm4YA kQcw==
X-Gm-Message-State: AGRZ1gLgTMO78mJ6NNBfoRFinuzkgNv34poR15UEJa9umQ9nUwi5nhti MwBab+TZRNQ9w45AzYDsR5JoedQ+p2dKz2VrUmbyKqw=
X-Google-Smtp-Source: AJdET5fcPfQX8U/2TpZmKpG8bpLfNv03Dd/nUwNM6fmRFXB5E93GWVC7pcaPKaqZgAX+ya1JZx/TYMfTzJR9o8NG96w=
X-Received: by 2002:a7b:c5d1:: with SMTP id n17mr13024295wmk.152.1542967008165; Fri, 23 Nov 2018 01:56:48 -0800 (PST)
MIME-Version: 1.0
From: Kieran O Leary <kieran.o.leary@gmail.com>
Date: Fri, 23 Nov 2018 09:56:36 +0000
Message-ID: <CAO7v-1Qci+eGHBbQYuHYn-fSb+WA+ac-=Z89zkcdcYpQaKGQEw@mail.gmail.com>
To: cellar@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/QL7-L5ljb4MtlnvZEUsggYsKbjc>
Subject: [Cellar] Mapping of MOV clean aperture values to Matroska
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 23 Nov 2018 09:56:54 -0000

Hi,

Would I be correct in saying that ideally, Clean Aperture values in a
MOV/MPEG-4 file should map to the PixelCrop element in Matroska?

I'm asking about this in regards to this ffmpeg ticket -
https://trac.ffmpeg.org/ticket/7437
As it appears that FFmpeg does not currently read the values in the
clap atom and it also does not map them to Matorksa files when
remuxing. It seems to make the most sense to map them to PixelCrop,
but I'd like to hear it from folks more knowledgable than me.

Another associated issue with the display of these kinds of values is
with VLC as it appears that

1) PixelCrop values in Matroska are not supported by VLC at the moment
- https://trac.videolan.org/vlc/ticket/21192
2) Clean aperture values are not supported by VLC at the moment
https://trac.videolan.org/vlc/ticket/21179

Best,

Kieran O'Leary
Irish Film Institute