Darktable integration with Gimp

**GUB** · 06-27-2019, 02:29 PM

It has been like this for a couple of years now but like usual I am a bit slow on the uptake.
So, with Gimp 2.10, Darktable is being treated as a plugin. (needs Darktable to be installed).
If you open a raw to Gimp it automatically opens Darktable first where you make your usual adjustments and then on closing Darktable it exports the image into Gimp.
There is one minor reference to this feature in the Darktable Coterie thread but otherwise this feature is largely unheralded.
It is going to make my workflow a lot smoother.
There is one small issue on my Linux build that took me a while to sort out though. Gimp rapidly got itself into a state that it couldn't select all / copy/ paste and the ram commited to memory grew enormous.
Solved it by closing OpenCL in Gimp preferences. Seems OpenCL wasn't playing nicely with either the type of image the raw had become in Gimp (still a raw?) or the fact OpenCL was running in Darktable.

**BigMackCam** · 06-27-2019, 03:17 PM - **1 Like**

Interesting...

My workflow is different. I use digiKam for my image library management. When I want to process a raw file, I "open with" Darktable from digiKam, then - when my image is ready - I export to TIFF from Darktable into dedicated export folders. Back in digiKam, I "open with" GIMP the image I want to process further, and export to JPEG when done.

It might seem a little long-winded, but it's really not. The essence of my workflow is that each stage in development is driven from, and launched from, my library management tool...

**GUB** · 06-27-2019, 03:33 PM - **1 Like**

Originally posted by BigMackCam

Interesting...

My workflow is different. I use digiKam for my image library management. When I want to process a raw file, I "open with" Darktable from digiKam, then - when my image is ready - I export to TIFF from Darktable into dedicated export folders. Back in digiKam, I "open with" GIMP the image I want to process further, and export to JPEG when done.

It might seem a little long-winded, but it's really not. The essence of my workflow is that each stage in development is driven from, and launched from, my library management tool...

Yes that is exactly how I have been doing it. I have figured that the tiff from DT was a useful backup but maybe the simpler workflow from this setup is worth it. Where I think it won't work is when I want to compare say a bunch of shots that are underexposed to find the best one.

Just been tinkering with the shortcut keys. My Gimp shortcuts have been customised for my purposes long ago. Key "1" is "export as".
Now in Digikam I have made "1" as "open with default application" (which has been set to gimp) and in DT "1" is quit.
So in Gub language "1" is move to the next step.

**GUB** · 06-27-2019, 03:37 PM - **1 Like**

I think it is because of our workflow that we havn't bumped into this feature.

**jbinpg** · 06-27-2019, 08:16 PM

In Gimp 2.10->Preferences->System Resources there is a checkbox for Use OpenCL. Did you have that checked?

**GUB** · 06-27-2019, 08:42 PM

Originally posted by jbinpg

In Gimp 2.10->Preferences->System Resources there is a checkbox for Use OpenCL. Did you have that checked?

Yes. But never had this problem until using DT this way. Funny thing is I think Gimp is running faster without opencl.

**jbinpg** · 06-27-2019, 11:09 PM - **1 Like**

OpenCL only works well with certain chipsets. Intel's opencl version is blacklisted by darktable so if you have an Intel CPU you are best to disable opencl in both darktable and gimp. Intel is working on a modern version so this should be rectified eventually.

**GUB** · 06-28-2019, 02:29 AM

Originally posted by jbinpg

OpenCL only works well with certain chipsets. Intel's opencl version is blacklisted by darktable so if you have an Intel CPU you are best to disable opencl in both darktable and gimp. Intel is working on a modern version so this should be rectified eventually.

Thanks for that

**GUB** · 06-28-2019, 03:22 AM

Actually I ran $ Darktable-cltest and everything seemed successful so I may leave it enabled. It would be a miracle if it was up and running correctly - it was all so over my head!

**jbinpg** · 06-28-2019, 10:00 PM

Then I would uncheck the "opencl enable" in the system resources in gimp. Perhaps the two implementations are fighting each other.

**GUB** · 06-29-2019, 01:36 AM

Originally posted by jbinpg

Then I would uncheck the "opencl enable" in the system resources in gimp. Perhaps the two implementations are fighting each other.

Umm that is what I did. (Last sentence OP)

