Re: [Cellar] matroska and side data vs timecode

Jerome Martinez <jerome@mediaarea.net> Sun, 03 November 2019 11:07 UTC

Return-Path: <jerome@mediaarea.net>
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 DBA8112004C for <cellar@ietfa.amsl.com>; Sun, 3 Nov 2019 03:07:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 Y52JrojdPxRh for <cellar@ietfa.amsl.com>; Sun, 3 Nov 2019 03:07:20 -0800 (PST)
Received: from 20.mo3.mail-out.ovh.net (20.mo3.mail-out.ovh.net [178.33.47.94]) (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 90988120019 for <cellar@ietf.org>; Sun, 3 Nov 2019 03:07:20 -0800 (PST)
Received: from player688.ha.ovh.net (unknown [10.109.160.143]) by mo3.mail-out.ovh.net (Postfix) with ESMTP id 2B4D322C930 for <cellar@ietf.org>; Sun, 3 Nov 2019 12:07:17 +0100 (CET)
Received: from mediaarea.net (p548F9A0D.dip0.t-ipconnect.de [84.143.154.13]) (Authenticated sender: jerome@mediaarea.net) by player688.ha.ovh.net (Postfix) with ESMTPSA id 521C1B984155 for <cellar@ietf.org>; Sun, 3 Nov 2019 11:07:17 +0000 (UTC)
To: cellar@ietf.org
References: <00F6A0BF-2922-4BAC-AC73-EB888767886F@dericed.com> <40b8c32e-9136-af70-e844-b9e9f2e1c75a@gmail.com> <CAO7v-1SkBrN33Y7NgY5GuSnYewfEhkW7f0o4LSkDP4raVA77Kg@mail.gmail.com> <6cd23d59-f9d7-0ab8-3a0d-729f9f106de7@noa-archive.com>
From: Jerome Martinez <jerome@mediaarea.net>
Message-ID: <2e267cc1-f764-ced1-3d17-6e46819a8f72@mediaarea.net>
Date: Sun, 03 Nov 2019 12:07:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <6cd23d59-f9d7-0ab8-3a0d-729f9f106de7@noa-archive.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Ovh-Tracer-Id: 13034824698179555473
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrudduuddgvdeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenuc
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/PQ58UXq5G4bb70fQNTRfj-CuU2w>
Subject: Re: [Cellar] matroska and side data vs timecode
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: Sun, 03 Nov 2019 11:07:22 -0000

On 30/10/2019 17:28, Tobias Rapp wrote:
> [...] Thus I think it would be better to store timecode data as a 
> separate track, similar to how it could be done in MOV.

Both methods have pro and cons.
Lot of MOV time codes are linked to a video track, so side data may make 
sense here, as something we could transmux easily (with slightly less 
container overhead than a dedicated track).

So maybe we should permit both (SMPTE ST 12 in either side data or 
dedicated track).