Invalid time string ... when shifting

[Archive]

[Originally posted by vg on 2009-02-12 11:06:15-08]

I use exiftool v7.67 (Windows Executable), and when I want to change field "CreateDate" in EXIF header (= DateTimeDigitized) and run

exiftool.exe -P -v0 -CreateDate-="0:0:0 0:58:52" -o "destdir\%%f.%%e" -r srcdir

for some files it gives messages like

Warning: Invalid time string (2009-02-12T11:11+05:00) when shifting CreateDate - srcdir/IMG_8997.jpg

but in result file exif changes ok:

Date taken: 2006:12:30 14:25:45

Date digitized: 2006:12:30 13:26:53

what can I do to avoid these warnings ?

[Archive]

[Originally posted by exiftool on 2009-02-12 11:37:32-08]

Thanks for this report.  It looks like the problem is missing seconds
in your XMP:CreateDate, which is causing exiftool to complain.
But this is allowed in the XMP specification, so I will fix this.

Until then, you can work around the problem by rewriting the XMP:CreateDate.
ExifTool will add the seconds when you do this:

Code:

exiftool -tagsfromfile @ -xmp:CreateDate FILE

After doing this, you should be able to shift the CreateDate properly.

This is all assuming that XMP:CreateDate is the problem, but this makes
sense since it is an XMP-formatted date/time string that is shown
in the error message.  It is also possible that somehow an XMP-formatted
date got written to the EXIF, but this is a far more unlikely happening.

- Phil

[Archive]

[Originally posted by vg on 2009-02-12 11:53:07-08]

Phil, thank you for the answer.

This warnings appears 3-5 times while processing ~1000 fotos, made from the same camera and automatically converted from raw to jpeg by photoshop script. So, the fields in all of these files are about the same.

If you wish, I can send to your email all headers from strange file and from it's neighbor

[Archive]

[Originally posted by exiftool on 2009-02-12 12:07:57-08]

It would be useful to have a copy of one of these files for testing.
If you could mail one to me, that would be great (philharvey66 at gmail.com).

Then I can test this to be sure the problem is fixed in the next
exiftool release.

Thanks

- Phil