Jump to content

Remove Lens Vignette in Develop Persona not responding on Canon RAW


Recommended Posts

When I open my Canon CR2 test photo in Affinity Photo, the application recognizes the correct Lens profile 'Canon EF 28mm f/1.8 USM'. So this profile is included in the application. The Distortion correction is not good, however. I also noticed that Chromatic Aberration Reduction and Remove Lens Vignette are not automatically checked. Turning Remove Lens Vignette on gives a better result but is still not perfect. This whole profile seems wrong.

So I decided to create my own lens profile for the Lensfun project and added distortion, tca and vignetting elements in the XML. I copied this XML to the correct directory and my lens profile is now visible in the list. To recognize my own profile I added two characters at the end of the name.

When I again open the test photo I have exactly the same results. Affinity Photo recognizes its own profile. When I change the Lens profile to my created profile, the distortion correction is way better. The application responds to my profile! Yeah. Still no checked boxes in the other two fields.

When I turn on Remove Lens Vignette I get exactly the same result as before. It even seems that this correction is not responding any lens profile I choose. I get the same result with different lenses from the list.

Where are Chromatic Aberration Reduction and Remove Lens Vignette getting its information from? Not from the Lensfun database I guess.

 

Link to comment
Share on other sites

Posted (edited)

Since the lens 'Canon EF 100mm f2 USM' is not supported, I also created a profile for this lens.

After opening a RAW photo, I see that Affinity Photo recognizes the lens and chooses my created profile. I also see that the fields Lens Profile, Chromatic Aberration Reduction and Remove Lens Vignette are automatically / initially checked.

The results after correction look good.

Edited by ptr-nl
forgot word 'auto'
Link to comment
Share on other sites

  • Staff

@ptr-nl Welcome to the forums.

If you can provide a copy of your custom profile (Canon EF 28mm f1.8 USM), I can ask one of our developers to take a look to confirm if the data is being read correctly.

Link to comment
Share on other sites

A shot in the dark as I don't have a suitable raw but I always start these files with

<!DOCTYPE lensdatabase SYSTEM "lensfun-database.dtd">
<lensdatabase version="2">

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

As a guess, when you want to replace an existing profile it must be in its own file. If you want to add lenses then they can be combined as you did, it's all voodoo

Vignetting correction looks excellent, hope you'll send this to lensfun as it's far superior to the crap they have at present
 

FixedIt.png

CanonEF28mmf1.8USM.xml

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

It gets more interesting...

About the crop factor or focal length multiplier:

Everyone writes on internet 'The camera has a full frame sensor so this is 1.0' but my camera is writing 0.971 ( 35 mm equivalent: 48.5 mm ) / ( Focal Length: 50.0 mm ) in the metadata of the raw.

The Lensfun database mentions a cropfactor of 1.0 which is not good in my case. So I also need to overwrite or replace the camera profile.

Is there a way to give priority to a local Lensfun database, then the central database, then some kind of default? So replace and not merge?

Link to comment
Share on other sites

Your previous raw for the EF 28mm shows conflicts in the exiftool report:

Cropped Image Width             : 3960
Cropped Image Height            : 2640

Focal Length                    : 28.0 mm (35 mm equivalent: 27.2 mm) -- my note: 27.2/28=0.971
Scale Factor To 35 mm Equivalent: 1.0

Sensor Width                    : 3960
Sensor Height                   : 2640
Sensor Left Border              : 0
Sensor Top Border               : 0
Sensor Right Border             : 3959
Sensor Bottom Border            : 2639

I suspect that it's being caused by using the crop mode, you could ask on the exiftool forum or use Canon's raw developer and see what that shows

You could experiment by changing the lens xml to
<camera>
<maker>Canon</maker>
<model>Canon EOS 5D Mark III</model>
<mount>Canon EF</mount>
<cropfactor>0.971</cropfactor>
</camera>
<lens>
<maker>Canon</maker>
<model>Canon EF 28mm f/1.8 USM</model>
<mount>Canon EF</mount>
<cropfactor>0.971</cropfactor>
etc
</lens>

but I think you'd be wasting your time and this would screw results using the same lens in full frame mode
35 mm equivalent is only stated as a convenience, I doubt that any software uses it so whether it's right or wrong doesn't matter
As it's a full frame lens on a full frame body I'd use a crop factor of 1 and ignore metadata

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

Use "exiftool -n" to get results 'without changes'.

Everything you write is correct. But I also have a Canon EF-S Body which I can use with EF lenses. And 3% difference does not look much but still. Somehow this information is needed to convert from raw to image with corrections.

Link to comment
Share on other sites

If you can demonstrate that the Photo correction is different for the same lens used on a full frame body and a crop body then carry on trying to modify the profiles to cope with both. I think that it would be a pain to select the right profile during development but then I'm not doing it.
If you are serious about lens correction I recommend a trial of PhotoLab. I use it with Viewpoint, it's easy and produces superb results. If I only had Affinity Photo for raw development I would go back to shooting rgb files from the camera
Hopefully a Serif expert will be along soon
I have nothing further to add, good luck

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.