Jump to content
Guest

Affinity Photo 1.7.3 - Batch Convert of Nikon RAW files into JPG gives VERY dark image results....

Recommended Posts

Guest

Software

- Affinity Photo 1.7.3

- Windows 10 Version 1909

- Plenty of RAM, disk space and graphics capability.

 

Just a quick question.

1. I've imported around 30 Nikon NEF RAW images directly from camera into Affinity Photo.

2. I have then carried out a Batch Copnvertion Process in Affinity Photo to get these images into JPG format.

3. The Affinity Photo Batch Convert Process was actually very smooth and fast enough - it worked well in terms of the time that it took and the method of carrying out the conversion process.

Anyway, this is when issues started

4. When looking at the results of this batch convert process, ALL of the resulting 30 JPG images are a little too dark to be useable to be honest, using the default settings for the import.

5. I've then gone and tested the same Nikon NEF RAW images in Adobe products, to look at the same images, to see how these turn out, and ALL of these NEF images convert into JPG and the results are totally fine - no issues at all with dark images via this route.

6. Just wanted to make you aware of this.

a) I only ran this process with default NEF images files direct from camera.

I did not try to convert camera images from NEF into DNG format BEFORE importing into Affinity Photo because I would prefer not to use

an additional DNG file because of storage issues, time taken to convert images twice and so on.

Kind Regards

Hazard

Share this post


Link to post
Share on other sites

Welcome to the Serif Affinity forums, @Hazard.

If you Open a RAW image it goes through the Develop Persona, and the Develop Assistant options provide some default processing. Any other use of a RAW image skips the Develop Persona and the Develop Assistant, and is likely to give worse results because of the more simplified processing.  This is well known to longer-term users of the software and readers of the forums, and to Serif. I think they view it as an opportunity for future improvement, rather than a bug, but I'm not sure of that.

You can try doing a batch conversion of one of the RAW files to .afphoto, and then recording a macro to make it look better. You can then apply that macro during the Batch processing to get an approximate result.

Share this post


Link to post
Share on other sites

Hi Hazard,

As @walt has pointed out, this is something we are aware of.

It's logged with the Dev team and should be resolved in a future update :) 

Share this post


Link to post
Share on other sites
Guest

Thanks for this, both of you.

I've also just posted a suggestion/query into the  "New Features Section" of the  Forum. This is to try and start further discussion on these processes.

This is because it's obvious from the notes above - and also from comments that I've read from other Affinity Users in the Forum's - that different users require different facilities/features in and from Affinity Photo Software. And I guess that it's not always possible to keep User's happy - all of the time, or some of the time !

 

 

 

Share this post


Link to post
Share on other sites
Guest

Thanks for the update on this. I'm running Windows 10 OS but this is interesting, especially as the "rename the app1.0 folder to 1.1 and so on'' does not actually improve the situation on a temporary basis in Win10 at the moment, nor does the reset option (holding down the ctrl key etc. etc.) 

IF anybody wants to see the Procedure to manually process 300+ images from RAW to JPG then I am happy to forward the loop (for information) but you are already probably very aware if it yourselves.

Kind Regards

Hazard

 

Share this post


Link to post
Share on other sites
7 hours ago, R C-R said:

the new 1.8.0.164 Photo Customer Beta for Mac lists "Improved handling of RAW files when using batch processing" as one of its changes.

FYI

The current Windows Beta 1.8.0.532 build does not have this fix included (changelist is here). This code was changed very recently and should be included in the next Windows beta (.555 or above)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.