Mask feathering (was Re: [darktable-dev] OpenCL issues)

2018-10-30 Thread Heiko Bauke
Hi, Am 29.10.18 um 22:55 schrieb Aurélien Pierre: Very pleased to hear that (not the bug part, though). [...] In particular, I need to enable blending on GPU.  Currently I am working on automatic mask refinement based on a guided filter, see http://kaiminghe.com/publications/eccv10guidedfilte

Re: [darktable-dev] OpenCL issues

2018-10-30 Thread sturmflut
Dear list, On 30.10.18 11:16, Andreas Schneider wrote: > Normally you need to select "very fast gpu" that darktable runs more stuff > via > OpenCL and this bright a huge boost when processing. > > However this doesn't work for me right now. I've started to use the ROCm open > soruce stuff fro

Re: [darktable-dev] OpenCL issues

2018-10-30 Thread Andreas Schneider
On Monday, 29 October 2018 22:55:44 CET Aurélien Pierre wrote: > Hallo Heiko ! > > Very pleased to hear that (not the bug part, though). > > Did you try with smaller pictures ? Usually, darktable falls back to CPU > when there is not enough ressource available on the GPU. > > You can try : > >

Re: [darktable-dev] OpenCL issues

2018-10-30 Thread Heiko Bauke
Dear Ulrich, Am 30.10.18 um 07:07 schrieb Ulrich Pegelow: The empty string is not the default for opencl_device_priority, default is "*/!0,*/*/*". Please note that manual device selection by this parameter is only effective if opencl_scheduling_profile=default. I checked what is written to dar

Re: [darktable-dev] OpenCL issues

2018-10-29 Thread Ulrich Pegelow
Am 29.10.18 um 23:35 schrieb Heiko Bauke: This did not help.  Finally, I set explicitly opencl_device_priority=*/!0,*/*/* which is according to the documentation is the default.  Now the GPU is enabled except for the preview pixelpipe, as also indicated by the log: 0.208921 [opencl_priorit

Re: [darktable-dev] OpenCL issues

2018-10-29 Thread Heiko Bauke
Am 29.10.18 um 22:55 schrieb Aurélien Pierre: You can try : 1. the command *nvidia-smi* to see how the GPU RAM is used (if there is not enough vRAM available, you will see an OpenCL error code -4). 2. setting opencl_async_pixelpipe=true in darktablerc 3. setting opencl_mandatory_timeout >

Re: [darktable-dev] OpenCL issues

2018-10-29 Thread Aurélien Pierre
Hallo Heiko ! Very pleased to hear that (not the bug part, though). Did you try with smaller pictures ? Usually, darktable falls back to CPU when there is not enough ressource available on the GPU. You can try : 1. the command *nvidia-smi* to see how the GPU RAM is used (if there is not en

[darktable-dev] OpenCL issues

2018-10-29 Thread Heiko Bauke
Hi, I own a laptop with a low-end OpenCL capable graphics card. Usually I explicitly turn OpenCL support off for darktable. Today I enabled OpenCL support in darktable for some testing purposes. Starting darktable (current git master with some extensions not related to OpenCL) with the opti