-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
JPEG XL (JXL) parameters not available #159
Comments
Hi, thank you very much for the suggestion. I will check if it is possible to implement the transcode functionality in Converseen. This depends on whether ImageMagick has this feature! |
Thanks to you for your work. I think your application will be the only one to have that feature implemented. Most of converters don't even know about that JXL feature and simply "reencode" to JXL, so image loss more information. Should I leave this thread open? |
That would be a really interesting addition, I hope it can be implemented using ImageMagick. :) Anyway you can leave the thread open! |
How did you set lossless in JPEG XL? I don't have any options, only for JPG. Converseen uses automatically lossy conversion. I tried with a large PNG, lossless it would have around 15MB and converseen gives me a 3MB file |
I am looking for a way to bulk convert my photos to JXL as well and I decided to bump this issue up again. It seems that ImageMagick doesn't support neither lossless encoding nor |
JXL format has a bunch of parameters, not only lossless or lossy compression. One interesting parameter is "transcode" from JPG. Is a conversion that doesn't loss any information from JPG file but makes it smaller. For example, cjxl command line tool from libjxl let users to losslessly transcode JPEG images into JPEG XL. Transcoding preserves the already-lossy compression data from the original JPEG image without any quality loss caused by re-encoding, while making the file size smaller than the original. Is Converseen using this JXL feature when converting JPG to JXL?
The text was updated successfully, but these errors were encountered: