P: Disable built-in lens profile

[Tokumeino]

I own Micro43 and compact cameras, where lens profiles are integrated in RAW files. With software like Capture One Pro, I can easily enable or disable theses built-in profiles. Actually, there is even a slider allowing to enable 0% or 100% of the built-in profile, and whatever percentage in between.

In LR (CC, Classic or LR6), the checkox for enabling or disabling profiles does not work with built-in profiles, which always stay enabled. This seriously limits the possibilities of several cameras which possibilities get unleashed by actual RAW developpers like Capture One Pro.

I'm actually a COP user (after switching from LR) but DAM sucks with COP and this built-in lens profile thing is the only deal breaker for me to come back. So please let users disable built-in lens profiles, or at least offer workarounds.

As a workaround, a dumb "zero" profile that would replace the built-in one (not coming on top of it) could do the job.

[ericw79554200]

I'm late to this party but I hazard the suggestion that the 'built-in' profile issue isn't just about distortion. Unless I am very much mistaken the profile for a Sony E-mount standard zoom (E16-70 f/4 ZA)  purchased last year also adds a certain amount of sharpening. I can find no other explanation for the edge artifacts I periodically see when I process images taken with this lens in Lightroom. It's certainly not a camera issue as images taken with an older (and slightly softer) lens attached to the same A6000 back are entirely free of this problem.

[Todd Shaner]

It's my understanding that the Adobe LR and ACR built-in lens profiles apply, only distortion, vignetting, and chromatic aberration correction and not necessarily all of them for specific camera models. Take a look at this post, which may be what you're seeing:

https://forums.adobe.com/message/10144570#10144570

[bryanh72432487]

Those built-in profiles can change the sharpening and noise reduction settings. Here's an example from the Nikon Z7. This is a SOC RAW file. It looks to me that Nikon is instructing Lightroom to modify the sharpening and noise reduction settings.

[John R Ellis]

"Those built-in profiles can change the sharpening and noise reduction settings. Here's an example from the Nikon Z7. ... t looks to me that Nikon is instructing Lightroom to modify the sharpening and noise reduction settings."

The Z6 and Z7 embed LR develop settings in the XMP metadata of their raw files.  See this thread: https://forums.adobe.com/message/10862123.  

These embedded develop settings are different, and have different capabilities, from the built-in lens profiles that the cameras also embed in the photos.  The embedded develop settings can be easily disabled using an Import develop preset.  But the embedded built-in lens profile can't be disabled (at least from within LR).

[Jao vdL]

John was quicker than me but he is absolutely right. The sharpening settings for Z6 and Z7 files have nothing to do with the lens profiles that are also built in to the nef files. The sharpening settings are dependent on the in-camera sharpening settings and are done by simply writing xmp camera raw default metadata into the nef file that Lightroom and camera raw pick up. I really wish there was a way to disable the built-in lens profile. 

[olidie]

After getting a Nikon Z6 I am too for the first time effected by ACR applying a built-in lens profile. Since I disabled this inside the camera and Nikon itself is not applying in NX-D I really wish Adobe would stop patronizing me. It's an absolute nogo, Adobe!

[jwaltman]

This is what I believe should be addressed and is probably a bug in ACR.  I turned off "Auto distortion control" in my Z7.  When I load a NEF in NX-D distortion correction is not automatically applied but it is in ACR.  The information to apply correction or not is properly written to the file.  Adobe is either not reading it correctly or ignoring it.

Interestingly, if I turn off vignetting control in camera it's not automatically applied in ACR (nor in NX-D) as expected.  There is at least some logic in ACR to turn on/off corrections based on what's written to the file...

At the end of the day, these are RAW files and users should be given the option to turn on/off any correction like this during processing.  If I wanted settings baked in straight out of the camera I'd shoot JPEG.  There's no reason this can't be done in ACR if it can be done in other RAW processors.

[Guest]

I've just bought a Fuji XT30. There is an in-body option to enable or disable lens distortion correction, which means that Fuji - just as Nikon - is perfectly fine with using the sensor uncroped. Unfortunately, LR doesn't honor the user choice and forces the profile to be enabled.

