[darktable-dev] Fwd: Re: [darktable-org/rawspeed] Regression: huffmantable is broken. (#100) rs-check.py 0.0.3 DRAFT

2018-10-30 Thread Michael Fritze
Ok, I attached my script. Version 0.0.3 DRAFT Required Parameter: path to folder containing raw files optional Parameter: -m: move files with errors to a sub dir It generates 3 report files in the picture folder: a log file, a list of ok files and a list of buggy files. Does not dive into sub di

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