Converting CR3 files to TIFF now very dark after 2.1.0 upgrade

[rairhart]

I've been using Affinity Photo batch process for a while to convert my Canon CR3 files to tiff. But after the 2.1 upgrade of Affinity Photo, my tiffs are very dark. Any idea if this is a bug or something that I can correct somehow? Thanks

[Dan C]

Hi @rairhart,

Welcome to the Affinity Forums

I can confirm this is a known issue when batch processing RAWs, which has been logged with our development team to be resolved ASAP.

I will be sure to 'bump' this report with your thread now - I hope this helps!

[rairhart]

Thank you. Do you know if there are any work arounds, or if it's possible to download the old version that worked?

[rairhart]

I found a workaround for now. I'll just use this:

https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html

[Dan C]

I believe there is a known workaround in-app, in that applying a macro whilst Batch Processing may stop this from happening - though I do appreciate you may not wish to create a macro as there may be no edits you wish to make to the exported TIFF files.
 

I was midway through writing my reply above and had just considered the DNG converter from Adobe - so I'm glad to hear you've also found this workaround for the time being

[Affinity Info Bot]

The issue "Batch Processing RAW files creates incredibly dark results, regression over 2.0.4" (REF: AFP-6187) has been fixed by the developers in build "2.1.1.1847".

This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions. 
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us

[Affinity Info Bot]

Build 2.1.1 (build 1847) is now available as a Customer Beta

We would appreciate you trying the beta build for yourself to check that the fix listed by Serif Info Bot above has been fixed for you. If it has NOT been fixed please post into the announcement post rather than here.