Lightroom Classic: "Edit In" or "Photo Merge" of a photo should result in the new photo having the same collection(s) affinity as the original

  • 1
  • Idea
  • Updated 4 months ago
  • (Edited)
"Edit In" or "Photo Merge" of a photo should result in the new photo having the same collection(s) affinity as the original.

Whether the collection browser panel is set to a particular collection, a collection set or under the catalog browser you've chosen "All Photographs" or other. The affinity of the photo with collections should remain on the duplicated or photo created as a copy for editing in the external program/bridge. Indeed - the generated photo should also appear 'near' the original photo in the filmstrip, assuming no change has been made to the collection or catalog browser panels in the mean time.

I found this feedback discussion (link below), and I decided to create an idea based on this given that I can confirm that this doesn't work sensibly in Lightroom CC 7.1 (CR 10.1) and I occasionally use Photoshop (latest version along with the Lightroom CC) and Noiseless (MacPhun) for 'Edit In' targets... and also using the built in Photo Merge 'HDR' tool as I often use bracketing on my camera with the aim for some photos to merge to an HDR image. So having the edited copy of the original, or the merged photo, not appear next to the original photo is somewhat annoying from a workflow point of view. I find myself having to go back into 'All Photographs' and find it, then assign it to the collection. Note that I found this due to having a collection set with two child collections, one for each of my cameras that I swapped between, and 'edit in'/'photo merge' in the filmstrip would result on the new photo 'disappearing'... because it didn't have a collection assigned to it.

https://feedback.photoshop.com/photoshop_family/topics/lightroom-cc-2015-8-edit-in-photoshop-cc-2017...
Photo of Alan Ogilvie

Alan Ogilvie

  • 5 Posts
  • 0 Reply Likes

Posted 5 months ago

  • 1
Photo of Philippe Coudé du Foresto

Philippe Coudé du Foresto

  • 20 Posts
  • 5 Reply Likes
Unless I misundertsand it, what you're asking for it's exactly how my version of LR (7.1 under Win 7) works.
If I use "Edit in" from a collection, after saving the duplicate image appears just before the original in the collection and is stacked with it. However, it doesn't appear in the other collections the original belongs to (which is what I expect).
If I do the same from the folder, the duplicate doesn't heritate the collection of the original as you describe.
Photo of Alan Ogilvie

Alan Ogilvie

  • 5 Posts
  • 0 Reply Likes
Ah indeed - that works - when you have a collection selected on the collection browser, but not when you have a collection *set* selected. My suggestion here was to make it thoroughly clear that making a duplicate/editing/etc an original photo would make the new instance have exactly the same collection affinity (and therefore in the case of having a collection set selected in the collection browser panel, the new photo instance wouldn't disappear and force you to go to 'all photos' and find it and then assign it to the logical collection).
The reference I made to the other thread demonstrated it probably confused people if they had the collection browser set differently ... certainly it confused me for a while.
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 3383 Posts
  • 854 Reply Likes
To follow through on this: If you have a collection set selected and you edit a photo that's in multiple child collections, the edited photo should be added to each of those collections, right? 
Photo of Alan Ogilvie

Alan Ogilvie

  • 5 Posts
  • 0 Reply Likes
So this is the thing - I'd like some form of consistency... so my view may not be the correct one.

What I *think* needs to happen is that any instance of a photo created from the original should have the same collection affiliation as the original, and it should appear in the filmstrip adjacent to the original. This is assuming I don't change the view from the collection browser panel in the intervening time (I might choose to 'Edit In', create a copy with Lightroom effects applied and then go to Photoshop... meanwhile I might switch back to Lightroom and change the collection visible by fiddling in the collection browser panel... I'd see this as *my fault* if I then go back to Photoshop and finish editing the photo and send back the changes to Lightroom and then can't immediately see the photo because I changed the collection and it didn't include the original photo on the filmstrip.)

As identified above - this affiliation happens in some situations... if I have the collection brower panel set to a collection specifically, and not a collection set, then the duplicate/edit-in copy appears next to the orginal photo... but if I have a collection set selected in the browser panel, then the new photo 'disappears' because it isn't affiliated with any of the collections in the collection set... I then need to go to 'all photographs' to find it and assign it to the correct collection.

For example, on a recent trip I took three cameras (big one, compact and a 360 toy one).

I created a collection that contained each set as I imported. Then I created a collection set for the trip. So in the collection browser panel it looked something like this...

• TRIP NOVEMBER 2017 [collection set]
   - DSLR [collection]
   - COMPACT [collection]
   - 360 [collection]

(I understand I probably could have just put everything in one collection and used metadata to filter the different cameras if I wanted to do something specific - but it's what I did)

So - I want to see all photos in 'TRIP'... from all of my camera import collections. So I click the 'TRIP NOVEMBER 2017' collection set. Now - when I find a photo in the library view, and in the film strip... I right click the photo in film strip and choose 'Edit In' Photoshop... create a copy with Lightroom effects applied, then edit in Photoshop and return to Lightroom... I don't see the photo I just created. This seems to be because the affiliation with the original photos collection has not been applied. Switching to 'All Photographs' in the Catalog browser panel let's me find the photo and then drag it to the collection.

I'd like that the new photo had the same collection affiliation as the original. And then I could skip the step of going to 'All Photographs' and hunting through there.

Does this make sense?
Photo of Philippe Coudé du Foresto

Philippe Coudé du Foresto

  • 20 Posts
  • 5 Reply Likes
I better understand why you need this. However, as John said, if the photo belongs to several collections (which might serve different purposes) a decision would have to be made about which collections the copy has to be affiliated to, not only "affiliates to all the same collection as the original"
This implies a selection box to be displayed each time we want to do a copy. In my opinion, this would complicate the process too much.
However, I see a small workaround to accommodate your need and the way you work. Once your photos are displayed in the collection set, click on on the little collection tag of the photo to go to the collection it belongs to. From there you can use the Edit in and the copy will be in the same collection, next to the original. (If you don't have the collection tag displayed, use can do a right-click instead and select "Go to collection" in the contextual menu).
(Edited)
Photo of Alan Ogilvie

Alan Ogilvie

  • 5 Posts
  • 0 Reply Likes
What this simplifies to is: whatever the collection affinity the original photo had should be applied to the copy (whatever the selection in the 'collection browser'). Having the copy not have any collection affinity, because I happened to have the collection browser on a collection set, and ending up having to visit the 'all photos' collection to find it again is a bad experience.