1.
-exec expressions work the same way as
--format expressions. The former generates a String value that is an argument value, the latter generates a String value that is a file path.
You can find a list of top-level bindings here, some of which are complex objects with dynamic properties, but since you're generally writing code here, even if just a variable name, the possibilities are rather inifinite:
https://www.filebot.net/naming.html#bindings
2.
I'm not actually clear what you're trying to do, and how
-exec in particular would be the best way to go about that, but I can give you an example that passes all the relevant information onto your custom script:
rednoah wrote: ↑14 Sep 2019, 19:43
Code: Select all
-exec /path/to/script.sh {f} {historic.f} {json}
I'd start with a test
script.sh for testing to see the variables that are passed along:
Code: Select all
#!/bin/sh -xu
echo "$1"
echo "$2"
echo "$3"
Note that the
amc script has it's own
--def exec option which is distinct from
-exec and although it can do the same thing, does work in a different way:
Code: Select all
--def exec="/path/to/script.sh {quote f, historic.f, json}"
3.
You can configure FileBot to write xattr metadata into a plain file structure instead:
https://www.filebot.net/help/xattr.html