IETF Logo Mail Archive

Re: [Cellar] matroska and side data vs timecode

Tobias Rapp <t.rapp@noa-archive.com> Tue, 26 November 2019 09:00 UTC

Return-Path: <t.rapp@noa-archive.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 3BE08120821 for <cellar@ietfa.amsl.com>; Tue, 26 Nov 2019 01:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 5iN6qoo6vm55 for <cellar@ietfa.amsl.com>; Tue, 26 Nov 2019 01:00:07 -0800 (PST)
Received: from mx02.mail.netstorage.at (mx02.mail.netstorage.at [IPv6:2a02:2410:b000:101:3000::d]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85255120808 for <cellar@ietf.org>; Tue, 26 Nov 2019 00:59:48 -0800 (PST)
Received: from p1002.netstorage.at (p1002.netstorage.at [89.207.146.186]) by mx02.mail.netstorage.at (Postfix) with ESMTPS id 8E30BA7DF9; Tue, 26 Nov 2019 09:59:43 +0100 (CET)
Received: from mailix (noaport.de [46.237.252.213]) by p1002.netstorage.at (Postfix) with ESMTPA id 15091817B5; Tue, 26 Nov 2019 09:59:43 +0100 (CET)
Received: from [192.168.0.107] (HSI-KBW-46-237-252-214.hsi.kabel-badenwuerttemberg.de [46.237.252.214]) by mailix with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128) ; Tue, 26 Nov 2019 09:59:42 +0100
To: Dave Rice <dave@dericed.com>
Cc: Steve Lhomme <slhomme@matroska.org>, Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
References: <00F6A0BF-2922-4BAC-AC73-EB888767886F@dericed.com> <CAOXsMF+_zZjKS9GRjBhpQMQ5dbQK04hph5x5o8UJjj5ngkaaMA@mail.gmail.com> <03b98f95-f426-24a9-be2b-d8cc4ab4ef65@noa-archive.com> <7B1163E2-FCD5-446C-8430-34F94E165101@dericed.com> <CAOXsMFLFkKB20tdVkC+bH+692q4LT8Wg4SeOOWA-vfAhLtZ9Qg@mail.gmail.com> <73669E32-8239-4017-8A39-F1521CB6E24D@dericed.com>
From: Tobias Rapp <t.rapp@noa-archive.com>
Organization: NOA GmbH
Message-ID: <ac5bfd79-bd3d-ac1f-c1a7-458bac6c7f40@noa-archive.com>
Date: Tue, 26 Nov 2019 09:59:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <73669E32-8239-4017-8A39-F1521CB6E24D@dericed.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <20191126085943.10558.21022@p1002.netstorage.at>
X-PPP-Vhost: noa-archive.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/tcakOfWSH8EulOUyrXyVHf992fM>
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: Tue, 26 Nov 2019 09:00:09 -0000

On 25.11.2019 21:25, Dave Rice wrote:
> 
>> On Nov 24, 2019, at 11:43 AM, Steve Lhomme <slhomme@matroska.org 
>> <mailto:slhomme@matroska.org>> wrote:
>>
>> Not necessarily ordered-chapters. A chapter already has a mandatory
>> start time, it could have one Timecode to define what that start time
>> corresponds to (or more variants of Timecode for the same start time).
>> Technically that means you could have on Chapter per frame to match
>> it's time exactly with a timecode, that would be a dirty hack.
> 
> Please no. :-O
> 
>> As for reset in tapes, After a reset you should use a different
>> Segment. If there are just gaps of time between continuous takes, you
>> can use on Chapter start/timecode after each discontinuity.
> 
> I think this is hacky as well. It seems like a lot more to ask a 
> recording tool to reset to a new Segment because the timecode skipped.
> Dave

Just out of curiosity: How many timecode jumps (excluding jumps due to 
corrupt signal) do you experience when recording? From my knowledge 
there is usually one timecode at the start of a program, and about 1-4 
different programs on one carrier tape.

Best regards,
Tobias

v2.23.0 | Report a Bug | By Email