BUG! Ultimate 2023 Lens Correction

[Regor250]

One disappointment I have with 2023 is that ACDSee has yet to implement the ability to read embedded lens correction data, hence still relying on the inaccurate LensFun database. Even worse, if LensFun data isn't using the exact EXIF Lens model name, ACDSee cannot auto detect the correct lens profile and users think there is a bug, when there isn't. Frustrating! Failing to implement the first (and best) option, perhaps ACDSee could implement a simple LensFun data update function to update a lens model in the appropriate LensFun data file for a manually selected lens profile to that shown in the EXIF?

Addendum: See ACDSee (Mark) post below... it actually does via the Map Default function :-)

[Regor250]

Here an example of erroneous data in the LensFun database, which is preventing auto detect (and there are perhaps several hundreds more like it). While I am more than capable to fix the data for myself, there are many users out there, frustrated that their lenses aren't auto-detected and ACDSee should (and can) do something about it.

Failing to implement the capability to read the embedded maker lens correction metadata, which is the preferred method and used by Adobe as one example, ACDSee could A. Correct the data and B. Add an Auto Detect function for the selected lens profile to match the EXIF Lens model, and automatically update the Lensfun data as I did above manually.

Tristan H, if your read this, can you please pass it on to the development team?

[AliGW]

Could you talk me through how to correct this? I have Olympus lenses and am always having to run lens correction every time I develop a photo - I'd love it to be automatic. Thanks.

[Greyfox]

Regor250

I'm not sure who's responsibility it would be to change the Lensfun data that is distributed to a number of software developers and is no doubt used under some sort of licence, but in terms of the LensFun database, is that even the problem? (it seems like a work around to me)

Having looked at the EXIF Metadata of an Olympus RAW image taken with an M.Zuiko lens, the identification of the lens type or model varies within the one image.

In the ex E-M10 MKII camera image metadata I looked at, the [Olympus] metadata (makers notes) gives the Lens type as Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ, but the Lens model as OLYMPUS M.14-42mm F3.4-5.6EZ. The [ExifIFD] gives the Lens Model only as OLYMPUS M.14-42mm F3.5-5.6 EZ, and the [ExifIFD] Lens Info as only 14-42mm F3.5-5.6 EZ. The [Composite] metadata give the Lens ID as the full Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ.

Nearly all of the M.Zuiko lens models in the LensFun database are given the full name (....M.Zuiko Digital ED...), and for the lens in question it is Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ.

When I open that same RAW image in Affinity Photo's Develop Persona, which I understand also uses the LensFun database, it auto corrects for Lens distortion, and shows the Lens Profile being used as Olympus M.Zuiko Digital ED 14-42mm f/3.5-5.6 EZ.

So perhaps the question is how does Affinity get it right using the LensFun database as it is. It would seem the two applications are not taking the Lens reference from the same place.

Maybe if they are going to continue to use LensFun then this is what ACDSee should be looking into ?

[Gasmansteve]

Hi guys
New to Acdsee and this is jjust what I joined the forum for and glad to see its already been asked. I`m presently trialling 2023 and getting quite quite frustrated with the lens correction and if memory serves me thats why I didnt go for the 2022 version. I`m not sure where the problem lies as Acdsee clearly recognises the lens correctly but fails to use the correct profile. This is quickly becoming a deal breaker for me as if you have many frames shot with different lenses its becoming a pita to have to manually put the right profile in each time. I`ve just tried the open source freebie Digikam (which uses the same LensFun database) and even that has the auto lens correction working perfectly so if the open source guys can do it how come not the pro`s?. I`m not a coder but surely it shouldn`t be too difficult to get one part of the app talking to another part?.
regards
Steve

[mcosgrove]

Hello,

As a workaround, please take a look at the Map Default button to map the current EXIF settings to a specific lens profile and then have the auto-apply option checked, do this once for each lens you own and you shouldn’t have an issue with the auto-detection anymore.

The lens mapping system just uses the current EXIF data being read for the lens and associates it with a specific profile inside Lensfun, which allows you to have the correct one selected automatically.

Example: If you look at the Info Palette in the bottom right whenever you get that camera name and lens name combination it will automatically select the current lens profile you have and apply it.
Whenever you have:
EXIF Camera: E-M5MarkIII
EXIF Lens: OLYMPUS M.17mm F1.8
It will populate and apply the profile:
LF Camera: E-M5MarkIII
LF Lens: Olympus M.Zuiko Digital 17mm f/1.8

