Skip to main content
Inspiring
November 8, 2021

P: Render Smart Previews from LrC edited w custom profiles correctly in all Lr Photos cloud clients

  • November 8, 2021
  • 22 replies
  • 1932 views

Raw images with a custom camera profile not look correct when synced from Lightroom Classic to the cloud.  This is r-e-a-l-l-y inconvenient for updating my Adobe Portfolio.  The images look lousy in lightroom.adobe.com, LIghtroom Mobile (Android and iPadOS).  The workaround is to export as jpg, and then reimport into LrC and sync the jpg to the cloud - but that is unmanageable for more than just a few images.

 

This topic has been closed for replies.

22 replies

Rikk Flohr_Photography
Community Manager
November 10, 2021

on iPad

From Lightroom iPad - 

Tap Share -

Edit in Photoshop

or

From Photoshop Desktop

Home Screen

Click Lightroom photos

Rikk Flohr: Adobe Photography Org
Inspiring
November 10, 2021

I installed Ps for iPad, but I think I"ll need some help driving.  "You can open a photo via Lr Photos there as well" 

Rikk Flohr_Photography
Community Manager
November 10, 2021

It would save me setting up a file to test but not necessary. Just something I was wondering.  It feels like that would fail similarly.

Rikk Flohr: Adobe Photography Org
Inspiring
November 10, 2021

I use Ps on Windows extensively, but have not yet installed it on my iPad.  I can, if it's of use to you.

Rikk Flohr_Photography
Community Manager
November 10, 2021

I am curiuos, if you have the iPad Photoshop App installed. You can open a photo via Lr Photos there as well. I wonder if PS is rendering the file right...

Rikk Flohr: Adobe Photography Org
Inspiring
November 10, 2021

An inoccuous preset is a great idea.  BTW, and you probably know or guessed this, if I go back to LrC and backout the change or make a real change to the image, then the synced image no longer looks correct in the cloud.  So change definitely has to be made in LrD.  I think color-tagging could help me/others remember to do the special sync-edit on images edited down the road.  You rock.

Rikk Flohr_Photography
Community Manager
November 10, 2021

Great news. I will list that as the primary workaround on the thread. 

The plan is to explore a permanant scalable fix.

 

One thing to consider is if you have a setting you almost never use (e.g.Texture or some other), you could build a preset to do the heavy lifting for you to apply the preset of +1 on a slider) It would have almost no visual impact but would force a rerender of the item in the cloud.  You could select a group in Grid and apply it to many. Still a kludge but saves some work. 

Rikk Flohr: Adobe Photography Org
Inspiring
November 10, 2021

This does look correct on all platforms.  It's an easier workaround than mine to be sure, don't have to keep up with extra jpgs just for portfolio, but it still doesn't scale well.  I can probably live with it, but I'll certainly overlook diddling images that get later-on edits until I notice them looking poorly in Portfolio.  But it's better than exporting and re-importing a "temporary" jpg.  Maybe I'll tag them with a color so I can 'notice' that subsequent edits in LrC will need to be diddled.  Is this a big issue to eventually fix?

 

Thank you for your help, Rikk, it's really appreciated.  Can I get some love on my other issue, which really botches my portfolio updates?
https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/synced-collections-missing-images-after-upgrade/m-p/12504137#M3812

Rikk Flohr_Photography
Community Manager
November 10, 2021

Thank you.  This boils down to a design limitation of the Smart Preview workflow and would be a feature request in our world, Hence, the title change and the post type change. 

 

One more workaround idea.

 

  1. Identify a file in LrClassic that is synced but shows the wrong preview.
  2. Allow to sync.
  3. Open the Synced Smart Preview in LrDesktop and perform a small edit. 
  4. Go to the next image to commit the sync of the image in step 3
  5. View this in Lr Web Galleries, Portfolio and Spark

 

Results?

Rikk Flohr: Adobe Photography Org
Inspiring
November 10, 2021

The exported-then-added-back image looks correct on all platforms.  

- The original image also happens to be a DNG (it's a HDR merge), but the behavior has been with DNG, TIF, CR3 files

- This idea is very similar to the workaround I have implemented (export as jpg and bring back in just for eventual inclusion in Portfolio), but it doesn't scale up very well when many images are involved.

- I'm surprised this is considered an "idea" rather than a bug.  Tomato tomahtoh LOL.  I appreciate the help!