Jump to content

Bug: Color/Gamut Clipping issue when RAW/RAF developing


Recommended Posts

It would appear that there is still the possibility that Affinity Photo can have issues with the color/gamut when developing certain RAW files. I know this was a big issue addressed in the v1.5 update as referenced here, but it would appear that there is still work that could be done to improve this behavior.

In all of the test photos, only Fuji RAW File Converter 3.x (SilkyPix 8.x engine) correctly rendered the color of the subject (ring) and didn't clip the colors. RawTherapee, DarkTable, LightZone, and CaptureOne v11 (Fuji) rendered it cool blue. All images are rendered with all processing off/neutral/default to ensure consistency.

For the Affinity Photo HDR and Median Stack images, I used a DCRAW script to dump both subframes from the RAF and composited them accordingly. As you can see, the development result is far superior to what the Serif RAW engine can produce.

Affinity Photo (RAW Develop):

ap2.thumb.png.92afd6edfffc7c48c9fdaeccf1b4c199.png

Affinity Photo (HDR Merge):

ap2_hdr.thumb.png.a63aad971c6412cef917778bd4d31f9f.png

Affinity Photo (Median Stack):

ap2_stack_median.thumb.png.2f15025204519a232b94cceeeb77e626.png

Link to post
Share on other sites

Here are examples from other RAW processing engines to compare to. Not all fared well, and as noted above, only RFC rendered it correctly. DarkTable clipped a bit, visually similar to the RAW import on Affinity Photo. CaptureOne rendered the left side of the ring brighter, as it should have been, but the color was completely wrong.

SilkyPix nailed the color, brightness, everything. Except the processing defaults make the image look like mush due to the excessive smoothing.

LightZone:

lightzone2.thumb.jpg.d03a53df47d5c57f59ac5f290605ef1c.jpg

RawTherapee:

rt2.thumb.png.93eedc95176df5c068d1c5fd44a48169.png

 

DarkTable:

dt2.thumb.png.911ec34a221118d7b3f1057ab2f86760.png

CaptureOne v11 (Fuji Edition):

captureOne2.thumb.jpg.4995ce578ff19f96c86a87c896a9f0b0.jpg

RAW File Converter 3.x (SilkyPix 8.x):

silkypix2.thumb.jpg.23fa0b74cf5ca7ee7cd7546cce44d0d9.jpg

Link to post
Share on other sites
  • 1 month later...

Affinity Photo Beta for Windows 1.7.0.184 (RAW Develop)

image.thumb.png.d33a670d67449e7ce30c8908e0961d84.png

All Assistant functions turned off, 32bit HDR as before. Shadow detail is recovered better, color is slightly more accurate and now the X-S1 Lens Profile is applied properly, but clipping is still a massive problem.

The image appears to be unchanged from the Beta 178 rendering.

Link to post
Share on other sites

Perhaps you missed Gabe's comment above, but this is the wrong forum for discussions about the Beta. 

Perhaps a moderator will split this, but if not you should repost in the correct beta forum.

-- Walt

Windows 10 Home, version 20H2 (19042.685),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop (2021-04-06):  32GB memory, Intel Core i7-10750H @ 2.60GHz
, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU
Affinity Photo 1.9.2.1035 and 1.9.4.1048 Beta   / Affinity Designer 1.9.2.1035 and 1.9.4.1048 Beta  / Affinity Publisher 1.9.2.1035 and 1.9.2.1024 Beta

Link to post
Share on other sites
8 hours ago, walt.farrell said:

Perhaps you missed Gabe's comment above, but this is the wrong forum for discussions about the Beta. 

Perhaps a moderator will split this, but if not you should repost in the correct beta forum.

Perhaps you missed that this is an extant issue with the RAW engine that predates the beta and that I am keeping a consolidated log of changes in processing behavior in this single thread while referencing it in the appropriate Beta forum.

I hope it isn't split as the ability to easily compare rendering across the various engines and versions will become more difficult.

 

Link to post
Share on other sites
  • 4 weeks later...

Affinity Photo Beta for Windows 1.7.0.209 (RAW Develop)

image.thumb.png.d50e5510eb9a1b5f5b17f4d871df3a7f.png

All Assistant functions turned off, 32bit HDR as before. Shadow detail is recovered better, color is slightly more accurate and now the X-S1 Lens Profile is applied properly, but clipping is still a massive problem.

The clipping, however, does appear to be reduced compared to the v184 beta and v189? beta. I'm not sure what changes have occurred, but this appears to be headed the right direction.

Edited by Saijin_Naib
Forgot version string.
Link to post
Share on other sites
  • 1 month later...

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

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.