Jump to content

Recommended Posts

Posted

Affinity photo ver2 does not display the lens Metadata of my Canon R7 raw files correct in Metadata Exif however the lens data is shown correctly in Metadata detail. This results in incorrect selection of the lens in the lens correction field. E.g. When the lens used is a RF50 f1.8 this is displayed as 280 in the Metadata Exif field and a Tamron AF 80-210 f4.8-5.6 280D is shown in the lens correction field automatically. When a RFs 18-150 mm is used this is displayed as 286 in Metadata Exif and "none" is shown in the lens correction field. In both cases by scrolling the lens correction field I can manually select the correct lens but when I close Affinity and restart it and open the same picture files the wrong lens data is displayed again. I am using version 2.0.4 of Affinity photo.

CR7_1129.CR3 CR7_1133.CR3

Posted

David, many thanks for your help, the file you sent did solve the problem with my RF 50-1.8 and RFs 18-150 lenses. However my previous post was just an example so I tried all my Canon lenses on both my R7 and RP bodies. The result was that all my EF-s lenses were properly recognized by Affinity on both bodies and all my EF lenses were also ok except for my EF 70-300 F4.5-5.6 IS II USM but that is because it is not in the database of Affinity lenses (yet). My remaining problem is with the RP 16mm F2.8 lens. Affinity shows it as lens 288 in the Metadata Exif field and the lens is therefore not automatically found in the lens correction field. I can select it manually because it is in the lens database. I also put the 3 problem lenses on the RP body and Affinity shows 280, 286 and 288 as lens codes so the problem seems to be caused by the lenses itself and not by the R7 body.

Is there also a Canon 288.xml file which can solve this problem?

The question still remains why Affinity does not show the full lens description in the Exif field and what would be happening with other RF lenses that I do not have (yet). In the Canon DPP software and also e.g. Darktable software there are no errors with any of the lens descriptions.

Posted

Photo uses the lensfun database for lens corrections but it's not the greatest at identifying lenses. Sometimes this can be overcome by modifying the lensfun data and including the mods as an xml file which will supersede anything that Photo has in its basic catalogue
The 16mm lens is currently here
https://github.com/lensfun/lensfun/blob/master/data/db/mil-canon.xml#L1106

xmls start with
<!DOCTYPE lensdatabase SYSTEM "lensfun-database.dtd">
<lensdatabase version="2">
end with
</lensdatabase>
and the lens stuff from lensfun goes in between.
Then it's a matter of sorting out what Photo needs to auto detect the lens and exiftool is very useful for that. Your lenses were easy as I'd answered a query about the 16mm a year ago and realised that it needed the Canon number 288
So now you know what I know which should help in creating xmls for lenses you may obtain in the future

Regarding the EF70-300mm f/4-5.6 IS II USM, there is no entry in the lensfun database however all is not lost
If you download the Adobe DNG converter it will create a directory
C:\ProgramData\Adobe\CameraRaw\LensProfiles\1.0\Canon
which contains
Canon (Canon EF 70-300mm f4-5.6 IS II USM) - RAW.lcp
and lcp files can be loaded into the Affinity LensProfiles folder just like an xml. I can't provide the lcp due to Adobe copyright but I found a random raw on the www and the lens is auto detected in Photo V1, good luck

19 hours ago, FredD7 said:

The question still remains why Affinity does not show the full lens description in the Exif field

Indeed it does but that's for someone clever from Nottingham to explain

RF16f28.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

Posted

David, thanks for your exhaustive reply. After I wrote my post yesterday I looked it little bit further into the structure of the .xml file you sent me and decided to create a new .xml for all three lenses using the RF16 2.8 data in the Lensfun file: mil-Canon.xml. The resulting file is attached below and it works like a charm! Maybe other Canon users can use that file also. Oddly enough the metadata of my RF35-F1.8 is recognized properly by Affinity so not all Canon RF lenses are a problem for Affinity.

I just deleted the Adobe DNG converter from my PC since it did not work properly but I will try your tip for the 70-300 mm lens also.

Hopefully all this will help to get some more bugs in the Affinity photo program corrected by the makers.

CanonR7-280-286-288.xml

Posted
23 minutes ago, FredD7 said:

The resulting file is attached below and it works like a charm!

Spot on, have a like

 

24 minutes ago, FredD7 said:

Maybe other Canon users can use that file also

I doubt that they'll find it. I made a suggestion ages ago that there should be a seperate category for user provided xml files so that they didn't get lost in the forum noise but that went down like a lead zeppelin

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

Posted
1 hour ago, David in Яuislip said:

I doubt that they'll find it. I made a suggestion ages ago that there should be a seperate category for user provided xml files so that they didn't get lost in the forum noise but that went down like a lead zeppelin

You could post them in Resources, where they could be more easily searched for.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

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.