Re: [darktable-user] OpenCL -- did I solve my problem?

That is exactly what happens. And indeed more an annoyance than a problem, as I do have the image Howard Helsinger On Sep 22, 2017 10:19 AM, "Ulrich Pegelow" wrote: > Am 22.09.2017 um 16:12 schrieb Howard Helsinger: > >> yes, as suggested, I'm running two displays

Re: [darktable-user] OpenCL -- did I solve my problem?

Am 22.09.2017 um 16:12 schrieb Howard Helsinger: yes, as suggested, I'm running two displays at 1920. problems seem to derive from the demosaic module Well, that's not fully correct. Problem derives from the fact that there is less GPU memory available than darktable thinks it has. The

Re: [darktable-user] OpenCL -- did I solve my problem?

yes, as suggested, I'm running two displays at 1920. problems seem to derive from the demosaic module On Fri, Sep 22, 2017 at 7:52 AM, Lorenzo Bolzani wrote: > > nvidia-smi may give some hint on the situation, for example running it as: > > watch -n 1 nvidia-smi > > > >

Re: [darktable-user] OpenCL -- did I solve my problem?

nvidia-smi may give some hint on the situation, for example running it as: watch -n 1 nvidia-smi 2017-09-22 11:27 GMT+02:00 thokster : > Am 22.09.2017 um 09:11 schrieb Remco Viëtor: > >> On vendredi 22 septembre 2017 07:35:32 CEST Michael Below wrote: >> >>> Just an idea:

Re: [darktable-user] OpenCL -- did I solve my problem?

On vendredi 22 septembre 2017 07:35:32 CEST Michael Below wrote: > Just an idea: should the headroom depend on the display resolution? Like: > 300mb for 1920, 400mb above? > > >... > >By default darktable assumes that it's sufficient to leave 300MB > >untouched for driver and display purposes.

Re: [darktable-user] OpenCL -- did I solve my problem?

Am 21.09.2017 um 22:00 schrieb Howard Helsinger: However, I don't quite understand why. I attach the output of   $ darktable -d opencl.    It says my  GeForce GTS 450 "allows GPU memory allocations of up to 239 MB. I think I don't understand the numbers. I try to explain and there are