Good catch! I said to myself over the weekend to try this parameter and then forgot.
When running lepton on the ImageOptimizer result it is further reduced
Original: 2.8MB
Lepton on original: 2.2MB (22% reduction)
ImageOptimizer: 2.3MB (18% reduction)
ImageOptimizer+Lepton on result file (with allowprogressive): 1.9MB (33% reduction in total, lepton reduced by 18% the result file of ImageOptimizer)
DropBox is using Lepton as an internal format on their service so jpg files uploaded to DropBox are actually saved in lepton format and decompressed on the fly when needed. Having this kind of ability in Magick.net would be amazing (same applies for a separate .net wrapper - you could be the 1st to have such a thing)
If possible when writing a wrapper add support for working on byte arrays or streams and not just on file names
Thanks for all your help
When running lepton on the ImageOptimizer result it is further reduced
Original: 2.8MB
Lepton on original: 2.2MB (22% reduction)
ImageOptimizer: 2.3MB (18% reduction)
ImageOptimizer+Lepton on result file (with allowprogressive): 1.9MB (33% reduction in total, lepton reduced by 18% the result file of ImageOptimizer)
DropBox is using Lepton as an internal format on their service so jpg files uploaded to DropBox are actually saved in lepton format and decompressed on the fly when needed. Having this kind of ability in Magick.net would be amazing (same applies for a separate .net wrapper - you could be the 1st to have such a thing)
If possible when writing a wrapper add support for working on byte arrays or streams and not just on file names
Thanks for all your help