TOS Posted September 3, 2019 Share Posted September 3, 2019 Hi all, the creation of a macro that changes the DPI setting only, leads to distorted pictures where this macro is applied to. All photos this macro is applied to receive the correct DPI setting but the pixel dimensions of the recording photo are applied as well. This is where the distortion happens. Macro was recorded like this: On loaded image select "Document" -> "Resize document" Uncheck "Resample" option -> pixel values become disabled (800x600px) Change DPI -> in my case to "300" Click "Resize" Stop recording and save the macro Applying this macro to a 72dpi photo with 1200x600px, the values become 300dpi with 800x600px. Looks like the unchecked "resample" setting is ignored on recording. I also tried to record the "uncheck resample" as a single step but it didn't work either, as well as deleting meta data. The 1 step macro is attached to this post. I am running the following setup: OSX 10.14.6 Mojave Affinity Photo 1.7.2 (desktop trail) Please have a look to this possible bug. Or if the problem is in front of the computer, just let me know how to record this macro correctly ;-) Best regards and thanks for building these awesome apps! Tim test.afmacros AutoKitty 1 Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted September 12, 2019 Staff Share Posted September 12, 2019 Hi @TOS. Welcome to the forums and sorry for the delayed reply. I replicated this and logged it with our developers. Thanks, Gabe. AutoKitty 1 Quote Link to comment Share on other sites More sharing options...
TOS Posted September 18, 2019 Author Share Posted September 18, 2019 Hi @GabrielM, thanks for your support! I'll check the release notes of upcoming versions then. Quote Link to comment Share on other sites More sharing options...
Bunny Photos Posted September 25, 2019 Share Posted September 25, 2019 I have the same problem. Quote Link to comment Share on other sites More sharing options...
AutoKitty Posted January 2, 2020 Share Posted January 2, 2020 Ditto. And since this was just in September, I'll assume it just hasn't been fixed, yet. Quote Link to comment Share on other sites More sharing options...
TOS Posted January 2, 2020 Author Share Posted January 2, 2020 Hey, nope it is not fixed! It occured in 1.7.2 and I re-checked after 1.7.3 was released. Still not working... Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 3, 2020 Share Posted January 3, 2020 As a workaround, another forum member provided a macro that does work, in another topic. We're not sure how he recorded it, but perhaps it is one he did back in 1.6. In any case, the macro works on 1.7 and (I believe) 1.8, so here it is in case some of you find it useful: AutoKitty 1 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
TOS Posted January 3, 2020 Author Share Posted January 3, 2020 Hey @walt.farrell, thanks for the info! I can confirm that the attached macro is working as expected. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 3, 2020 Share Posted January 3, 2020 You're welcome, @TOS. 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
AutoKitty Posted January 3, 2020 Share Posted January 3, 2020 @walt.farrell Thanks! I’ll have to check it out and see if I can edit it to 72, instead of 300. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 3, 2020 Share Posted January 3, 2020 Just now, AutoKitty said: @walt.farrell Thanks! I’ll have to check it out and see if I can edit it to 72, instead of 300. I don't think you'll be able to. Sorry. 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
John Rostron Posted March 1, 2020 Share Posted March 1, 2020 @TOS, I have produced a set of macros which change the dpi without affecting pixel dimensions here. John 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 Link to comment Share on other sites More sharing options...
TOS Posted March 31, 2020 Author Share Posted March 31, 2020 Hey, we just reached version 1.8.2 and after half a year has passed this is still an issue! The topic was pushed to "pre 1.8"... So this will not be worked on? Could a mod please move the topic to the current bug category as it affects the current version as well? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted March 31, 2020 Share Posted March 31, 2020 26 minutes ago, TOS said: The topic was pushed to "pre 1.8"... So this will not be worked on? Could a mod please move the topic to the current bug category as it affects the current version as well? They do not forget about bugs, once they are acknowledged/logged. They may sometimes take a very long time to resolve them. But it will be worked on, when Serif's manpower and the bug's priority permit. Gabe 1 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
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.