2 ms·
>Currently, this runs at approximately 0.7 megapixel/sec on a GPU with unoptimized TensorFlow. Forgive me, is that in encoding or decoding? And size of library
by ksec 6y ago
>Currently, this runs at approximately 0.7 megapixel/sec on a GPU with unoptimized TensorFlow.
Forgive me, is that in encoding or decoding? And size of library required to decode it? ( Edit: Looks like answered below )
It was only an hour ago I was looking at some pictures encoded with VVC / H.266 reference encoder, it was better than BPG / HEVC, but this HiFiC still beats it by quite a bit.
This whole thing blows up my mind on limitation I thought we had on image compression.
May be I should take back my words on JPEG XL is the future. This seems revolutionary.
- gtoderici 6y ago(coauthor here) The 0.7 megapixels/sec is PNG decode (to get input)+encoding+decoding+PNG encoding (to get output we can visualize in a browser) speed. Thanks for your kind comment!
- JyrkiAlakuijala 6y agoJPEG XL and HiFiC are developed in the same team. JPEG XL is just positioned for slightly less compute than HiFiC.