Feature #11666
Integrate MozJPEG encoder (to produce more efficiently coded JPEG files)
0%
Description
https://github.com/mozilla/mozjpeg
It seems to use licenses all compatible with GPL.
It's compatible with libjpeg API and ABI, and can be used as a drop-in replacement for libjpeg
History
#1
Updated by Roman Lebedev over 1 year ago
Sarge Borsch wrote:
https://github.com/mozilla/mozjpeg
It seems to use licenses all compatible with GPL.
It's compatible with libjpeg API and ABI, and can be used as a drop-in replacement for libjpeg
Sounds like a distro problem then.
#2
Updated by Sarge Borsch over 1 year ago
Roman Lebedev wrote:
Sounds like a distro problem then.
What does it mean?
#3
Updated by Roman Lebedev over 1 year ago
Sarge Borsch wrote:
Roman Lebedev wrote:
Sounds like a distro problem then.
What does it mean?
It's compatible with libjpeg API and ABI, and can be used as a drop-in replacement for libjpeg
^ so distributions can decide to build with MozJPEG instead of libjpeg / libjpeg-turbo, without any changes to the software
#4
Updated by Sergei Datsenko 5 months ago
Mozjpeg is highly-biased towards producing optimized JPEGs at the expense of high CPU usage during compression, so distributions will never switch to it as a default implementation. But for photoeditors that's would be a better option because producing the best possible JPEG is one of the main goals, right? Also, some optimizations are available only if one uses extended part of the API that goes beyond libjpeg-compatible subset.
Of course ideally libjpeg and mozjpeg would merge and just provide "mode options", but this don't seem to ever happen, mostly because of human nature.
#5
Updated by Roman Lebedev 5 months ago
Sergei Datsenko wrote:
Mozjpeg is highly-biased towards producing optimized JPEGs at the expense of high CPU usage during compression, so distributions will never switch to it as a default implementation. But for photoeditors that's would be a better option because producing the best possible JPEG is one of the main goals, right? Also, some optimizations are available only if one uses extended part of the API that goes beyond libjpeg-compatible subset.
Of course ideally libjpeg and mozjpeg would merge and just provide "mode options", but this don't seem to ever happen, mostly because of human nature.
I'd start by at least packaging it in the distributions.
Even debian does not have it.
And it does not looks like they want to have it packaged.