I think it's the apostrophes that fixed that. Seems that without them, the shell tries to interpret parts of the command as a shell command. There is some documentation of the ${} syntax at the exiftool site; seems that it should be avoided if possible but sometimes it's necessary.
The documentation is, I'm sure, quite thorough but for a newbie it's an impenetrable wall of stuff with no structure or index. It's inconceivable to me that no one has offered to write a user-friendly manual, so I assume it's not a welcome contribution. I'd be happy to take a stab at it once I learn my way around, though.
Dead on with the documentation. It's impenetrable. I spend so much time looking for that 'one thing' that I've never really got a grasp on the language as a whole.
I've asked for help in forums. I always get, "RT*M, it's #15 in FAQ8, numbskull." And they'll link to FAQ8 and they'll be right, so I guess that's helpful. Can't say it isn't in the documentation.
I'm a pretty good BASH guy. I only use EXIFtool to pull data from individual image files, then parse those files with shell scripts. Didn't need to learn a ton about EXIFtool for that.
Let us know if (and how) you figured out how to write to a CR3 file. I've never played with a writeback. But I have been playing with AI editing software, and some of those strip out all the exif data from the result image. I've been wondering if there's a way to use EXIFtool to copy that data back in from the original image.
I just looked. There's no O'reilly book.

