Skip to main content
Inspiring
November 7, 2017
Released

P: Disable built-in lens profile

  • November 7, 2017
  • 131 replies
  • 8476 views

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.

131 replies

johnrellis
Legend
July 19, 2019
"please do not overchampion your Adobe's advocacy"

Trying to understand Adobe's behavior is hardly advocating for them or agreeing with their decisions. Indeed, I wrote above, "In my opinion, [Adobe and manufacturers] are equally negligent in ignoring the desires of their customers." 

I also wrote above that Adobe appears unusual in its legal interpretation regarding non-standard, manufacturer-specific data in photos and that other companies haven't adopted that interpretation. Observing that Phase One may be one of those companies doesn't help us understand Adobe's position or contradict my analysis.
Bob Somrak
Legend
July 19, 2019
Different company, different or no contract.
M4 Pro Mac Mini. 48GB
deejjjaaaa
Inspiring
July 19, 2019
>  But the issue appears to be driven by legal and contractual concerns. 

PhaseOne example clearly shows that it does not
deejjjaaaa
Inspiring
July 19, 2019
> 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: 

dear, to read the data is one thing - and what to do about it is another story ... for example PhaseOne is also not a one man shop that might be under the radar of camera manufacturers and yet they allow users to disable profiles... so please do not overchampion your Adobe's advocacy... 
johnrellis
Legend
July 19, 2019
Technically, of course, it's trivial to allow the lens profile to be disabled. But the issue appears to be driven by legal and contractual concerns.  Adobe believes it needs contractual permission from the manufacturers to read their proprietary raw files, which gives the manufacturers negotiating leverage to ask Adobe not to allow disabling of lens profiles embedded in those raw files. 
Community Expert
July 18, 2019
They don’t need to read any data fields, simply give us the raw data as they are in the file and don’t apply the profile
Todd Shaner
Legend
July 18, 2019
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.


Known Participant
July 18, 2019
That shouldn't be an issue here since the suggested workaround strips this data completely and RAW conversion still works.
johnrellis
Legend
July 18, 2019
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...
Known Participant
July 18, 2019
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.