Legend

Released

P: Inconsistent dates for files missing date/time metadata

42 replies
1783 views
Translate

If an image or video is missing metadata date/time fields, then LR 3.4.1 uses the file's date-modified for filtering, sorting, and pre-populating the Metadata > Edit Capture Time dialog, but it uses the file's date-created to display in the grid view. It should use date-modified consistently for all of those. (When Windows copies or restores a file, the date-modified is preserved, but date-created is usually set to "now".)

This problem trips up people managing scanned images and videos, since scanners typically don't add any metadata and LR doesn't understand much video metadata.

See these threads for examples and details:

http://forums.adobe.com/message/37343...

http://forums.adobe.com/message/38293...

Windows

This topic is closed to new replies. Start a new post to keep the conversation going.

B

Beany from Brooklyn

Known Participant

Thanks as always John!

Translate

johnrellisAuthor

Legend

There still appears to be a problem for video files. See this new topic (since this topic has been marked as "solved"):

http://feedback.photoshop.com/photosh...

Translate

B

Beany from Brooklyn

Known Participant

Thank you John. I am now following those threads!

Translate

johnrellisAuthor

Legend

LR has never done a great job of importing video metadata. One problem is that LR will screw up the time zone of Quicktime-format videos:

http://feedback.photoshop.com/photosh...

See this thread for more general issues with LR's handling of video metadata:

http://feedback.photoshop.com/photosh...

Translate

B

Beany from Brooklyn

Known Participant

Umm, when I import a mix of pictures (raw and jpg) and videos from my Sony Nex7 the videos are 4 hours off.

Translate

johnrellisAuthor

Legend

I just verified that the original problem I reported is indeed fixed in LR 5.5. Thanks!

Translate

F

FeedbackCommunityMember

Inspiring

That's great, Ben. I wish the bug had been fixed during the lifetime of LR 4, though, for those of us still on that version. Three years and two major versions later is really too big a waterfall.

Translate

B+Warde

Adobe Employee

This is fixed in Lightroom 5.5, which is now available. (Note that there are several distinct problems discussed in this thread, so when I say that "this is fixed" I'm referring to the problem which John Ellis originally reported.)

Thanks,
Ben

Translate

H

heinim

Participant

I'm new to Lightroom and noticed this bug the third day I used it. It took me several hours to figure out what the problem is and how to work around it (see http://feedback.photoshop.com/photosh...). I hope you understand that it didn't help to build trust in the product. Please bump your bug priority once again.

Translate

F

FeedbackCommunityMember

Inspiring

Thank you, Ben. (And if my backhanded remark came across as a backhanded compliment, then that was entirely unintentional!) You've taken my point well, which was that having a feature on the features list doesn't mean much when the feature doesn't work properly, and having a bug in the bug database doesn't mean anything when the bug doesn't get any attention whatsoever.

You guys have (understandably) moved well beyond fixing bugs in Version 4 at this point, so I know that for me anyway, I'll never see this problem go away unless I pony up for a new version that might just maybe not have this bug. It's frustrating, really.

Translate

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.