Lightroom Classic: Lens Corrections defaults not correct if Previews are "Embedded & Sidecar"

  • 3
  • Problem
  • Updated 3 weeks ago
  • Acknowledged
  • (Edited)
I'm testing with a Canon RAW files from a EOS 7D with EF 70-200 L IS USM lens.

I have set the Develop Default Setting for this camera to enable "Remove Chromatic Aberration" and "Enable Lens Corrections".

1) When I import the files and have Build Previews set to "Minimal" the 2 check boxes ("Remove Chromatic Aberration" and "Enable Lens Corrections") are checked and the correct Make, Model and Profile are found.

2) When I import the files and have Build Previews set to "Embedded & Sidecar" the 2 check boxes are checked BUT Make, Model and Profile are "None". HOWEVER if I click on the photo, go to the Develop module, click on a different photo in the filmstrip then click on the original photo the correct Make, Model and Profile are displayed most of the time.

I also noticed if I click Auto tone or if I adjust a slider and then hit Command-Z then the correct Make, Model and Profile are displayed.
Photo of NicholasG

NicholasG

  • 10 Posts
  • 2 Reply Likes

Posted 2 months ago

  • 3
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1533 Posts
  • 618 Reply Likes
I assume that's because 'Embedded & Sidecar' means that the preview you are looking at is the embedded preview that the camera added to the raw file. Lightroom's lens corrections are obviously not applied to that preview. Only when Lightroom has created its own preview, the lens corrections are applied and visible.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1533 Posts
  • 618 Reply Likes
Yes, I always import with 'Embedded & Sidecar' to speed up import. After the images have been imported I let Lightroom generate its own previews. Lens corrections and chromatic aberration are then applied automatically and correctly.

I have to admit that this could be because I also apply a develop preset on import.
(Edited)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
"I have to admit that this could be because I also apply a develop preset on import."
That's not the same type of Import we are discussing here. If you apply a 'Develop Preset' in the Import module LR will automatically build standard previews. This also negates the speed benefit of using 'Embedded & Side car' previews and will prevent you from seeing the issue discussed here.
To duplicate this issue you will need to:
1) Change your 'Default Develop settings with 'Enable Profile Corrections' checked.

2) Import with NO Develop Setting selected in the Import module and 'Embedded & Sidecar' Preview selection.
Once the import has completed confirm you can see the double-arrow icon on the filmstrip in the upper left-hand corner of the thumbnail. Then switch to the Develop module without applying any settings and view the Lens profile panel. What do you see?
(Edited)
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1533 Posts
  • 618 Reply Likes
No, Lightroom will not automatically build standard previews. It will only do that when I tell it to. The images come in with Embedded previews, and this stays that way until I click on the double-arrow icon in the upper left corner to tell it to build standard-sized previews. Or they will be built when Lightroom is idle (if you set that in the preferences). Maybe I won't see the issue you are discussing, but please don't think you can tell me how my own workflow works.
(Edited)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
I never apply Develop presets on Import, but just tried it. Using 'Embedded & Sidecar' preview setting and a Develop preset that applies 'Lens Profile' and 'Chromatic Aberration' settings the Embedded preview is retained as you stated. My apology! However, I still see the issue being discussed her. When I switch to the Develop module 'Lens Profile' shows as 'None' and message 'Unable to load lens profile' (see screenshot below).

Please try the test as I outlined in my last reply and see if you can replicate the issue. Thank you!
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1533 Posts
  • 618 Reply Likes
I’m sure you see what you see. I don’t doubt that. As I’m typing this on my iPad, I cannot verify your findings. All I can say is that in my workflow I do not have any problems of lens corrections not being applied, probably because the preset forces Lightroom to update its rendering (it also applies auto tone). I never get into the situation where I have switched to the develop module and then still see the embedded preview. When I switch to the develop module, I see a Lightroom rendered preview (with correctly applied lens corrections).
(Edited)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
I can confirm what you are seeing using LR 7.5 on Windows 7 with Canon 5D MKII and 6D cameras with 17-40mm F4L and 16-35mm F4L IS lenses. With 'Embedded & Sidecar' Import Preview setting the Lens Corrections panel appears as below and has the error message 'Unable to load lens profile.' Interestingly when I switch back to the Library module the image displays with the Lens Profile and other 'Default Develop Settings' applied and is no longer using the Embedded Preview. This is without applying ANY setting in the Develop module.

