• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • Dark mode now has a single preference for the whole site! It's a simple toggle switch in the bottom right-hand corner of any page. As it uses a cookie to store your preference, you may need to dismiss the cookie banner before you can see it. Any problems, please let us know!

Setting a Photo to READ ONLY

Status
Not open for further replies.

Paul_DS256

Senior Member
Premium Classic Member
Joined
Mar 29, 2015
Messages
1,200
Lightroom Experience
Intermediate
Lightroom Version
Classic
Lightroom Version Number
LR Classic 9.1
Operating System
  1. Windows 10
I know sounds strange but here is the situation. I use TOPAZ tools for sharpening and denoising as needed. The plug-in works great because the resulting TIFF file is stacked with the original RAW file but is displayed unstacked.

More than once, I've gone back to do further editting on the photo and mistakenly made changes to the TIFF rather than continuing on the RAW file. What I would like to do is flag the TIFF file as read only to prevent this from happening. Yes, I know user error.

One approach is to show the TIFF in File Explorer and change the properties to R/O. I could then likely use Locktastic plug-in to show the file labelled red.

I hope I'm not the first person to try and solve this. Looking for other ideas as well.

Thanks
 
1) Call me confused. Once you denoise and sharpen in topaz and get the Tiff back, why would you then go back to the unsharpened. noisy original RAW file for further edits? Wouldn't you want to do your further edits on the denoised and sharpened Tiff image?

2) not familiar with "Lockstastic' but if it's your purpose in using it is to turn on the RED color label, instead just select the image and press the "6" key on your keyboard.

3) LR is non destructive so your original RAW or Tiff returned from Topaz are not modified by LR. Your edits to these files are just entries in the catalog and do not actually change the data in the image file. Therefore if you discover the you edited a "wrong" file, just go to the history panel in the Develop module and click down the list list of entries till you get to the entry before you started mistakenly editing. Or, if you'd like to revert to the "as imported" version just use the "Reset" button.

4) I wojld be reluctant to change the properties in the file system to R/O. First because it is time consuming and second because LR doesn't write changes to the image files anyway (other than some metadata).
 
Locktastic is a very simple plugin of mine - here.
 
Call me confused. Once you denoise and sharpen in topaz and get the Tiff back, why would you then go back to the unsharpened. noisy original RAW file for further edits? Wouldn't you want to do your further edits on the denoised and sharpened Tiff image?
That is exactly his problem. He doesn’t want to do that, but it sometimes happens by mistake.
 
why would you then go back to the unsharpened. noisy original RAW file
I hadn't thought of that Califdan. I'd always assumed the RAW and it's changes were the preferred way. I was treating the TIF as a derivative image. You've given me something to think about
I wojld be reluctant to change the properties in the file system to R/O
Ya, after I came to same decision
 
That is exactly his problem. He doesn’t want to do that, but it sometimes happens by mistake.
"Stupid user tricks". I do them all the time. Still apart from the annoyance, the first derivative TIFF remains unchanged. The TIFF is also lossless, so a second derivative would only be a modification of the first.
 
Last edited:
Thanks all. I'd never thought about the lineage from RAW to TIFF to TIFF etc. Getting my head around that. More of a personal issue than making sense.
 
And perhaps make a VC (Virtual Copy) for all the new TIFF's you would want to mess around with...
 
I know sounds strange...I hope I'm not the first person to try and solve this. Looking for other ideas as well.
It’s not strange, because you’re not the first person to ask for something like this. Over on the official Lightroom Feedback site, where Adobe accepts feature requests, and users vote and discuss them, others have submitted similar ideas:

Ability to lock photos. Please protect me from myself!
Posted 9 years ago, 116 votes

Mark a photo as the FINAL version
Posted 3 years ago, 296 votes

Obviously there is user support for these requests, based on the number of votes. It’s not clear how or when locking images will bubble up to be a higher priority for Adobe to implement versus other potential new features that they have to consider.
 
It’s not strange, because you’re not the first person to ask for something like this
Thanks for confirming my sanity Conrad ;-) albeit that mine may not have been in the right context.
 
Status
Not open for further replies.
Back
Top