Lightroom Classic: Sync issue for flags with CC

  • 1
  • Question
  • Updated 9 months ago
  • (Edited)
I've been working back through some travel pictures from several years ago. At the time, I took a bunch of sets of bracketed exposure shots with the intent of doing some HDR work, then got busy and the project was put aside until tonight. 

Because HDR merge is not available in CC, I went back over to Classic. Working from the folder with the images (not a collection), I identified the sets I wanted to work on, merged them using the "Merge to HDR Pro in Photoshop" option (which I prefer to LR's own functionality), and saved the finished projects.  I then flagged most of the individual frames used in the process as rejects (with the intention to delete them to free up cloud space). I also used the "positive" flag to mark the HDR frames, knowing that keyword changes won't sync.

But it turns out that, as far as I can tell, the new images won't sync. 

I've synced the folder several times, and the reject flags on the originals did make it to the cloud, but the new images in the folder have not. 

Any thoughts?
Photo of Mike Dunford

Mike Dunford

  • 31 Posts
  • 9 Reply Likes

Posted 9 months ago

  • 1
Photo of Alec Dann

Alec Dann

  • 6 Posts
  • 0 Reply Likes
I had the same issue but an even simpler use case.  I upgraded to Lightroom Classic and Photoshop CC 19.0 over the weekend.   On Monday, I had worked an image in LR and decided to test syncing between LR and PS when the image is opened from LR as a Smart Object in PS (Edit-->Edit in-->Open as a Smart Object in Photoshop). 

My goal was to see how changes made in Adobe Camera Raw which would be written to the XMP file (my LR is set to automatically write to XMP) would be picked up in LR.

After the image opened I double-clicked the Background layer and opened it in ACR.  I made a big change to Exposure and Contrast (to make the change evident), then saved the changes in ACR and saved and closed the file in Photoshop.

When I switched back to LR, I could see the new TIFF file created in PS (my Edit-in preferences are set to TIFF), but the changes I made in ACR didnt show up.

Here's the weird thing...while writing this, I tested it again and the sync worked.  

I dunno.
Photo of Rick Spaulding

Rick Spaulding, Champion

  • 564 Posts
  • 221 Reply Likes
Hey Mike,

I think I understand what you're doing but I wasn't able to make it happen. Can you make it happen again and if so can you list the steps necessary to reproduce it?

Cheers,

Rick
Photo of Mike Dunford

Mike Dunford

  • 31 Posts
  • 9 Reply Likes
To be clear, Rick:

Current workflow:

1: In Classic, identify images for HDR Merge.
2: Select images, select "Merge to HDR Pro in Photoshop" command.
3: In Photoshop, fine-tune HDR.
4: In Photoshop, save image using CMD-S. 
5: Image then saves to Classic. 

Saved image, even in folder where metadata changes are syncing, does not sync to cloud. Must instead be dragged or otherwise placed in a synced collection/album* 

To this, I can now add: 

Once saved to a collection/folder, they not only sync, but start showing up under the date in CC, and metadata changes made in the original "by date" folder in Lightroom (e.g. toggling the flag) sync as normal.

Best,
Mike

*PS. The different names for collections/albums/folders in CC and Classic strikes me as kinda sorta inconvenient.
(Edited)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4125 Posts
  • 1471 Reply Likes
Are we talking sync to the cloud (since you mentioned CC), or the synchronize folder command to import additional photos into the catalog? If sync to the cloud, have you added the new photos to a synced collection or All Synced Photos collection in the Catalog panel?
Photo of Mike Dunford

Mike Dunford

  • 31 Posts
  • 9 Reply Likes
The photos saved to the by-date folder for the day the source images were created (which was appropriate). I used the synchronize folder command for that folder. (To be clear: it's the by-date folder in the original catalog, which was migrated to CC when I updated to the new Classic and installed the new CC. 

I considered the possibility that I would have to move the new files to a new collection to get them over. I first attempted to create a new folder in CC. The (empty) folder synced and shows up in my Classic library as a collection. I attempted to add the new files to that folder, but could not. I then attempted to add them to an old collection, but they can't be dragged. They won't move.
Photo of Mike Dunford

Mike Dunford

  • 31 Posts
  • 9 Reply Likes
OF course, they MIGHT have moved if I was grabbing photos and not frames, but that would have been very easy and required me to not be a moron.
Photo of Alec Dann

Alec Dann

  • 6 Posts
  • 0 Reply Likes
I use LR Classic.  I don't know about Mike (original poster).  As I mentioned in my reply, I havent been able to replicate the issue.  I thought it might have something to do with the fact that I had not updated the Process version in Lightroom but when opening in ACR, I was automatically in the current version there.  Still sync should handle version conflicts (offer to update, etc).
Photo of Mike Dunford

Mike Dunford

  • 31 Posts
  • 9 Reply Likes
Re-attempted. This time I made sure I was working from the massive collection created when the catalog was migrated rather than from within the original folder. When the new image was saved in Photoshop, however, it did not save to the massive collection; it just saved to the original folder. 


 It looks like the situation is this:

1: HDR-merge images save from Photoshop back to the original folder in Lightroom. This applies regardless of whether the images are selected for HDR Merge from within the original folder or from within the massive collection created when the Lightroom catalog was migrated to CC. 

2: Metadata changes (except keywords) to files which were in this location when the catalog was migrated sync back to the cloud without difficulties. However, new images in this location apparently do not get added when the folder syncs. (Q: is the sync not looking for new images in Classic because such a workflow violates presumptions?) 

3: The new files can be added to the cloud either by manually dragging them to a synced collection or by creating a new synced collection. (Which are folders in CC but still collections in Classic because reasons.) 


This is a spectacularly inconvenient workflow. 

I have to run some errands. When I get back, I'll go ahead and try selecting a set of images for HDR work in CC, putting them in a folder in CC, and working from that folder in Classic. 

But regardless of whether that works or not, there has to be a better solution. Or is CC simply not designed for any photographer, even relatively unsophisticated ones like me, who wants to merge to HDR or panorama? 

EDIT: Whenever I said "folder" in reference to CC, I meant "album."
(Edited)
Photo of Mike Dunford

Mike Dunford

  • 31 Posts
  • 9 Reply Likes
Further effort/experimentation:

1: Created "HDR" Folder in CC's Album. 
2: Created "HDR Fodder" album in "HDR" Folder in CC.
3: Added 7-exposure set of photos to "HDR Fodder" folder. 
4: Folder and album both sync to Classic, with contents.
5: In Classic, select 7 photos.
6: In Classic, select "Merge to HDR Pro in Photoshop"
7: In Photoshop, fine-tune and run HDR merge.
8: In Photoshop, save resulting .TIF 

At this point, the new image appears in the HDR Fodder folder in Classic and will sync (in that folder) to CC, and will also immediately show up in the proper "by date" under "My Photos."

So it looks like I've found a workaround of sorts - photos need to be identified and moved into an album in CC before going to Classic to do the merge, or finish products can be moved into a synced collection in Classic after creation. But, even though the "by date" organization in Classic acts like a shared folder for the purposes of things like metadata updates, etc, working directly from this folder for merges will not result in new files syncing - even if you are working within the synced collection created during migration.

Not optimal, but I guess I'll have to make it work for now.