"Locking" Edits

Status
Not open for further replies.

Duncanh

DuncanH
Premium Classic Member
Premium Cloud Member
Joined
Jul 27, 2011
Messages
78
Location
Rutland, UK
Lightroom Experience
Intermediate
Lightroom Version
Classic
Is there anyway to "lock" an image once you have finished processing so that you can not inadvertently (read my stupidly) change edits ?
Cheers
 
No, 'fraid not. Often requested, but not yet possible. Some folks will use one of the colour labels to designate "finished".
 
You could also make a Snapshot of the edited image. Then you could always easily get back to it if you inadvertently make further edits.
 
You could also make a Snapshot of the edited image. Then you could always easily get back to it if you inadvertently make further edits.
My images are complete only after they are "Published" using the Publish Service. Each time they are Published. a "publish" entry gets entered into the Develop history log. I can always revert to that point to return to that develop state. I also use a colored label that indicates "Published" and another colored label to indicate "Complete but not Published" Any time I choose to further "develop" one of those images, I create a new virtual copy and work from that. If you have integrated your workflow thoroughly into LR you only need to make one pass through the process.
 
I like the snapshot option and also when exported there's a step for that in history.
Biggest problem I have is that I can rarely open an old photo and not illuminate it in the light of what I've learned since I 'finished' with it. With improvements in LR and PS, there's always ways to improve them. Very sidetracking ...and for me they are perpetual works in progress.
 
Last edited:
Another possible route is to rename the image with a small a small code added to the original filename such as "cf" for "Client Final" or "me" for "Master Edit".
Obviously not fool-proof but it does provide a another visual cue.
The colour labels already suggested are a good solution if they are not being used for some other task.


Tony Jay
 
I like the snapshot option and also when exported there's a step for that in history.
Biggest problem I have is that I can rarely open an old photo and not illuminate it in the light of what I've learned since I 'finished' with it. With improvements in LR and PS, there's always ways to improve them. Very sidetracking ...and for me they are perpetual works in progress.

I am exactly the same. I often carryout some improvement / upgrades to previously "finished" photos. I create snapshots of the way they were and then after improvement. the difference between PV2010 and PV2012 is sometimes quite remarkable, particularly when accompanied with improved technique. I agree that they are perpetual works in progress !
 
Thanks for those ideas, I'll add the suggestions to my work flow. I am surprised by now a lock flag isn't there, probably my fear is making changes when syncing various images. The other thing I thought of was deleting history when finished editing so any mistaken edits afterwards would obvious, are syncing changes written in history and reversible ?
Thanks for your advice.
 
... I am surprised by now a lock flag isn't there, probably my fear is making changes when syncing various images. The other thing I thought of was deleting history when finished editing so any mistaken edits afterwards would obvious, are syncing changes written in history and reversible ?
Thanks for your advice.
There is a link at the top of this webpage that I would encourage you to use to communicate your ideas to Adobe.

If you use the Publish Service instead of creating a Snapshot, an entry is written into the develop history for that image. It works like the snapshot in that selecting the history entry brings the develop state back to that point in history. Presumably a Published image (exported derivative) represents a "final" and a state in history that can be returned to over and over.
 
I'll have a closer look at publishing, thanks.
I've posted to the ideas link.
 
Status
Not open for further replies.
Back
Top