![]() I mention this because the majority of the editable fields I see in your screenshot are not on the "official" list, and your explanation seems to confirm this. There's a lot of flexibility with Exif, it's easy to put custom fields in there, but the official fields could remain what they were. BTW, I'm not sure if the "shooting" fields in NLP are "secret sauce" fields to be read by NLP only, or the actual Exif data. Yes, absolutely, the edited Exif data are the "official" fields. With this method you can change whatever you want without a plugin for free, and this is baked into the file so it's recognised by any software/operating systemĮDIT: PS my examples are for Windows, no idea if it works on Apple computers I have a series of copies like this in a special folder named "ExifTool custom"Įxiftool(-a -u -g1 -w txt).exe : Produces a text file next to the original file listing all the EXIF data included in the fileĮxiftool(-Model='X-T3').exe : changes the model of the camera, so that you can fool the PP software, for instance to make available film sim's that are not available for the actual camera (I used this when Classic Chrome was not yet available for my X-T1, but I don't know if it still works, Fuji/Adobe/C1 might have circumvented this ability since then) You can add the aperture as well of course. ![]() Your exif will now show the correct lens and focal length. LensTagger does 2 things: it modifies the official Exif data, and it adds its owh fields if you choose to populate the film data tabįWIW, if you want just to change the focal lenght in the actual Exif, a easy procedure (not needing a plugin or a specific editor like LR or C1, is the following:ģ: rename the executable like this (for example): " exiftool(-LensModel='X-Fujinon Macro 55mm f3.5' -FocalLength='55' -overwrite_original).exe"Ĥ: drag the files you want to modify onto this instance of Exiftool. ![]() ![]() Click to expand.Yes, absolutely, the edited Exif data are the "official" fields.
0 Comments
Leave a Reply. |