Nikkho

Have checked MP3 processing and it should not strip metadata. According to the log file it executes mp3packer without -t -s Start: 2024/08/22 17:34:48 End: 2024/08/22 17:34:49 Level: 9 Original: 5414467 Optimized: 5350569 Errorlevel: 0 Input: C:\Users\JavierG\Desktop\MP3\Lennox Annie - (10) - ItS Alright , BabyS Coming.mp3 Output: Plugin: MP3packer (1/1) Commandline: D:\PROYECTOS\FileOptimizer\Plugins64\mp3packer.exe -z -a "" -A -f "C:\Users\JavierG\Desktop\MP3\Lennox Annie - (10) - ItS Alright ,...

I will add to my todo listo to debug and try to check possible failured during the invocation to the plugins. Regarding the option of clearing metadata it is not the scope of FileOptimizer, but I will not discard creating a new tool for bulk removing it in several file types. For MP3 processing I am using MP3Packer and if "Copy metadata" is enabled FO will pass it the -t and -s flags which should not stripg metadata according to the plugin documentation: -t Strip non-MP3 data at the beginning (mainly...

Thank you so much for posting your conclusions. Indeed it is stated in FO itself in the tooltip as you noticed but also in the FAQ at: https://nikkhokkho.sourceforge.io/?page=FileOptimizer "Have the optimized files same degree of compatibility as the original ones? Generally yes, they have the same degree of compatibility. The exception is JPEG images, when you have enabled the User arithmetic encoding option. It generates smallest files with the same quality, but require recent software to render...

It is hard to catch. I run the optimization process over those three files 10 times and never happened. But as you say, it is only happening sometimes. The thing is that the checks in FO are even more exhaustive than you suggest, if you take a look to it you will see: https://sourceforge.net/p/nikkhokkho/code/HEAD/tree/trunk/FileOptimizer/Source/cppMain.cpp#l3047 1) Plugin execution is checked for being correct. 2) If it is the optimize size is checked. It required fille to exists. It should be greater...

Indeed this is what FO is doing. Unless the plugin returns OK, optimized file is not keep. Can you attach a sample of file, please?

Sure. Take look at the FAQ section: https://nikkhokkho.sourceforge.io/?page=FileOptimizer See how to enable the log, and then how to disable a plugin until you get the one failing.

Thank you Anton. Can you try to isolate the plugin failing?

Improved donator check