JPEG XL: libjxl 0.7.0 released(github.com)
github.com
JPEG XL: libjxl 0.7.0 released
https://github.com/libjxl/libjxl/releases/tag/v0.7.0
2 comments
is paying a large sum of money the only way to learn about JXL? What about JPEG?
You can probably learn something from what is available on jpeg.org and jpegxl.info, as well as looking at the libjxl or j40 implementations. Is there anything in particular you would like to know?
i just want to write a rust binding to the existing j40 and learn about its implementation while I am at it (always has been fascinated by file formats)
If you are interested in making a J40 binding in Rust, please also take a look at the future Rust version itself. I've made an initial issue [1] about this effort.
[1] https://github.com/lifthrasiir/j40/issues/10
[1] https://github.com/lifthrasiir/j40/issues/10
come to discord to talk about JXL
I believe the authors have made a very late draft available, as they have been unable to work around the processes that prevent them releasing the actual standard.
The person who recently re-implemented it in C mentioned this.
I thought it was in the Readme but maybe it was a comment here at HN:
https://github.com/lifthrasiir/j40
Found it:
https://news.ycombinator.com/item?id=32885536
The person who recently re-implemented it in C mentioned this.
I thought it was in the Readme but maybe it was a comment here at HN:
https://github.com/lifthrasiir/j40
Found it:
https://news.ycombinator.com/item?id=32885536
You can download the ISO docs from the usual places you pirate books.
I wish it were that simple, newer ISOs or papers take months or more to find its way. If I had 200 bucks to spare, I'd do it myself
- Decode/encode api for metadata (Exif, XMP etc)
- Decode api for getting separate layers and spot colors (by default, the decoder blends layers and spot colors automatically and only returns the merged image)
- Improved api for progressive decoding
- Improved api for HDR and color management
- Command line tools cjxl and djxl were reimplemented and are now using the library api (they predated the library api so before they were directly calling internal functions; using the library reduces their binary size dramatically)
Some aspects of the api were improved, changed or deprecated; this release mostly serves as a preparation step towards 1.0 - the (non-deprecated parts of the) 0.7 api are expected to remain in the 1.0 api.