Hi there, I believe I have found the solution to both the artifacts and the “correction failed at the execute stage”.
My support ticket came back with the dev team saying that this was an error in the Radeon driver (my card is a Radeon RX570 8GB) and that this could not be solved by modifying DeepPrime code.
I did a clean reinstall of the driver and associated software using the AMD cleanup utility, but that didn’t make a difference.
But I finally stumbled up this article: https://support.dxo.com/hc/en-us/articles/360050525632-DeepPRIME-hardware-acceleration
I applied the suggested tweak of a hidden parameter and that seems to work. I have been test-exporting random images with Lightroom open in the background, I tried all the scenarios that failed before, and all the images that were problematic and gave those artifacts, and have not yet experienced a failed export. I did have one error that triggered the error reporting popup, but I realy was stress-testing the system. I have now exported successfully over 50 images without a problem. Processing time is much faster too: in between 15 and 25 seconds for a 26MP Fuji raw file, that’s an average of 10 seconds faster than before (when it worked, that is). My GPU is now at a 60% load during DeepPrime processing, instead of 100%.
After 5 month of struggling with this, deep frustration and several support tickets and forum posts, I have now something that works, finally. This is what I did (as per the instructions:)
Close DxO PhotoLab.
Locate and edit the following file: "C:\Program Files\DxO\DxO PhotoLab 4 or 5\DxO.PhotoLab.exe.config”.
Just under the “WinMLUseGraphicQueue” setting, replace “<value>False</value>” with “<value>True</value>”.
Restart DxO PhotoLab.
The support website search NEVER found this article: I was actually checking the DeepPrime minimum requirements for a GPU card, because after receiving the reply from support, I was on the verge of buying another one. So I googled “DxO compatible GPU” and got there. Saved my a couple of 100’s € for a new card… glad I insisted!
Hope this will help others. It could work for you too.
But I’d suggest that this hidden parameter should be exposed in the performance tab in preferences.
That would have saved me, and others, a lot ot time and frustration
Cheers
Dirk