Menu

16.80 still deleting all JPEG Metadata.

NOR
2024-11-13
2024-12-06
1 2 > >> (Page 1 of 2)
  • NOR

    NOR - 2024-11-13

    Just tried new version 16.80. And as with 16.70 it still keeps deleting all metadat of JPG-Files, though option do keep metadat is set. 16.60 ist the last version that does not have this bug.

     
  • Nikkho

    Nikkho - 2024-11-13

    Can you please isolate the plugin removing metadata?

     

    Last edit: Nikkho 2024-11-13
  • NOR

    NOR - 2024-11-13

    Oh, how can do that? I just tried the 32-Bit version and the problem does not occur with it. So it is only a matter of the 64-Bit version

     
    • Nikkho

      Nikkho - 2024-11-13

      It makes sense because 32 bit version uses older plugins. The authors of some of them have not been updated in the 32 bit flavour for a while. In order to know the plugin broking metadata, you will need to disable them and try until you find the faulty one:

      From the FAQ:

      How can I disable a particular plugin?
      You can use the INI setting DisablePluginMask= to allow excluding execution of certain plugins. For instance DisablePluginMask=leanify;advpng.exe will prevent executing any plugin containing in its name leanify or advpng.exe.
      As you can see it is case insensitive, and allows more than one item to be specified by using semicolon (;) as separator.

       
  • Ambunge Rodrigues

    Any news on how to solve this?

     
    • Nikkho

      Nikkho - 2024-11-18

      I guess we are still pending to isolate which is the faulty plugin and report the issue to the devs.

       
  • Ambunge Rodrigues

    Too bad that with the same set of files, version 16.60.2819 keeps metadata but only gets to 65% of the original files, whereas 16.90.2829 gets to a whooping 35%, but does not keep metadata!

     
    • Nikkho

      Nikkho - 2024-11-18

      Probably it is a bug in a plugin updated between 16.60 and 16.90. I regularly update all plugins, so it is a matter of knowing the faulty one, and reporting to the developers.

       
  • James Pous

    James Pous - 2024-11-18

    Hello all together! I did a test with the latest version 16.90 and my jpeg files have EXIF-metadata.
    Do you have a test file, you can give us for testing?

    Which meta datas do you mean? EXIF data e.g. camera model, exposure, ISO, etc.?

    Which settings do you use in FileOptimizer?

    I test it with:

    JPEG => copy metadata
    other files => copy metadata

    It did not see any problems with my smartphone jpg files.

     

    Last edit: James Pous 2024-11-18
  • Ambunge Rodrigues

    Windows Explorer - right click - Details, all the data under Origin, Image, Camera, etc is gone after the optimization.
    Both JPG and Miscellaneous have Copy Metadata selected.

    EDIT: by the way, running the program without "Allow lossy optimizations" keeps the metadata OK! But filesize shrinks only about 10%, losing the main advantage (for me) of the program.

     

    Last edit: Ambunge Rodrigues 2024-11-19
  • NOR

    NOR - 2024-11-19

    @James Pous: Missing Metadata are e.g. rating, GPS-coordinates, location, keywords etc. - almost everything is gone after optimization.

    If you still use the 32Bit-Version or if your are on V16.60 (or lower) than this problem does not occur. It only happens with 64Bit V16.70 and newer. As Nikkho explained it is probably a matter of the new 64Bit plugins.

    @Nikkoh: I have not had much time to try out all plugins. I tried disabling the plugins that contain the word "JPG" in their filenames for I assume they will be used in the JPG optimization process. However, metadata were still gone then. So it must be a different plugin then. It would be helpful if you could name the plugins that are involved in the JPG optimization process so we may focus on those.

     
    👍
    1
  • Renard Voß

    Renard Voß - 2024-11-19

    It is not "a matter of the new 64Bit plugins" but this problem is caused by two things:

    [1] Bug - FO x64 doesn't keep EXIF data of jpegs when lossy operations are allowed

    Since V. 16.70 (when jpegli was added - which is great be the way) FO x64 doesn't keep EXIF data of jpegs when lossy operations are allowed. I don't know if this problem is caused by cjpegli.exe, but it came up with it.

    [2] Bug - cjpegli.exe missing in Plugins32 folder

    Since V. 16.70 FO x86 doesn't make lossy operations, when lossy operations are allowed, because jpegli was added only to the Plugins64 folder and not to the Plugins32 folder, too.

    That's why FO x86 keeps EXIF data.

    When cjpegli.exe is added from "jxl-x86-windows-static.zip" (from https://github.com/libjxl/libjxl/releases) FO x86 uses cjpegli.exe and delivers the same result FO x64 does (smaller file & deleted EXIF data).

    Thus, it would have been better to open a ticket and not a discussion!

     

    Last edit: Renard Voß 2024-11-19
    • Nikkho

      Nikkho - 2024-11-19

      Thank you so much for your investigations and your findings. I guess I already identified cjpegli to remove metadata. This is why I only enabled it when allow lossy compression in JPEG was set. In my opinion if you authorize to be lossy, you are authorizing to loss metadata too.
      Unfortunately it seems that cjpegli does not support any option to keep the metadata. So nothing much I can do.

       
  • Renard Voß

    Renard Voß - 2024-11-19

    Uh, that's really bad!

    But you could this:

    Go back to the plugins that were used until V. 16.60 and make jpegli optional with a checkmark on the jpeg option tab (including a warning, that jpegli will cause the loss of all EXIF data).

     
  • Renard Voß

    Renard Voß - 2024-11-19

    And/or look here:

    https://github.com/libjxl/libjxl/blob/main/CHANGELOG.md#090---2023-12-22

    • cjxl can now be used to explicitly add/update/strip Exif/XMP/JUMBF metadata using the decoder-hints syntax, e.g. cjxl input.ppm -x exif=input.exif output.jxl
    • djxl can now be used to extract Exif/XMP/JUMBF metadata

    So, you could save metadata with djxl with the first command and bring it back with the last one, when all optimizations are done.

    Such a solution could also help with "my" cpdf problem (you'll remember my mail concerning cpdf).

     

    Last edit: Renard Voß 2024-11-19
    • Nikkho

      Nikkho - 2024-11-19

      Thank you, will take a look at using cjxl in FO.
      In the meantime I just updated cjpegli to 0.11.0 and there is not a direct switch to keep metadata.

       
    • Nikkho

      Nikkho - 2024-11-19

      Sorry so much Renard. I am focused in my job and my Youtube channel and forget about it.
      Can you please open a thread or a ticket with the issue so it is on my mind?

       
  • Renard Voß

    Renard Voß - 2024-11-19

    And this could be relevant, too:

    https://github.com/libjxl/libjxl/issues/3193

     
  • Renard Voß

    Renard Voß - 2024-11-19

    I opened a ticket:

    https://sourceforge.net/p/nikkhokkho/tickets/140/

    Too bad, that you don't have much time at present.

    There are many things, I wanted to propose for the 17.x milestone.

    I'll do it anyway, but 17.x will certainly have to be released soon because of the cjpegli problem.

     

    Last edit: Renard Voß 2024-11-19
    • Nikkho

      Nikkho - 2024-11-20

      Thank you so much. In fact I have almost stoped the work on my books and want to continue with it. At the end there are too many activities eating my spare time.
      Thank you for the ticket.

       
  • Ambunge Rodrigues

    One could use Exiftool to copy the original metadata to the optimized files, but it is a tedious additional step.

     
  • NOR

    NOR - 2024-12-05

    Just want to confirm that the new "cjpegli.exe" available for Plugins32 and Plugins64 has solved the problem. So metadata a kept even with lossy compression enabled. Just download and copy to the respective Plugins-Folder. Thanks for taking care of this issue!

    https://sourceforge.net/p/nikkhokkho/code/1831/

     
    • Nikkho

      Nikkho - 2024-12-05

      Excellent @NOR. Thanks for confirming. New version will be bundled with FO 17.00.

       
  • Renard Voß

    Renard Voß - 2024-12-05

    I really tried everything, but I was not able to confirm this.

    Neither with 0.11.0 nor with 0.11.1 and neither with jxl-x64-windows-static nor with jxl-x86-windows-static.

    Did you compile JXL?

     

    Last edit: Renard Voß 2024-12-05
  • NOR

    NOR - 2024-12-06

    I checked again and have to correct myself. It is still NOT working. Metadata are still being deleted. My previous positive result was triggered by the fact that I still had cjpegli disabled in the INI-File.

     
1 2 > >> (Page 1 of 2)

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.