Re: [darktable-user] Heavily disappointed about openCL

On Wed, 21 Feb 2018 07:35:32 +0100 Bernhard wrote: > > ~ $ nvidia-smi > Wed Feb 21 07:17:20 2018 > +-+ > | NVIDIA-SMI 384.111    Driver Version: 384.111   > |

Re: [darktable-user] Heavily disappointed about openCL

Michael Rasmussen schrieb am 20.02.2018 um 22:57: On Tue, 20 Feb 2018 21:57:31 +0100 Ulrich Pegelow wrote: With today's typical amount of graphics cards memory we should probably increase the default setting of that parameter to maybe 400 or 450. With 2GB of

Re: [darktable-user] Heavily disappointed about openCL

On Tue, 20 Feb 2018 21:57:31 +0100 Ulrich Pegelow wrote: > With today's typical amount of graphics cards memory we should probably > increase the default setting of that parameter to maybe 400 or 450. > With 2GB of GPU RAM I have found the sweet spot to be

Re: [darktable-user] Heavily disappointed about openCL

With today's typical amount of graphics cards memory we should probably increase the default setting of that parameter to maybe 400 or 450. In "the old days" when we only had like 1GB a too high value would have forced darktable to go into useless tiling, but with more GPU memory that's

Re: [darktable-user] Heavily disappointed about openCL

Am 20.02.2018 um 20:09 schrieb Ulrich Pegelow: That's an out-of-resources problem on your graphics card. Try to increase darktable's config variable opencl_memory_headroom (in file darktablerc) to something like 400. Shouldn't that be configured in darktable GUI settings options? e.g. With

Re: [darktable-user] Heavily disappointed about openCL

Hi Ulrich, thanks for quick response. I found this http://darktable-devel.narkive.com/K9FwaE0y/opencl-problem in the meantime and already tried a value of 500 (does this have side affects?) and could not reproduce the problem til now. darktable reports [pixelpipe_process] [thumbnail] using

Re: [darktable-user] Heavily disappointed about openCL

That's an out-of-resources problem on your graphics card. Try to increase darktable's config variable opencl_memory_headroom (in file darktablerc) to something like 400. Please also make sure that no other application uses substantial amounts of GPU memory. You can use program nvidia-smi to

[darktable-user] Heavily disappointed about openCL

Hi, I ran into another problem with my new GeForce GTX 1050 Ti in my system regarding openCL. Every now and then I see a message about darktable finding problems with openCL and disabling it "for this session". I then have to reboot the complete machine to get this working again - but not for

Re: [darktable-user] Darktable on Windows

André Felipe Carvalho schrieb am 20.02.2018 um 11:56: Well, I think I could try to go back to 14.04 and use the packaged version of dt. Did you backup your database/profile before upgrading to dt 2.4 (which I presume is what you used in ubuntu 16.04)? Otherwise you might run into problems

Re: [darktable-user] Darktable on Windows

I'm not sure you would benefit from OpenCL. As someone already pointed out, you need a somewhat decent GPU to make use of it. Did it work before the upgrade to 16.04? Your overall slow performance may also be due to heat problems. Have you checked the temperature of your CPU and GPU? Older

Re: [darktable-user] Darktable on Windows

Hi André, I'm in a very similar situation to what you describe: I have an AMD R9 280 with an i5-4690 CPU @ 3.50GHz, and am running Ubuntu 17.10 as my daily OS. I have stuffed around with the new AMDGPU-PRO and open source equivalents to try to get opencl under modern Ubuntu, but although

Re: [darktable-user] Darktable on Windows

I thank you all for your comments. There's another issue that I thought last night, about changing operating systems. I produce some publications, photobooks, etc, with a software that I choose only because it has a Linux version. They have a windows version, of course, but my books were made in