06-27-2019, 02:29 PM	#1
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760	Darktable integration with Gimp It has been like this for a couple of years now but like usual I am a bit slow on the uptake. So, with Gimp 2.10, Darktable is being treated as a plugin. (needs Darktable to be installed). If you open a raw to Gimp it automatically opens Darktable first where you make your usual adjustments and then on closing Darktable it exports the image into Gimp. There is one minor reference to this feature in the Darktable Coterie thread but otherwise this feature is largely unheralded. It is going to make my workflow a lot smoother. There is one small issue on my Linux build that took me a while to sort out though. Gimp rapidly got itself into a state that it couldn't select all / copy/ paste and the ram commited to memory grew enormous. Solved it by closing OpenCL in Gimp preferences. Seems OpenCL wasn't playing nicely with either the type of image the raw had become in Gimp (still a raw?) or the fact OpenCL was running in Darktable.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Before and after in Darktable and Gimp	GUB	Digital Processing, Software, and Printing	11	03-21-2015 08:37 PM
Concept: Computationally generated DOF by zValue integration	spade111	Photographic Industry and Professionals	5	11-06-2014 01:46 PM
Integration	njphotog	Monthly Photo Contests	5	08-13-2014 11:55 PM
GIMP 2.6.12 vs. GIMP 2.8.0	Vasyl	Digital Processing, Software, and Printing	13	06-19-2012 02:00 PM
PENTAX and RICOH Announce Integration of Consumer Camera Products Marketed and Distri	Adam	Homepage & Official Pentax News	9	04-19-2012 04:40 PM

06-27-2019, 03:17 PM - 1 Like	#2
BigMackCam Digitiser of Film Join Date: Mar 2010 Location: North East of England Posts: 20,670	Interesting... My workflow is different. I use digiKam for my image library management. When I want to process a raw file, I "open with" Darktable from digiKam, then - when my image is ready - I export to TIFF from Darktable into dedicated export folders. Back in digiKam, I "open with" GIMP the image I want to process further, and export to JPEG when done. It might seem a little long-winded, but it's really not. The essence of my workflow is that each stage in development is driven from, and launched from, my library management tool...

06-27-2019, 03:33 PM - 1 Like	#3
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760 Original Poster	Originally posted by BigMackCam Interesting... My workflow is different. I use digiKam for my image library management. When I want to process a raw file, I "open with" Darktable from digiKam, then - when my image is ready - I export to TIFF from Darktable into dedicated export folders. Back in digiKam, I "open with" GIMP the image I want to process further, and export to JPEG when done. It might seem a little long-winded, but it's really not. The essence of my workflow is that each stage in development is driven from, and launched from, my library management tool... Yes that is exactly how I have been doing it. I have figured that the tiff from DT was a useful backup but maybe the simpler workflow from this setup is worth it. Where I think it won't work is when I want to compare say a bunch of shots that are underexposed to find the best one. Just been tinkering with the shortcut keys. My Gimp shortcuts have been customised for my purposes long ago. Key "1" is "export as". Now in Digikam I have made "1" as "open with default application" (which has been set to gimp) and in DT "1" is quit. So in Gub language "1" is move to the next step.

06-27-2019, 03:37 PM - 1 Like	#4
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760 Original Poster	I think it is because of our workflow that we havn't bumped into this feature.

06-27-2019, 08:16 PM	#5
jbinpg Site Supporter Join Date: Mar 2008 Location: Prince George, BC Photos: Gallery \| Albums Posts: 3,546	In Gimp 2.10->Preferences->System Resources there is a checkbox for Use OpenCL. Did you have that checked?

06-27-2019, 08:42 PM	#6
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760 Original Poster	Originally posted by jbinpg In Gimp 2.10->Preferences->System Resources there is a checkbox for Use OpenCL. Did you have that checked? Yes. But never had this problem until using DT this way. Funny thing is I think Gimp is running faster without opencl.

06-27-2019, 11:09 PM - 1 Like	#7
jbinpg Site Supporter Join Date: Mar 2008 Location: Prince George, BC Photos: Gallery \| Albums Posts: 3,546	OpenCL only works well with certain chipsets. Intel's opencl version is blacklisted by darktable so if you have an Intel CPU you are best to disable opencl in both darktable and gimp. Intel is working on a modern version so this should be rectified eventually.

06-28-2019, 02:29 AM	#8
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760 Original Poster	Originally posted by jbinpg OpenCL only works well with certain chipsets. Intel's opencl version is blacklisted by darktable so if you have an Intel CPU you are best to disable opencl in both darktable and gimp. Intel is working on a modern version so this should be rectified eventually. Thanks for that

06-28-2019, 03:22 AM	#9
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760 Original Poster	Actually I ran $ Darktable-cltest and everything seemed successful so I may leave it enabled. It would be a miracle if it was up and running correctly - it was all so over my head!

06-28-2019, 10:00 PM	#10
jbinpg Site Supporter Join Date: Mar 2008 Location: Prince George, BC Photos: Gallery \| Albums Posts: 3,546	Then I would uncheck the "opencl enable" in the system resources in gimp. Perhaps the two implementations are fighting each other.

06-29-2019, 01:36 AM	#11
GUB Loyal Site Supporter Join Date: Aug 2012 Location: Wanganui Photos: Gallery \| Albums Posts: 5,760 Original Poster	Originally posted by jbinpg Then I would uncheck the "opencl enable" in the system resources in gimp. Perhaps the two implementations are fighting each other. Umm that is what I did. (Last sentence OP)