Regards,
Mark

[Regor250]

Thank you Mark, I never realized Default Map was for a Camera+Lens combo and not just a camera, though now that I look at it, it is rather obvious... dumb me! I'll give that a try too. That at least addresses auto-detect. :-)

[Regor250]

[Gasmansteve what version of ACDSee are you showing? This is what Ultimate 2023 looks like with the Map Default button referred by Mark above:

[Regor250]

Could you talk me through how to correct this? I have Olympus lenses and am always having to run lens correction every time I develop a photo - I'd love it to be automatic. Thanks.

You can do what Mark has suggested and check the auto-apply as shown:



or you can drop the attached xml file (in Zip container) into the LensFun folder to replace the mil-olympus.xml file (backup the old mil-olympus.xml so you can go back to it if you wish to later). It won't auto-apply but will auto-detect without mapping.

[Regor250]

Regor250

I'm not sure who's responsibility it would be to change the Lensfun data that is distributed to a number of software developers and is no doubt used under some sort of licence, but in terms of the LensFun database, is that even the problem? (it seems like a work around to me)

Having looked at the EXIF Metadata of an Olympus RAW image taken with an M.Zuiko lens, the identification of the lens type or model varies within the one image.

In the ex E-M10 MKII camera image metadata I looked at, the [Olympus] metadata (makers notes) gives the Lens type as Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ, but the Lens model as OLYMPUS M.14-42mm F3.4-5.6EZ. The [ExifIFD] gives the Lens Model only as OLYMPUS M.14-42mm F3.5-5.6 EZ, and the [ExifIFD] Lens Info as only 14-42mm F3.5-5.6 EZ. The [Composite] metadata give the Lens ID as the full Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ.



Nearly all of the M.Zuiko lens models in the LensFun database are given the full name (....M.Zuiko Digital ED...), and for the lens in question it is Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ.

When I open that same RAW image in Affinity Photo's Develop Persona, which I understand also uses the LensFun database, it auto corrects for Lens distortion, and shows the Lens Profile being used as Olympus M.Zuiko Digital ED 14-42mm f/3.5-5.6 EZ.

So perhaps the question is how does Affinity get it right using the LensFun database as it is. It would seem the two applications are not taking the Lens reference from the same place.

Maybe if they are going to continue to use LensFun then this is what ACDSee should be looking into ?

Interesting, the plot thickens. It seems that the reason it works in one app and not the other (ACDSee) would depend on what metadata field (hence version of the lens model) is used to match a lens profile. It seems that ACDSee is using the Lens Model field, which sometimes is and other not what LensFun uses. The database is now open domain, no licensing I am aware of. I myself created and contributed lens correction data, which is how I know how inaccurate it can be!

[Greyfox]

..As a workaround, please take a look at the Map Default button to map the current EXIF settings to a specific lens profile and then have the auto-apply option checked, do this once for each lens you own and you shouldn’t have an issue with the auto-detection anymore.

The lens mapping system just uses the current EXIF data being read for the lens and associates it with a specific profile inside Lensfun, which allows you to have the correct one selected automatically.

Thanks for that information - works for me.

[TomV]

[Gasmansteve what version of ACDSee are you showing? This is what Ultimate 2023 looks like with the Map Default button referred by Mark above:

TomV here, I get the same Lens Correction window as GasManSteve without the Map Default and Manage Defaults buttons. Just downloaded the 16.0.0.3162 version a few days ago.

[AliGW]

Regor250 Thank you so much for this! I am going to try what Mark suggested first, once I've resolved the other issues I'm having with 2023, then if that fails, I'll try your suggestion.

[Gasmansteve]

Hi guys Sorry not near my desktop at the moment so unsure which version of Ultimate 2023 I have, it was downloaded about 5 days ago from the Acdsee site. So the latest version has a map default button now?.

[Greyfox]

TomV here, I get the same Lens Correction window as GasManSteve without the Map Default and Manage Defaults buttons. Just downloaded the 16.0.0.3162 version a few days ago.

You are looking at the Lens correction panel in Edit mode. It doesn't have the Map Default and Manage Default buttons.

Those buttons are in the Lens Correction panel in Develop mode, accessed from the Geometry Tab.