Hi Phil, my mistake - the bat works on the XMP sidecar, not the RAW itself. Exiftool should read the tag from the ARW and write it to the XMP sidecar - this is how the bat file worked on my Vista machine. It still works just fine there, and my current workflow is actually to generate the XMPs on my laptop and port them over to my Win7 desktop - obviously very unwieldy.
I'm afraid I'm simply way over my head here - everything seems to be fine but nothing is working. Exiftool detects the file, is told to read the LensID tag from the ARW and write it to the XMP. Except it doesn't :E Running the command with pause on my vista laptop shows no differences at at all - the only difference being that it does write the correct Lens ID to the exif.
Thanks again for your help
I'm afraid I've still not managed to make it work - I've tried running the batch on the XMPs and on the folder containing RAWs and XMPs.
Here's what happens when I run the batch on my Vista machine:www.jaggerbramley.com/good.xmp
The basic information such as the location, copyright etc was added to the XMP created upon import. The batch file adds the aux:LensCarl Zeiss Vario-Sonnar T* 24-70mm F2.8 ZA SSM (SAL-2470Z)/aux:Lens line.
A file run through the exact same process on my Win 7 machine comes up with the following:www.jaggerbramley.com/bad.xmp
As you can see, the Lens string is absent - exiftool simply hasn't done its job. Why I just can't answer!
Many thanks for your patience! The latest version of the batch file reads like this:
I ran this on both the ARW and the XMP and neither was succesful - both ran exiftool and gave me the help option.
and once more exiftool ran with the help interface. I usually run Exiftool through a custom button which launches the bat file externally, but during this testing I've been trying to run it by dragging both the XMP and the RAW, as well as the whole folder onto the bat.
I think that at this stage it would be useful to give you a real overview of what I'm doing - I wrote a post a while ago to explain my method to others:
and I have also shared my troubles on the same forum where a couple of other users have described running Win7 64bit and not having any problems:
I look forwards to your response! Adam
But this also gave me the help screen. Unless exiftool is royally screwed on my machine...
I'm running the perl version of exiftool because I believe that only using the perl version do you get access to the /lib/Image/Exiftool/Minolta.pm file - I've edited this to reflect the lenses that I use. Do I get access to this file using the .exe? If that's the case and it would be simpler to go with that than to fuss around with perl then I'm more than willing!
To install exiftool, I followed the instructions here: http://www.sno.phy.queensu.ca/~phil/exiftool/install.html. I installed the 64bit version of activeperl from here: https://www.activestate.com/activeperl/downloads/ choosing the 64bit windows version. This is the only change that I've made from my 32bit vista install - although I have to admit that I installed everything so long ago that I can't remember my exact steps back then.
I'm good to go with the command line - I couldn't get it to work before because I'd not set the associations (or they didn't work in the DOS environment) so I wasn't typing perl exiftool.pl -ver. That all works now and I'm actually still on v7.56 - will update that now...
I've updated to v 7.99 and I've not noticed any difference. Dragging XMLs onto the batch still results in Exiftool running the help line - the only difference being that because I've not authed the new version to run as admin it now asks me if I want to do so. Thanks for your persistance - I'll be back in the morning! Adam
I've cleared my machine of perl and the perl version of exiftool and I've replaced everything with the latest .exe. When I drag an XMP onto the .exe it correctly displays the exif of the file. I now need help making the exe do what I want it to!
I've started off by simply replacing the reference to exiftool.pl with exiftool.exe in my bat file - I get the error that 'C:\exiftool\exiftool is not recognised as a valid executable or batch file'. Is the error because the .exe is not being picked up for some reason? My batch reads like so:
I have replaced the temp minolta.pm with my custom version - however if this is going to be deleted every time windows decides to clear its temp files then maybe I'll look into the custom file. Look forwards to getting this one working - thanks again for your continued support!
Thanks once more for your help - I'll pass my experience onto the folks at Dyxum too. Even after Adobe supported abbreviated lens IDs in LR 2.5, many people still seem to be using exiftool.