11/05/23559 EXIF bug - any news yet?

Status
Not open for further replies.
C

Captain Slocum

Member
Premium Classic Member
Premium Cloud Member
Joined
Feb 2, 2009
Messages
34
2,3'1 of my 24,755 photos show the wrong EXIF Datetime Original, Datetime Digitised and Datetime in LR 2.3. They all show as 11/'5/23559.

They are a mixture of downloads from different cameras, imports from disc and various dates from between last week and seven years ago. Some are CR2 some are JPEG some are TIFF some are PS.

They all display the date correctly in other programmes such as Bridge or PS so the fault lies in LR2. Others who have had the 23559 problem in LR2 did not have it in LR1. Oddly, in a handful of cases, the Datetime (but not the Datetime Original or Datetime Digitised) displays correctly

I note this has been reported several times a year ago (search this forum with the term 23559 and you will find the threads) but clearly nothing has been done.

Anybody have any idea why this happens and why Adobe have still not fixed it?
 
Sort by date Sort by votes
Hi Captain Slocum

I haven't a clue why it happens, but I just wanted you to know you're not being ignored!

I'd love to see if I can replicate it here - fancy dropped me one of the problem files?
 
Upvote 0 Downvote
Hello,
I have the same problem. I posted this on Adobe forums about a month ago.
"I know this has been posted before, including by me, but I've just upgraded to 2.3 and the problem is still there. I had also raised a bug report with Adobe but to no avail.
The issue is all photos imported with a capture year of 2''6 get the capture date corrupted, usually to 5/11/23559 or 5/12/23559, but also a few to 1/1/5414 and to 1/1/561'. All other years, back to 1999, are correct.
It is only in the LR catalogue and not in the photos. I have looked at the photos with other programs and they are correct.
I know it is a repeatable problem because I have tried importing the photos from scratch at each new release since version 2.', and nothing has changed. It doesn't matter whether I import the photos fresh or reimport them from my 1.4.1 catalogue. I get the same results.
It's a very annoying problem and I'm not sure what to do next to try to fix it.

I'm running XP SP3 on a 1.5 G Dell Inspiron laptop."

What file do you want, a cut down version of my catalogue? There does not seem to be any point in sending the photos, becasue the only difference is the date captured. I've got photos taken in 12/'6 and '1/'7 on the same holiday, and the '6 ones are in error.
 
Upvote 0 Downvote
I checked out some of Captain Slocum's files, and they appeared correct on my machine, which just deepens the mystery. I would be quite interested to see how they've been recorded in your catalog, so an 'export from catalog' of those couple of pictures, along with the related images, would be an interested exercise, if you're up for investigation cweng. You can drop them on my server: http://vbftp.net
 
Upvote 0 Downvote
Hello Victoria,
I have uploaded a catalogue with 3 files, a .jpeg, a Canon .CR2, and a Canon .CRW, along with the sources files and copies of them exported from this catalogue. You will see the date captured on all photos is correct, but the date capture in this catalogue on my machine is incorrect.
Cheers
 
Upvote 0 Downvote
Thanks Charles, got them safely. REALLY interesting exercise. I opened up the catalog in a database viewer to see what was actually recorded, and when it's imported your files, it's recorded the harvested EXIF with the fixed 23359 date.

I then started a clean catalog on my machine and imported them in - and came up with the correct dates recorded. I've emailed you that catalog (zipped) - why not open it up on your machine and see if it still reads the correct dates.
 
Upvote 0 Downvote
[FONT=&quot]Hi Victoria,[/FONT]
[FONT=&quot]Nice to have someone who knows more about Lightroom than me looking at this. I opened the database on my machine and got the 23359 dates. I’ve returned the database in case it’s something environmental on my machine causing the problems.[/FONT]
[FONT=&quot]Regards[/FONT]
[FONT=&quot]Charles[/FONT]
 
Upvote 0 Downvote
Investigating the 11/05/23559 bug

I also have this problem (with lightroom2.3 on winXP) and did some tests to investigate:

I scrapped my catalog and reimported all my images into a fresh catalog - the problem persisted (the date for some images after a certain date is still 11/'5/23559), so it's not a catalog problem.

While the fresh catalog was updating itself (e.g. creating previews, gathering metadata in newly imported images) I noticed that image which were initially showing the correct date were changed to the corrupt date as the catalog synched itself with the images on disk.

Then I scrapped all XMP data from my images and reimported them. For raw images I deleted the XMP files while I used exiftool to remove XMP data from JPGs. After reimporting them the date was shown correctly.

This leads to the conclusion that the error is in the XMP data. I also suspect that the error was introduced in a recent update of Lightroom (possibly version 2.3), and only images imported after a certain date with the faulty version are affected.

I suggest that Adobe provide a free tool to correct the XMP data and work on a permanent fix for lightroom 2.4.

Thanks for listening.
 
Upvote 0 Downvote
Welcome to Lightroom Forums, and nice job with the investigation.

I'd suggest you write that up (or just cut & paste it) into a bug report to Adobe; the link is on the blue bar at the top.
 
Upvote 0 Downvote
I heard back from Adobe on this today. It looks like it's a combination of hardware and software resulting from an underlying Windows API. Yeah, didn't mean a whole heap to me either! End result - not an easy fix, so the more data, the better the chances of tracking it down.
 
Upvote 0 Downvote
I experienced this problem when I started using Lightroom back in Nov. 2''8 - and posted on this forum about it.

Eventually I discovered it only occurred on RAW image files which I subsequently 'imported' to Imatch. (I think when Imatch read the associated XMP sidecars some change was made to file modify date/time settings in a manner which confuses LR2 when you re-open it and the image files are reread.)

Since changing the Imatch preference settings so that no write actions are allowed this problem has not recurred. This suggests that the 23559 issue relates to the way in which LR handles caching of changes. I also found out the hard way that having LR and Imatch running simultaneously was a sure way to encounter 23359.
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top