Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.compression > #4004 > unrolled thread

Neural Image Compression

Started byJustin Tan <justin.tan@coepp.org.au>
First post2020-09-20 21:29 -0700
Last post2020-09-21 17:50 +0000
Articles 3 — 3 participants

Back to article view | Back to comp.compression


Contents

  Neural Image Compression Justin Tan <justin.tan@coepp.org.au> - 2020-09-20 21:29 -0700
    Re: Neural Image Compression Stephen Wolstenholme <steve@easynn.com> - 2020-09-21 15:45 +0100
    Re: Neural Image Compression Eli the Bearded <*@eli.users.panix.com> - 2020-09-21 17:50 +0000

#4004 — Neural Image Compression

FromJustin Tan <justin.tan@coepp.org.au>
Date2020-09-20 21:29 -0700
SubjectNeural Image Compression
Message-ID<23ba620b-a85c-41d8-ad91-bacc2cffe70fn@googlegroups.com>
Hi,

I'd like to share a side project I worked on which generalizes transform coding to the nonlinear case. Here the transforms are represented by neural networks, which learn the appropriate form of the transform. The result of the transform is then quantized using standard entropy coding.

Github: https://github.com/Justin-Tan/high-fidelity-generative-compression
Interactive Demo: https://colab.research.google.com/github/Justin-Tan/high-fidelity-generative-compression/blob/master/assets/HiFIC_torch_colab_demo.ipynb

There are some obvious shortcomings to this method - such as, that it only caters for image data, cannot be adjusted to attain a variable bitrate, short of training a different model, and is unrealistically slow for practical applications.
 
I'm not a traditional compression expert, so would appreciate any insight about the deficiencies of this method from those who are. Note this is not my original idea and is a reimplementation.

[toc] | [next] | [standalone]


#4005

FromStephen Wolstenholme <steve@easynn.com>
Date2020-09-21 15:45 +0100
Message-ID<plehmf91qo6eltn58j2fmeahmcvjmqtt6v@4ax.com>
In reply to#4004
On Sun, 20 Sep 2020 21:29:48 -0700 (PDT), Justin Tan
<justin.tan@coepp.org.au> wrote:

>Hi,
>
>I'd like to share a side project I worked on which generalizes transform coding to the nonlinear case. Here the transforms are represented by neural networks, which learn the appropriate form of the transform. The result of the transform is then quantized using standard entropy coding.
>
>Github: https://github.com/Justin-Tan/high-fidelity-generative-compression
>Interactive Demo: https://colab.research.google.com/github/Justin-Tan/high-fidelity-generative-compression/blob/master/assets/HiFIC_torch_colab_demo.ipynb
>
>There are some obvious shortcomings to this method - such as, that it only caters for image data, cannot be adjusted to attain a variable bitrate, short of training a different model, and is unrealistically slow for practical applications.
> 
>I'm not a traditional compression expert, so would appreciate any insight about the deficiencies of this method from those who are. Note this is not my original idea and is a reimplementation.

EasyNN has image mode built in. I don't know how well it compresses
images because the person who tested and validated image encoding has
retired. I wrote the code a long time ago but I forget how it works.
I'm getting old!

Steve
  
-- 
http://www.npsnn.com

[toc] | [prev] | [next] | [standalone]


#4006

FromEli the Bearded <*@eli.users.panix.com>
Date2020-09-21 17:50 +0000
Message-ID<eli$2009211350@qaz.wtf>
In reply to#4004
In comp.compression, Justin Tan  <justin.tan@coepp.org.au> wrote:
> I'd like to share a side project I worked on which generalizes transform
> coding to the nonlinear case. Here the transforms are represented by
> neural networks, which learn the appropriate form of the transform. The
> result of the transform is then quantized using standard entropy coding.
> 
> Github: https://github.com/Justin-Tan/high-fidelity-generative-compression
> Interactive Demo:
> https://colab.research.google.com/github/Justin-Tan/high-fidelity-generative-compression/blob/master/assets/HiFIC_torch_colab_demo.ipynb
> 
> There are some obvious shortcomings to this method - such as, that it
> only caters for image data, cannot be adjusted to attain a variable
> bitrate, short of training a different model, and is unrealistically
> slow for practical applications.

Also:

   Clone repo and grab the model checkpoint (around 2 GB). 

If you need 2GB of data around to compress / decompress images, you need
a lot of images before this starts "winning".

> I'm not a traditional compression expert, so would appreciate any
> insight about the deficiencies of this method from those who are. Note
> this is not my original idea and is a reimplementation.

I'm no expert in compression, I just read this group for the occasional
insight.

Elijah
------
particularly interested in image compression

[toc] | [prev] | [standalone]


Back to top | Article view | comp.compression


csiph-web