If I uncheck “activate OpenCL support”, restart darktable, then try and export, the export just hangs.
Do you mind trying this one too. It might be more challenging in terms of processing power:
DSCF7564.RAF (35.8 MB)
DSCF7564.JPG.xmp (985 Bytes)
Correct xmp??? No real processing…
Threw on 3 x blur and 3x diffuse…no issues with that image…
EDIT Beautiful image by the way… Maybe just for giggles create a new temp folder to use as a config folder and run DT with --configdir pointing to that …should use fresh config files…see if that lets it work properly??
Thanks Todd.
So the fact it is working for you would suggest it’s probably a problem with OpenCL or my graphics card. This may be a daft question, but where should I be looking to read the output of OpenCL info when I use diagnostic parameters to start darktable? Is it output to the darktable-log.txt file in C:\Users\XXX\AppData\Local\Microsoft\Windows\INetCache\darktable on Windows?
I have never done any OpenCL testing before. Thanks!
To be honest I always forget what goes where… I think you can do something like append > c:\opencltesting\log.txt to redirect it to where you want… perhaps there is a more elegant way??
I installed Bill’s last package and I’m still getting the problem. The image loads fine in the darkroom. I then try and export it. It says it has exported successfully, but then I get the driver timeout error and the jpeg is black. After that, the image is also black in the darkroom and I have to restart darktable to see it again.
Did you used the tune opencl performance in preferences at least once?
Also, do the log with -d opencl -d memory -d perf
I have set it to “memory size and transfer” for tuning OpenCL performance. Did some processing, closed darktable, relaunched it. Everything seems to work just fine… until I try to export that photo. When I turn off the Blurs modules (I have 2 instances), it exports fine. As soon as I enable just one of them and try to export, I get the driver timeout error.
As for this, interestingly I did manage to successfully export the image with just one Blurs module activated, but only once. Here are the logs I managed to get:
I think you should just run the tuning once and that’s it.
One of the log file has information, but the other is seems like it is missing the important information. Ideally you should have a log file when you do get the driver timeout. What driver is timing out on you?
I’m just getting a generic AMD popup:
I don’t really know how to use the OpenCL performance tuning yet on the 3.9 dev build (not sure if it’s in the dev manual yet). I tried setting the OpenCL scheduling to “very fast GPU” and it worked! But just once and that was at a 50% smaller file size. Subsequent attempts have failed again.
What happens if you turn off the AMD software?
Are you using the latest AMD drivers? 22.4.1?
https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580
I’m running the latest stable drivers, which are 22.3.1. The latest are beta drivers, which might be fine, but I’m skeptical they would solve this issue.
When you say turn off the AMD software, there’s about 7 AMD processes in task manager, you mean end all those?
22.3.1 should be recent enough for this.
What I mean with the software is likely in the right hand side near the clock. Exit the program or something.
You can’t do it from the system tray. There’s only a hide option, but it still works in the background.
Based on the fact that my system runs absolutely fine with games and other graphics programs, this just seems to be a problem with the Blurs module and darktable, so I’m reluctant to mess too much with drivers, etc. I’ll probably just avoid that module now until I upgrade my GPU in the future.
games and other graphics programs … games use OpenGL instead of OpenCL which is a different story.
We had a number of AMD specific DT bugs in 3.8 , difficult to know if this a problem here.
You might have to increase that … the default has increased for 4.0
1 Like
I think this is not a darktable bug, but the AMD software is detecting a driver timeout and reacting to it. I think it would be wise for the OP to temporarily disable the AMD software to test if it is still a problem.
I agree and given this post there could be a variety of things at play…not DT related… good list of things to try here