How to use external editor in Darktable?

Yes, but can I with one click export a RAW as a 16bit TIFF at 300ppi into Photoshop?

different tools, different usecases …

at least it’s so ‚major inconvenience‘ that no one implemented the one click to rule them all aproach :wink:
darktable developers are known to eat their own dogfood…

It’s never too late to implement a feature that would benefit a large segment of the user base. I do not understand the thinking. That for as long as darktable has been around that this feature is still missing. It seems so logical that the software would have it.

Its not missing, it is just implemented differently than in the editor you’re already familiar with.

Still it’s a work around rather than hard coded into the software. It’s not something every one would feel confident installing or should have to.

It is not a work around, its how darktable’s lua functionality is designed.

Its a handful of clicks to get it going, similar to RT, no?

No, not even close. Assuming that Lua has the export implementation that would work the same as RT, why is it not in the exe? Is it that it can only be run as a plug-in?

In order to edit an image in an external editor, such as GIMP or Photoshop, the image must first be exported in a format the external editor can handle. If you enable the gimp lua script, it adds a new export target, Edit with GIMP. You choose the format, resolution, bit depth, etc. that you want. Save it as a preset. Make the preset active and then when you’re in darktable editing an image you can click the export button to open it in GIMP.

If you using the external editors script, select the editor you want to use, make it a preset, then click the export button to edit in the external editor.

So, it is possible to have 1 click to edit in an external editor.

The advantage of the lua approach is that changes can be implemented quickly. If we code it into the darktable executable, then you are looking at 6 months between releases. If there is a problem with the implementation, then you’re probably looking at another 6 months until it’s fixed.

Thanks Bill, I will give it another try.

I don’t see where to single click in order to send the Tiff file to PS. Single clicking on “export” sends the tiff to my designated folder location. Then I have to select the Tiff file in order to send it to Photoshop.

Perhaps I need an update to the Lua script?

DT_1

Under “Storage Options” > “Target Storage” > select what you want.

I did that. Does not work. Won’t send RAW to PS with single click in Tiff format

OK well help us help you, you’re giving us absolutely nothing to go on.

Fair enough

I installed the Lua script using this video.

OK and??

The Script Manager" loads correctly and I was able to set PS as an external editor. That works fine as long as I go through these steps. .

  1. “Export” to tiff.
  2. Select Tiff in “Light Table”
  3. Send to PS via the “External Editor”

Bill says. .

I can not get this to work the way that Bill describes.

Did you make a preset?

The “External Editor” “reset” and “preset” icons are inactive. When I click on them nothing happens.

Let me do some playing.

1 Like

Progress is the typical 1 step forward, 2 steps back.

ext_editors.lua does not work the way I thought so my statement above was incorrect with respect to that. GIMP does work the way I said, so you can one click edit with that.

After figuring that out my thought was to use gimp.lua as a base for an external_editor.lua script that worked the same but let you specify the external editor.

Then we took 2 steps back. I realized that there wasn’t an easy way to specify the external editor, so I started looking at executable_manager.lua. It currently allows you to specify the location for any external programs that it knows about. It doesn’t let you randomly add an executable, so I set out to fix that. When I started executable_manager it didn’t show up in the UI. I played with the positioning and finally got it to show up when I specified that it should be above script_manager rather than below. This was all in Win 10. So I tried Win 11 and Win 7 and it worked in both.

So then I started trying to figure out what was going on. I did more testing on Win 11 and found I just got lucky the first time and it hasn’t worked since (using the launcher). I did discover that if I run darktable from the command line or from a bat file (which is essentially the command line) then the UI works correctly. I’m not sure what the difference is as far as GTK is concerned but at least I have a workaround. Next to explore is compatibility settings to see if that has any effect.

Once I get the UI thing figured out, I’ll finish the external_editor.lua script and include it here.

2 Likes