Macro not working in Batch

[Nigel Kendall]

Hi,

I have been trying very hard to get a simple 300dpi macro to work on a batch of 200 images. I have tried them in JPG and Affinity Photo format, but nothing seems to work.  The only time it has worked the images have been left without their individual ratios.

Help!

Nigel Kendall

[walt.farrell]

There's a bug in recording macros that has existed since 1.7 and which causes problems like you have described. 

Try using the macro provided here, which was recorded using Photo 1.6.

 

 

[Nigel Kendall]

Thanks for the advice. I have used the macro you have suggested without success. The images still become distorted. Is there anyway of knowing if the macro has downloaded successfully? I use a iMac.

[walt.farrell]

1 hour ago, Nigel Kendall said:

Thanks for the advice. I have used the macro you have suggested without success. The images still become distorted. Is there anyway of knowing if the macro has downloaded successfully? I use a iMac.

Interesting. I will check later as I haven't tried it on 2.2.1, nor on a Mac since I acquired one.

Can you provide more information on how you used it, perhaps a screenshot of the Batch dialog where you applied the macro? 

If the macro loaded into Photo, it was downloaded successfully.

[walt.farrell]

I've now tried it using 2.2.1 on my Mac, and the macro seems to have worked fine. Perhaps you're doing something else, in addition to the macro, that is distorting the images?

[John Rostron]

@Nigel Kendall, I am the author of the ChangeDPI macros recorded with Photo 1.6.

I have just tried it using 2.2.1 on my PC and the macro works fine, both as a one-off and as a batch.

John

[Affinity Info Bot]

The issue "Resample tickbox ignored and always true when recording a macro" (REF: AF-990) has been fixed by the developers in the latest beta build (2.6.0.2900). The fix 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 @Affinity Info Bot to notify us.