Jump to content
Richard Liu

File | New HDR merge... doesn't apply automatic lens correction not applied to individual RAW files

Recommended Posts

Is there some reason why automatic lens distortion corrections that are applied to a single RAW file when the assistant is so configured, are not applied to RAW files that participate in File | New HDR merge... ?  It would seem to be one of the more evident things to do.  Now I find myself having to remove pin cushion and barrel distortion in a separate step.

I am running ver. 1.6.7 on a Mac.

Share this post


Link to post
Share on other sites

Thanks for the reply.  Other than the issue at hand, the results seem perfectly fine when I use the the RAW files directly instead of developing them individually first.  I have the Develop Assistant configured not to use a tone curve and to apply color noise reduction.  As far as I am aware, Affinity Photo does not support batch development (but correct me if I'm wrong).  Thus, manually developing even a half-dozen RAW files could be rather tedious, even if the "development" consists only in opening the RAW file and clicking Develop.

Share this post


Link to post
Share on other sites
1 hour ago, Richard Liu said:

As far as I am aware, Affinity Photo does not support batch development (but correct me if I'm wrong).

It does support that. You can use File > New Batch Job and select RAW files as the input and it will work. However, as the various Develop Assistant settings are not applied (or applied differently?) some users have reported sub-optimum results.

Share this post


Link to post
Share on other sites

Just tried batch job.  No joy.  I can at least confirm that, despite being configured in the Develop Assistant, lens correction is not applied to any RAW files in a batch job.  I have no idea whether any of the configurable default actions in the Develop Assistant are honored.  Viewing the situation from the end of a forty-year career in IT, given the fact that macros that can be applied to batch jobs are created and run in the Photo Persona, then some minimal development -- to use Affinity Photo's terminology -- must be performed on a RAW file before it can be processed by any macros.  One such minimal development might have been to (virtually) open the RAW file, perform any default actions, and "click Develop."  Performing default actions configured in the Develop Assistant could be an option in Batch Job.  As things stand now, it is unclear what Affinity Photo is doing to a RAW file that it encounters in a batch job before handing it over to the Photo Persona, and, above all, why it should be doing anything differently than when a RAW file is opened manually.

Share this post


Link to post
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.


×
×
  • 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.