Hello CameronD,CameronD wrote:... In my workflow, I make a big distinction between image data and metadata. Storing image transformation instructions rather than burning them in is always a good idea, but this has to apply to the raw image, rather than a jpeg. To me, a jpeg is never "the original"...
... You are right, it's better to use the Raw files as originals files (original image data + original exif metadata ...) ... but the majority of people shoots mostly in jpg (less hdd storage and time consuming), then in this case the originals data are the .jpg files.
Ok, in this case, I also think than it's the best way to do.My aim is for maximum interoperability between software packages, and to my mind that means I have no option but to embed the metadata within the jpeg image whenever possible.
...Yes, in this case you can also have an option to tick all in one time "all write op." (and/or sub chooses to only tick the required metadata (ex): comments, icc, iptc, xmp, embedded thumb rebuild, etc ...)The last thing I want is to have to tick numerous options to turn that on, so if there is a single option then it should switch between:
Metadata: use sidecar files whenever possible, or
Metadata: embed within image file whenever possible
... I see your problematic, in this case, it's the messWith the list of override options, I can imagine a potential nightmare of situations brought about by: "When I write metadata X to image files of type Y then software Z does not read it, so I'll need to write that one the other way around".
EDIT, see here too:
http://newsgroup.xnview.com/viewtopic.p ... 85#p117985