mozjpeg: default to fastest compression profile#311
Merged
Conversation
libultrahdr wraps but does not expose these
kleisauke
approved these changes
Dec 19, 2025
Collaborator
kleisauke
left a comment
There was a problem hiding this comment.
Nice catch! I suppose this would also be useful when encoding a TIFF with JPEG compression (AFAIK, it currently triggers this warning).
kleisauke
added a commit
to kleisauke/wasm-vips
that referenced
this pull request
Dec 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the prebuilt binaries, libultrahdr wraps mozjpeg (via the libjpeg API) but does not expose any of the underlying settings, so gainmap generation is ~3x slower than expected due to use of the default compression profile.
This change matches the default behaviour of libvips.
/cc @kleisauke as you might be interested in this for wasm-vips etc.