This feature request beeing 1 year old, and still not taken into account by Adobe, I now beleive that they will never put the 1/2 day developer effort to solve the issue. I've now switched to Capture One Pro which lets the user the creative choice of which correction to apply. For multi-device work, backup and face recognition, I subscribed to Mylio which compliments COP just perfectly. So bye bye, Adobe.

It is really a shame that an official rep of Adobe doesn't even write a word or too, even "we won't support that because we want to force you to crop your sensor". At least, we would know. It was a memeber of the support team who asked me to post here to get feedback, and I have none.

[d-hob]

Automatically and irreversibly applying built-in lens profiles is also a serious bug in Adobe Camera Raw. When processing DNG files from, for example, a drone like the DJI Mavic 2 Pro, Adobe Camera Raw automatically applies the lens correction built into DJI’s DNG files. As a result, lens distortion is applied and CANNOT BE UNDONE. The lens distortion correction is so extreme that it causes serious image degradation, especially in the corners. Adobe: What is the point of a raw file if you force the user into accepting edits that cannot be undone?! Adobe has just turned all the advantages of a raw file into all the limitations of a JPEG.

To get around this problem, I’ve had to switch to a raw editor that does not do this. As a result I purchased Affinity Photo. The more I use Affinity Photo, the more I like it. And I especially like it in consideration of Adobe’s recent threat to price their Photo plan at $20 per month instead of the current $10 per month. To be honest, I’m now one step away from leaving Adobe once and for all, and this is coming from a professional photographer!

[deejjjaaaa]

> To get around this problem

just use exiftool and get null the tags in DNG files ...

[bryanh72432487]

I tried to figure EXIFtool out and it doesn't make much sense. It would be nice if there was an easy way to use EXIFtool in Lightroom.

[John R Ellis]

Here's how to remove embedded lens corrections:

1. Convert a folder of raws to DNG using Adobe's DNG Converter:
https://helpx.adobe.com/photoshop/using/adobe-dng-converter.html

2. Run ExifTool over the folder to remove the lens corrections:
https://forums.adobe.com/message/10070106#10070106

3. Import the modified DNGs into LR.

[DBinkard]

We need to have the option to disable built-in lens profiles from being automatically applied. Not having this option takes away from the freedom we should have to work with raw files. There is no good reason to force users to accept a lens profile, particularly when image data might be cropped out, as seen in some of the above examples. I have no problem with the profiles being applied by default, but I want the freedom to turn them off.

The current arrangement is little different from being locked into a high-contrast color profile, with no option to use a neutral color profile.

[Starrfish77]

Two years later, and we still don't have a fix?

I was in a drone forum today, where someone was sure his "RAW files were being
cropped" and I assured him this wasn't the case. Until someone said that
Capture One allows you to disable the embedded lens profiles, and that opens up the final "cropping" step after the bit fiddling the lens fixing does.

So we have a large group of people (drone fliers), who see one thing on their screen, compose the shot perfectly, shoot in RAW (like we should almost always do), and when they open it in ACR or Lightroom, they are FORCED into this weird cropping, which removes visible data, and there's no current way to turn the application of these embedded lens profiles off.

Please consider a checkbox option to allow us to disable embedded lens profiles in ACR and LR. (I use LR CC Classic and have an Adobe Creative Cloud account.)

Thanks!

[John R Ellis]

It's frustrating LR doesn't let you disable the embedded lens profile. But there is a tedious workaround: 
https://feedback.photoshop.com/photoshop_family/topics/disable-built-in-lens-profile?topic-reply-lis...

[Starrfish77]

Yeah, I saw that workaround and it's less than ideal. I shoot thousands of images per day, and I don't want to add another two or three steps to my RAW workflow.

I can't imagine this would take Adobe more than a day to implement, test and push out with the latest Adobe CC release. Why isn't this a thing yet? Have any engineers replied? Two years is unacceptable.

[Guy T.]

The thundering silence from Adobe employees on this thread likely suggests that it's a business decision, and not a product (user-oriented) decision, perhaps to curry favor with some manufacturers. Can an Adobe employee please comment on this thread to let us know the real reason you chose to take control away from your users, rather than empower us to make our own choices?

