I have installed the latest version 4.4-2-win64 on my Windows 10 Home 64bit laptop.
When I click on opening Darktable, a command window flashes for a fraction of a second, and nothing else happens.
I tried:
I have been unable to use darktable for many weeks and it disrupts my workflow, any suggestions are very welcome!
Thank you very much
Can you post the output of darktable-cltest?
Apologies, but how do I run cltest? I googled but was unable to find an answer.
Thank you!
This link should jump you to the correct section. I suspect you have the OpenCL compatibility app installed.
Thatâs all it shows?
yes, that is all that shows up for a fraction of a second, before dissappearing
This is strange.
Can you navigate to the folder via cmd and do darktable-cltest by typing instead of clicking? It might show more information that way.
I changed the current directory in cmd and ran the cltest file through there, indeed this resulted in 1 more line:
I think you will be able to start darktable with: darktable --disable-opencl
But the magick error is not normal. I think this should be raised as an Issue on GutHub.
Thanks g-man, it finally does open up!
Is there any way to open it with opencl disabled without having to go through command prompt every time?
Happy to raise the magick error on github, for the awareness of the community, I will post it in Issues · darktable-org/darktable · GitHub - let me know if you thought it should go somewhere else.
I think we saw the same error recently here: Windows 11 Darktable 4.4.2 won't start - #3 by kofa
And thereâs been a handful of these cases of dt âjust wonât startâ.
Could it be something related to a Windows update?
You can disable OpenCL in the preferences by unticking the checkbox:
I must confess Iâm not sure if this is enough to prevent the startup issue.
Great news that it does start. That ensures we could focus on OpenCL only. Yes start the Issue in GitHub to get better documentation if this happens with the new version of darktable (see below). Like Steven shared, we had some recent reports of issues but you are the first one sharing good details.
The next version of darktable is 4.6 and should be released around 21Dec. In the forum we share a pre release version of it to get early feedback on windows. Can you install it and see if it resolves the issues? darktable windows insider program 12/3
Please do not open a new issue. It has been reported over and over (I also added a duplicate):
Then perhaps the original issue should be reopened. Itâs now marked as closed, so probably wonât get any attention.
If users shouldnât open new issues on this, how can they report it?
Itâs fixed in master - or can you reproduce it with a dev build? On the phone now, sorry, cannot search or investigate much.
My mistake, I took your reference to the issue # 14733 as you marking it as a duplicate of that issue, which was marked as solved, for version 4.4.1.
Kofa, I disagree. The issue you linked is missing information. The information posted in this thread shows a failure very early (when it is opening the opencl library). This is different than what weâve seen in the past with the Compatibility. My request is to start the issue if happens using master. Some of the questions I posted should help us understand what is the root cause of the issue. Also having someone actively trying to test/solve it is beneficial.
Sure, if it can be reproduced using the current master build, a new issue will be needed. This is not something I can help testing, as darktable runs fine on the Windows 10 laptop I have access to.
I have seen a few issues like this; this happens while linking the required OpenCL driver functions but we can never be sure if that link is correct/valid âŠ
