How is the compression from PIK used in Jpeg XL? In FUIF I understand that the same algorithm is used both for Loossless and Lossy compression.
JPEG XL (at least the current version of the spec) has 4 modes, which basically correspond to pik-lossy, pik-lossless, fuif, brunsli
Hi, pardon the question, but is FLIF dead?
The Jared Wilcurt
@viluon FLIF is a filetype. There are tools to convert from other file types to it, and tools to view those files. It is open source so anyone can contribute to it to improve it, or create their own encoding/decoding tools based on the spec and existing source code.
Active development efforts seem to have moved from it to FUIF and JPEG XL, which will have FUIF essentially built in, and FUIF has many ideas that are taken from FLIF
UGUI_FLIF doesn't seem to do anything. Running on MacOS
Neil Sandage anagram"Nile_EdenAgs" Hamilton+Sandys
I want to replace JPEG, since FLIF is better than JPEG, how soon Fuji Camera, and Replace Motion JPEG aka MPEG video? ~ any guess about h.264 h.265 or VC1 or my favorite Matroska
The Jared Wilcurt
@NEdenags_twitter All of the good ideas from FLIF and FUIF are being added into JPEG-XL.
JPEG XL will have slightly better lossless compression than FLIF, and it will decode about twice as fast on single-core and be parallelizable. Lossless encode is still rather slow atm, we still need to improve that.
We took MANIAC from FLIF, turned it into MA-ANS, and made it significantly more powerful: it also does lz77-style references, it has a predictor and multiplier per MA context, and more predictors and MA properties.
The FLIF/FUIF-based mode in JPEG XL is called "Modular mode", and it is used for various things: lossless mode, the DC (1:8 image) in lossy mode, alpha and other extra channels, and all kinds of internal auxiliary images in lossy mode (the adaptive quantization map, block type selection map, chroma from luma coefficients, custom quantization tables, filter strength maps).
Version 0.1 was released last week. Plan is to reach 0.2 soon (bw-compatible bitstream), then 0.3 (stable libjxl api) by January, and hopefully we can get in the next Android and in Chrome somewhere in 2021.