Re: [darktable-user] Test
Thank you. I signed up immediately. Am 19.10.23 um 17:24 schrieb Richard Hobday: On 19/10/2023 15:03, Volker Lenhardt wrote: I haven't got any postings for weeks. So I try this one. Greetings Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org Possibly because many users have switched to: https://discuss.pixls.us/c/software/darktable/19 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
Re: [darktable-user] Test
Good news. Works. Sorry for being tedious. Volker Am 19.10.23 um 16:03 schrieb Volker Lenhardt: I haven't got any postings for weeks. So I try this one. Greetings 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
Re: [darktable-user] xmp metadata and language
That's very interesting, and it makes sense. Thanks Volker Am 30.09.22 um 21:37 schrieb Top Rock Photography: Not entirely certain of this, but here is my understanding of the language tag and the title/description (etc.) fields. There can be several title/description fields; one for each language. A language field set as “default” means, “Use this title/description when no language is given by the viewer, or if the viewer's preferred language is not present.” Any field with a specified language means, “use this title/description if the viewer's preferred language matches this one.” E.g., if I have English (non-specific) language title listed as, “Bread & Wine Festival”, French language title as, « La fête du pain et du vin », and default language title as, “Trinidad September Celebration”, then anyone with their language set to anything but French or English will see, “Trinidad September Celebration,” while someone with their language set to English or French will see the appropriate title, (and the French will see the accent in « fête »). This will mean that, if I only had one language title set up, default, with, « La fête du pain et du vin », and the circumflex shows up as tofu, changing my language to French is not necessarily going to make the ‘ê’ suddenly show up. Why Gimp is showing an empty string is that you had a default language title, in Arcen, then /added/ a second language title in Arcen-Schlossgärten to the file, without adding the new title. So when your viewer language is set to, “Arcen. Schlossgärten,” Gimp correctly shows you the appropriate title field, which is empty, instead of the “default/Arcen” title field, in Arcen-Schlossgärten language. So one wants to change the metadata encoding of the XMP metadata to UTF-8 so that one gets the accents instead of tofu, (which, I understand, is possible for XMP data but not for IPTC data), but also add a title in Arcen-Schlossgärten, (or change the default language from “default:Arcen”, to “default:Arcen-Schlossgärten”). IIRC,the default encoding for XMP data is, indeed, UTF-8, which is more than adequate for most non-CJK languages —which need UTF-16-cs, I understand,— and that the default —and only— encoding for IPTC is Latin-1. I may be wrong on this. The long and short is that some accented characters may not show up in IPTC title fields, and adding a title language in metadata will only show up if the new title is also added along with the language. Please, others correct what I may have incorrect here. Sincerely, Karim Hosein Top Rock Photography 754.999.1652 On Thu, 29 Sept 2022 at 13:14, Volker Lenhardt mailto:volker.lenha...@uni-due.de>> wrote: But I'm sorry, but to include iptc tags doesn't seem to have any effect on the xmp tags. I do get xmp.dc.title and xmp.dc.description, but gimp shows an empty string whenever there is a special character within. I'm not sure if it is a gimp problem, but I cannot find the trick to tell it to use utf-8 with metadata. I hope that dt exports them as utf-8. 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
Re: [darktable-user] Export xmp metadata with correct lang
Relief! There was a bug in gimp 2.10.22. I updated to 2.10.32 and all is easy. Am 29.09.22 um 20:02 schrieb Šarūnas: On 9/29/22 13:13, Volker Lenhardt wrote: But I'm sorry, but to include iptc tags doesn't seem to have any effect on the xmp tags. I do get xmp.dc.title and xmp.dc.description, but gimp shows an empty string whenever there is a special character within. I'm not sure if it is a gimp problem, but I cannot find the trick to tell it to use utf-8 with metadata. I hope that dt exports them as utf-8. You can check exported images in Finder - Command I (File>get info). In my quick test on Monterey it does show accented characters in Title and Description, which where entered dt. Gimp does show them as well. macOS is the default US English install, no International settings. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Export xmp metadata with correct lang
Thank you, Patrick and Šarūnas, for your nice help. My locale is de_DE and it seems to be alright with dt, for the check with finder-info shows that all the special characters are there in the metadata. I will have to find the bug in gimp. To my shame I have to admit that the bug of forgetting the formula in the preferences dialog sits in front of the screen. I found out that I have to leave the formula input field first before saving. This explains that when I had inserted 2 metadata fields only the first one kept the formula. And when I later tested with only one field I could never succeed. Best regards Volker Am 29.09.22 um 20:02 schrieb Šarūnas: On 9/29/22 13:13, Volker Lenhardt wrote: But I'm sorry, but to include iptc tags doesn't seem to have any effect on the xmp tags. I do get xmp.dc.title and xmp.dc.description, but gimp shows an empty string whenever there is a special character within. I'm not sure if it is a gimp problem, but I cannot find the trick to tell it to use utf-8 with metadata. I hope that dt exports them as utf-8. You can check exported images in Finder - Command I (File>get info). In my quick test on Monterey it does show accented characters in Title and Description, which where entered dt. Gimp does show them as well. macOS is the default US English install, no International settings. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Export xmp metadata with correct lang
You are right, Patrick, the manual has grown into a really fine tool. That's where I started in the first place. But I'm sorry, but to include iptc tags doesn't seem to have any effect on the xmp tags. I do get xmp.dc.title and xmp.dc.description, but gimp shows an empty string whenever there is a special character within. I'm not sure if it is a gimp problem, but I cannot find the trick to tell it to use utf-8 with metadata. I hope that dt exports them as utf-8. By the way, I cannot set formulas to manually inserted iptc metadata any more. They are accepted to be saved, but they are not executed and don't show, when I reopen the preferences, even "=" is lost. I use dt 4.0.1 on macos Monterey 12.6. My gimp is 2.10.22. To improve my workflow I need gimp with these metadata. To abstain from special characters would be a somewhat ugly solution. Many thanks Volker Am 29.09.22 um 14:30 schrieb Patrick Shanahan: * Volker Lenhardt [09-29-22 06:19]: I want to export my images from dt as jpeg containing xmp metadata, especially Title and Description, e.g. 'Arcen' as Matadata.Title. If I open these files with gimp I find the contents of Xmp.dc.title as 'lang="x-default" Arcen'. I am German, and I want to use umlauts, too. So my Metadata.Title should be 'Arcen. Schlossgärten'. But in this case the exported Xmp.dc.title remains empty. How can I set the correct lang for the export from dt? in the fine manual: https://docs.darktable.org/usermanual/development/en/module-reference/utility-modules/shared/export/#metadata-preferences darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Export xmp metadata with correct lang
I want to export my images from dt as jpeg containing xmp metadata, especially Title and Description, e.g. 'Arcen' as Matadata.Title. If I open these files with gimp I find the contents of Xmp.dc.title as 'lang="x-default" Arcen'. I am German, and I want to use umlauts, too. So my Metadata.Title should be 'Arcen. Schlossgärten'. But in this case the exported Xmp.dc.title remains empty. How can I set the correct lang for the export from dt? Greetings Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] No Opencl on macOS 11 (Big Sur)
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 : 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 m
Re: [darktable-user] No Opencl on macOS 11 (Big Sur)
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
Re: [darktable-user] No Opencl on macOS 11 (Big Sur)
OT: After 20 years with Linux I switched to Apple two years ago. Living now with some cons I experience sufficiently enough pros to stay by it. After all there's a Linux VBox :-) Am 22.11.20 um 12:47 schrieb Matt Maguire: Apart from blowing away Big Sur and installing Linux? Not sure... I'm still on Mojave, and thinking this will probably be my last Mac... darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] No Opencl on macOS 11 (Big Sur)
Thank you. The workaround helps. I am relieved. Have a good time. Am 22.11.20 um 12:36 schrieb parafin: https://github.com/darktable-org/darktable/issues/6918 On Sun, 22 Nov 2020 12:25:55 +0100 Volker Lenhardt wrote: 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
[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
Re: [darktable-user] dt 3.0.2 on German macOS Catalina with some Russian translations
Am 27.05.20 um 18:48 schrieb Jack Bowling: Display encoding is controlled by the "preserve chrominance" setting in the Look tab of filmicRGB. Turning this off or selecting on of the other settings can have a large effect on some images, not much effect on others. You need to experiment with it. Jack That's interesting. I'll give it a try. Volker On 2020-05-27 6:46 a.m., Volker Lenhardt wrote: Am 27.05.20 um 14:45 schrieb parafin: Try explicitly selecting (changing) a language in preferences. Thank you, that did the trick. But still I'm looking for a "display encoding" module in vain. Volker On Wed, 27 May 2020 14:25:50 +0200 Volker Lenhardt wrote: Can you reproduce that there are some Russion translations in dt 3.0.2 on a German macOS Catalina? In the darkroom the image history includes a module "Bывод на монитор", which I think is "Display encoding", but in the list of modules I cannot find it, neither in English nor Russian nor German. One of the modules is called "Pаздельное тонирование" instead of "Split-toning" or the German "Teiltonung". Interestingly the contents are correctly in German. The "Crop and rotate" module is called "Zuschneiden und drehen" as it should be. But the columns are titled "Oбщие" and "Поля". I haven't scanned all of the modules so far, but the occurrence of the Russian phrases seems to be limited to new items. But when there is no German translation available, why the Russian one instead of the English original? If I doubleclick on one of the history entries a message appears for a very short moment: "Oперация выполня́ется". Very reassuring. The operation is performed. 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 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
Re: [darktable-user] dt 3.0.2 on German macOS Catalina with some Russian translations
Am 27.05.20 um 14:45 schrieb parafin: Try explicitly selecting (changing) a language in preferences. Thank you, that did the trick. But still I'm looking for a "display encoding" module in vain. Volker On Wed, 27 May 2020 14:25:50 +0200 Volker Lenhardt wrote: Can you reproduce that there are some Russion translations in dt 3.0.2 on a German macOS Catalina? In the darkroom the image history includes a module "Bывод на монитор", which I think is "Display encoding", but in the list of modules I cannot find it, neither in English nor Russian nor German. One of the modules is called "Pаздельное тонирование" instead of "Split-toning" or the German "Teiltonung". Interestingly the contents are correctly in German. The "Crop and rotate" module is called "Zuschneiden und drehen" as it should be. But the columns are titled "Oбщие" and "Поля". I haven't scanned all of the modules so far, but the occurrence of the Russian phrases seems to be limited to new items. But when there is no German translation available, why the Russian one instead of the English original? If I doubleclick on one of the history entries a message appears for a very short moment: "Oперация выполня́ется". Very reassuring. The operation is performed. 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
[darktable-user] dt 3.0.2 on German macOS Catalina with some Russian translations
Can you reproduce that there are some Russion translations in dt 3.0.2 on a German macOS Catalina? In the darkroom the image history includes a module "Bывод на монитор", which I think is "Display encoding", but in the list of modules I cannot find it, neither in English nor Russian nor German. One of the modules is called "Pаздельное тонирование" instead of "Split-toning" or the German "Teiltonung". Interestingly the contents are correctly in German. The "Crop and rotate" module is called "Zuschneiden und drehen" as it should be. But the columns are titled "Oбщие" and "Поля". I haven't scanned all of the modules so far, but the occurrence of the Russian phrases seems to be limited to new items. But when there is no German translation available, why the Russian one instead of the English original? If I doubleclick on one of the history entries a message appears for a very short moment: "Oперация выполня́ется". Very reassuring. The operation is performed. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] How to set export file name preference
Hi and Happy Easter to all of you. I want to thank thokster for his very good advice (in a personal conversation) that helped to clear my brains. Now that I reorganize my photo filing system I can easily use $(FILE_FOLDER) to get what I want. It's my lot to think in a too complicated way. Volker Am 09.04.20 um 20:30 schrieb Volker Lenhardt: I use to export my images to jpg with a standardized file name: $(FILE_NAME:4)-???_$(EXIF_YEAR)-$(DESCRIPTION) The "???" is a placeholder for a part of the path, which I type in for the time being, but which I want to find an automized way to replace, too. One after the other. How can I set the preference from the default "$(FILE_NAME)" to my user defined string? I couldn‘t find a way, so I thought about some lua script. Lua seems to be somewhat simple, but I find the lua API not so easy to look through. Anyhow I find "events.intermediate-export-image.callback" promising to intercept and change the filename, but how do I proceed? My skills are on the scale of pre-beginners for now. I haven’t got further than scanning through existing lua scripts to catch a glimpse of what to do, but I‘m confident in raising my learning curve soon. Please set me on the track. 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] How to set export file name preference
I use to export my images to jpg with a standardized file name: $(FILE_NAME:4)-???_$(EXIF_YEAR)-$(DESCRIPTION) The "???" is a placeholder for a part of the path, which I type in for the time being, but which I want to find an automized way to replace, too. One after the other. How can I set the preference from the default "$(FILE_NAME)" to my user defined string? I couldn‘t find a way, so I thought about some lua script. Lua seems to be somewhat simple, but I find the lua API not so easy to look through. Anyhow I find "events.intermediate-export-image.callback" promising to intercept and change the filename, but how do I proceed? My skills are on the scale of pre-beginners for now. I haven’t got further than scanning through existing lua scripts to catch a glimpse of what to do, but I‘m confident in raising my learning curve soon. Please set me on the track. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Scaling the font size of watermarks?
I use watermarks as foto captions within the bottom margins. It‘s tedious to rescale the watermark each time I change the text making it shorter or longer. If I select the watermark‘s text font from the dialog box there is an option to choose the font size, too. But this font size seems to be neglected in the watermark module. How can I use the font size as the scaling target instead of the whole text box? Is this possible at all? I used to apply a gimp script-fu as a post-processing method to create the margins and captions. In this macro I calculate the adequate font size according to the picture size. Is there a way to manage it with LUA? I don‘t know anything about LUA, but I‘d give it a try. I‘d like to keep all processes in one box, i.e. DT. All the best Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Many thanks to all of you for your help. Nevertheless my performance
problems persist. To set opencl_use_pinned_memory=TRUE yields no
perceivable improvement.
Before I reinstall DT I'll try and install a mouse to see if there are
some differences in behavior. If I need more help I'll open a new thread.
Volker
Am 03.12.18 um 18:48 schrieb Ulrich Pegelow:
I don't see anything specifically broken here. Let's take for example
the snippet from the quote below.
Time spent in OpenCL kernels including memory I/O is 0.055 seconds.
Total time in pixelpipe is 0.123 seconds. There is a bit of overhead
here but that's not dramatical. You may try to set
opencl_use_pinned_memory=TRUE which might improve this a bit.
Overall the time spent in this sections is between timestamps 130.658s
and 130,781 which matches the figures above.
I'd say if you are losing performance it's probably not in the pixelpipe
and likely not OpenCL related. That also fits to your observation that
you don't see a difference with/without OpenCL.
Ulrich
Am 03.12.18 um 18:20 schrieb Volker Lenhardt:
130,658562 [pixelpipe_process] [full] using device 0
130,660026 [dev_pixelpipe] took 0,001 secs (0,002 CPU) initing base
buffer [full]
130,680802 [dev_pixelpipe] took 0,021 secs (0,020 CPU) processed
`Raw-Schwarz-/Weißpunkt' on GPU, blended on GPU [full]
130,682650 [dev_pixelpipe] took 0,002 secs (0,002 CPU) processed
`Weißabgleich' on GPU, blended on GPU [full]
130,684399 [dev_pixelpipe] took 0,002 secs (0,001 CPU) processed
`Spitzlicht-Rekonstruktion' on GPU, blended on GPU [full]
130,700017 [dev_pixelpipe] took 0,016 secs (0,013 CPU) processed
`Entrastern' on GPU, blended on GPU [full]
130,704482 [dev_pixelpipe] took 0,004 secs (0,004 CPU) processed
`Basiskurve' on GPU, blended on GPU [full]
130,708880 [dev_pixelpipe] took 0,004 secs (0,004 CPU) processed
`Eingabefarbprofil' on GPU, blended on GPU [full]
130,717590 [dev_pixelpipe] took 0,009 secs (0,007 CPU) processed
`Schärfen' on GPU, blended on GPU [full]
130,724571 [dev_pixelpipe] took 0,007 secs (0,006 CPU) processed
`Ausgabefarbprofil' on GPU, blended on GPU [full]
130,781679 [dev_pixelpipe] took 0,057 secs (0,078 CPU) processed
`Gamma' on CPU, blended on CPU [full]
130,781716 [opencl_profiling] profiling device 0 ('AMD Radeon Pro 570
Compute Engine'):
130,781720 [opencl_profiling] spent 0,0005 seconds in [Write Image
(from host to device)]
130,781723 [opencl_profiling] spent 0,0001 seconds in rawprepare_1f
130,781740 [opencl_profiling] spent 0,0002 seconds in whitebalance_1f
130,781742 [opencl_profiling] spent 0,0002 seconds in highlights_1f_clip
130,781744 [opencl_profiling] spent 0,0004 seconds in ppg_demosaic_green
130,781746 [opencl_profiling] spent 0,0005 seconds in
ppg_demosaic_redblue
130,781749 [opencl_profiling] spent 0,0002 seconds in border_interpolate
130,781764 [opencl_profiling] spent 0,0120 seconds in
interpolation_resample
130,781766 [opencl_profiling] spent 0,0022 seconds in basecurve_lut
130,781768 [opencl_profiling] spent 0,0017 seconds in colorin_unbound
130,781770 [opencl_profiling] spent 0,0019 seconds in sharpen_hblur
130,781772 [opencl_profiling] spent 0,0022 seconds in sharpen_vblur
130,781774 [opencl_profiling] spent 0,0025 seconds in sharpen_mix
130,781777 [opencl_profiling] spent 0,0036 seconds in colorout
130,781779 [opencl_profiling] spent 0,0270 seconds in [Read Image
(from device to host)]
130,781781 [opencl_profiling] spent 0,0550 seconds totally in command
queue (with 0 events missing)
130,781789 [dev_process_image] pixel pipeline processing took 0,123
secs (0,137 CPU)
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
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 03.12.18 um 17:58 schrieb Ulrich Pegelow: Two observations: 1) the total time that darktable reports per pixelpipe lies in the range of 0.15s. That's not particularly fast, given your very undemanding history stack, but it's also not extremely slow either. What wonders me is your observation that the time spent in pixelpipe does not sum up to your wall time with a discrepancy of a factor 10. There might be other elements eating up performance on your system... 2) you don't report profiling info per OpenCL kernel. This is normally printed along the other information when running with '-d opencl -d perf'. Did you happen to set opencl_number_event_handles to zero? You should set this to a reasonable high value like 25. As I found that opencl was running I wanted to keept the output shorter. I repeated the procedure this time with -d opencl and with the arrow keys kept pressed while scrolling. The total time was reduced to 35 seconds. This is the output: macspinne:~ volker$ /Applications/darktable.app/Contents/MacOS/darktable -d opencl -d perf (process:1223): GLib-GObject-CRITICAL **: 18:10:34.841: g_object_set: assertion 'G_IS_OBJECT (object)' failed 0.150148 [opencl_init] opencl related configuration options: 0.150168 [opencl_init] 0.150171 [opencl_init] opencl: 1 0.150174 [opencl_init] opencl_library: '' 0.150191 [opencl_init] opencl_memory_requirement: 768 0.150196 [opencl_init] opencl_memory_headroom: 500 0.150199 [opencl_init] opencl_device_priority: '*/!0,*/*/*' 0.150202 [opencl_init] opencl_mandatory_timeout: 200 0.150207 [opencl_init] opencl_size_roundup: 16 0.150209 [opencl_init] opencl_async_pixelpipe: 0 0.150211 [opencl_init] opencl_synch_cache: 0 0.150214 [opencl_init] opencl_number_event_handles: 25 0.150217 [opencl_init] opencl_micro_nap: 1000 0.150219 [opencl_init] opencl_use_pinned_memory: 0 0.150222 [opencl_init] opencl_use_cpu_devices: 0 0.150224 [opencl_init] opencl_avoid_atomics: 1 0.150226 [opencl_init] 0.150715 [opencl_init] found opencl runtime library '/System/Library/Frameworks/OpenCL.framework/Versions/Current/OpenCL' 0.150763 [opencl_init] opencl library '/System/Library/Frameworks/OpenCL.framework/Versions/Current/OpenCL' found on your system and loaded 0.150768 [opencl_init] found 1 platform 0.156224 [opencl_init] found 2 devices 0.156305 [opencl_init] discarding CPU device 0 `Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz'. 0.156320 [opencl_init] device 1 `AMD Radeon Pro 570 Compute Engine' supports image sizes of 16384 x 16384 0.156323 [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 GLOBAL_MEM_SIZE: 4096MB MAX_WORK_GROUP_SIZE: 256 MAX_WORK_ITEM_DIMENSIONS: 3 MAX_WORK_ITEM_SIZES: [ 256 256 256 ] DRIVER_VERSION: 1.2 (Oct 16 2018 21:18:14) DEVICE_VERSION: OpenCL 1.2 0.157070 [opencl_init] options for OpenCL compiler: -cl-fast-relaxed-math -DUNKNOWN=1 -I/Applications/darktable.app/Contents/Resources/share/darktable/kernels 0.158483 [opencl_init] compiling program `demosaic_ppg.cl' .. 0.160661 [opencl_load_program] loaded cached binary program from file `/Users/volker/.cache/darktable/cached_kernels_for_AMDRadeonPro570ComputeEngine/demosaic_ppg.cl.bin' 0.160668 [opencl_load_program] successfully loaded program from `/Applications/darktable.app/Contents/Resources/share/darktable/kernels/demosaic_ppg.cl' 0.161009 [opencl_build_program] successfully built program 0.161017 [opencl_build_program] BUILD STATUS: 0 0.161020 BUILD LOG: 0.161022 0.161029 [opencl_init] compiling program `atrous.cl' .. 0.162101 [opencl_load_program] loaded cached binary program from file `/Users/volker/.cache/darktable/cached_kernels_for_AMDRadeonPro570ComputeEngine/atrous.cl.bin' 0.162108 [opencl_load_program] successfully loaded program from `/Applications/darktable.app/Contents/Resources/share/darktable/kernels/atrous.cl' 0.162206 [opencl_build_program] successfully built program 0.162213 [opencl_build_program] BUILD STATUS: 0 0.162216 BUILD LOG: 0.162218 0.162224 [opencl_init] compiling program `basic.cl' .. 0.165420 [opencl_load_program] loaded cached binary program from file `/Users/volker/.cache/darktable/cached_kernels_for_AMDRadeonPro570ComputeEngine/basic.cl.bin' 0.165428 [opencl_load_program] successfully loaded program from `/Applications/darktable.app/Contents/Resources/share/darktable/kernels/basic.cl' 0.165836 [opencl_build_program] successfully built program 0.165843 [opencl_build_program] BUILD STATUS: 0 0.165846 BUILD LOG: 0.165848 0.165855 [opencl_init] compiling program `blendop.cl' .. 0.168005 [opencl_load_program] loaded cached binary program from file `/Users/volker/.cache/darktable/cached_kernels_for_AMDRadeonPro570ComputeEngine/blendop.cl.bin' 0.168013 [opencl_load_program] successfully loaded program from
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 03.12.18 um 12:11 schrieb Volker Lenhardt: Am 02.12.18 um 17:12 schrieb Volker Lenhardt: There's still the problem of too slow response with shifting a zoomed in image to have e.g. a quick look at the corners to detect chromatic aberration. And cropping an image is slow, too. All of this rating is compared to what I was used to under Linux with less confined equipment. I made another test using the command+arrow_keys to scroll once around a zoomed in image. It is a good deal faster than using the trackpad. I scrolled from the middle to the upper border, then to the left border, down to the bottom, then to the right and up again and back to the middle (i.e. once around the outer part of the image). Counted by the output of "darktable -d perf" it took about 5 (6 CPU) seconds. In real time I measured 50 seconds. That's no fun. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 02.12.18 um 17:12 schrieb Volker Lenhardt: There's still the problem of too slow response with shifting a zoomed in image to have e.g. a quick look at the corners to detect chromatic aberration. And cropping an image is slow, too. All of this rating is compared to what I was used to under Linux with less confined equipment. Below is the output of "darktable -d perf", while I 1. Start DT and open the selected image in darkroom: (process:697): GLib-GObject-CRITICAL **: 10:20:10.648: g_object_set: assertion 'G_IS_OBJECT (object)' failed (darktable-bin:697): GLib-GObject-WARNING **: 10:20:10.855: invalid cast from 'GtkMenuBar' to 'GtkWindow' (darktable-bin:697): Gtk-CRITICAL **: 10:20:10.855: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed wait time 0,141157s 26,167340 [dev] took 0,119 secs (0,107 CPU) to load the image. 27,202603 [dev] took 0,000 secs (0,000 CPU) to load the image. 27,253541 [dev_pixelpipe] took 0,008 secs (0,019 CPU) initing base buffer [full] 27,271309 [dev_pixelpipe] took 0,018 secs (0,015 CPU) processed `Raw-Schwarz-/Weißpunkt' on GPU, blended on GPU [full] 27,277290 [dev_pixelpipe] took 0,006 secs (0,005 CPU) processed `Weißabgleich' on GPU, blended on GPU [full] 27,280500 [dev_pixelpipe] took 0,003 secs (0,003 CPU) processed `Spitzlicht-Rekonstruktion' on GPU, blended on GPU [full] 27,322458 [dev_pixelpipe] took 0,042 secs (0,039 CPU) processed `Entrastern' on GPU, blended on GPU [full] 27,345844 [dev_pixelpipe] took 0,022 secs (0,054 CPU) processed `Basiskurve' on GPU, blended on GPU [full] 27,352620 [dev_pixelpipe] took 0,005 secs (0,005 CPU) processed `Eingabefarbprofil' on GPU, blended on GPU [full] 27,364456 [dev_pixelpipe] took 0,012 secs (0,012 CPU) processed `Schärfen' on GPU, blended on GPU [full] 27,375174 [dev_pixelpipe] took 0,011 secs (0,010 CPU) processed `Ausgabefarbprofil' on GPU, blended on GPU [full] 27,484298 [dev_pixelpipe] took 0,109 secs (0,207 CPU) processed `Gamma' on CPU, blended on CPU [full] 27,484362 [dev_process_image] pixel pipeline processing took 0,239 secs (0,371 CPU) 28,359220 [dev_pixelpipe] took 0,000 secs (0,000 CPU) initing base buffer [preview] 28,361283 [dev_pixelpipe] took 0,002 secs (0,004 CPU) processed `Raw-Schwarz-/Weißpunkt' on CPU, blended on CPU [preview] 28,363002 [dev_pixelpipe] took 0,002 secs (0,003 CPU) processed `Weißabgleich' on CPU, blended on CPU [preview] 28,364711 [dev_pixelpipe] took 0,002 secs (0,003 CPU) processed `Spitzlicht-Rekonstruktion' on CPU, blended on CPU [preview] 28,381042 [dev_pixelpipe] took 0,016 secs (0,043 CPU) processed `Entrastern' on CPU, blended on CPU [preview] 28,387261 [dev_pixelpipe] took 0,006 secs (0,015 CPU) processed `Basiskurve' on CPU, blended on CPU [preview] 28,416517 [dev_pixelpipe] took 0,029 secs (0,089 CPU) processed `Eingabefarbprofil' on CPU, blended on CPU [preview] 28,431370 [dev_pixelpipe] took 0,015 secs (0,035 CPU) processed `Schärfen' on CPU, blended on CPU [preview] 28,50 [dev_pixelpipe] took 0,013 secs (0,028 CPU) processed `Ausgabefarbprofil' on CPU, blended on CPU [preview] 28,447031 [dev_pixelpipe] took 0,003 secs (0,014 CPU) processed `Gamma' on CPU, blended on CPU [preview] 28,47 [dev_process_preview] pixel pipeline processing took 0,129 secs (0,338 CPU) 2. Zoom in with option_key+1 (I cannot zoom with two fingers spreading on the trackpad!) 587,281321 [dev] took 0,000 secs (0,000 CPU) to load the image. 587,284834 [dev_pixelpipe] took 0,003 secs (0,003 CPU) initing base buffer [full] 587,290492 [dev_pixelpipe] took 0,006 secs (0,009 CPU) processed `Raw-Schwarz-/Weißpunkt' on GPU, blended on GPU [full] 587,293384 [dev_pixelpipe] took 0,003 secs (0,003 CPU) processed `Weißabgleich' on GPU, blended on GPU [full] 587,295763 [dev_pixelpipe] took 0,002 secs (0,002 CPU) processed `Spitzlicht-Rekonstruktion' on GPU, blended on GPU [full] 587,323806 [dev_pixelpipe] took 0,028 secs (0,027 CPU) processed `Entrastern' on GPU, blended on GPU [full] 587,334101 [dev_pixelpipe] took 0,010 secs (0,008 CPU) processed `Basiskurve' on GPU, blended on GPU [full] 587,338850 [dev_pixelpipe] took 0,005 secs (0,004 CPU) processed `Eingabefarbprofil' on GPU, blended on GPU [full] 587,364415 [dev_pixelpipe] took 0,013 secs (0,011 CPU) processed `Schärfen' on GPU, blended on GPU [full] 587,370479 [dev_pixelpipe] took 0,006 secs (0,005 CPU) processed `Ausgabefarbprofil' on GPU, blended on GPU [full] 587,485152 [dev_pixelpipe] took 0,112 secs (0,206 CPU) processed `Gamma' on CPU, blended on CPU [full] 587,485224 [dev_process_image] pixel pipeline processing took 0,204 secs (0,291 CPU) 3. Move image down completely (The action depends on how fast I can move the mouse pointer, but it is always done in multiple moves. Sometimes I have to stop and start all over again from the point at which the part move ends). The whole process took about 5.3 (6.5 CPU) seconds in 39 single steps. And this was onl
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 02.12.18 um 16:42 schrieb Michael Rasmussen: On Sun, 2 Dec 2018 15:52:02 +0100 Volker Lenhardt wrote: See also 'opencl_avoid_atomics' here: https://www.darktable.org/usermanual/en/darktable_and_opencl_amd.html Did you see above? Sorry for not having told you. Changing made no difference. Am 02.12.18 um 15:59 schrieb Ulrich Pegelow: > > For this case I would like to see the full output of 'darktable -d > opencl -d perf' with activated OpenCL from program start to where you > process the image with profiled denoise. > I've found a wrong option setting: I had the central option (in German) "OpenCL-Scheduler-Profil" set to "mehrere GPUs". I don't know why. Now it is set to "Standard". The processing time decreased to less than a fourth. Profiled denoise: 144,177185 [dev_process_image] pixel pipeline processing took 4,058 secs (1,591 CPU) Is this to be tolerated? Do you still need the long output? Then please wait until tomorrow, I'm on the run at the moment. There's still the problem of too slow response with shifting a zoomed in image to have e.g. a quick look at the corners to detect chromatic aberration. And cropping an image is slow, too. All of this rating is compared to what I was used to under Linux with less confined equipment. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 02.12.18 um 16:41 schrieb Michael Rasmussen: On Sun, 2 Dec 2018 16:10:00 +0100 Michael Kefeder wrote: There's an off chance your dedicated GPU is device 1 and your cpu is 0. By default the config only does consider one GPU in the system = 0, you can try (make sure the scheduler is default) to force use of device 1: opencl_device_priority=1,!0/!0,!1/1,!0/1,!0 Default setting is not to use CPU for opencl: opencl_use_cpu_devices=false This is set and not changed. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 02.12.18 um 14:05 schrieb Michael Rasmussen: On Sun, 2 Dec 2018 13:43:06 +0100 Volker Lenhardt wrote: I think I should either reinstall DT or start a new subject request. Or do you have an idea? In your darktablerc file you could try change default setting for these options: opencl_memory_headroom=550 opencl_memory_requirement=768 See also 'opencl_avoid_atomics' here: https://www.darktable.org/usermanual/en/darktable_and_opencl_amd.html The opencl_memory_headroom is of special concern since this setting controls how much memory darktable will reserve for other programs and device drivers requiring GPU memory. As can be seen above I have slightly increased the setting. Changing opencl_memory_headroom doesn't make any difference. Nevertheless thanks for the idea. Am 02.12.18 um 14:02 schrieb Ulrich Pegelow:> Looks like OpenCL is properly loaded. To better analyse the slow response time of your system run with 'darktable -d opencl -d perf'. After each processing step you get profiling output. For the start only look at lines like 17,607291 [dev_process_image] pixel pipeline processing took 0,212 secs (1,374 CPU) You will see the same output if you switch off OpenCL so this should give you a first estimate on how strong the GPU is able to boost performance on your system. Note that you need to activate some of the more demanding modules to really see a difference. Try for example profiled (denoise). Deactivated openCL: Next image in darkroom: 885,336719 [dev_process_image] pixel pipeline processing took 0,512 secs (1,761 CPU) Profiled denoise: 1033,212575 [dev_process_image] pixel pipeline processing took 18,907 secs (73,211 CPU) Activated openCL Next image: 1118,913519 [dev_process_image] pixel pipeline processing took 0,434 secs (1,555 CPU) Profiled denoise: 1219,319104 [dev_process_image] pixel pipeline processing took 18,669 secs (72,306 CPU) There's practically no difference. BTW: the images are cr2 files with sizes of about 23 MB. What next? Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 02.12.18 um 12:32 schrieb Michael Kefeder: Normally you should restart "darktable -d opencl" many times until the output looks like this, no errors compiling the kernels: ... 2,535671 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_accu' (175) for device 0 2,535708 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_finish' (176) for device 0 2,535748 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_backtransform' (177) for device 0 2,535783 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_decompose' (178) for device 0 2,535820 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_synthesize' (179) for device 0 2,535858 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_reduce_first' (180) for device 0 2,535891 [opencl_create_kernel] successfully loaded kernel `denoiseprofile_reduce_second' (181) for device 0 after that you can enable OpenCL in the settings (otherwise this is not available) I run Darktable on Mojave fine using opencl, even with the blackmagic eGPU. If you cannot enable opencl in the settings, redo the "multiple runs until all opencl kernels are compiled" stuff (can happen after darktable or macOS upgrades). hth mike Am So., 2. Dez. 2018 um 12:19 Uhr schrieb Volker Lenhardt mailto:volker.lenha...@uni-due.de>>: Am 01.12.18 um 22:59 schrieb Volker Lenhardt: > > /Applications/darktable.app/Contents/MacOS/darktable -d opencl > > There's a lot of output. OpenCL seems to be enabled. But for all the > rest it's too late tonight. I'll come to that the next days and will > report. For the time being my thanks to Archie and Ulrich. So long. First I started DL from the terminal without any option: macspinne:~ volker$ /Applications/darktable.app/Contents/MacOS/darktable The output: (process:501): GLib-GObject-CRITICAL **: 11:25:06.904: g_object_set: assertion 'G_IS_OBJECT (object)' failed (darktable-bin:501): GLib-GObject-WARNING **: 11:25:07.665: invalid cast from 'GtkMenuBar' to 'GtkWindow' (darktable-bin:501): Gtk-CRITICAL **: 11:25:07.665: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed After closing DT: (darktable-bin:501): GLib-GObject-CRITICAL **: 11:26:44.700: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Are these errors relevant within the Apple environment? When I start DT with the "-d opencl" option these errors are still there. But all output concerning openCL shows no errors. If requested I can post the lines. My output looks much the same as yours and Michael's. So I am now convinced that I was wrong putting the blame for my DT's shortcomings to openCL. There seems to be some flaw in the graphics. But the output concerning the graphics card looks ok: 0.069794 [opencl_init] found opencl runtime library '/System/Library/Frameworks/OpenCL.framework/Versions/Current/OpenCL' 0.069829 [opencl_init] opencl library '/System/Library/Frameworks/OpenCL.framework/Versions/Current/OpenCL' found on your system and loaded 0.069832 [opencl_init] found 1 platform 0.077176 [opencl_init] found 2 devices 0.077218 [opencl_init] discarding CPU device 0 `Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz'. 0.077246 [opencl_init] device 1 `AMD Radeon Pro 570 Compute Engine' supports image sizes of 16384 x 16384 0.077250 [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 GLOBAL_MEM_SIZE: 4096MB MAX_WORK_GROUP_SIZE: 256 MAX_WORK_ITEM_DIMENSIONS: 3 MAX_WORK_ITEM_SIZES: [ 256 256 256 ] DRIVER_VERSION: 1.2 (Oct 16 2018 21:18:14) DEVICE_VERSION: OpenCL 1.2 0.077944 [opencl_init] options for OpenCL compiler: -cl-fast-relaxed-math -DUNKNOWN=1 -I/Applications/darktable.app/Contents/Resources/share/darktable/kernels ... 0.085891 [opencl_init] kernel loading time: 0.0078 0.085897 [opencl_init] OpenCL successfully initialized. 0.085899 [opencl_init] here are the internal numbers and names of OpenCL devices available to darktable: 0.085901 [opencl_init] 0 'AMD Radeon Pro 570 Compute Engine' 0.085904 [opencl_init] FINALLY: opencl is AVAILABLE on this system. 0.085906 [opencl_init] initial status of opencl enabled flag is ON. I think I should either reinstall DT or start a new subject request. Or do you have an idea? Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 01.12.18 um 22:59 schrieb Volker Lenhardt: /Applications/darktable.app/Contents/MacOS/darktable -d opencl There's a lot of output. OpenCL seems to be enabled. But for all the rest it's too late tonight. I'll come to that the next days and will report. For the time being my thanks to Archie and Ulrich. So long. First I started DL from the terminal without any option: macspinne:~ volker$ /Applications/darktable.app/Contents/MacOS/darktable The output: (process:501): GLib-GObject-CRITICAL **: 11:25:06.904: g_object_set: assertion 'G_IS_OBJECT (object)' failed (darktable-bin:501): GLib-GObject-WARNING **: 11:25:07.665: invalid cast from 'GtkMenuBar' to 'GtkWindow' (darktable-bin:501): Gtk-CRITICAL **: 11:25:07.665: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed After closing DT: (darktable-bin:501): GLib-GObject-CRITICAL **: 11:26:44.700: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Are these errors relevant within the Apple environment? When I start DT with the "-d opencl" option these errors are still there. But all output concerning openCL shows no errors. If requested I can post the lines. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 01.12.18 um 21:01 schrieb Ulrich Pegelow: Am 01.12.18 um 20:32 schrieb Volker Lenhardt: This is one more riddle. I had tried so and have repeated it just now from the terminal. I get "-bash: darktable: command not found". It seems the best I can do is to reinstall Darktable. What do you think? You probably need to give the full path of the darktable executable. I have no idea how to get the path on MacOS, maybe some MacOS user knows. Eventually I found the path. /Applications/darktable.app/Contents/MacOS/darktable -d opencl There's a lot of output. OpenCL seems to be enabled. But for all the rest it's too late tonight. I'll come to that the next days and will report. For the time being my thanks to Archie and Ulrich. So long. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 01.12.18 um 20:07 schrieb Ulrich Pegelow: You are probably aware that you can find out more about OpenCL problems by starting darktable from a shell with option 'darktable -d opencl'. Likewise you may try 'darktable -d perf' for more info on what (module) makes darktable feel sluggish. This is one more riddle. I had tried so and have repeated it just now from the terminal. I get "-bash: darktable: command not found". It seems the best I can do is to reinstall Darktable. What do you think? Thanks. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Am 01.12.18 um 19:11 schrieb Archie Macintosh: On Sat, 1 Dec 2018 at 17:45, Archie Macintosh wrote: Sorry, I just realised I'm on a 2017 iMac. Is yours 2018? See https://support.apple.com/en-gb/HT202823 Doh! Just remembered there aren't any 2018 iMacs yet. So you should have OpenCL on yours. I bought my iMac 4 weeks ago. It was shipped with macOS High Sierra. I updated to Mojave. Of course I had activated OpenCL in the DT options. My trackpad troubles could be some hint to a different installation problem to be the cause for both. The sluggishness is e.g. very prominent, when I try to find image faults in the corners with highly zoomed in image. To move the image around takes much too much time with many pauses between. But nice to hear from you that it should work. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT on iMac with Mojave: no openCL
Sorry, I forgot: DT 2.4.4 > Am 01.12.2018 um 16:49 schrieb Volker Lenhardt : > > I migrated from Linux (openSUSE) to a new iMac (27" 5K) with macOS Mojave. > > 3.4 GHz Quad-Core Intel Core i5, 8 GB DDR4, Radeon Pro 570 (4 GB VRAM), Magic > Trackpad 2. > > > OpenCL doesn't seem to be enabled by Mojave any more. So DT is very very > sluggish, on the edge of being unusable. What's more, it doesn't respond to > some Trackpad gestures, e.g. zooming the picture with two fingers or > selecting from an option's choice list in the preferences dialog with a > simple click. Is there some way or other to get openCL to work or to use > Metal 2 instead. > > > Can you confirm my experiences? > > > 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
Re: [darktable-user] Darktable on Apple iMac under macOS 10.14 (Mojave)
Am 22.10.18 um 18:13 schrieb Glenn Malling: DT is running on my 2012 MacPro5,1 under Mojave. I had to install a "Metal" capable graphics card which is required for Mojave. If you are considering new iMac it will undoubtedly have the necessary graphics support for Mojave. I am NOT a DT expert but so far I have not encountered anything that does not work. Glenn Thank you Glenn. I'll give it a try, expensive as it is. Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darktable on Apple iMac under macOS 10.14 (Mojave)
Am 22.10.18 um 17:55 schrieb Michael Kefeder: I run darktable on mac for many years now, and in fact I recently played with it and benchmarked an eGPU using Mojave. Works perfectly fine for me, migrated my image library yesterday. For best performance, just make sure all opencl kernels are compiled. May I suggest to get an iMac with a dedicated graphics card (Radeon Pro 5xx) because I noticed my system becomes unresponsive when opencl is used on the Intel Iris Plus only. And on top of this issue, opencl on Intel Graphics doesn't really give you a proper speed advantage - a dedicated GPU however does (very much so). enjoy DT on mac ;) mike Thank you for reassurance. I'll try and buy it. It will be the one with Radeon Pro 570 graphics card, so I can look forward to joyful foto editing. (By the way, the LO people are encouraging me just as well.) Have a good time Volker Am Mo., 22. Okt. 2018 um 17:34 Uhr schrieb Volker Lenhardt mailto:volker.lenha...@uni-due.de>>: I'm interested in an iMac, but I fear that DT won't run under Mojave. On the download site I find that "This bundle supports macOS versions starting with 10.7 (Lion)". This should actually include the newest 10.14 version. But with similar circumstances with LibreOffice the Apple people made certain that LO won't run all the same. So I fear that DT encounters the same fate. Which of you has experiences with Apple and DT? darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Darktable on Apple iMac under macOS 10.14 (Mojave)
I'm interested in an iMac, but I fear that DT won't run under Mojave. On the download site I find that "This bundle supports macOS versions starting with 10.7 (Lion)". This should actually include the newest 10.14 version. But with similar circumstances with LibreOffice the Apple people made certain that LO won't run all the same. So I fear that DT encounters the same fate. Which of you has experiences with Apple and DT? Volker darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
