-
-
Notifications
You must be signed in to change notification settings - Fork 699
Include JXL as Foreign TIFF Compression #3951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I was going to suggested this idea as I used Tiff with JPEG all the time. I just was doing some testing and still found JXL format slower than libjpeg-turbo in writing. Another limitation I am seeing, is that even if jxl claimed to be larger than jpeg, I can't write an image larger than 10kx10k pixel successfully, while in jpeg, I can write 65kx65k with no issue. The file size will be huge but I can do it. In JXL, The writing above 10k, will finish by crashing and saying jxlsave not found. It can't handle larger files. |
It depends on which version of That said, JXL has a lossless mode which is where I see myself using this feature. I have a lot TIFF containers with special metadata or layers and being able to losslessly compress in 32/16bit is something JPEG cannot do. JXL is also better for some kinds of scientific data as it can contain far more channels including non-visible and (obviously) alpha. |
There's a TIFF tag for JXL compression:
So I suppose we'd just need to compress each tile with libjxl, rather like jp2k. You can see the compression enum here: https://github.com/libvips/libvips/blob/master/libvips/foreign/vips2tiff.c#L294-L299 So we'd need to add https://github.com/libvips/libvips/blob/master/libvips/foreign/jp2ksave.c#L1191-L1420 So perhaps another 300 lines there. I'd guess 2 or 3 day's work, plus the same for |
@jcupitt Do you plan to include this as part of your fulfilment of the NGI Zero grant? |
No, I'll be looking at HDR and streamed encode and decode under the NGI grant. |
Hi @jcupitt , any news about this enhancement? Thank you. |
@jcupitt I would also be curious to know if there are plans to add support |
I've no immediate plans. I'm finishing nip4 right now, then a conference, then some work on DICOM, then the next libvips, and then the NGI grant, I think. Maybe after that? I'd be happy to help anyone else who wanted to add this feature, of course. |
@jcupitt Thank you for the transparency and for all your time. If this were within my skill set I would absolutely make a pull request, but it's much beyond me |
Ah, no problem, it's just a question of scheduling. Too much to do, too little time, etc. Plus I'm a little unsure how useful it'd be. I don't know of any other software that supports JXL-in-tiled-TIFF yet. |
Vips would be the first open source project to support it (that I know), but I've read a few posts by people making use of JXL in tiff and their workflows might be simplified. Adobe's DNG uses it and that's more or less TIFF, anyways. It is niche, though, and I understand why it's not a priority. |
Discussed in #3818
Originally posted by AngelaDMerkel January 17, 2024
Libvips struggles to properly handle metadata when moving between TIFF and JXL. Allowing JXL as foreign compression much like it does JPEG would help to realise many of the lossless space savings of JXL alongside the wide feature set of TIFF— without needing to compromise on metadata quality.
There is some precedent for this by Adobe. Adobe is using JXL compression inside their DNG files when performing a photomerge in Ligthtroom based on the logic of space savingings in linear DNG files.
The text was updated successfully, but these errors were encountered: