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
  • 2508 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

    Pattie F
    Pattie F
    Participating Frequently
    May 6, 2013
    Philip

    You are correct that the previews are uploaded first and then the original file. This allows you to look at the thumbnails in Revel sooner. You should not run into a situation where you get the thumbnail and not the original.

    Pattie
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    May 6, 2011
    FWIW, I created a proposal regarding a particular form of an essential history that also supports "undo" at any place in the edit history.
    john beardsworth
    Community Expert
    john beardsworthCommunity Expert
    Community Expert
    April 12, 2011
    "That's not fair either. Just because I don't want a change doesn't mean that I shouldn't get to influence how that change ends up looking like if Adobe does in fact decide to make the change. "

    "Don't want" ranges from a neutral "do not care" to definitely disliking an idea. In either case, less time for things that you do want. That's why I asked for a "do not like" button.
    areohbee
    areohbee
    Legend
    April 12, 2011
    Voting comment/question copies to getting started / faq as suggested - thanks. - R

    Personally, I hate being shoved into too small a box. I'd even go for:

    Enter your ranking:
    0-10, where 0 means "bad idea" and 10 means one of the best ideas.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 12, 2011
    Rob, I think you should probably raise that question in the Getting Started & FAQ thread.

    I think your list is too fine-grained;
    -1 (detractor),
    1 (mild support),
    2 (top support)
    would be sufficient, AFAIC.

    Perhaps voters that choose "-1" (and perhaps "2") should be required to leave a comment to justify their choice. Staff could then include or exclude such votes from the (internal) tally depending on the merit of the comment.

    I'd be against allowing "-1" without a required comment because there is a chance that people will unduly dismiss ideas just because they want to help other ideas by voting down ideas that don't seem to have any value for them.
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    April 12, 2011
    I fully agree with Dan's reply.
    areohbee
    areohbee
    Legend
    April 11, 2011
    Perhaps a better scheme than a no-vote/pro-vote would be a priority ranking. I'm often in a quandry - do I vote for something that I think is a good idea, but isn't one of my top priorities? - Some have said "absolutely not" - since it dilutes the priorities. Others have said "yes, of course" - a good idea is a good idea...

    If one was able to vote:
    0 - this would be a step backwards... - I wouldn't want this, period.
    1 - If everything else were already done, then this good too...
    2 - good idea but not high priority
    3 - good idea but not top priority
    4 - top priority.

    Would it be better?
    Sean Phillips
    Sean Phillips
    Known Participant
    April 11, 2011
    (Having said that, I actually am one of the 3 that Liked this idea. But it's taken on a whole new life in the conversation since the FR was posted...)
    Sean Phillips
    Sean Phillips
    Known Participant
    April 11, 2011
    "Folk who don't like the idea don't get to vote."

    That's not fair either. Just because I don't want a change doesn't mean that I shouldn't get to influence how that change ends up looking like if Adobe does in fact decide to make the change.
    Ian Lyons
    Community Expert
    Ian LyonsCommunity Expert
    Community Expert
    April 11, 2011
    Dan,

    My post was not intended to be condescending, but if that's how it reads then my apologies to Victoria and anyone else who was offended.

    re the thread as a whole:

    Statistical data on top right says 56 replies, 10 participants and 3 people like the idea. Folk who don't like the idea don't get to vote.
    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