Ron P. Posted December 14, 2022 Posted December 14, 2022 I noticed the RAW Lens Profile went wacky, in all versions of AP. Prior to the recent update, they were correct in auto-detecting, choosing the correct lens for my CR2 files. It says the lens used was a Nikkor, a Nikon... Oh those are fighten' 😡🤣 curse words for a Canonnista, (Canon shooter). Besides the lens is a Sigma 150-600mm Contemporary. Any photographer that has a little knowledge of DSLRs, knows you can not use Nikkor lenses on Canon bodies.. Something happened to the Lens Profiles, AP always selected the proper lenses for me until now. Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
Ron P. Posted December 15, 2022 Author Posted December 15, 2022 I've done further testing on this, and discovered my Sigma 150-600mm and Sigma 17-50mm lenses are the only ones AP mistakenly detects as Nikon. My other lenses, Canon 100mm macro, Tamron 70-300mm and Sigma 70-200mm were correctly detected. Those 2 Sigma lenses have been correctly detected until recently. Also I need to further investigate the Removing Lens Vignette. For those 2 lenses it doesn't seem to work. Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
David in Яuislip Posted December 15, 2022 Posted December 15, 2022 Can you post raw files with the lenses that don't work and I'll try them here? Quote 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
andersp5 Posted December 15, 2022 Posted December 15, 2022 I get a similar problem, my Sigma 18-300mm F3.5-6.3 DC Macro HSM lens is detected as the Sigma 18-35mm F/1.8 DC HSM [A] for Canon mount in both V1 & V2. The metadata from the camera as shown by Digital Photo Professional software (DPP) from Canon is correct. However all the data in both versions of Affinity Photo displays the incorrect lens even in the metadata. The interesting thing is that in the list of lenses the Sigma 18-35 is the next lens to the Sigma 18-300 thus I suspect the data for the 18-300 is incorrect and being attributed to the Sigma 18-35 in the dataset. One for the developers to check I suspect! Quote
Ron P. Posted December 15, 2022 Author Posted December 15, 2022 3 hours ago, David in Яuislip said: Can you post raw files with the lenses that don't work and I'll try them here? Ok, here you go. FWIW, I'm finding there are some AP correctly detects. IMG_0187.CR2 20140627-IMG_0024.CR2 David in Яuislip 1 Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
Ron P. Posted December 15, 2022 Author Posted December 15, 2022 1 hour ago, andersp5 said: I get a similar problem, my Sigma 18-300mm F3.5-6.3 DC Macro HSM lens is detected as the Sigma 18-35mm F/1.8 DC HSM [A] for Canon mount in both V1 & V2. The metadata from the camera as shown by Digital Photo Professional software (DPP) from Canon is correct. However all the data in both versions of Affinity Photo displays the incorrect lens even in the metadata. The interesting thing is that in the list of lenses the Sigma 18-35 is the next lens to the Sigma 18-300 thus I suspect the data for the 18-300 is incorrect and being attributed to the Sigma 18-35 in the dataset. One for the developers to check I suspect! Kinda of odd, you're having problems with Sigma lens too. Since I discovered this issue, I've reinstalled AP-1, and AP-2. With AP-1, the issue seems to gone away, it correctly detects those lenses now, but with AP-2, (which I've not updated to the 2.0.3 since reinstalling), still says those lenses are Nikkor. I just checked right before I uploaded them. Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
carl123 Posted December 15, 2022 Posted December 15, 2022 On both images 2.0.0 detects the lens incorrectly (Apple iPhone!!!) 2.0.3 beta, detects the lens correctly Chris B 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Ron P. Posted December 15, 2022 Author Posted December 15, 2022 I spoke too soon earlier when I stated that AP-1 the issue has gone away. Nope, still there, launched it and checked several images, and it too, thinks those lenses are Nikkor. I'm not sure where AP-2 grabs the Lens Profile data. I've checked the .affinity path, it has a Lens Profile folder, but it's empty. For AP-1 the Lens Profile folder is in the Program Data>Affinity>Photo>1.0 folder. Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
AlainP Posted December 15, 2022 Posted December 15, 2022 Here 2.0.0 and 2.0.3 beta display the correct lenses. Quote -- Window 11 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060 -- iPad Pro 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 9th gen 256 gb - Apple Pencil 1 -- Macbook Air 15" - Mac mini M2-Pro - 16 gb
David in Яuislip Posted December 15, 2022 Posted December 15, 2022 Both images select a lens automatically in Photo V1 but I think the 150-600 is wrong, see the long boring story below: ExifTool Version Number : 12.41 File Name : IMG_0187.CR2 Lens Type : Canon EF 100-400mm f/4.5-5.6L IS USM or Sigma Lens - weird or what??? Lens ID : Sigma 150-600mm f/5-6.3 DG OS HSM | C or Sigma 150-600mm f/5-6.3 DG OS HSM | S Scale Factor To 35 mm Equivalent: 1.6 There are three such lenses in lensfun https://github.com/lensfun/lensfun/blob/master/data/db/slr-sigma.xml <maker>Sigma</maker> <model>Sigma 150-600mm f/5-6.3 DG OS HSM | C</model> <mount>Canon EF</mount> <mount>Sigma SA</mount> <mount>Nikon F AF</mount> <cropfactor>1.534</cropfactor> <!-- Taken with Nikon D7200 --> which has no vignetting data <maker>Sigma</maker> <model>Sigma 150-600mm f/5-6.3 DG OS HSM | C</model> <mount>Canon EF</mount> <mount>Sigma SA</mount> <mount>Nikon F AF</mount> <cropfactor>1</cropfactor> <!-- Taken with Nikon D800 --> <maker>Sigma</maker> <model>Sigma 150-600mm f/5-6.3 DG OS HSM | C</model> <mount>Canon EF</mount> <mount>Sigma SA</mount> <mount>Nikon F AF</mount> <cropfactor>1.613</cropfactor> <!-- Taken with Canon EOS 80D --> which has vignetting data and is used for the attached Sigma150-600.xml file, however the Remove Lens Vignette slider does nothing If you put that into the Lens Profile Folder it will be selected on opening a raw file, you can see Sigma 150-600mm f/5-6.3 DG OS HSM | C rather than the built-in Sigma 150-500mm f/5-6.3 APO DG OS HSM. Oddly lensfun doesn't show APO for that lens so dunno where that's from. The new profile has a slightly tighter crop and different correction but which is more accurate is beyond me, maybe take a snap of a brick wall to see ExifTool Version Number : 12.41 File Name : IMG_0024.CR2 Lens Type : Canon EF 85mm f/1.2L USM or Sigma or Tamron Lens - more weirdness Lens ID : Sigma 17-50mm f/2.8 OS HSM or Tamron SP 17-50mm f/2.8 XR Di II VC (B005) On opening a raw file, you can see Sigma 17-50mm f/2.8 EX DC OS HSM is selected, there is a difference between this and the built-in version as the screenshot shows but they both introduce barelling for your image and I prefer it uncorrected, effect probably varies with focal length, zip file contains jpegs of both IMG-0024.zip Sigma17-50.xml Sigma150-600.xml Quote 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
Ron P. Posted December 20, 2022 Author Posted December 20, 2022 @David in Яuislip, Thanks for the files. I tried them but got the same result. I think I finally discovered what's happening. AP is misreading the XMP sidecar files. When I first shot the images, I developed them in LR 6.14ish version, and had XMP sidecar files produced. So today I disabled the Load metadata from XMP sidecar files (in Preferences). Opened several of the files known to give the wrong lens, and now I get the correct lens selected automatically. Also for files that did not have XMP files, AP detected the correct lenses. The XMP files are not the problem, because other programs, like PSP give the correct lenses. I've attached the XMP files for the images I uploaded before, if someone wants to test my theory.. Thanks IMG_0187.xmp 20140627-IMG_0024.xmp Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
David in Яuislip Posted December 20, 2022 Posted December 20, 2022 exiftool -len* IMG_0024.CR2 Lens Type : Canon EF 85mm f/1.2L USM or Sigma or Tamron Lens Lens Drive No AF : Focus search on Lens Info : 17-50mm f/0 Lens Model : 17-50mm Lens Serial Number : 0000000000 Lens : 17.0 - 50.0 mm Lens ID : Sigma 17-50mm f/2.8 OS HSM or Tamron SP 17-50mm f/2.8 XR Di II VC (B005) Lens : 17.0 - 50.0 mm (35 mm equivalent: 26.8 - 78.8 mm) <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c128 79.159124, 2016/03/18-14:01:55 "> aux:LensInfo="17/1 50/1 0/0 0/0" aux:Lens="17-50mm" aux:LensID="137" aux:LensSerialNumber="0000000000" crs:RawFileName="IMG_0024.CR2"> stEvt:softwareAgent="Adobe Photoshop Lightroom 6.14 (Windows)" Looks like the xmp has overwritten the cr2 file lens data, unusual for Lightroom to make a cockup but there's always a first time Ron P. 1 Quote 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
andersp5 Posted December 21, 2022 Posted December 21, 2022 On 12/15/2022 at 1:44 PM, Ron P. said: Kinda of odd, you're having problems with Sigma lens too. Since I discovered this issue, I've reinstalled AP-1, and AP-2. With AP-1, the issue seems to gone away, it correctly detects those lenses now, but with AP-2, (which I've not updated to the 2.0.3 since reinstalling), still says those lenses are Nikkor. I just checked right before I uploaded them. Just checked after installing latest update V2.0.3 and still have the same problem....not fixed but I note some have been? Quote
Ron P. Posted December 21, 2022 Author Posted December 21, 2022 1 hour ago, andersp5 said: Just checked after installing latest update V2.0.3 and still have the same problem....not fixed but I note some have been? Have you tried disabling the Load metadata from XMP sidecar files in the Preferences for AP ? It's found at the bottom of the General tab. Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
andersp5 Posted December 22, 2022 Posted December 22, 2022 22 hours ago, Ron P. said: Have you tried disabling the Load metadata from XMP sidecar files in the Preferences for AP ? It's found at the bottom of the General tab. I hadn't but I have now and it made no difference unfortunately, thanks for advice. Quote
Recommended Posts
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.