pmp Posted September 26, 2024 Posted September 26, 2024 hallo in die runde, ich habe seit dem letzten update von photo 2 (2.5.5) ein problem mit den jr makros. diese funktionieren nicht mehr (sind zwar da, die regler haben aber keinerlei auswirkung auf das bild). ich habe die makros bereits mehrmals deinstalliert und wieder installiert, nichts ändert sich. bis zu diesem update haben sie immer, auch nach updates reibungslos funktioniert. da ich meine photos sehr oft mit den jr makros bearbeite ist das für mich fast eine katastrophe. es würde mich freuen, wenn jemand eine lösung wüßte.
walt.farrell Posted September 26, 2024 Posted September 26, 2024 Welcome to the Affinity forums, @pmp. JR supplies many different macros in many different sets of macros. Can you tell us one in particular that exhibits this problem for you? I think I probably know what's going on, but I would like to know which macro to confirm it. In the meantime, my guess is that you are experiencing the problem logged as AF-3284, which was introduced in Photo 2.5. -- 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 1: Windows 11 Pro 24H2, 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 26.0, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1
pmp Posted October 1, 2024 Author Posted October 1, 2024 thank you for your answer, sorry for my late reaction, i was very busy last days. the macro with problems is: jr macros: channels. since affinity photo version 2.5.5. there is no üpossibility tlo change the parameters within the macros. this problem appears in every macro from the set jr macros: channels. i reinstalled the macros several times, but with no positiv result.
walt.farrell Posted October 1, 2024 Posted October 1, 2024 Thanks, @pmp. Probably that known bug I mentioned, then. -- 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 1: Windows 11 Pro 24H2, 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 26.0, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1
walt.farrell Posted October 1, 2024 Posted October 1, 2024 You're welcome. -- 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 1: Windows 11 Pro 24H2, 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 26.0, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1
pmp Posted February 3 Author Posted February 3 hello again, now we have february 2025 and nothing changed to solve the problem. so i think it was enough time. can anyone tell me why? thank you.
walt.farrell Posted February 3 Posted February 3 2 hours ago, pmp said: can anyone tell me why? They've fixed some other macro-processing bugs in the 2.6 Beta, but apparently not this one. Only someone from Serif can comment on that. -- 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 1: Windows 11 Pro 24H2, 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 26.0, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1
Staff Affinity Info Bot Posted February 7 Staff Posted February 7 The issue "Adjustable Macro parameters are no longer honoured, default parameters are always used" (REF: AF-3284) has been fixed by the developers in the latest beta build (2.6.0.3106). 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.
Recommended Posts