Hi Martin,
thank you for this piece of advice.
Parafin already gave me the link to the workaround for Big Sur: it works
well with dt 3.2.1.
I took a look into the opencl settings and found the following:
0.179000 [opencl_init] found 1 platform
0.213121 [opencl_init] found 2 devices
0.213180 [opencl_init] discarding CPU device 0 `Intel(R) Core(TM)
i5-7500 CPU @ 3.40GHz'.
0.213198 [opencl_init] device 1 `AMD Radeon Pro 570 Compute Engine'
supports image sizes of 16384 x 16384
0.213201 [opencl_init] device 1 `AMD Radeon Pro 570 Compute Engine'
allows GPU memory allocations of up to 1024MB
[opencl_init] device 1: AMD Radeon Pro 570 Compute Engine
So after discarding the CPU device and program compiling only one opencl
device ist left:
0.261312 [opencl_init] OpenCL successfully initialized.
0.261314 [opencl_init] here are the internal numbers and names of OpenCL
devices available to darktable:
0.261315 [opencl_init] 0 'AMD Radeon Pro 570 Compute Engine'
0.261340 [opencl_init] FINALLY: opencl is AVAILABLE on this system.
I think that for my hardware the default setting is adequate:
opencl_device_priority=*/!0,*/*/*
It results in
10,522398 [pixelpipe_process] [thumbnail] using device 0
10,774635 [pixelpipe_process] [preview] using device -1
18,358848 [pixelpipe_process] [full] using device 0
I don't estimate dt performance as too slow (now that opencl runs on
BigSur), I am pleased. As I can't anyway compare directly to my former
Linux environment I don't pay any attention to half a second more or
less processing time when I e.g. denoise (profile) a zoomed in image.
I'm looking forward to dt 3.4.
Have a good time
Volker
Am 22.11.20 um 20:22 schrieb Martin Straeten:
For osx it’s very important to tweak opencl preferences in
.config/darktable/darktablerc.
I found my macbookpro 16 gives best performance if used in opencl mode
‚default‘ with forcing full pixelpipe being processed by amd gpu (1) and
preview pixel pipe with cpu (-1)
(opencl_device_priority=1,0,*/!1,!0,*/1,0,*/0,*/*) in combination with
performance mode (new with upcoming 3.4) and reduced resolution of
preview image. The other opencl modes prioritized the on chip gpu (0) at
cost of speed ...
You can evaluate the processing time and used gpu device runnig
darktable from terminal:
darktable -d perf -d opencl | grep -e'processing took' -e'using device'
Happy tweaking ...
To enable opencl on osx 11 use the workaround described at
https://github.com/darktable-org/darktable/issues/6918#issuecomment-727595566
<https://github.com/darktable-org/darktable/issues/6918#issuecomment-727595566>
Am 22.11.2020 um 19:05 schrieb Volker Lenhardt <volker.lenha...@uni-due.de>:
Hi Marc,
when I started dt two years ago for the first time on my new
iMac-5k-screen, in full screen as I had been used to on my former HD
screen, I was shocked by the slow performance. My first idea was to
blame Apple. But when I did realize that full screen even extended the
pixel size of my pictures I changed the mode of my operation. I reduced
both the dt window and my distance from the screen, put my reading
glasses on and eventually got a decent dt performance.
The point is that you shouldn't so much pay your attention to higher
resolution but to more free screen space. What's the use of a 5k screen
when you remove yourself from it so that it looks the same as a HD
screen? We don't talk of UHD movies, do we.
All the best
Volker
Am 22.11.20 um 16:04 schrieb Marc Cabuy:
Hi Volker,
Further to that opencl issue, that slow response time you had/have may
be related to the high resolution display. That's my experience with
dt 3.2.1 on Windows. I now reduce my display resolution prior to
editing (feels stupid, I know). See also here:
https://www.mail-archive.com/darktable-user@lists.darktable.org/msg10305.html.
I would be interested to hear whether that is an issue too on MAC.
Marc.
-----Oorspronkelijk bericht-----
Van: Volker Lenhardt [mailto:volker.lenha...@uni-due.de]
Verzonden: zondag 22 november 2020 12:26
Aan: darktable-user@lists.darktable.org
Onderwerp: [darktable-user] No Opencl on macOS 11 (Big Sur)
After upgrading to macOS 11 (Big Sur) I experience very long response
behavior of DT on my 5K screen (iMac 2017), about at least double
compared to the already slow performance under macOS Catalina.
Especially denoising is nerve-racking.
I see that OpenCL isn't supported any more. There is Metal instead. Is
there a way out to sufferable working conditions?
Stay healthy
Volker
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to
darktable-user+unsubscr...@lists.darktable.org
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