So it appears there are two issues. It's my understanding that when using Embedded & Sidecar Import Preview setting the Library Preview will not be updated until Develop module settings have been applied. Merely viewing the image in the Develop module without applying any adjustment settings should not cause LR to discard the Embeded & Sidecar Preview and rebuild a new preview.

The only way I am able to "repeatably" get the Lens Profile to be applied in the Develop module is to click on the Reset button (applies my default settings) or Sync the Lens Profile setting across images.


Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1533 Posts
  • 618 Reply Likes
“Merely viewing the image in the Develop module without applying any adjustment settings should not cause LR to discard the Embeded & Sidecar Preview and rebuild a new preview.”

Actually, it’s a bit more complicated. The develop module uses its own previews, which are not the same as the previews in the Library and other modules. So switching to the develop module should always cause Lightroom to show you a new preview. The Develop module should never show the embedded preview. However that new Develop preview does not replace the (embedded) one of the Library module either. The Library preview is only re-rendered when you have applied edits, and I think that simply switching to the develop module is already seen as such (perhaps to avoid confusion).
(Edited)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
"The Develop module should never show the embedded preview."

It's not showing the embedded preview in the Develop module. Just to be clear it correctly shows the Develop preview, but without the Lens Profile applied.

"However that new Develop preview does not replace the (embedded) one of the Library module either."

When switching back to the Library module with NO settings applied in the Develop module the Library module creates a standard preview with the 'Default Develop Settings' applied and the 'Embedded Preview' is removed.

"The Library preview is only re-rendered when you have applied edits"

In previous versions of LR (prior to 7.5) the Embedded Preview would remain in the Library module until an actual Develop setting adjustment was applied to the image.

"and I think that simply switching to the develop module is already seen as such (perhaps to avoid confusion)."

This is actually not the issue of concern here and if Adobe changed this behavior it is just an undocumented change. I'll take it either way!

Just to be clear the real issue is that when using 'Embedded & Sidecar' the LR 'Default Develop Settings' for Lens Profile are not being respected when 'Enable Profile Corrections' is a part of those settings. In fact an error condition is created, "Unable to load lens profile."

Photo of NicholasG

NicholasG

  • 10 Posts
  • 2 Reply Likes
Todd,

So you agree this looks like a bug? I'm new here, do I need to do anything so Adobe is make aware of this?

Thanks,
Nicholas
Photo of Todd Shaner

Todd Shaner, Champion

  • 1092 Posts
  • 352 Reply Likes
Nicholas, I do agree it is a bug and this is the correct place to report it. I've added my 'Me To' which is the best way to get Adobe's attention.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3853 Posts
  • 1011 Reply Likes
After poking around at this for quite a bit with Todd, looking at Lens Profile field values via the plugin SDK, I think this bug is related to two other long-standing bugs:

- When you sync Lens Profile Corrections with a batch of photos, the SDK returns invalid values for the Lens Profile Name until you force the previews to be re-rendered by scrolling or rebuilding previews.  
https://feedback.photoshop.com/photoshop_family/topics/lightroom-sdk-photo-getdevelopsettings-return...

- When you apply Auto to a batch of photos, subsequent changes to Develop settings can be lost unless you first cause the previews to be re-rendered by scrolling or rebuilding previews.
https://feedback.photoshop.com/photoshop_family/topics/applying-auto-tone-to-a-batch-of-photos-loses...

It appears that LR has an internal architecture where for some batch operations like Auto and assigning lens profiles, it marks the photos with an annotation that the operation should be computed "when needed" in the future, but doesn't actually do the computation. This allows the batch operation to complete quickly. But other parts of LR forget to check for that "when needed" annotation and get confused.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
"Until recently, Lightroom would first generate all the standard previews, and then as the last step they would appear in the collection. That made import very slow, and 'Embedded & Sidecar' made it much faster. Now the sequence seems to have changed."

