Thanks a lot, that helped!

[australiaescortshub]

Thanks a lot, that helped!

But I got a bit more questions:)

- Now I tried to export metadata to JSON with `-json` but this format looks not complete, i.e. it doesn't contain Canon:* and CanonCustom:* fields, am I right guessing it's not suitable to transfer proprietary data?
- Is there a way to make exiftool to treat proprietary fields like Canon:*, CanonCustom:* passed via commandline as a complete section of data to write?
- Is there a way to pass some XML/JSON/any other structured data exiftool's STDIN as metadata source instead of command line args or files?

Thanks a lot!

[StarGeek]

- Now I tried to export metadata to JSON with `-json` but this format looks not complete, i.e. it doesn't contain Canon:* and CanonCustom:* fields, am I right guessing it's not suitable to transfer proprietary data?

Impossible to answer without knowing what your command looks like. But my quick test here shows all the Canon data when I add the -j (-json) option.  FAQ #3 might help if you don't see all the data, specifically with regards to the -a (-duplicates) option.

- Is there a way to make exiftool to treat proprietary fields like Canon:*, CanonCustom:* passed via commandline as a complete section of data to write?

You can't create MakerNotes tags such as the Canon or CanonCustom tags.  They have to already exist in the file.  See note #2 under FAQ #23.

- Is there a way to pass some XML/JSON/any other structured data exiftool's STDIN as metadata source instead of command line args or files?

You can use the hyphen - to indicate STDIN.  For example, -j - will read json from STDIN the same way it would from a file.