Re: [video-codec] NHW Project - new version - very high compression - Interesting for IETF?

Michael Niedermayer <michael@niedermayer.cc> Thu, 04 October 2018 12:37 UTC

Return-Path: <michael@niedermayer.cc>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E1A130E47 for <video-codec@ietfa.amsl.com>; Thu, 4 Oct 2018 05:37:31 -0700 (PDT)
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 kUFJ2EHVSa9Z for <video-codec@ietfa.amsl.com>; Thu, 4 Oct 2018 05:37:28 -0700 (PDT)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 530DD130E59 for <video-codec@ietf.org>; Thu, 4 Oct 2018 05:37:28 -0700 (PDT)
X-Originating-IP: 213.47.41.20
Received: from localhost (213-47-41-20.cable.dynamic.surfer.at [213.47.41.20]) (Authenticated sender: michael@niedermayer.cc) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id B74CD1C0004; Thu, 4 Oct 2018 12:37:25 +0000 (UTC)
Date: Thu, 04 Oct 2018 14:37:24 +0200
From: Michael Niedermayer <michael@niedermayer.cc>
To: Raphael Canut <nhwcodec@gmail.com>
Cc: video-codec@ietf.org
Message-ID: <20181004123724.GK26818@michaelspb>
References: <CAKE58qHX4bmskJb+BWEHOhcxSiDy9ZOxd8B94HAZVomRzs0sXw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="1hKfHPzOXWu1rh0v"
Content-Disposition: inline
In-Reply-To: <CAKE58qHX4bmskJb+BWEHOhcxSiDy9ZOxd8B94HAZVomRzs0sXw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/video-codec/ST7SUA9D76MdyKlFx7-LBGRQ3FU>
Subject: Re: [video-codec] NHW Project - new version - very high compression - Interesting for IETF?
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/video-codec/>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2018 12:37:31 -0000

Hi Raphael

On Wed, Oct 03, 2018 at 06:42:01PM +0200, Raphael Canut wrote:
> Hello,
> 
> Maybe it could be interesting for professional people of this list, I have
> improved the NHW Project image compression codec.
> 
> This new version is better and I have added very high compression, which is
> very competitive with x265 (HEVC).Maybe this version could be now
> interesting for the IETF video codec working group...
> 
> For reminder, the NHW Project has more neatness than x265 (HEVC) and I find
> it visually more pleasant, it is royalty-free, and it is at least 50x
> faster to encode and at least 15x faster to decode than x265 (optimized
> HEVC)! So it is meeting the criteria of the IETF video codec.
> 
> You can find more at: http://nhwcodec.blogspot.com/
> 
> Sorry again if you find that I am "spamming" the list (do not hesitate to
> let me know), but it is extremely difficult for me to reach the Industry
> for my codec.

I cant speak about NHW (as i have not looked at it yet) or for IETF
but somewhat on topic and related, if you are interrested in
working on a IETF "standarized" video codec". As the author of the
original FFV1 spec. I and i belive "we" at IETF cellar would be very interrested
in seeing work done to improve future iterations of FFV1. And while
FFV1 is not a wavelet codec really i think there are no real constraints
of what a future v5, v6 or whatever might do, it could use a completely
different algorithm if the people on IETF-cellar feel thats the right
way forward.
I had always imagined long before cellar-IETF existed that future revissions
of FFV1 would be designed based on some sort of competition between 
different algorithms being tested with the aim being simplicity, 
high compression, speed and losslessness.
Also image coding and intra only coded video are very closely related,
its basically almost the same problem.

Thanks

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes