Quote from: australiaescortshub on September 09, 2021, 01:16:16 PM- 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 (https://exiftool.org/exiftool_pod.html#j-JSONFILE--json). FAQ #3 (https://exiftool.org/faq.html#Q3) might help if you don't see all the data, specifically with regards to the
-a (
-duplicates) option (https://exiftool.org/exiftool_pod.html#a---a--duplicates---duplicates).
Quote- 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 (https://exiftool.org/faq.html#Q23).
Quote- 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.