I have just installed Manjaro 18.1.4 Juhraya and have no issues running
darktable latest git (master) with OpenCL on my nvidia.
This is the location on my system:
locate libnvidia-opencl
/usr/lib/libnvidia-opencl.so
/usr/lib/libnvidia-opencl.so.1
/usr/lib/libnvidia-opencl.so.418.113
Am Di., 24
I am using an older Nvidia processor and have installed:
nvidia-418xx-utils, opencl-headers and opencl-nvidia-418xx
None of the files shown on your 'locate' are seen on my system. The
cudas appear to have been installed with the utils.
My libopencl files appear to be located in
/opt/intel/op
I want to remove everything related to DT 2.6.3 to start clean and
fresh when DT3 will be out.
Which directories do I need to remove (and backup before hand)?
--
sknahT
vyS
darktable user mailing list
to unsubscribe se
On Mon, 23 Dec 2019 16:58:58 -0800
David Vincent-Jones wrote:
>The Manjaro/Arch package manager has installed all of the libopencl
>elements but apparently not in a location that dt is seeking them.
>Possibly this is as a result of my running the git version.
>
>So my simple question is, to which
* David Vincent-Jones [12-23-19 19:58]:
> The Manjaro/Arch package manager has installed all of the libopencl elements
> but apparently not in a location that dt is seeking them. Possibly this is
> as a result of my running the git version.
>
> So my simple question is, to which folder should I c
The Manjaro/Arch package manager has installed all of the libopencl
elements but apparently not in a location that dt is seeking them.
Possibly this is as a result of my running the git version.
So my simple question is, to which folder should I copy the libopencl
items? ... or does that not w
* David Vincent-Jones [12-23-19 18:23]:
> dt does not find my libopencl.so /1/2 despite the fact that it appears to in
> about 20 locations in my system.
>
> 0.277507 [opencl_init] opencl: 1
> 0.277512 [opencl_init] opencl_library: ''
> 0.277517 [opencl_init] opencl_memory_requirement: 768
> 0.27
dt does not find my libopencl.so /1/2 despite the fact that it appears
to in about 20 locations in my system.
0.277507 [opencl_init] opencl: 1
0.277512 [opencl_init] opencl_library: ''
0.277517 [opencl_init] opencl_memory_requirement: 768
0.277521 [opencl_init] opencl_memory_headroom: 300
0.2775
Am Mon, 23 Dec 2019 21:38:50 +0100
schrieb Аl Воgnеr :
> Am Mon, 23 Dec 2019 17:36:04 +0100
> schrieb Ulrich Pegelow :
>
> > Am 23.12.19 um 16:37 schrieb Аl Воgnеr:
> > >
> > > 7,393968 [dev_process_export] pixel pipeline processing took 0,608
> > > secs (0,915 CPU)
> >
> > This is blazingly fa
Am Mon, 23 Dec 2019 17:36:04 +0100
schrieb Ulrich Pegelow :
> Am 23.12.19 um 16:37 schrieb Аl Воgnеr:
> >
> > 7,393968 [dev_process_export] pixel pipeline processing took 0,608
> > secs (0,915 CPU)
>
> This is blazingly fast.
Did you see the log, there is not a lot of image processing compared
Is it just me or is there a considerable difference in time to access an
image in darkroom mode from lighttable when using
versus switch-view which I have set to .
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.orgopenSUSE Community Member
Am 23.12.19 um 16:37 schrieb Аl Воgnеr:
7,393968 [dev_process_export] pixel pipeline processing took 0,608 secs
(0,915 CPU)
This is blazingly fast.
Interesting is:
Spitzlicht-Rekonstruktion' on GPU, blended on GPU [export]
With the bench.srw it was calculated by the cpu. So the use of the c
Am Mon, 23 Dec 2019 11:22:57 +0100
schrieb Ulrich Pegelow :
> Am 23.12.19 um 10:22 schrieb Аl Воgnеr:
> > I tried "opencl_memory_headroom=100"
> >
> > 10,485934 [dev_process_export] pixel pipeline processing took 3,299
> > secs (8,980 CPU)
> >
> > So there is no big difference.
>
> Assuming tha
Hi all,
Is the version in git tagged 'release-3.0' identical with the 3.0
release?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
https://pgp.key-server.io/pks/lookup?search=0xD3C9A00E
mir datanom net
https://pgp.key-server.io/pks/lookup?search=0xE501F51C
* David Vincent-Jones [12-23-19 00:31]:
> Using the exposure module with a parametric mask to isolate the flesh/faces
> only used g, H, S and L. The image turns to B&W and there is no yellow
> mask display.
>
> current git version ... Manjaro/Arch
current git version is not specific, git8.7
regarding tiling look at Ulrich's answer, I didn't notice it while
looking at your log.
Regards,
Holger
On 12/23/19 11:36 AM, Holger Wünsche wrote:
I tried "opencl_memory_headroom=100"
[...]
So there is no big difference.
I just noticed, the tiling is only happening for Jochen and not for
> I tried "opencl_memory_headroom=100"
[...]
> So there is no big difference.
I just noticed, the tiling is only happening for Jochen and not for you. In
that case this option does not change a whole lot, because the memory is not a
problem for you as far as I can see (only skimmed the log, so
Am 23.12.19 um 10:22 schrieb Аl Воgnеr:
I tried "opencl_memory_headroom=100"
10,485934 [dev_process_export] pixel pipeline processing took 3,299
secs (8,980 CPU)
So there is no big difference.
Assuming that the history you provided is a typical one then there is
only one direction where Open
Am Mon, 23 Dec 2019 09:45:43 +0100
schrieb Аl Воgnеr :
> So should opencl_memory_headroom be a small value and 300 is fine?
> 3000 is the half memory of my GPU.
I tried "opencl_memory_headroom=100"
10,485934 [dev_process_export] pixel pipeline processing took 3,299
secs (8,980 CPU)
So there is
Am Mon, 23 Dec 2019 09:26:46 +0100
schrieb Ulrich Pegelow :
> Also note that in your case there is are a few modules which are
> processed on the CPU:
>
> 6,983092 [dev_pixelpipe] took 0,096 secs (0,997 CPU) processed
> `Spitzlicht-Rekonstruktion' on CPU, blended on CPU [export]
> 7,069714 [dev
Also note that in your case there is are a few modules which are
processed on the CPU:
6,983092 [dev_pixelpipe] took 0,096 secs (0,997 CPU) processed
`Spitzlicht-Rekonstruktion' on CPU, blended on CPU [export]
7,069714 [dev_pixelpipe] took 0,087 secs (1,365 CPU) processed
`Entrastern' on CPU,
opencl_memory_headroom tells darktable how much memory to leave for the rest of
the system (so less is better for performance), at least that is how I
understand it. Looking at the memory usage from Xorg a realistic value seems to
be 650-700MB. I would not expect setting it to these numbers woul
22 matches
Mail list logo