[John R Ellis]

I agree, it's a tedious workaround for a trivial omission from LR.

[bryanh72432487]

I agree. It's like when Nikon was saying that all Nikon users should run the RAW files through Nikon's software before using Adobe's software. It was a business decision and not one that favored users.

[bryanh72432487]

I've also noticed that panoramic shots using Photo Merge aren't stitching right when this setting is on. You still have to go into the drop menu and find the right lens. Shooting a D850 and Z 7 next to each other with the same lens and the same pano gear results in near perfect results with the D850 and messed up results with the Z 7. There shouldn't be much if any difference between the two when it comes to getting a good stitch. 

[John R Ellis]

Camera Raw Engineer Chris Castleberry has stated that Adobe obeys the wishes of Sony with respect to external lens profiles:
https://feedback.photoshop.com/photoshop_family/topics/disable-built-in-lens-profile?topic-reply-lis...

So it's a reasonable assumption that Adobe is also obeying the wishes of manufacturers with respect to embedded lens profiles. If that's true, people should be complaining to the manufacturers at least as loudly as to Adobe.  (In my opinion, both are equally negligent in ignoring the desires of their customers.)

The underlying dynamic is likely driven by Adobe's legal department, rather than a business or product decision for "currying favor" with camera manufacturers. In another context (reading capture-date time zones from metadata), an Adobe engineer indicated that Adobe's legal department believes that Adobe software should not, without the manufacturer's legal permission, read information from non-industry-standard, manufacturer-specific metadata fields (e.g. Makernotes and raw information). 

Thus, it appears that Adobe needs contractual permission from each manufacturer to read their raw files. This gives the manufacturers like Sony negotiating leverage with Adobe over what LR may do.

I don't know of other software vendors who have adopted Adobe's legal interpretation about non-standard, manufacturer-specific data fields in raw files. There's certainly a lot of software out there that reads all sorts of non-standard manufacturer-specific metadata.  I spent some time a couple years ago looking online to learn if this legal interpretation was used by other companies and couldn't find anything. In general, laws about "reverse engineering" are a complicated mess and vary by country (and even within the US). 

[Guy T.]

I'm not a lawyer but I would be very surprise if Sony, or any other manufacturer, claimed legal rights over how the files produced by their products are used (can you imagine Microsoft demanding to have a say in the content of documents created on MS-Word?).
Manufacturers have a vested interest in forcing certain settings to make up for possible weaknesses in their products (e.g. softness at edges of some lenses, or imperfect color rendition). Adobe should not. And users deserve to know what the data actually looks like when making buying decisions.
Perhaps Adobe has consented to this in exchange for early/better access to manufacturer specifications, but clearly this comes at a cost to users. I see nothing wrong with allowing manufacturers to provide their own profiles, and to give users the option of using them, but they should not be forced onto users. If Adobe is legally bound to do so, whoever negotiated this deal, perhaps unwittingly, has put their RAW conversion products at a disadvantage as other software vendors clearly do allow users to override these profiles.

[John R Ellis]

According to Adobe Principal Computer Scientist Simon Chen, the Adobe legal department believes that Adobe needs permission from manufacturers to read non-standard data fields: 

https://feedback.photoshop.com/photoshop_family/topics/iphone_video_capture_time_is_shifted_upon_imp...

[Guy T.]

That shouldn't be an issue here since the suggested workaround strips this data completely and RAW conversion still works.

[Todd Shaner]

I've been testing the Luminar Flex plugin for LR by Skylum software. It allows opening the LR raw image file using its own raw converter with built-in distortion correction disabled. It's a destructive workflow, but another way to achieve that objective. I then use PS's Adaptive Wide Angle Filter to correct distortion with very little loss of image area. See below link:

https://console.getsatisfaction.com/photoshop_family/conversations/disable-built-in-lens-profile?rep...

Here's the Luminar Flex output file with no distortion correction compared to LR rendering. Skylum doesn't seem to have any issues with disabling the built-in lens corrections.