Skip to main content
F
FeedbackCommunityMember
Inspiring
April 7, 2011
Open for Voting

P: Prevent loss of Edit Histories when Reimporting Photos

  • April 7, 2011
  • 66 replies
  • 2513 views

When importing DNGs with stored edits (included XMP data) then the history of the photo just shows "Imported..." instead of the list of edits.

I have a corrupt catalogue. (I did nothing to cause the correction :()
The catalogue contains photos which are not associated to folders in the library module. When I choose "Got to folder in Library module" from the context menu for such photos, nothing happens. I imported them just like any other photos, but somehow the corresponding library folder wasn't created or lost.

I tried synchroning the parent folder but the missing subfolders are not created again.

That's why I decided the only way forward is to create a new catalogue. However, the new catalogue doesn't have any of the edit history. The rendering is OK and I can reset it to see the original version of the photos but I cannot see the edit history anymore.

Why is the edit history not recreated? The essence of it must be available because otherwise the correct final rendering could not be created.

I believe edit histories should be available for JPGs, RAW and DNG files. When I decided to use DNG files vs RAW files with sidecar (XMP) files, I didn't know that I'd lose the history with a fresh import of a DNG file. I suppose that if I had XMP files, I could copy these and still had my edit histories.

    66 replies

    Show previous replies
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 7, 2011
    Yes, it does. Thanks Chad! It doesn't really read like a feature request, though. If it is clear what I'm after then that's OK with me. I'd be happy to rephrase the original bug report as a feature request, if this would be useful.
    Chad Baker
    Adobe Employee
    Chad Baker
    Adobe Employee
    April 7, 2011
    It should be showing as an "idea" now.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 7, 2011
    Question (to the staff): Should I post this as a feature request? It seems it is not really a bug because the loss of the edit histories is "as designed". But it seems that there might be cases when saving editing histories in or with photo files would be desirable.

    It seems that I cannot convert this bug report into a feature request anymore, so should I create a new one?
    Chad Baker
    Adobe Employee
    Chad Baker
    Adobe Employee
    April 7, 2011
    Thanks for the update. Glad to hear things are working again!
    areohbee
    areohbee
    Legend
    April 7, 2011
    That is good news!

    One time, simply optimizing my catalog improved performance by A LOT, meaning it went from buggy slow to normal.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 7, 2011
    Good news:
    I discovered that the corrupted catalogue had only one corrupt entry. It was an image whose "root folder" was "nil".

    I exported all photos in the corrupted catalogue -- except for the one problematic one -- to a new catalogue and, surprise, surprise -- the new one shows all the missing subfolders again!

    So LR stumbled across one corrupt database row, causing it to drop a number of library folders from the display. I also noticed that LR became very slow with the corrupted catalogue in some operations (displaying "All Photographs").

    Maybe (wild speculation) corrupted catalogues can sometimes be the source of some "performance" problems?
    areohbee
    areohbee
    Legend
    April 7, 2011
    OK. The Lr database is simple and straight-forward in some respects, and a bit complicated and intimidating in other respects. Some things may be readily transferable, other things - not so much...
    areohbee
    areohbee
    Legend
    April 7, 2011
    I dont know what all the integrity check does, but I now know one thing it does not do. Do you know any SQL, TK?
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 7, 2011
    Rob, thanks a lot for the offer! I'll see what I can do myself first. I hope I won't have to bother you with this.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 7, 2011
    "One idea is to create a new catalogue, and then use File > Import as Catalog to import the corrupt catalogue.": Thanks a lot for this suggestion. I thought about doing that but wasn't sure what end result to expect from it. I'll try it. Thanks again.

    The only other place I reported about the corruption is when I suggest that a folder synchronise should bring back / restore missing subfolders.

    I agree that having options regarding what is saved in XMP files / DNG metadata would be desirable.
    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