I use FileOptimizer all the time (and have donated once, too little), it is great. I especially like the fact, that it allows to keep the metadata, even if the plugin (like guetzli) strips them away.
Speaking of guetzli (and the reason for my question): it would be great if one could force the use of a certain plugin. Take guetzli: I believe it is in the chain, but almost never used on lossy JPG optimization. I even tried deactivating all other lossy optimization plugins (via Disable plugin mask, like "jpeg-recompress;ImageMagick;mozjpegtran;ECT;rehuff;rehuff_theora"), still guetzli doesn't kick in.
So it would be great if you'd also implement a Force plugin mask, so you could use FileOptimizer as a simple front-end for each plugin. Maybe with a check box either respecting the normal chain and the disable plugin mask, or using only the plugin in the Force plugin mask.
In accordance with some requests from the past, it would be cool to see the plugin chain that will be used. Right now, I can only check the log after running FileOptimizer to see what plugins have been used.
Equally, it had been asked, some tools can be configured, like guetzli, so it would be great indeed the user could control this, either by a config file for each tool or a singel config file for all tools.
Okay, quite a few ideas goin beyond the original subject's scope :)
Have a nice day, week, month ;)
Holger
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your support Hoiger. It is something I want to implement since years ago. But honestly do not know how to do it.
The case of guetzli would be trivial, it is only used for JPEG kind images and when Lossy is Enabled and Copy Metadata disabled. But this is not the usual thing.
A plugin execution depends on the filetype. Take in mind pingo, used for PNG and JPEG. It uses different paramenters depending on the filetype, and furthermore, the compression level is calculated depending on the level of FileOptimizer.
The idea of having a textfield with parameters for each filetype and used plugin will end in about 500 textfields. It will be unusable. Just for JPEG we will have pingo, guetzli, jpeg-recompress, jhead, Leanify, ect, jpegoptim, jpegtran, mozjpegtran; and for PNG apngopt, pngquant, PngOptimizer, TruePNG, pngout, optipng, pngwolf, Leanify, ect, pingo, advpng, deflopt, defluff, deflopt
Some of them are excluded at runtime, for instance APNG is not used if the file is not animated, some of them excluded if you wanted to keep metadata because the plugin always overwrites it, and some other tweaks to avoid execution of plugins in files they will not handle well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hola Javier,
I use FileOptimizer all the time (and have donated once, too little), it is great. I especially like the fact, that it allows to keep the metadata, even if the plugin (like guetzli) strips them away.
Speaking of guetzli (and the reason for my question): it would be great if one could force the use of a certain plugin. Take guetzli: I believe it is in the chain, but almost never used on lossy JPG optimization. I even tried deactivating all other lossy optimization plugins (via Disable plugin mask, like "jpeg-recompress;ImageMagick;mozjpegtran;ECT;rehuff;rehuff_theora"), still guetzli doesn't kick in.
So it would be great if you'd also implement a Force plugin mask, so you could use FileOptimizer as a simple front-end for each plugin. Maybe with a check box either respecting the normal chain and the disable plugin mask, or using only the plugin in the Force plugin mask.
In accordance with some requests from the past, it would be cool to see the plugin chain that will be used. Right now, I can only check the log after running FileOptimizer to see what plugins have been used.
Equally, it had been asked, some tools can be configured, like guetzli, so it would be great indeed the user could control this, either by a config file for each tool or a singel config file for all tools.
Okay, quite a few ideas goin beyond the original subject's scope :)
Have a nice day, week, month ;)
Holger
Thank you for your support Hoiger. It is something I want to implement since years ago. But honestly do not know how to do it.
The case of guetzli would be trivial, it is only used for JPEG kind images and when Lossy is Enabled and Copy Metadata disabled. But this is not the usual thing.
A plugin execution depends on the filetype. Take in mind pingo, used for PNG and JPEG. It uses different paramenters depending on the filetype, and furthermore, the compression level is calculated depending on the level of FileOptimizer.
The idea of having a textfield with parameters for each filetype and used plugin will end in about 500 textfields. It will be unusable. Just for JPEG we will have pingo, guetzli, jpeg-recompress, jhead, Leanify, ect, jpegoptim, jpegtran, mozjpegtran; and for PNG apngopt, pngquant, PngOptimizer, TruePNG, pngout, optipng, pngwolf, Leanify, ect, pingo, advpng, deflopt, defluff, deflopt
Some of them are excluded at runtime, for instance APNG is not used if the file is not animated, some of them excluded if you wanted to keep metadata because the plugin always overwrites it, and some other tweaks to avoid execution of plugins in files they will not handle well.