Wrong file size and proportions in RAW develop (or blank image with Apple Core Image)

[mrhakala]

Hi,

I'm trying to import this DNG frame to Affinity Photo for processing. The image is 4608x2592 pixels. When using RAW develop the Serif Labs RAW engine renders the file as 4656x2624 pixels. In addition to the obvious the rightmost part of the image is corrupted in the process (possibly to compensate for the wrong image proportions). Switching to Apple Core Image RAW does not help as it gets me completely black image.

I'm working on Mac OS High Sierra.

Unfortunately I need the software to be pixel perfect in order to move the frames back to my video editing software. Is there a solution to this or am I forced to switch to Adobe CC? Hope not, I have been trying to avoid that for so long...

Thanks in advance, 

Markku

A122_02231425_C004_000000.dng

[Gabe]

Hi @mrhakala,

Welcome to the forums. 

When we load a raw image, we do not take into consideration any in-camera settings, including in-camera crop. We only read the Full image resolution, which in your case is 4656x2624. I have moved this to feature requests.  

As for the image being black with Apple RAW, we use Apple's RAW engine for that, and they cannot open the file. If you open it with preview, it shows as black. I suggest you log this with apple directly.

Thanks,

Gabe. 

 

[mrhakala]

Thanks. This clarified the issue for me. As a workaround I will use Davinci Resolve to export the frames with the correct crop. Keep up the good work!

Markku

[walt.farrell]

4 minutes ago, mrhakala said:

Thanks. This clarified the issue for me. As a workaround I will use Davinci Resolve to export the frames with the correct crop.

You could, of course, simply crop the images to the dimension you want in Affinity Photo. But if Resolve suits your workflow better, that's fine, too

[Pšenda]

I consider processing in full resolution, and thus in fully available image information, an advantage - it is always possible to cut, not vice versa.

[mrhakala]

10 hours ago, Pšenda said:

I consider processing in full resolution, and thus in fully available image information, an advantage - it is always possible to cut, not vice versa.

True. In this particular case the image data outside the crop is partly corrupted. Don't know why. In any case, the native sensor size of the camera (Ursa Mini 4.6K) is 4608 x 2592 so there shouldn't be any crop in the first place. Leaves me puzzled, but at least there was a workaround.

[Pšenda]

37 minutes ago, mrhakala said:

the native sensor size

No, native "sensor" size is 4656 x 2624 pixels. 4608 x 2592 is cropped image after processing.

[mrhakala]

2 hours ago, Pšenda said:

No, native "sensor" size is 4656 x 2624 pixels. 4608 x 2592 is cropped image after processing.

Oh. Interesting...