Jump to content
Sign in to follow this  
Otto Manuel

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

Share this post


Link to post
Share on other sites

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


Win 10 x64 System with Intuos Pen & Touch
 - Sys : Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

 

Share this post


Link to post
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! :)

Share this post


Link to post
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!

Share this post


Link to post
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


Win 10 x64 System with Intuos Pen & Touch
 - Sys : Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

 

Share this post


Link to post
Share on other sites
5 minutes ago, AiDon said:

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 ... :)

Some of that is still lost.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×