From nobody Sun Dec 17 09:14:56 2017 Return-Path: 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 859921271FD for ; Sun, 17 Dec 2017 09:14:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=bunkus.org 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 RoCv61u0AnE6 for ; Sun, 17 Dec 2017 09:14:53 -0800 (PST) Received: from adara.bunkus.org (adara.bunkus.org [144.76.6.84]) (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 B47EB127137 for ; Sun, 17 Dec 2017 09:14:53 -0800 (PST) Received: from liselle.bunkus.org ([2a01:4f8:190:8147::105:1]:53826) by adara.bunkus.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1eQcWW-0000tR-2Q; Sun, 17 Dec 2017 18:14:48 +0100 Received: from sweet-chili.local (unknown [192.168.191.4]) by liselle.bunkus.org (Postfix) with ESMTPS id 3BC2F65412CE; Sun, 17 Dec 2017 18:14:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bunkus.org; s=mail2017070101; t=1513530888; bh=ODZW28LDGTNnsvmq69Ky8b5Q6s06vRGBj6a3n8qmN1k=; h=From:To:Subject:Date:From; b=datrKbfC7A+3luKVABTD2nrj/rbQzmbdLIOdwUbKxZdbdG4AD5DPh4KFpZCrVFuTa LFvwAkh1oMFP1f2tF8DVfGleb+XbxXDrdmm1NzrJrU10Jjpb/FuY5LfxPd41Js5e3+ jmpHiqdRunmc/tG/0ypC009PoTeezYGkRlYtdaMfAZtTOAinwhVz6kIoS5OFx15Da6 1YloRfe0c/R1/hEUZ4S2XO6/HSZn9ZZcko/A0S1F+Pi/HxWtX6C/go2iFgqKbfETRV al6VmBn/xHC5m2w2HS/xzPPLCjusqPkkXKeIfHPOpoOymaX2AtUMbrTsr+uAKgifM1 uERmsyVM7vN9zOnDz6Qt18Hmw0PYnPY94J2IXFjDB7HgAj3C8m+e3KpLArCdNnpp9m ajJYfrcKtJH770ncsWnPKDl4eANCx0Ylyc34+3+G60f+sDh6lk9nSxoJR0SQV8FMLv JLHJdiQWbaxd9r7vHZo6D91sBmtS4Txypd+G9hIvfIe4rCNfkIFVXpaVkQaf09ez+1 xbjuT9pHhbtf5/b7pxXgX6jhne6i9Desi339ZRD4rdK214pjD2tb7av4bpOGp7gN15 w82bz+6XK/bnOYjHV4TDrR49ogA0YQsoWChBXUrkV290z6NQhKmxgVpnyJunXOItv0 BZspSRR+qQxAESpZW0HQdemY= Received: from sweet-chili (localhost [IPv6:::1]) by sweet-chili.local (Postfix) with ESMTP id 1B8DF280D6FB; Sun, 17 Dec 2017 18:14:47 +0100 (CET) User-agent: mu4e 0.9.18; emacs 25.3.1 From: Moritz Bunkus To: Cellar list , help Questions Date: Sun, 17 Dec 2017 18:14:47 +0100 Message-ID: <87bmix1dko.fsf@bunkus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Archived-At: Subject: [Cellar] MKVToolNix v19.0.0 released X-BeenThere: cellar@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Codec Encoding for LossLess Archiving and Realtime transmission List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 17:14:55 -0000 Hey people, the year's almost over, so I'm just in time for the last release of the year: MKVToolNix v19.0.0 is out. It's not that big of release, but it still contains a couple of improvements all over the place — and two nice performance improvements on Windows that people will likely notice. There were no changes for package maintainers. Here are the usual links: …to the source code: https://mkvtoolnix.download/source.html …to the binaries: https://mkvtoolnix.download/downloads.html The Windows and macOS binaries are available already. The Linux binaries are stil being built and will be available of the course of the next couple of hours. Here are the NEWS since the previous release: ------------------------------------------------------------ # Version 19.0.0 "Brave Captain" 2017-12-17 ## Important notes * The MKVToolNix project now contains a [Code of Conduct](https://mkvtoolnix.download/doc/CODE_OF_CONDUCT.md). * The MKVToolNix project's source code repository, bug tracker and wiki have been moved to [GitLab](https://gitlab.com/mbunkus/mkvtoolnix/). ## New features and enhancements * mkvmerge: splitting by duration, by timestamps or by timestamp-based parts: mkvmerge will now consider the first key frame within 1ms of the requested value to be eligible for splitting. * MKVToolNix GUI: the GUI will now save and restore the widths of columns in tree and list views. Implements #2057. * MKVToolNix GUI: header editor: when closing or reloading a modified file, the GUI will now focus the first element that's been modified before asking the user for confirmation regarding discarding unsaved changes. ## Bug fixes * mkvmerge: fixed reading text files encoded in UTF-16 order UTF-32 that have different forms of line endings (new lines, carriage returns or a mix of both). Fixes #2160. * mkvmerge: MP4 reader: fixed mkvmerge's interpretation of edit list entries with `segment_duration == 0` when there's more than one edit list entry. In that case mkvmerge was reading the whole content more than once. Fixes #2152. * mkvmerge, GUI's multiplexer: MIME types: added the `font` top-level media types from RFC 8081. This means that the following new MIME types for fonts can be used: `font/ttf`, `font/otf`, `font/woff` and `font/woff2`. * mkvmerge: MPEG transport stream reader: fixed slow speed on Windows due to lack of buffering. * mkvextract: fixed slow track extraction speed on Windows due to lack of buffering. Fixes #2166. * MKVToolNix GUI: multiplexer: changing the "subtitle/chapter character set" drop-down was ignored when the selected track was a chapter track. Fixes #2165. * MKVToolNix GUI: multiplexer: once a "subtitle/chapter character set" was set for a track it couldn't be changed back to the empty entry (= auto-detection) anymore. * MKVToolNix GUI: header editor: fixed re-translating several displayed strings when the GUI language is changed if the language the GUI was started with was not English. Fixes #2159. * MKVToolNix GUI: header editor: whenever a file did not contain a "date" element in its segment information section, the GUI would erroneously ask the user to confirm discarding unsaved changes when closing or reloading the tab. Fixes #2167. * MKVToolNix GUI: job queue: jobs are now saved when their status changes in addition to when the program exits. Fixes #2168. ------------------------------------------------------------ Have fun :) mosu From nobody Thu Dec 28 09:28:38 2017 Return-Path: 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 C49D012D94A for ; Thu, 28 Dec 2017 09:28:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 10P4CQ6cP4Lr for ; Thu, 28 Dec 2017 09:28:34 -0800 (PST) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 5A739127058 for ; Thu, 28 Dec 2017 09:28:34 -0800 (PST) Received: by mail-qk0-x234.google.com with SMTP id j137so32584873qke.10 for ; Thu, 28 Dec 2017 09:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=MsGSiieTAVUfFdVxj/jrEUetvvgJn2IDR3N30cuPFA8=; b=ZG8YrACgDm0AREu0aapcx+HL203UrQ6l3jmfpveyvkPoI2Vt5BFEzlc53gxqkqmXyc 1MDUJwXDdGAnOfMgWlMyEcH12KhFVWkd0ZcW/JjD/LVgmZJGn3vSaNa281w6A/OHnEC/ HiJwzYJqNKZRdxXTSxzMm0UpyuBe5gg7eOXWQCbV2ScGY/eXM4ls+CWp1ORFeqhDgHBl PkL9zLwLVrvgz/JQzF8b4upijU9+x3/4V+EA786BAis8PUJgb+SxPy1TPtD3jlShpJJE w/8u8/i8hTd19CZSzYKc+C/9oERPNYW4EKjVrMZTnjXqQqgTUaVmSsu0LYrc5/Ykxrea KziA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=MsGSiieTAVUfFdVxj/jrEUetvvgJn2IDR3N30cuPFA8=; b=jurQe5dgdDARhqIYb02S9PenmhEKLt7HT/I+sb5kJd4TbWk01bzQIpva9rLPZLLnQs Bx1poXVQL/9E/JDP+VUZ++7pRxoGxXXR3mmViN4w9BCIbeEEERPaEmVqsK6sGKEj4dno PmRXt9TsDyBLfV+JY634Z1RNqbfNj3+wNjrxVkW+DetAkBG225EuWgKhCYWdUfOXOc6C RsfopNP0+9zEMhg/E1IOWJu3Iw68bQFjDPUM9kjJWPQB3h0p9rt2ajTYKGZBMsU/q/z8 ZuTaFAF8b3R0HuV0iyVNhd2V5lqszU5WfVZsSc6C+xjUhbg/YadFL5aaek9+/LH5PVK/ k2Cw== X-Gm-Message-State: AKGB3mKgAqTFiQ8uOqW3C9hamBUD2gXy+U53n9vn8fF9u/xlDr2oBr5m bKuYcrieXD2TrIRo7OkSnTQQ1RPxN9SV6rlyoN/6PQ== X-Google-Smtp-Source: ACJfBosoh21WkcgcobAxvJaxjjuy7DcuJ11GPGiPWu5ds/cTcV6oWYO5NQW0/Oj/s+kVVddjcGSECid5ivo+H1fNRh8= X-Received: by 10.55.19.229 with SMTP id 98mr25363754qkt.333.1514482112943; Thu, 28 Dec 2017 09:28:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.83.178 with HTTP; Thu, 28 Dec 2017 09:28:32 -0800 (PST) In-Reply-To: References: <99534033-A516-425E-A9A5-84F9F0B39183@dericed.com> From: Ashley Blewer Date: Thu, 28 Dec 2017 12:28:32 -0500 Message-ID: To: Codec Encoding for LossLess Archiving and Realtime transmission Content-Type: multipart/alternative; boundary="001a113ff8365c5e50056169d861" Archived-At: Subject: Re: [Cellar] status of FFV1 and EBML drafts X-BeenThere: cellar@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Codec Encoding for LossLess Archiving and Realtime transmission List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2017 17:28:37 -0000 --001a113ff8365c5e50056169d861 Content-Type: text/plain; charset="UTF-8" [thread bump] Can we figure out how to come to a consensus on these couple of issues? Ashley On Sun, Nov 26, 2017 at 4:07 AM, Steve Lhomme wrote: > Hi, > > I won't comment on FFV1, although I should probably read it to see if > there's anything I don't understand. > > For EBML I think there are still things to be done: > - clarify how to handle bogus data > https://github.com/Matroska-Org/ebml-specification/issues/48 > - kind of relates to junk in Master Elements > https://github.com/Matroska-Org/ebml-specification/issues/92 > In the context of long term storage it's probably very important to > solve these issues. > > - DocType 0 as experimental/internal. We need to agree on this and then > word it > https://github.com/Matroska-Org/ebml-specification/issues/157 > > After that I think we're good to got for EBML. There's currently no > pending pull request. > > 2017-11-19 16:47 GMT+01:00 Dave Rice : > > Hi cellar, > > > > At the IETF99 meeting in the minutes at https://datatracker.ietf.org/ > doc/minutes-99-cellar/ it discusses having a WG last call for FFV1 and > EBML but also the need for more reviews of these documents. Is one issue > blocking another? Meaning: should the group announce a last call in order > to encourage more reviews or are more reviews needed in order to have a > last call? > > > > Best Regards, > > Dave Rice > > > > _______________________________________________ > > Cellar mailing list > > Cellar@ietf.org > > https://www.ietf.org/mailman/listinfo/cellar > > > > -- > Steve Lhomme > Matroska association Chairman > > _______________________________________________ > Cellar mailing list > Cellar@ietf.org > https://www.ietf.org/mailman/listinfo/cellar > --001a113ff8365c5e50056169d861 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
[thread bump]

Can we fi= gure out how to come to a consensus on these couple of issues?

Ashley

= On Sun, Nov 26, 2017 at 4:07 AM, Steve Lhomme <slhomme@matroska.org= > wrote:
Hi,

I won't comment on FFV1, although I should probably read it to see if there's anything I don't understand.

For EBML I think there are still things to be done:
- clarify how to handle bogus data
https://github.com/Matroska-Org/ebm= l-specification/issues/48
- kind of relates to junk in Master Elements
https://github.com/Matroska-Org/ebm= l-specification/issues/92
In the context of long term storage it's probably very important to
solve these issues.

- DocType 0 as experimental/internal. We need to agree on this and then wor= d it
https://github.com/Matroska-Org/eb= ml-specification/issues/157

After that I think we're good to got for EBML. There's currently no=
pending pull request.

2017-11-19 16:47 GMT+01:00 Dave Rice <dave@dericed.com>:
> Hi cellar,
>
> At the IETF99 meeting in the minutes at http= s://datatracker.ietf.org/doc/minutes-99-cellar/ it discusses havin= g a WG last call for FFV1 and EBML but also the need for more reviews of th= ese documents. Is one issue blocking another? Meaning: should the group ann= ounce a last call in order to encourage more reviews or are more reviews ne= eded in order to have a last call?
>
> Best Regards,
> Dave Rice
>
> _______________________________________________
> Cellar mailing list
> Cellar@ietf.org
> https://www.ietf.org/mailman/listinfo/cellar



--
Steve Lhomme
Matroska association Chairman

_______________________________________________
Cellar mailing list
Cellar@ietf.org
https://www.ietf.org/mailman/listinfo/cellar

--001a113ff8365c5e50056169d861-- From austin.einter@gmail.com Sun Dec 31 09:02:15 2017 Return-Path: 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 A7DDD126B7F for ; Sun, 31 Dec 2017 09:02:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 jIWCRitffK4f for ; Sun, 31 Dec 2017 09:02:13 -0800 (PST) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 99B081241F8 for ; Sun, 31 Dec 2017 09:02:13 -0800 (PST) Received: by mail-wm0-x229.google.com with SMTP id b76so55203636wmg.1 for ; Sun, 31 Dec 2017 09:02:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EyX/8lKYzC3Ni4VvUwYBGpQu1ro6U826RF8JZpVNvkM=; b=f1CqjiTXeNhW8vhirHHem7vHlue89k3Wdc1nfnC0+HrhnNvrPRAiziYORKd0HBlgvJ Cn4weTcOf29E1qEHOu2ui1pV181gQGeULDhBQy+ZBNM+8fqViipQKMkpoAfZ0TcAFkyc M+duHVKAOdBAUA+LnUTzhcw7gl0RsPi3dCqcGNrbDAGjFiCFt0iYECEiQSgPoGAvTmI8 P8OByBd7JmEyBh12TogiwhrjJPqlfNab3Vzmoln0TqssuoonSl08RWE0oERx9K3x0Owg hqqnxz1KfN6UeaYQhF3RgEqb/VkBmoFfUYR8DA23UplWGdRORLDTgJoaSvVwbLy1/okT Qbtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EyX/8lKYzC3Ni4VvUwYBGpQu1ro6U826RF8JZpVNvkM=; b=AKkQoQfU7STXQhqNo/10xObb5o2PE+tkPi8eGjNb2Cr/7FAQ1KsplP2mIr3BF4uKUO zab8PaUcXM2jyunt4m1z7cc+fxeX9hRDUM1YFcBbgHneUmQ4pKIyNx2EjJStSAvoE+N5 R7hF72Df8ZtuaJZQ0pR9MQpqx5r+gP0xW9UdcK5Y8II5BXRFi+HWnP/T3Q89BqZvQ0rC IG7o1sH34GkSeBI/q/3SWnPMz2gakT191nTT0vfhiOo1vGCZnB+Fcm3QB0h1+3LAvzof 9EICKIPGBx1i+gDSGhH/d6o4SzkIO9V+FesI8TuHWAasZ7ni2eOn9vKsKefocVegwpZc b1DA== X-Gm-Message-State: AKGB3mK6qZujZD6ZmKrVbDDOqdFizaHZiPDaIZSc8MaRvz3j0CSf5OF2 MPRKa9ZA5PhoXsNBLsfh9Zr6PRgzT1phDTupY9U= X-Google-Smtp-Source: ACJfBosN6KxnbbAbTuiUJu034uuXE7wESquvYbwHyziL+H2clmyG4zF14FoumdqloeDzPtX4pg1eKb38xb27gWWNAiY= X-Received: by 10.80.174.230 with SMTP id f35mr53619887edd.25.1514739731663; Sun, 31 Dec 2017 09:02:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.177.233 with HTTP; Sun, 31 Dec 2017 09:02:11 -0800 (PST) From: Austin Einter Date: Sun, 31 Dec 2017 22:32:11 +0530 Message-ID: To: cellar@ietf.org Content-Type: multipart/alternative; boundary="f403045c2154a211360561a5d3ff" Archived-At: Subject: [Cellar] Understanding VP8 data in a MKV file X-BeenThere: cellar@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Codec Encoding for LossLess Archiving and Realtime transmission List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2017 17:12:00 -0000 --f403045c2154a211360561a5d3ff Content-Type: text/plain; charset="UTF-8" I have a mkv file, that contains VP8 encoded data. I need to stream this data to chrome (through RTP), and need to play it in chrome. I have parsed the mkv file, and I have VP8 data. I will be sending this VP8 data in RTP packetc. Looks I need to follow RFC 7741 to put VP8 descriptor / header in RTP packet followed by VP8 data. Now I have several doubts, kindly try to help me to understand. 1) What is a partition in VP8 and from MKV file how do I get partition information. 2) I need to put partition size in VP8 header. From where I get the partition size. 3) How do I know partition index, this I need to put in VP8 descriptor. Does VP8 data I read from mkv file contains this. Regards Austin --f403045c2154a211360561a5d3ff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have a mkv file, that contains VP8 encoded data.
I n= eed to stream this data to chrome (through RTP), and need to play it in chr= ome.

I have parsed the mkv file, and I have VP8 da= ta.
I will be sending this VP8 data in RTP packetc.
Loo= ks I need to follow RFC 7741 to put VP8 descriptor / header in RTP packet f= ollowed by VP8 data.

Now I have several doubts, ki= ndly try to help me to understand.

1) What is a pa= rtition in VP8 and from MKV file how do I get partition information.
<= div>2) I need to put partition size in VP8 header. From where I get the par= tition size.
3) How do I know partition index, this I need to put= in VP8 descriptor.

Does VP8 data I read from mkv = file contains this.

Regards
Austin
=

--f403045c2154a211360561a5d3ff--