I can submit this on github as a bug, but I just wanted to see if anyone here could tell me if I was missing something obvious first.
I have found that the blurs module is causing a driver timeout error when I try to export images to JPEG. The JPEG generated is completely black and darktable usually needs to be restarted to get full functionality back. Disabling the blurs module seems to allow the image to be exported fine. I have found this with two images so far.
I have never had any problems with exporting before, nor problems with openCL. This problem first occurred in the middle of exporting multiple images, and all of them exported fine until it got to the one with the Blurs module.
Anyone have an idea what’s going on? My feeling is that the module is doing something that the GPU can’t handle, although my 580 with 8GB VRAM should be able to handle most things that darktable throws at it.
How much memory headroom do you have for OpenCL? Can you start darktable with -d opencl from the CLI and post the output? Also share the OpenCL settings in preferences.
Your card seems beefy enough, so I’d guess either a buggy driver or you need to tweak your OpenCL settings in darktable.
I started darktable from the command line as you said, but I wasn’t sure where to look for the output. Am I right that it’s in darktablerc? If so, this is what I found:
Doesn’t look like a challenging set of modules…is it only with OpenCL activated?? Exports fine for me…I have a 3060Ti… You could try boosting the handles …your other settings don’t seem extreme in any way and should work I would think??
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.
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 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.
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?
