Forum

Author Topic: Convert images drops xmp metadata  (Read 3094 times)

jolle

  • Newbie
  • *
  • Posts: 3
    • View Profile
Convert images drops xmp metadata
« on: May 11, 2022, 04:36:06 PM »
On metashape 1.8.1 - build 13915 on Windows, when using the convert images functionality, the converted images have no xmp metadata.

Steps to reproduce:
 - Create a new metashape project with 1 chunk.
 - Add a number of .jpg files to the chunk
 - Right click the chunk, choose export --> convert images
 - In the convert images dialog, keep the default settings and click OK.
 - Select a folder for exporting.

We observe that the exported .jpg's have no xmp metadata (by running exiftool -b -xmp on the exported files).
Our expectation is, that the exported .jpg's have the same xmp metadata as their counterparts in the metashape project camera groups.

Is this a bug, or are we missing a setting/toggle/etc. in metashape? Or is this by design?

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14813
    • View Profile
Re: Convert images drops xmp metadata
« Reply #1 on: May 11, 2022, 05:34:30 PM »
Hello jolle,

Can you please check, if you are observing that in Metashape 1.8.3?
Best regards,
Alexey Pasumansky,
Agisoft LLC

jolle

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Convert images drops xmp metadata
« Reply #2 on: May 12, 2022, 02:46:11 PM »
Hi Alexey,

I just did a test with version 1.8.3 (the application is listing build 14431), and I am observing the same behaviour with that version.

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14813
    • View Profile
Re: Convert images drops xmp metadata
« Reply #3 on: May 13, 2022, 12:50:34 PM »
Hello jolle,

Please then send the example of JPG file to support@agisoft.com that we can use to reproduce the issue with XMP meta data.
Best regards,
Alexey Pasumansky,
Agisoft LLC

smiller

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: Convert images drops xmp metadata
« Reply #4 on: October 10, 2022, 10:26:16 AM »
Hello, was this issue resolved in 1.8.4?