IETF Logo Mail Archive

Re: [Cellar] matroska and side data vs timecode

Dave Rice <dave@dericed.com> Tue, 26 November 2019 14:02 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 52EA11200FF for <cellar@ietfa.amsl.com>; Tue, 26 Nov 2019 06:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level:
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] 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 fGzN8iFOhDNu for <cellar@ietfa.amsl.com>; Tue, 26 Nov 2019 06:02:44 -0800 (PST)
Received: from server172-3.web-hosting.com (server172-3.web-hosting.com [68.65.122.111]) (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 37CCC120048 for <cellar@ietf.org>; Tue, 26 Nov 2019 06:02:44 -0800 (PST)
Received: from [146.96.19.240] (port=24596 helo=[10.10.201.20]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <dave@dericed.com>) id 1iZbQL-003JoO-Ga; Tue, 26 Nov 2019 09:02:42 -0500
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Dave Rice <dave@dericed.com>
In-Reply-To: <ac5bfd79-bd3d-ac1f-c1a7-458bac6c7f40@noa-archive.com>
Date: Tue, 26 Nov 2019 09:02:27 -0500
Cc: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>, Steve Lhomme <slhomme@matroska.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <76AF6036-FA4F-49E6-BAB9-905135917796@dericed.com>
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> <ac5bfd79-bd3d-ac1f-c1a7-458bac6c7f40@noa-archive.com>
To: Tobias Rapp <t.rapp@noa-archive.com>
X-Mailer: Apple Mail (2.3445.104.8)
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/cA6NdqXEKZWCH-_Zxzrxe-GAQGo>
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 14:02:47 -0000


> On Nov 26, 2019, at 3:59 AM, Tobias Rapp <t.rapp@noa-archive.com> wrote:
> 
> 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?

A non-sequential timecode could happen on every frame. For instance a tape to tape duplication where the source tape was left in pause mode while the other tape was recording would leave a long series of frames with identical timecode values.

> 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
> 
> _______________________________________________
> Cellar mailing list
> Cellar@ietf.org
> https://www.ietf.org/mailman/listinfo/cellar

v2.23.0 | Report a Bug | By Email