Skip to main content
johnrellis
johnrellis
Legend
July 30, 2011

P: Inconsistent dates for files missing date/time metadata

  • July 30, 2011
  • 42 replies
  • 1685 views

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...

    This topic has been closed for replies.

    42 replies

    B
    Beany from Brooklyn
    Known Participant
    December 13, 2014
    Thanks as always John!
    johnrellis
    johnrellisAuthor
    Legend
    December 10, 2014
    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...
    B
    Beany from Brooklyn
    Known Participant
    July 8, 2014
    Thank you John. I am now following those threads!
    johnrellis
    johnrellisAuthor
    Legend
    July 8, 2014
    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...
    B
    Beany from Brooklyn
    Known Participant
    July 8, 2014
    Umm, when I import a mix of pictures (raw and jpg) and videos from my Sony Nex7 the videos are 4 hours off.
    johnrellis
    johnrellisAuthor
    Legend
    June 27, 2014
    I just verified that the original problem I reported is indeed fixed in LR 5.5. Thanks!
    F
    FeedbackCommunityMember
    Inspiring
    June 19, 2014
    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.
    B
    Community Manager
    Benjamin WardeCommunity Manager
    Community Manager
    June 19, 2014
    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
    H
    heinim
    Participant
    June 11, 2014
    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.
    F
    FeedbackCommunityMember
    Inspiring
    April 3, 2014
    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.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices