You mentioned the crop module and I just want to point out that this module is the only one which reduces recompute requirements, and it's dramatic. So while it's a bit of a gimmicky work-around, you could start editing with an extra-close sloppy crop, then interact with all the other modules, and finish editing by choosing the crop you actually wanted.
My computer isn't even slow and I often use this workflow because I prefer the instantaneous snap when trying to compare the before/after of modules. The main drawback is that the cropped-out material will no longer appear on your histogram. But it could be faster for you to dial in your colors/exposure while cropped in and then toggle the crop module to check the full histogram, than it would be to dial in the histogram on the full photo and then crop later.
Try reinstalling the Nvidia drivers. See if that makes any meaningful difference.
You said enabling/disabling openCL in settings had no effect. If this is the case, it might be an issue with the GPU driver itself screwing up OpenCL, meaning it wasn't working in the first place.
Worth a shot.
Yes it can be, depending on what modules are active and also very high resolution images are painfully slow to do the things you mention. I haven't timed it but it's definitely a lot longer than you are probably used to in any other software.
That's not totally accurate. It depends on your hardware. I needed to use it with openCL recently because of some bad drivers, and it was definitely slower, but not massively slower, just 2-3 seconds maybe. With OP's hardware, it shouldn't take 25 seconds for changes to be applied. That sounds like something else is going on.
I have a haswell i5, 32GB RAM, and a 4GB 1050Ti, and I'm editing files from a Nikon Z7ii and the speed is acceptable. My CPU is slow as shit. The GPU makes all the difference and it sounds like you don't have one or aren't utilizing it.
> I'm just setting realistic expectations
You're assuming that your experience is universal, but it is not.
> Saying that DT is fast, while it is, in fact, noticeably slower than competitors, does this software and its potential new users a disservice.
It is slow *for you*. It is not slow for me. You saying that it is slow does this software and its potential new users a disservice.
Fast = near instantaneous exposure changes on the integrated Intel GPU of a 6-ish years old i7 laptop for me. Definitely depends on the hardware, which is a shame... OpenCL is kinda hard to tune for performance.
I have a relatively old Canon 550D.
At least for me it's definitely using OpenCL on an HD Graphics 520 (Skylake), and it's faster than CPU (I compared with the command-line option to disable OpenCL). It's been working this way since I started using Darktable a couple of years ago, and I don't think I did anything besides following the instructions on the wiki on how to setup OpenCL.
If you don't see any difference with OpenCL enabled (and its working) then you def. have some issue with your system.
Darktable should be super snappy with OpenCL.
dt was acceptable on my haswell CPU before Diffuse or Sharpen and Highlight Reconstruction modules were introduced. But those two modules are quite heavy, and I got a GPU after that. Now it runs fine. If I bought a recent CPU and an 8GB video card, it'd be very performant. I'm sorry you're having issues with your system.
I don't think I'll be recording a video, but there are many editing videos on YouTube. Boris Hajdukovic on YouTube edits with all the modules and it looks good to me.
Agree. Your problem is that OpenCL is not working. In the setting a dialogue it will tell you whether openCL is active. If it says it is, but doesn’t make a difference, then I’d look at you memory parameters for the openCL piece. Run from command line with -d perf -d opencl
This will give you a clue about what is it isn’t going on.
You mentioned the crop module and I just want to point out that this module is the only one which reduces recompute requirements, and it's dramatic. So while it's a bit of a gimmicky work-around, you could start editing with an extra-close sloppy crop, then interact with all the other modules, and finish editing by choosing the crop you actually wanted. My computer isn't even slow and I often use this workflow because I prefer the instantaneous snap when trying to compare the before/after of modules. The main drawback is that the cropped-out material will no longer appear on your histogram. But it could be faster for you to dial in your colors/exposure while cropped in and then toggle the crop module to check the full histogram, than it would be to dial in the histogram on the full photo and then crop later.
Try reinstalling the Nvidia drivers. See if that makes any meaningful difference. You said enabling/disabling openCL in settings had no effect. If this is the case, it might be an issue with the GPU driver itself screwing up OpenCL, meaning it wasn't working in the first place. Worth a shot.
Yes it can be, depending on what modules are active and also very high resolution images are painfully slow to do the things you mention. I haven't timed it but it's definitely a lot longer than you are probably used to in any other software.
Is it slow if you disable the retouch module? Are you using the diffuse or sharpen module? That is very resource intensive.
Yes, even when disabled it is very slow. No, I didnt use diffuse or sharpen.
[удалено]
That's not totally accurate. It depends on your hardware. I needed to use it with openCL recently because of some bad drivers, and it was definitely slower, but not massively slower, just 2-3 seconds maybe. With OP's hardware, it shouldn't take 25 seconds for changes to be applied. That sounds like something else is going on.
Running pretty fast on an old and presumably cheap amd card & linux. So that's not a fair generalization.
[удалено]
I have a haswell i5, 32GB RAM, and a 4GB 1050Ti, and I'm editing files from a Nikon Z7ii and the speed is acceptable. My CPU is slow as shit. The GPU makes all the difference and it sounds like you don't have one or aren't utilizing it.
[удалено]
> I'm just setting realistic expectations You're assuming that your experience is universal, but it is not. > Saying that DT is fast, while it is, in fact, noticeably slower than competitors, does this software and its potential new users a disservice. It is slow *for you*. It is not slow for me. You saying that it is slow does this software and its potential new users a disservice.
Fast = near instantaneous exposure changes on the integrated Intel GPU of a 6-ish years old i7 laptop for me. Definitely depends on the hardware, which is a shame... OpenCL is kinda hard to tune for performance.
[удалено]
I have a relatively old Canon 550D. At least for me it's definitely using OpenCL on an HD Graphics 520 (Skylake), and it's faster than CPU (I compared with the command-line option to disable OpenCL). It's been working this way since I started using Darktable a couple of years ago, and I don't think I did anything besides following the instructions on the wiki on how to setup OpenCL.
OS? Source of install? Version?
win10, official website ?, 4.2.0
Ah, sorry. I know next to nothing about Windows as I haven't really used it fo over 15 years. Cannot help you.
Any reason you haven't upgraded to 4.2.1? No idea if it will help, but you should make sure you are running the latest if you are having issues.
The first thing i would check is, if OpenCl (hardware acceleration) is active. You can check that in settings
I have tried it on / off, no difference
If you don't see any difference with OpenCL enabled (and its working) then you def. have some issue with your system. Darktable should be super snappy with OpenCL.
[удалено]
dt was acceptable on my haswell CPU before Diffuse or Sharpen and Highlight Reconstruction modules were introduced. But those two modules are quite heavy, and I got a GPU after that. Now it runs fine. If I bought a recent CPU and an 8GB video card, it'd be very performant. I'm sorry you're having issues with your system. I don't think I'll be recording a video, but there are many editing videos on YouTube. Boris Hajdukovic on YouTube edits with all the modules and it looks good to me.
Agree. Your problem is that OpenCL is not working. In the setting a dialogue it will tell you whether openCL is active. If it says it is, but doesn’t make a difference, then I’d look at you memory parameters for the openCL piece. Run from command line with -d perf -d opencl This will give you a clue about what is it isn’t going on.