Thread

Posted on Tue Jan 2 04:19:50 2007 by rmarkley
Entries in IFD0 out of sequence
I have been running ExifTool ver 6.66 against some .nef images from a Nikon D200. I had the year off by 1 for a large number of images and want to fix that.

The dates are named and are of the format: exif:DateTimeOriginal: 2006-04-16T06:53:04.24-04:00 and exif:DateTimeDigitized: 2006-04-16T06:53:04.24-04:00. When I run the commandline exiftool "-DateTime Original+=1:: 0" h:\redate, I get the message "Warning: entries in IFD0 were out of sequence. Fixed." -h:\redate/_DSC0328.NEF. It does update one of the fields, though. When I run this using -AllDates, all date fields get advanced by 1 year, including some that don't need to be. That's the characteristic of -AllDates, I suspect.

I ran the -AllDates against some files that had both .nef and .xmp. It did only 1 .xmp, and changed only the DateTimeOriginal. The DateTimeDigitized was not changed. I would like to change only the DateTimeDigitized and DateTimeOriginal in both exif and XMP areas. Is this possible?

Direct Responses: 3949 | Write a response
Posted on Tue Jan 2 14:40:11 2007 by exiftool in response to 3942
Re: Entries in IFD0 out of sequence
The "out of sequence" warning is issued because according to the TIFF specification the tags must be in numerical order within an IFD. Since NEF is TIFF-based, this is checked, but the warning is non-critical.

AllDates is a shortcut for DateTimeOriginal, CreateDate and ModifyDate. If you don't want all of these changed, or if you want to change other dates, then you can specify the ones you want individually on the command line.
Direct Responses: 3950 | 3951 | Write a response
Posted on Tue Jan 2 16:39:37 2007 by rmarkley in response to 3949
Re: Entries in IFD0 out of sequence

Thanks for your quick response.

I think that I found at least one of the problem areas. The .nef files that I was converting the dates on had all been touched either by Adobe Bridge or IDimager to add keywords. this must have messed with the order. When I ran exifTool against some .nef files that were "untouched" right out of camera, the date correction ran OK with no error messages.

The program will change the DateTimeOriginal and nothing else, if I put that in the command line, i.e. exiftool "-DateTimeOriginal+=1:: 0" h:\redate. all dates get changed if I run this with AllDates. The command line won't run if I use DateTimeDigitized. Is It possible to change only DateTimeOriginal and DateTimeDigitized, and not change ModifyDate. Is CreateDate the command I should use to change DateTimeDigitized? I will go check that.

Write a response
Posted on Tue Jan 2 16:41:20 2007 by rmarkley in response to 3949
Re: Entries in IFD0 out of sequence

Thanks for your quick response.

I think that I found at least one of the problem areas. The .nef files that I was converting the dates on had all been touched either by Adobe Bridge or IDimager to add keywords. this must have messed with the order. When I ran exifTool against some .nef files that were "untouched" right out of camera, the date correction ran OK with no error messages.

The program will change the DateTimeOriginal and nothing else, if I put that in the command line, i.e. exiftool "-DateTimeOriginal+=1:: 0" h:\redate. all dates get changed if I run this with AllDates. The command line won't run if I use DateTimeDigitized. Is It possible to change only DateTimeOriginal and DateTimeDigitized, and not change ModifyDate. Is CreateDate the command I should use to change DateTimeDigitized? I will go check that.

Direct Responses: 3952 | Write a response
Posted on Tue Jan 2 17:06:56 2007 by rmarkley in response to 3951
Re: Entries in IFD0 out of sequence
CreateDate does indeed change only DateTimeDigitized. So, the command line I will use is exiftool "-DateTimeOriginal+=1:: 0" "-CreateDate+=1:: 0" h:\redate to update files in the redate folder.
Direct Responses: 3953 | Write a response
Posted on Tue Jan 2 17:28:56 2007 by exiftool in response to 3952
Re: Entries in IFD0 out of sequence
No you've got me confused. Writing CreateDate only changes CreateDate. Perhaps it is called DateTimeDigitized by some other application?
Write a response