Hello.
Export of PNG(16) is slow, export of TIFF(16) is very-very-very-very slow. It’s not HDD, 'cause i use a RAM-drive. Although OpenCL checkbox is ON, GPU load is 0% but CPU - 25% (1 core).
And export is impossible when the path contains non-ascii simbols.
DT 2.4.0rc0
Win 7x64
About the slowness of tiff export this has been reported in a French forum. It looks like it affects the Windows version since on Linux it is quite fast. No idea why though as I’m not involved in the Windows port at all.
Where is it?
The export to paths with non-ASCII characters, for JPEG that works, right?
Hello everybody,
I am trying to use darktable for windows.
the software crashes when I try to import .raf images.
Anyone encountered the same problem?
any solution?
@marcof
Do you have an example .raf image, that crashes.
When darktable crashed, did it tell you about a backtrace it wrote to disk? If so, we would like to see that file.
Hi,
Following the installation of the latest wacom driver, I just had a traceback with the 2.4 RC1. DT shut down and then restarted without problems and the tablet is working well.
darktable_bt_SHC3AZ.txt (8.8 KB)
Win 10 1709
Only for TIFF does not work.
Is this a problem which you can repro, or was a one-off? If you can repro, pls let us know what are the steps to reproduce.
Hello,
I do not see any message about a “backtrace”. Is there a specific place where I should look for it?
I downloaded Marco’s .RAF file. It opens without problem in the Linux version of 2.4.0~rc0. However, with the Windows version it opens, but then crashes almost immediately. So at least the problem seems to be reproducable.
I have downloaded it too, and opened it with dt rc0 and rc1, without any problem. Could any of you share the backtrace file which has been produced as dt has crashed?
Hi,
No, I can not reproduce it. As I said, it only happened once and the following launches went well.
I transmitted this traceback because it exists and can be revealing a hidden problem, without more.
Hi,
I’m a new user with darktable and do not have so much experience with it, my experience is Lightroom till 6.13. I’m using DT to find out the differences and if it delivers better results.
Now the actual (may be) problem with the .RAF:
I can open and edit and export it without problems.
My equipment:
a notebook Lenovo Y720 with 16 GB memory, a 256 GB system SSD, a 1 TB data HD and a GeForce GTX 1060 graphics card. The NVIDIA activity tool shows me, that DT is using it.
My notebook runs with Windows 10 64-bit Home ver 1709.
Peter, this morning I was able to open the .RAF without problems. This time, though, I imported it through the usual darktable dialog. Yesterday, when it crashed, I was right-clicking on the downloaded file, and specifying ‘open with darktable’. Perhaps this is a clue?
Ha! I just tried opening another file, .ORF this time, using the right-click procedure … and it crashed. That file also opens fine via the import dialog. Don’t know if this has anything to do with Marco’s problem.
I’m afraid you’ll need to tell me how to generate a backtrace in WIndows. Now if it was Linux I think I could do that!
Hi,
finally, tonight the same problem has occurred.
The approach is simple: after the first startup of the PC, at the first launch of DT, the light table is displayed and very quickly the window announcing the traceback opens. By clicking OK, DT closes. The following launches are OK.
So exactly like yesterday. It seems that it is necessary to shutdown the pc and re turn on it so that the problem returns.
I changed the driver of the Wacom because the old one no longer displayed the control panel of the tablet since Win 10 1709.
Win 10 Home 1709 - Wacom driver 6.3.25-5.
Regardsdarktable_bt_PHYEBZ.txt (8.8 KB)
Hi,
I get not sharp pictures in the lighttable after I have edited (sharpend, rotated and croped) them, lighttable is set to zoomable and I zoom to max (=fullscreen). In this view I can switch via left or right arrow to other (not edited) pictures and these are sharp. Also if I e.g. only rotate a little bit a picture, back in lighttable it is no longer sharp. Do I make something wrong? It’s DT Windows 2.4.0rc0 …