I remember the same behavior when first using Embedded & Sidecar Preview workflow with LR Classic 7.0 back in October 2017. I didn't run any tests to compare it against Standard Import Previews because it was clearly much faster. It would still be useful if you have to review a shoot at 1:1 Zoom view before editing since building 1:1 Import Previews will take much longer. Begs the question as to what changed and is it a bug?
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1532 Posts
  • 618 Reply Likes
It seems to me that importing with standard previews is now much faster than it used to be, so if that is a bug, then I would like to see a lot more bugs like that! :)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
"It seems to me that importing with standard previews is now much faster than it used to be"

Agreed. It used to take ~2.0 sec to build a Standard Preview with my Canon 5D MKII 21 Megapixel raw files. Using LR 7.5 it takes <0.7 sec. with the same 2560 px Medium Preview settings. If Adobe did something to speed-up Standard Preview building that slows down Embedded & Sidecar I'd call that a bug. I didn't run a benchmark previously using Embedded & Sidecar Previews so it's hard to say for sure something has changed, but It seems slower. If it's not much faster than using Standard Import Previews the only benefit is if you need to do extensive 1:1 Zoom review before editing. I don't think that was Adobe's intention so it looks like a bug may have been introduced.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3853 Posts
  • 1011 Reply Likes
Todd, when you timed import with various settings, did you purge the ACR cache (Preferences > Performance Purge Cache) before each run?  I'm doing some timing and observed that standard previews build about as fast as embedded previews when you re-import the photos but go about twice as slow on an empty cache (I think I remember a comment by Chris Cox or Simon Chen a long time ago to this effect).
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
No I did not. I just tried importing 25 Canon PowerShot G9 X MKII 20 Megapixel raw files from a new shooting session. These have never been imported into LR and the time with Build Standard Previews was 1.2 sec. with 'Generate Previews in Parallel' (same as before). The 5D MKII raw files are 21 Megapixel so only 5% larger. You are correct that the Camera Raw cache building increases the import time (~.7 sec. and 1.2 sec.). But it's ~40% faster than the previous import time of 2.0 sec. so a definite improvement.
Photo of NicholasG

NicholasG

  • 10 Posts
  • 2 Reply Likes
I have tested with a single Canon 5D4 RAW file and get the same results, even when Previews is set to Minimal.

Import RAW file. Switch to Develop module get "Unable to load lens profile." error. Switch to Library and navigate to a different folder. Go back to original file and switch to Develop, lens profile information is now filled in and the error is gone.
(Edited)
Photo of dmeephd

dmeephd

  • 211 Posts
  • 49 Reply Likes
I've seen this 'bug' for years and that's why I never use LRs lens profiles.  I open images I wish to post-process in DxO (from within LR as an external editor), apply the DxO profiles—which are far superior IMHO—to the raw files, and close DxO.  The resultant raw files goes back into LR with an attached .dop file and the lens corrections remain in place.

Sometimes one needs a specialist application like DxO to do what a generalist application like Lightroom can't hope to accomplish.  (I have also found that DxO updates their lens/camera combinations far more often than does Adobe.)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4253 Posts
  • 808 Reply Likes
Thanks Todd, for the videos. Please leave them posted for the team to review. I was able to reproduce and have logged a bug for this. 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1106 Posts
  • 357 Reply Likes
Will do–Thanks Rikk!
Photo of RFP

RFP

  • 26 Posts
  • 4 Reply Likes
This reply was created from a merged topic originally titled DJI Osmo Mobile 2 LR imports.

Distorted DJI Osmo Mobile 2 imports (solved)
Hey All,
I found and solved and issue with photos imported to Lightroom mobile from the DJI app for iOS.
Ensure you deselect the "Lens Profile Corrections" for importing photos in the setting.

When "Lens Profile Corrections" is on -it will warp the your photo to an unusable state. 

After the photo has been imported you can apply the lens correction if needed, Just don't do it at import! It will remain distorted if then imported to Lightroom Classic from Lightroom CC. 

Looks to be a bug with the camera profile metadata saved to the image within the DJI app.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3845 Posts
  • 1008 Reply Likes
In the discussion of the original topic, it looks like the cause of these symptoms is the same, using embedded previews.