#682397 darktable: recommend opencl package

Package:
darktable
Source:
darktable
Description:
virtual lighttable and darkroom for photographers
Submitter:
Sladjan
Date:
2024-02-20 01:54:03 UTC
Severity:
wishlist
#682397#5
Date:
2012-07-22 12:00:33 UTC
From:
To:
Dear Maintainer,

I have a Nvidia OpenCL capable card, and Darktable provides an option to use
OpenCL also.
I just installed the nvidia binary drivers, expecting OpenCL to work, after
installing Darktable. But I had to install the nvidia-opencl-icd package too,
to get the feature working.
It would be nice if Darktable installed this as a recommended package
automatically.

Regards,
Sladjan

#682397#10
Date:
2012-07-23 14:17:31 UTC
From:
To:
Sladjan <sladjanri@gmail.com> writes:

Hi Sladjan;

Since that package is non-free, Debian policy forbids recommending it.
It could be a suggests, but I'm not sure there is much advantage to
that. If we did add a suggests then I suppose we would want something
for ati and intel as well.

d

#682397#15
Date:
2012-07-25 11:56:49 UTC
From:
To:
It might work to build darktable against

http://packages.debian.org/sid/ocl-icd-opencl-dev

which advertises the ability to be be an icd for amd or intel.

Currently this would need a patch to use the packaged headers instead of
the embedded ones.

#682397#20
Date:
2013-06-07 06:32:05 UTC
From:
To:
Darktable already builds for OpenCL support in Debian. This is what I
get after installing ocl-icd-libopencl1:

anarcat@marcos:~$ darktable -d opencl
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 0
[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_avoid_atomics: 0
[opencl_init] opencl_omit_whitebalance: 0
[opencl_init]
[opencl_init] trying to load opencl library: '<system default>'
[opencl_init] opencl library 'libOpenCL' found on your system and loaded
[opencl_init] could not get platforms: -1001
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.

It says not available because there are no OpenCL libraries for Intel on
Debian, because they are non-free software (not even distributable). And
anyways, i would need 1GB+ of video RAM, which I really don't have here.

See also:

http://lists.debian.org/debian-devel/2012/06/msg01108.html

A.

#682397#25
Date:
2024-02-19 08:00:01 UTC
From:
To:
Hi,

10 years later, the situation doesn't have changed much.  At least for
AMD and NVidua GPUs, you need vendor packages from external sources to
use OpenCL and get a performance gain.  In the current state, the
rusticl OpenCL implementation, which is part of Mesa, seems to lack
features and/or is still too buggy.  At least it can not be used for
darktable and AMD support has to be enabled by setting an environment
variable.

This is a general issue that the darktable package can not change.  So
I propose to close this bug.

Regards,
Tino

#682397#28
Date:
2024-02-19 08:00:01 UTC
From:
To:
Hi,

10 years later, the situation doesn't have changed much.  At least for
AMD and NVidua GPUs, you need vendor packages from external sources to
use OpenCL and get a performance gain.  In the current state, the
rusticl OpenCL implementation, which is part of Mesa, seems to lack
features and/or is still too buggy.  At least it can not be used for
darktable and AMD support has to be enabled by setting an environment
variable.

This is a general issue that the darktable package can not change.  So
I propose to close this bug.

Regards,
Tino

#682397#33
Date:
2024-02-20 01:41:33 UTC
From:
To:
Tino Mettler via Pkg-phototools-devel
<pkg-phototools-devel@alioth-lists.debian.net> writes:

I wonder if having the bug helps people see that there is no point in
filing more bugs on the same topic. I guess we can always leave the next
OpenCL bug open if that occurs.