Jump to content

Developing a 8688x5792 .CR2 RAW file in Affinity Photo creates a 8736x5856 .afphoto


Recommended Posts

Developing a 8688x5792 .CR2 RAW file in Affinity Photo creates a 8736x5856 .afphoto

Title says it all.

My .CR2 file from a Canon camera is expected to be sized as 8688x5792 pixels, but after opening and developing the data into a .afphoto format the  pixel dimensions are 8736x5856.

It seems as if the demosaic process differs from that used by Canon, Phase One, DXO and Adobe RAW converters.

What is up with that?

Win 7 Pro x64 SP1 with latest updates. Affinity Photo 1.7.1.404

Link to comment
Share on other sites

Yes I have noticed that with EOS 5DsR images it seems to get confused.

Both PC’s Win 11 x64 System with Intuos Pen & Touch 
PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM

- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB
PC2 HP Pavilion - 
Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

iPad (8th Gen) 2020

 

Link to comment
Share on other sites

1 hour ago, Mark Ingram said:

Hi, this is intentional right now (perhaps in the future we can add an option to apply the sensor's clip to the image). This means we return all of the pixels that were captured by the sensor, whereas other applications will clip those out.

That is one thing I really like about Affinity Photo, the little extra resolution you squeeze out of our cameras! :)

Desktop: AMD Ryzen 9 5900X, 32GB Ram, RTX 3070, LG 27" 4K 10Bit

Windows 11 22h2

Dell Laptop: i7 7700, 32GB Ram, GTX 1060, 16" 4K

Windows 10 22h2

Link to comment
Share on other sites

3 hours ago, Mark Ingram said:

Hi, this is intentional right now (perhaps in the future we can add an option to apply the sensor's clip to the image). This means we return all of the pixels that were captured by the sensor, whereas other applications will clip those out.

 

Hi,

Thank you for the helpful reply.

I just made an overlay with an example of a CR2 conversion made by Affinity Photo on the bottom layer, and an example made elsewhere on top.

After aligning the pixels, I can see the narrow strips of additional information at the margins. Nice!

Thank you!

Link to comment
Share on other sites

4 hours ago, Mark Ingram said:

Hi, this is intentional right now (perhaps in the future we can add an option to apply the sensor's clip to the image). This means we return all of the pixels that were captured by the sensor, whereas other applications will clip those out.

This is the sensor details ... I'm wondering how 8736x5856 is reached. 8736 is less than the sensor width of 8896 & 5856 is less that the sensor height of 5920? No issue, just looking for an explanation ... :)

image.png.425344aa6e25d11056c615793d068f87.png

Both PC’s Win 11 x64 System with Intuos Pen & Touch 
PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM

- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB
PC2 HP Pavilion - 
Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

iPad (8th Gen) 2020

 

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.