Re: [Cellar] On the multiplicity of Info elements

Steve Lhomme <slhomme@matroska.org> Sat, 02 January 2016 08:47 UTC

Return-Path: <slhomme@matroska.org>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F09041A6F62 for <cellar@ietfa.amsl.com>; Sat, 2 Jan 2016 00:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=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 W50iaQXRzit4 for <cellar@ietfa.amsl.com>; Sat, 2 Jan 2016 00:47:49 -0800 (PST)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 C27131A03AB for <cellar@ietf.org>; Sat, 2 Jan 2016 00:47:48 -0800 (PST)
Received: by mail-vk0-x22d.google.com with SMTP id k1so103481811vkb.2 for <cellar@ietf.org>; Sat, 02 Jan 2016 00:47:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=matroska-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=CF3yEaMmQooxFjzkiTahnKCb+nqxJkS08+Y12idaifM=; b=GwsMH6G9hKLte7zXpZCuHVhu6cQlJPg4PrX17qdt7373P8ZIlz0oB9g7z2IlA7R7vi wkTMSlcWvO6Zt2/V3pzTnCufqoS8GmHlYBdQqlFtyHI7Hy0YBhb95wWpgEGqwacx7bNX I2rEGHK8X+G4zR2Cp0gDU94T7G/9v4zFxhCASG9TitxVJloSS0geEZ+NQ8FuNwzr/nnG g1DqTdzgvbV92wBYpgQurLQRnUhoTH+OIZH6A7kDxY1SQ7IHqhoGNMtZDmnHUAIgBRuz KQfWTvXUP9FRb/2SOgNrXIBANJv4MvXAH53RGVuU+Vb7U6UIsi0Sms1FV7CvCdReA6Yd 4FLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CF3yEaMmQooxFjzkiTahnKCb+nqxJkS08+Y12idaifM=; b=ZLD+sNeSvFjlFdCj3U22XyFGnSt7QJpjI7gSQt0r5s60ABh/EFCCWjbo91Eq/z2Gnb ndIqI3PuZdqftyneDdGGYrL38P/gsoZeBg8Y/01DjUOUeXfSjPRUr9cyImMS2qptk1Xi jPzO0fplbt3HH85ntYGbBpwFLSRD80qDjy3kCymgNJsjk0umT0iiepCnFXueRke4WGlI 0yt5zL5dLRE5gHWJ33EBruCNccuHVJtXOWyNJnxSyzqmFS/+gvmUXKsdi0lBsYQWizTn RyPHtoWDwZt3zImMB/I+05FLu0kLscMbF78CVnYOEb39kVBNHHRWz1oTAg/y2no0M/iT WdTA==
X-Gm-Message-State: ALoCoQlKO7rdsO1X3fpebSxPE0/scY4TX5cP6sAcG7pfgBAE90m3iHhvncIup/Q5/qhagkD6ZX2Xc4sUawoPevODkKqafDtrmA==
MIME-Version: 1.0
X-Received: by 10.31.54.196 with SMTP id d187mr52676101vka.18.1451724467944; Sat, 02 Jan 2016 00:47:47 -0800 (PST)
Received: by 10.31.8.84 with HTTP; Sat, 2 Jan 2016 00:47:47 -0800 (PST)
In-Reply-To: <20151230091811.GA19636@bunkus.org>
References: <CAHUoETLC4dQQ7=TOuTXZ3aDjKCCJgz2s-8Gb33MoSAP3hgRQiQ@mail.gmail.com> <BEA72D66-EA3D-4CF0-987D-836E95287F39@dericed.com> <20151230091811.GA19636@bunkus.org>
Date: Sat, 02 Jan 2016 09:47:47 +0100
Message-ID: <CAOXsMFLCbe-W=h+tQpdRa8Nh0jz=xdbZTXEmoXsgQTbA=4OPCQ@mail.gmail.com>
From: Steve Lhomme <slhomme@matroska.org>
To: Moritz Bunkus <moritz@bunkus.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/cellar/W3K7PGhifMNT1SkBEobsRgANizY>
Cc: cellar@ietf.org
Subject: Re: [Cellar] On the multiplicity of Info elements
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 02 Jan 2016 08:47:50 -0000

2015-12-30 10:18 GMT+01:00 Moritz Bunkus <moritz@bunkus.org>:
> Hey,
>
> I only remember the discussion around Tracks being multiple, not
> particularly for the other ones. Our intent way back when was to allow
> muxers to write multiple instances of _the same information_ in
> different places in order to make the file more resilient against
> damage or incomplete downloads with protocols like BitTorrent.

Yes, that's the idea for the Track Info as it's vital to the usability
of the file, as well as the Segment Info. I'm not sure it's used in
practice though.
Since the goal of CELLAR is archiving solutions it may still make sense.

> The same reasoning could be applied to Info. Both elements are
> absolutely crucial to playback; the other level 1 elements safe for the
> clusters simply aren't.
>
>> SeekHead, Info, Cluster, Tracks, and Tags are multiple.
>
> SeekHead and Cluster must be multiple. SeekHead in order to allow moving
> a SeekHead to the end of the file while still referencing it from the
> start (so that normal players will still find it quickly). Cluster for
> obvious reasons.
>
>> And Cues, Attachments, and Chapters are non-multiple.
>
> I have no idea why Tags is multiple and these three aren't.
>
> To me the following would make sense:
>
> - Info, Tracks – multiple but only if each instance contains the same
>   information
>
> - SeekHead, Cluster – multiple without restrictions
>
> - Attachments, Chapters, Cues, Tags – single
>
> Kind regards,
> mosu
>
> _______________________________________________
> Cellar mailing list
> Cellar@ietf.org
> https://www.ietf.org/mailman/listinfo/cellar
>



-- 
Steve Lhomme
Matroska association Chairman