marciomendonsa Posted September 6 Share Posted September 6 As shown in the attached images, I created a macro that makes the sliders available for further adjustment once the macro is applied. Although the sliders appear when the macro is activated, adjusting them does not change anything, as demonstrated in the images. What am I doing wrong? Thank you all. Quote Link to comment Share on other sites More sharing options...
Wolfgang D. Posted September 6 Share Posted September 6 When I bought Affinity Photo version 2.4.1, this worked. Now in the current version 2.5.5 I have the same problem. marciomendonsa 1 Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 6 Share Posted September 6 @marciomendonsa: From static images I'm not sure I understand what you're saying/seeing. Trying this on macOS, I see that when I play a macro, and it displays the adjustment sliders provided by the macro: Moving the slider does not change the value in the box; and Moving the slider does not change the image immediately. However, when I release the slider the image changes, and the value in the box updates. Like this: Screen Recording 2024-09-06 at 11.18.55 AM.mov Compare with directly applying an Adjustment, where you're working directly with the sliders on the Adjustment dialog, not indirectly via the macro, and both the image and the box adjust as you move the slider: Screen Recording 2024-09-06 at 11.20.30 AM.mov Is that what you mean? 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.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...
carl123 Posted September 6 Share Posted September 6 15 minutes ago, walt.farrell said: Moving the slider does not change the value in the box; and Moving the slider does not change the image immediately. 3. However, when I release the slider the image changes, and the value in the box updates. Like this: On Windows, 1 & 2 are the same but 3 does nothing to the image. (The value in the box does change but nothing on the image changes) walt.farrell 1 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. Link to comment Share on other sites More sharing options...
walt.farrell Posted September 6 Share Posted September 6 1 hour ago, carl123 said: On Windows, 1 & 2 are the same but 3 does nothing to the image. (The value in the box does change but nothing on the image changes) That definitely is wrong. In fact, on Windows, the Adjustment Layer is created using the values that were originally set in the macro, completely ignoring the changes made by the sliders while executing the macro: 20240906-1736-36.9394994.mp4 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.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...
smadell Posted September 6 Share Posted September 6 I am using 2.5.5 and I am seeing expected behavior. (I am using a Mac, and cannot speak to whether this is a Windows-only problem.) In creating the macro, I clicked on the "cog" to the right of the "Set adjustment properties" line. Then, I clicked on each of the 6 color sliders in the dialog box that opened. I had to save each of the sliders separately, and gave them their default names. But, having done all that, the macro executes as I would have expected, with all changes made during the macro surviving after the Apply button was clicked. Black and White Macro.mp4 Quote Affinity Photo 2, Affinity Publisher 2, Affinity Designer 2 (latest retail versions) - desktop & iPad Culling - FastRawViewer; Raw Developer - Capture One Pro; Asset Management - Photo Supreme Mac Studio with M2 Max (2023); 64 GB RAM; macOS 13 (Ventura); Mac Studio Display - iPad Air 4th Gen; iPadOS 18 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 6 Share Posted September 6 33 minutes ago, smadell said: I am using 2.5.5 and I am seeing expected behavior. (I am using a Mac, and cannot speak to whether this is a Windows-only problem.) In creating the macro, I clicked on the "cog" to the right of the "Set adjustment properties" line. Then, I clicked on each of the 6 color sliders in the dialog box that opened. I had to save each of the sliders separately, and gave them their default names. But, having done all that, the macro executes as I would have expected, with all changes made during the macro surviving after the Apply button was clicked. I think you're showing the same behavior I showed in my first recording in this thread, but it seems you clicked a slider to change it, rather than dragging it. If you drag it, you should see what I reported (no changes until you release the slider, then the numbers in the box change and the image changes). And yes, then on macOS the changes are actually applied. On Windows they aren't, as I showed in my video just above yours. 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.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...
smadell Posted September 6 Share Posted September 6 4 minutes ago, walt.farrell said: it seems you clicked a slider to change it, rather than dragging it @walt.farrell - in the video, I did click. But dragging also gives me the anticipated results, i.e. nothing changes (slider values, image preview) until the mouse button is released. This is the same behavior I’ve seen since Macros were first released. And, click or drag, those slider changes survive the macro and can be updated using the Black and White panel afterward. Quote Affinity Photo 2, Affinity Publisher 2, Affinity Designer 2 (latest retail versions) - desktop & iPad Culling - FastRawViewer; Raw Developer - Capture One Pro; Asset Management - Photo Supreme Mac Studio with M2 Max (2023); 64 GB RAM; macOS 13 (Ventura); Mac Studio Display - iPad Air 4th Gen; iPadOS 18 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 6 Share Posted September 6 6 minutes ago, smadell said: But dragging also gives me the anticipated results, i.e. nothing changes (slider values, image preview) until the mouse button is released. This is the same behavior I’ve seen since Macros were first released. Thanks. I wasn't exactly sure how that should work, especially the numbers in the slider boxes. So it is just a Windows issue, then, where releasing the slider doesn't change anything in the image, and when Apply is clicked gives you a default Adjustment layer with none of the changes you made via the sliders for that run of the macro. 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.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...
Wolfgang D. Posted September 7 Share Posted September 7 19 hours ago, walt.farrell said: Thanks. I wasn't exactly sure how that should work, especially the numbers in the slider boxes. So it is just a Windows issue, then, where releasing the slider doesn't change anything in the image, and when Apply is clicked gives you a default Adjustment layer with none of the changes you made via the sliders for that run of the macro. Thank you. At least we have clarified that it only affects the Windows version. However, with versions <2.5 it also worked perfectly under Windows. Since I didn't create that many macros with this option, I only noticed it after some time. The question is, is Affinity Support reading this, or is it more expedient to email this problem to affinity@serif.com? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 7 Share Posted September 7 1 minute ago, Wolfgang D. said: is Affinity Support reading this Yes. But please be patient as they are very busy. 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.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...
Wolfgang D. Posted September 7 Share Posted September 7 2 minutes ago, walt.farrell said: Yes. But please be patient as they are very busy. Thank you. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 7 Share Posted September 7 You're welcome. 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.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...
Staff Callum Posted September 20 Staff Share Posted September 20 Hi All, Apologies for the delayed response, this seems to be a known issue that is currently logged with our developers to be fixed in a future update. Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
Wolfgang D. Posted September 20 Share Posted September 20 3 hours ago, Callum said: Apologies for the delayed response, this seems to be a known issue that is currently logged with our developers to be fixed in a future update. Thank you very much! Quote 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.