John Rostron Posted September 18, 2021 Posted September 18, 2021 I created a set of macros to change the DPI of an image, originally in Photo 1.6 which worked well then, and worked in later versions. I found however, thet re-recording these macros in later versions (including 1.10) do not work. I report here my investigations as to what is going wrong. I re-created the individual macros using a simple image to work on. They all seemed to work OK. I then tried on a different image and discovered that they do not. What seems to have happened is that the macro records the size of the image when recording, so that when applied to another image it resizes to that new size, despite the Resample box not being ticked. Edit: I have now added change DPI to 120. John Chris B 1 Quote Windows 11, Affinity Photo 2.4.2 Designer 2.4.2 and Publisher 2.4.2 (mainly Photo). CPU: Intel Core i5 8500 @ 3.00GHz. RAM: 32.0GB DDR4 @ 1063MHz, Graphics: 2047MB NVIDIA GeForce GTX 1050
Staff Chris B Posted September 28, 2021 Staff Posted September 28, 2021 Hi John, I've just got around to checking this one - you are indeed correct and I can easily reproduce this. I'll pass this to the developers. Thank you! John Rostron 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
PaoloT Posted November 4, 2021 Posted November 4, 2021 I think I have the same issue in the Mac version (Photo 1.10.4, but it was also in the previous versions). 1. I start recording a macro. 2. Then open the Resize Document dialog. 3. Change the size and the resampling method, and confirm. 4. Stop macro recording. Playing the macro does nothing. Paolo Quote
walt.farrell Posted November 4, 2021 Posted November 4, 2021 8 minutes ago, PaoloT said: Playing the macro does nothing That's not the problem being discussed here. For this problem, the macro plays but does the wrong thing; it resamples when it shouldn't. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.2.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
carl123 Posted November 4, 2021 Posted November 4, 2021 5 hours ago, PaoloT said: Playing the macro does nothing. Works fine here 1.10.4 (Windows) Can you upload your macro? Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
PaoloT Posted November 4, 2021 Posted November 4, 2021 9 hours ago, walt.farrell said: That's not the problem being discussed here. Sorry, I did misunderstand. I've created a new topic here, with the macro attached: walt.farrell 1 Quote
John Rostron Posted March 29, 2024 Author Posted March 29, 2024 I have now re-installed Photo 1.6 and recorded my Change DPI macro for 120ppi. It works OK with Photo 2.4.1 I attach below the macro Change DPI to 1201.6.afmacro and the updated macro library to include this macro Change DPI 1.6.afmacros John Macros Change DPI 1.6.afmacros Change DPI to 120 1.6.afmacro Quote Windows 11, Affinity Photo 2.4.2 Designer 2.4.2 and Publisher 2.4.2 (mainly Photo). CPU: Intel Core i5 8500 @ 3.00GHz. RAM: 32.0GB DDR4 @ 1063MHz, Graphics: 2047MB NVIDIA GeForce GTX 1050
Staff Affinity Info Bot Posted November 26, 2024 Staff Posted November 26, 2024 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. Quote
Recommended Posts
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.