Skip to main content
Adobe Photoshop Family
marcel_smits_7209713's profile

9 Messages

 • 

240 Points

Fri, Jun 21, 2019 11:23 AM

Closed

Not a problem

Lightroom Classic: Smart Collection with "Has adjustments" set to false go to Develop losses the image

If you have a smart collection with:

"Has adjustments" = "false" 
"Rating" => 1 star or "Picked" = "flagged"

Then you have all the images selected by culling but don't have any adjustments yet.
When I select one of those images and go to develop and make an adjustment it drops out of the smart collection as expected. But also the develop window losses the image before it is finished.

And yes i can add the images to a non smart collection first but it can't be right that Develop losses the image because it drops from a smart collection.....

This conversation has been merged. Please refer the main conversation:

Lightroom: Lock lib-filtered and smart-collected contents temporarily so photos don't disappear...

Responses

Champion

 • 

3.4K Messages

 • 

58.9K Points

2 years ago

Of course that is right. You have selected an image in a smart collection. If you change the image so it no longer fits the criteria of that smart collection, then the image disappears from it. And so it disappears from any view, regardless of what view that is. It may be annoying, and you may wish it would be different, but it is completely correct.

Johan W. Elzenga,

http://www.johanfoto.com

9 Messages

 • 

240 Points

That is your opinion, in the library it's expected. But when i'm in Develop with an image it has to stay open regardless of the way i opened it.

Champion

 • 

3.4K Messages

 • 

58.9K Points

No, that is not my opinion, that is how Lightroom works. The Develop module cannot display an image that is not present in the currently selected collection. If the image disappears from the current collection for whatever reason, it will disappear from the Develop module (or any other module you may be in). This has nothing to do with “how you opened it”, this is because an image needs to be selected to be displayed, and it cannot be selected if it is not in the current collection.

I agree that this can be annoying, and there are other situations where you see the same problem (try adding two keywords by using the ’Recent Keywords’ panel while you are in a ‘No Keywords’ smart collection), but that is the way it is.

Johan W. Elzenga,

http://www.johanfoto.com

522 Messages

 • 

12.6K Points

I agree with Johan.  It's a fundamental aspect of how LR works.  For an image to be seen in any module it must visible on the film strip, and the film strip only contains images in selected source(s) and that also satisfy any filters.  In your case the source is the smart collection.  

Here's a workaround.
1) Add a keyword called 'KeepInXYZcollection'
2) Add a rule to your smart collection that is Or'd with your other two:   "keyword",  Contains", "KeepinXYZcollection"
3) Images with the Keyword will stay visible in modules as long as they have that keyword (regardless of other 2 rules in smart collection)

Here's 2nd work around
1) Go to your smart collection as normal
2) copy images to Quick Collection
     2a)  <ctrl>+<shift>+b to clear quick collection  (on macs sub "cmd" instead of "ctrl")
     2b)  <ctrl>+a to select all images in smart collection
     2c)  click letter "b" on keyboard to add all images to quick collection
     2d) <ctrl>+b to change source to quick collection
3) Go to Develop module
4) Image will stay in develop module while you work on it.  
When done with that image click letter "b" to remove it from Quick Collection if desired which will remove it from film strip and it will disappear from develop module.

Champion

 • 

3.4K Messages

 • 

58.9K Points

Another work around (very similar to the first one Dan mentions) is to reserve a star rating (one star, for example) for the unedited images and add this as an ‘or’ criterium to the smart collection. Then just before you start editing you press the keyboard shortcut (1) for the rating. That will keep the image in the smart collection while it is being edited. When you are finished you press the shortcut for the original rating, or you press zero to remove the rating.

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

3.4K Messages

 • 

58.9K Points

Ah, I see you already use one star as rating. You can also use a color label in the same way, for example the blue label. Press '9' to add a blue label so the image stays in the smart collection (because you added 'or label = blue' to it), when finished editing press '9' again to remove it.

Johan W. Elzenga,

http://www.johanfoto.com

108 Messages

 • 

2.7K Points

I agree with the original complaint. This behaviour needs changing. When we select a file and start the Develop module, that file should remain in the Develop module until we exit Develop. The human should be allowed to continue to develop the image that they selected to develop, not have it disappear because they started to develop it. Sorry to wake your programmers up, but this rule is silly.

Champion

 • 

3.4K Messages

 • 

58.9K Points

I think we have to separate two things here. 1: How a smart collection works and 2: what you would like as an exception to how they work. The original post was to report a problem. We explained that it's not a problem, because it works just the way it is expected to work.

Of course you could file a feature request that smart collections would work differently. For example that an image in a smart collection that is selected, will never disappear from that smart collection for as long as it is still selected. That is how smart albums in Aperture worked, and I agree that would be a nice solution. That would not only keep the image in the develop module in this example, it would also solve the 'no keywords' smart collection example I mentioned. I you write up such a feature request, I will vote for it.

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

3.4K Messages

 • 

58.9K Points

In fact, this has been requested already a long time ago. Strangely enough it was marked as 'implemented', which is definitely not true, so I undid that. So go here and add your vote: https://feedback.photoshop.com/photoshop_family/topics/lightroom_lock_lib_filtered_and_smart_collect...

Johan W. Elzenga,

http://www.johanfoto.com