One idea: please try what happens if you set opencl_use_pinned_memory to
TRUE. You can find this config variable in
$HOME/.config/darktable/darktablerc. In addition please also test with
opencl_async_pixelpipe set to TRUE.
Ulrich
Am 09.09.2016 um 17:25 schrieb Aurélien PIERRE:
OpenCL config :
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ''
[opencl_init] opencl_memory_requirement: 768
[opencl_init] opencl_memory_headroom: 300
[opencl_init] opencl_device_priority: '*/!0,*/*/*'
[opencl_init] opencl_size_roundup: 16
[opencl_init] opencl_async_pixelpipe: 0
[opencl_init] opencl_synch_cache: 0
[opencl_init] opencl_number_event_handles: 25
[opencl_init] opencl_micro_nap: 1000
[opencl_init] opencl_use_pinned_memory: 0
[opencl_init] opencl_use_cpu_devices: 0
[opencl_init] opencl_avoid_atomics: 0
[opencl_init] opencl_omit_whitebalance: 0
Any clues ?
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to [email protected]
