Version 2.1.1 batch - hazy results

[rddpozi8]

Why does Version 2.1.1 batch bring on haze?

Please see attachments below, also please note my concerns attached:

1- Original .RAF

2-Macro procedure .afmacro

3-Macro steps as screen capture

4-Result from Single macro application  -- not good, but still better than batch 

5-Result from Batch macro application -- haze increases compared to single photo

6-Result from Adobe Elements with similar macro steps -- Significantly stronger effects.  I hope to "strengthen" or "scale up" the enhancement effects with Affinity the way Adobe provides.

Original.RAF test macro.afmacro

[Lee_T]

Hi rddpozi8,

Batch processing uses a simpler version of the RAW develop engine, so you may see some differences when using this method additional processing.

Lee

 

[rddpozi8]

Ok. Maybe a secondary question but more to the point-what to do to clean out the haze and to bring out more saturation like in the last photo?

[Lee_T]

I would recommend a batch process with no macro to a format such as a 16bit TIFF to maintain dynamic range. Then run the TIFF's through the batch processor with your macro.

Lee.

[walt.farrell]

1 hour ago, Lee_T said:

Batch processing uses a simpler version of the RAW develop engine,

I thought that, since sometime in 1.8 or 1.9, the batch processing uses the full Develop engine, including all the Develop Assistant settings. The documentation or comments from Serif staff have indicated that Open and New Batch Job used the complete engine, but other functions (Place, Stacking) used the simplified Develop engine.

[rddpozi8]

On 6/30/2023 at 5:29 AM, Lee_T said:

I would recommend a batch process with no macro to a format such as a 16bit TIFF to maintain dynamic range. Then run the TIFF's through the batch processor with your macro.

Lee.

It did the same with TIFF as with RAW. But since then I have other macros that do what I want, so I’ll just throw out that one instead of wondering about it.
Still a thing that comes out of this is the need to apply macro to a set of still opened photos so you don’t have to save them first.

[NotMyFault]

The auto contrast / levels / adjustments might work differently to PS. Using them multiple times on same picture is not advisable.

and maybe the haze removal has the same flaw as other recorded adjustments: it might bake-in data from the image used during macro recording, instead of doing a new calculation during execution time for the actual image. Only Affinity can say for sure.

[walt.farrell]

4 hours ago, NotMyFault said:

and maybe the haze removal has the same flaw as other recorded adjustments: it might bake-in data from the image used during macro recording, instead of doing a new calculation during execution time for the actual image. Only Affinity can say for sure.

It should be simple enough to experiment with that and determine it empirically, I think. Record the macro using one photo. Try a batch job. If it misbehaves, manually run it against a photo where it misbehaved during a batch job. If it misbehaves when run manually, but still behaves correctly against the original photo, it's a problem with "baked-in" values.