Re: [Cellar] Anyone heard of "MagicYUV"?
"Peter B." <pb@das-werkstatt.com> Tue, 28 February 2017 08:03 UTC
Return-Path: <pb@das-werkstatt.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 AE1D7128B44 for <cellar@ietfa.amsl.com>; Tue, 28 Feb 2017 00:03:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 TepznJCRdtga for <cellar@ietfa.amsl.com>; Tue, 28 Feb 2017 00:03:38 -0800 (PST)
Received: from zucker.schokokeks.org (zucker.schokokeks.org [178.63.68.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F73B1289B0 for <cellar@ietf.org>; Tue, 28 Feb 2017 00:03:38 -0800 (PST)
Received: from [10.0.0.11] (1360030002.d-dsl.at [::ffff:81.16.105.50]) (AUTH: PLAIN bubestinger@schokokeks.org, TLS: TLSv1/SSLv3, 128bits, ECDHE-RSA-AES128-GCM-SHA256) by zucker.schokokeks.org with ESMTPSA; Tue, 28 Feb 2017 09:03:36 +0100 id 0000000000000032.0000000058B52ED9.00007D9E
Message-ID: <58B52ED8.50208@das-werkstatt.com>
Date: Tue, 28 Feb 2017 09:03:36 +0100
From: "Peter B." <pb@das-werkstatt.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
References: <r470Ps-10116i-B39A8E418683409A81CD2BB9B5F7F7A9@Castor.local>
In-Reply-To: <r470Ps-10116i-B39A8E418683409A81CD2BB9B5F7F7A9@Castor.local>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/lzM3d59p7xdx6S65SJse2XItfHI>
Subject: Re: [Cellar] Anyone heard of "MagicYUV"?
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Feb 2017 08:03:39 -0000
On 02/27/2017 04:51 PM, Reto Kromer wrote: > Peter B. wrote: > >> and it seems quite >> proprietary. > Yes, it is. I have an SDK (not the current version 2), but > they keep the codec itself "secret" and I didn't had the > energy so far for doing some reverse engineering. > > I suspect HuffYUV has been the starting point, as many of us > did. I could perform some tests with resonance patterns that > hurt HuffYUV which would give a clue, if needed. Thanksalot for your input! But don't bother doing anything with MagicYUV. Since its author doesn't want it to be open and accessible, I don't see any need in further investigating this codec. Just posted it here so we know what else "exists" ;) Nice greetings, Pb
- [Cellar] Anyone heard of "MagicYUV"? Peter B.
- Re: [Cellar] Anyone heard of "MagicYUV"? Reto Kromer
- Re: [Cellar] Anyone heard of "MagicYUV"? Peter B.