[Cellar] Re: Introductions and a new I-D that may be appropriate for CELLAR
Sam Whited <sam@samwhited.com> Mon, 02 March 2026 18:05 UTC
Return-Path: <sam@samwhited.com>
X-Original-To: cellar@mail2.ietf.org
Delivered-To: cellar@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 49BA1C2644FB for <cellar@mail2.ietf.org>; Mon, 2 Mar 2026 10:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=samwhited.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 067Z2luLbxqr for <cellar@mail2.ietf.org>; Mon, 2 Mar 2026 10:05:22 -0800 (PST)
Received: from 004.priority.relay.mayfirst.org (004.priority.relay.mayfirst.org [204.19.241.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1E00DC263B6D for <cellar@ietf.org>; Mon, 2 Mar 2026 10:03:53 -0800 (PST)
Received: from 003.route.relay.mayfirst.org (003.route.relay.mayfirst.org [204.19.241.87]) by 004.priority.relay.mayfirst.org (Postfix) with ESMTP id 4fPmyV0WdXz4w7H for <cellar@ietf.org>; Mon, 2 Mar 2026 18:03:46 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=samwhited.com; s=mayfirst1; t=1772474626; bh=d0cPQUez6aiMtjD52b3T3ulWO/oSrBGtWh0fan2xf40=; h=Date:Subject:To:References:From:In-Reply-To:From; b=2Pf0t/JOSIv5m40YYx4xqHScDPlR+isWTwbhn/YUU0rKamjWRS2w2GjN7rqGgQyKq IPuh5zhtE1pxLthpwHXCOnP6ULneR9ruJDFKijvZpEMDQnYwIBOrRaSkKC7Aqru454 vggESQBJABFGAddIO+QO0NLFUrxVh2gULK0ZUyrI9jeyXugelVZDE6GK2ILll01zix J1w3KP5ZemfbM1CjsOD/DkpSB19Zi54rK/IB+x72AWrmmj3S435dvblQuqKmool9bw tiZH6rHoBnRmXNZQRMng705+ft/zxy1AHVpsi8EGmEFleVPWNEskv3D14VnDR7EjHZ TLDdvS+lPauzQ==
Received: from filter.mayfirst.org (mailfilter003.mayfirst.org [209.51.172.10]) by 003.route.relay.mayfirst.org (Postfix) with ESMTP id 4fPmyT6nySz6ty1 for <cellar@ietf.org>; Mon, 2 Mar 2026 18:03:45 +0000 (UTC)
Received: from filter.mayfirst.org (localhost [127.0.0.1]) by filter.mayfirst.org (Postfix) with ESMTP id 4fPmyT5PY0z2w4k for <cellar@ietf.org>; Mon, 02 Mar 2026 18:03:45 +0000 (UTC)
X-Spam-Language: en
X-Envelope-From: <sam@samwhited.com>
Received: from mail.mayfirst.org (mailcf001.mayfirst.org [209.51.180.236]) by filter.mayfirst.org (Postfix) with ESMTPS id 4fPmyT5130z2w4g for <cellar@ietf.org>; Mon, 02 Mar 2026 18:03:45 +0000 (UTC)
X-Mayfirst-Relay: priority
Message-ID: <12ca3987-a4eb-4218-910d-94415bf66872@samwhited.com>
Date: Mon, 02 Mar 2026 13:03:42 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: cellar@ietf.org
References: <67bf643c-9a4f-4443-998a-01d4d1f5eea6@samwhited.com> <ca8918ea-f10a-46a1-b752-e128899507c1@samwhited.com> <CAKKJt-dc2HU1XzrwT+fvEpjT92WPSt3_NC8qZaUCzDzxthOqvA@mail.gmail.com>
Content-Language: en-US
From: Sam Whited <sam@samwhited.com>
Autocrypt: addr=sam@samwhited.com; keydata= xjMEYQ9TGxYJKwYBBAHaRw8BAQdA1uioUF7QcW5zHL8JZngkgggUHz6IkaiHuD+orF0vBRLN HlNhbSBXaGl0ZWQgPHNhbUBzYW13aGl0ZWQuY29tPsKQBBMWCAA4FiEEgiFNf7VNyaO8DNrh FtUTjlK4SbMFAmEPUxsCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQFtUTjlK4SbOK UQD/bMy4TOMOojgJZrcdobguB5mXLprol3bW2g70DDQ8DKwBAK7QVx7EqNEsf3dI9/DUV5xV EdS7NVVGzyRXPIp0cxgMzjgEYQ9TGxIKKwYBBAGXVQEFAQEHQMqWNKV2p/GhJnwRucCXB7gk uFt6k71ny/wX7McE+R1LAwEIB8J4BBgWCAAgFiEEgiFNf7VNyaO8DNrhFtUTjlK4SbMFAmEP UxsCGwwACgkQFtUTjlK4SbM3mwD+KFVyE0rJIvc2+a5Y+tVfqaipVBVFz73/mJIndt83Z/EA /RN2WT6/IXF0V0UYgLubjXfKmrodyWHod697aMYJeJMM
In-Reply-To: <CAKKJt-dc2HU1XzrwT+fvEpjT92WPSt3_NC8qZaUCzDzxthOqvA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Message-ID-Hash: OY6VRWALECKHSQO2KNQH2ORNYEIKH4I3
X-Message-ID-Hash: OY6VRWALECKHSQO2KNQH2ORNYEIKH4I3
X-MailFrom: sam@samwhited.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cellar.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Cellar] Re: Introductions and a new I-D that may be appropriate for CELLAR
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/tD-W9sjGZLJgBvTQgSrFy11lzdA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Owner: <mailto:cellar-owner@ietf.org>
List-Post: <mailto:cellar@ietf.org>
List-Subscribe: <mailto:cellar-join@ietf.org>
List-Unsubscribe: <mailto:cellar-leave@ietf.org>
Hi Spencer, Thanks for the reply! To answer your main question, I believe this is just a profile and no changes need to be made to Matroska to support stem files. Whether there's any benefit to the cellar working group taking the draft on as opposed to me just submitting it to the editor myself I don't know, but I do believe there is some value in having these be standardized for use in multiple DJ applications since right now there isn't any open standard and buying stem files is a bit of a mess depending and depends on where you get them. My current main sticking point is whether Matroska or Ogg is a better wrapper for it. I'm currently leaning towards Ogg because of it's simplicity and how much easier it is to read and write the files, but Matroska has much better support for metadata which is nice, and if I'm not mistaken you can seek faster in Matroska (though DJ applications would likely pre-compute seek points anyways to avoid any possibility of latency). Also, in either format, I'm struggling to figure out where best to indicate that this is a specific profile of the format (webm uses the doctype, but that's a violation of the matroska spec if I'm reading this correctly). I'll likely just make up some metadata for this, but it seems like something for this would already exist that I should imitate. —Sam On 2026-03-02 12:17, Spencer Dawkins at IETF wrote: > Hi, Sam, > > You're definitely in the right place to be asking questions. > > We talked about this draft last week at our monthly meeting, mostly > from the perspective of what CELLAR might need to do. > > The meeting minutes are here: > https://datatracker.ietf.org/meeting/interim-2026-cellar-02/materials/minutes-interim-2026-cellar-02-202602242000-00, > but just to save you a click, I can summarize ... > > Mailing list question about draft-swhited-ogg-stems/ > Is this draft/technology in scope for CELLAR? It's really a request > for a Matroska profile > What standardization is actually needed? > We have already started mailing list discussion with Sam Whited (the > draft-swhited-ogg-stems/ author). We'll have more discussion, > and will figure out whether anything needs to be updated in our > working group specifications, and whether anything must be written > down in order to achieve interoperability > > > Our biggest question is whether there are changes to existing working > group documents needed, in order to support STEMS. > > Beyond that - if STEMS is a profile, and does not require any changes > to Matroska, we can talk about the advantages of producing that > profile in CELLAR. One obvious question is whether the profile would > help interoperability if it's published by CELLAR, as opposed to just > appearing as a web page (there is nothing wrong with web pages!). > > But you're engaged with the right people for now, and focused on > technical discussion. Please continue! > > Best, > > Spencer -- Sam Whited sam@samwhited.com
- [Cellar] Introductions and a new I-D that may be … Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Martijn van Beurden
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Steve Lhomme
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Spencer Dawkins at IETF
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Steve Lhomme
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Robert Sparks
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited