Jump to content

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


Recommended Posts

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

Link to comment
Share on other sites

  • Staff

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. 

 

Link to comment
Share on other sites

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

-- 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.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

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

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.5.2636 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.5.2636 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

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.