3d illusions Posted August 9, 2024 Posted August 9, 2024 This is the export: This is how it looks in affinity photo: It was working fine before I enabled the IGPU so I can get better video encoding speed in handbrake. In the affinity preferences I've tried both gpu's individually, and both produce the same artefacts in random places. Quote
walt.farrell Posted August 9, 2024 Posted August 9, 2024 Generally when you have problems like that you needd to Disable OpenCL compute acceleration in Affinity. It usually indicates that your GPU drivers have issues, possibly in how they handle the OpenCL requests issued by the Affinity application. It might be possible to update your GPU drivers and get past this, while still leaving OpenCL support enabled. This FAQ provides some additional information for updating your drivers: 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.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
3d illusions Posted August 9, 2024 Author Posted August 9, 2024 Thanks for the response. You're right, it's caused by hardware acceleration being turned on by the looks of it. I think the issue is with how affinity is making the requests because all other hardware accelerated applications are operating correctly (handbrake, davinci resolve, edge, etc) Perhaps they've fixed it in version 2 of affinity photo? Quote
walt.farrell Posted August 9, 2024 Posted August 9, 2024 9 minutes ago, 3d illusions said: I think the issue is with how affinity is making the requests because all other hardware accelerated applications are operating correctly (handbrake, davinci resolve, edge, etc) There are many different ways to use hardware acceleration, and each program probably uses it differently and for different purposes. We have seen user examples where GPU driver X has worked properly, and the update from the GPU manufacturer to driver Y has failed, and then the update to Z has worked again. We can tell, from that, that the Affinity programming was OK and it's the driver with the issues. That does not mean that there is never an issue with the Affinity OpenCL programming, but I think there are more users not experiencing issues than those who do experience them. 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.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
walt.farrell Posted August 9, 2024 Posted August 9, 2024 I should also note that only the Affinity team would know for sure what errors they have logged against their OpenCL code. I haven't tried to search the forums to look for them. 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.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
3d illusions Posted August 9, 2024 Author Posted August 9, 2024 Thanks. I think the problem is affinity doesn't allow to specify which hardware to use for acceleration. It's probably leading to miscommunication in scheduling, resulting in some pixel blocks being considered completed when they aren't, leading to the black blocks of pixels which are randomly placed differently with each exported image. I tried letting windows control which gpu affinity uses, but it didn't make any difference: All drivers are current. I'd be surprised if it's not possible to specify which hardware to use for acceleration in C++ . The only resolution would be to specify the hardware to use for it, because it's quite likely that GPU drivers from two different vendors aren't going to play nicely. Quote
Staff NathanC Posted August 10, 2024 Staff Posted August 10, 2024 15 hours ago, 3d illusions said: Perhaps they've fixed it in version 2 of affinity photo? With regard to corruption lines/artefacts appearing on exports to raster formats such as JPEG and PNG with OpenCL enabled, there have been improvements to OpenCL rendering within V2 and we do see significantly less reports of this problem. There were a few similar problems reported following the 2.4.2 update specific to exporting RAW files with OpenCL enabled however as far as I can see this was resolved in 2.5.X. I'd suggest picking up the 6 month trial and then enabling OpenCL in V2, as you should hopefully find this problem has been resolved. 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.