Leaning heavily on scripts written by wpferguson and ChristianBirzer I’ve written a couple of Lua scripts to integrate DxO PureRAW and Zerene Stacker into my Darktable workflow.
I’ve put them on Github at GitHub - fjb2020/darktable-scripts: Some Lua scripts for darktable in case others are interested.
The DXO script does not work on Linux as there is no DXO version for linux, and the Zerene script does not yet work on linux as I’ve not got a suitable linux platform to test on.
Good day, I have tried your DXO Purer 4 script with DT 5 and Mac OS Sequoia 15.2 without success. I did try to edit the script by replacing DXO_PureRaw with DxO PureRaw 4, but that does not help.
Any help would be appreciated.
TIA
Glyn
I used a trial installation of Pureraw 4 and the script did work. One thing may be to check is the setting for DxO_pureRAW executable in the Lua options setting. It needs to be the actual executable file, not the .app file - e.g. on my system it’s /Applications/DxO PureRAW 3.app/Contents/MacOS/PureRaw3 - I’m also on DT 5, Sequioa 15.2
@fjb2020 Can you please tell me where are lua option settings are located on a windows pc? I found this entry in darktablerc . .lua/module_DxO_PureRAW/DxO_pureRAWExe=
Thanks,
Mike
Mine is set to
lua/module_DxO_PureRAW/DxO_pureRAWExe=C:\Program Files\DxO\DxO PureRAW 3\PureRawv3.exe
I set it via the Lua Options tab of darktable preferences rather than editing darktablerc directly
MacOs 15 Purerawv4 and DT 5 image type ORF
I have set the application path to the correct directory.
the Lua script starts without issue in darktable but when an image is selected and process with DxO Pureraw, this error appears
“could not start DxO_pureRAW application - is it set correctly in Lua Options?”
any ideas please?
I uploaded an updated version of the script last week which improved handling of the DxO executable in macOS (to GitHub - fjb2020/darktable-scripts: Some Lua scripts for darktable)
Please could you try this updated version, making sure that the Lua Options setting for DxO_pureRAW executable is set to the DxO 4 ‘.app’ (mine is /Applications/DxO PureRAW 3.app for info).
Hope this helps
I’ve just installed a trial version of PureRAW 4 and found the operation of the latest release is very different from PureRAW 3 - so whilst the changes I made to the script will probably fix the application launch issue, there are other changes in PureRAW that will cause my script to fail. I’m looking in to whether I can accommodate them but am not sure yet. Sorry 
Hi,
I’m also quite interesting in this script. I’m not much of a coder, but what I have found that seems to have changed is the naming of the processed files. It’s “-DxO_DeepPRIME” rather than “_DxO[…]” and the new xd2s algorithm carries that in the file name too.
But that alone doesn’t seem to solve it for me, something else seems to be wrong. If anyone could explain to me how I can see the error output (error log?) of the lua script, I could possibly help. I seem to remember that the log is saved somewhere when darktable is started with a certain command line option or so?
I’m on Windows 11 btw
Thanks for the start, though. Once working as intended, I think this script is very useful and I’m trying to help 
This approach might be a work around until you get it sorted at least for DXO???
I made some minor changes to the ext_editor.lua script and I can now direct my raw files from Darktable to any other program from within the External Editor script. From within the script:
-- allowed file extensions for external editors
local allowed_file_types = {"JPG", "jpg", "JPEG", "jpeg", "TIF", "tif", "TIFF", "tiff", "EXR", "exr", "PNG", "png","CR2", "CR3","dng", "DNG"}
All this did was add CR2, CR3, and DNG formats as allowed extensions and then I added my external editors as usual. If I send a raw file to DXO Pure Raw 4, it will perform the denoise and then return a DNG file to collections where I can edit in Darktable.
This has been really nice because I can now use Darktable as more of a central hub that integrates across programs. I even set up Firefox and XnView MP as external editors so I can directly view my exported files without having to go through File Explorer. This wouldn’t work with Zerene because the script won’t handle multiple images, so I would love to see a solution for that.
This has been working fine on Windows 11, but hopefully this would work on other OS.
This is a great idea, thanks. I didn’t even think of this. However, what doesn’t work for me is that the resulting DNG is imported back into darktable.
In other words, I can launch DXO as the external editor, I can do my denoising there, write out the dng file and then I exit.
But then nothing happens in darktable and I have to manually import the newly created dng.
In the video as well as from your description it sounds like you somehow managed to get it to import the dng automatically? Is there an option somewhere to “auto-import new files in the current folder” or something else that I’m missing?
Thanks again!
If you’re responding to my post, then I had forgotten that I had the option within DxO PR to export back to Darktable, in which case the resultant DNG will load and open.
I’ve now posted an updated version ofthe DxO script which supports DxO_pureRAW 4 - check the separate readme file for details on running it as it’s a bit clunky at the moment, but it works on my macOS and windows 11 installations
@fjb2020 - I just tried your updated script and ran into some issues. I sent you a separate message with some thoughts.
Thank you Dave, this is working now. I totally missed the point of exporting it back to darktable. That’s pretty neat and really helps with my workflow.
Fiona - thanks for keeping on improving this script. I’ll try it out when I have a moment
I added “NEF” to that list but I still get file type not supported. Any other changes made? Script opens jpg ok.
It seems to be case sensitive, so I added file extensions in both upper and lower case.
@Dave22152 , Can these changes be placed anywhere in the script?
You would add your extension under line 119 of the script. This is the how it appears in the formal configuration:
local allowed_file_types = {“JPG”, “jpg”, “JPEG”, “jpeg”, “TIF”, “tif”, “TIFF”, “tiff”, “EXR”, “exr”, “PNG”, “png”}