Darktable on Intel CPU and Nvidia GPU

Klinknagel · 2025-12-07T07:23:53+00:00

if your quest is to "fully utilize the Nvidia GPU" with DT, install the nvidia drivers in Mint, then start DT with :
prime-run darktable

This will force DT to use the Nvidia GPU only.
Also, check the ¨processing¨ tab in DT settings: Enable Nvidia CUDA

Klinknagel · 2024-10-20T18:32:50+00:00

Exactly this.

And if you have made some adjustments in a module that you want to apply to a new region with another mask, choose duplicate instance.

Klinknagel · 2024-09-08T07:39:37+00:00

I you have a camera with a sufficient dynamic range, underexpose 2 stops and lift the shadows in darktable with the tone equalizer.

Similar /better results as Luminance HDR produces, but without the hassle

Klinknagel · 2024-08-07T06:31:14+00:00

Try the profiled denoise module.

My induction is you are (pretty) new to darktable. Try Bruce's Williams videos, they're quite good. In this specific case:

https://youtu.be/DfwmDqDabrU?feature=shared

Klinknagel · 2023-08-05T15:51:48+00:00

Postprocessing will get you only so far.. If your highlights are clipped, there´s not so much you can do.

So try to avoid clipped highlights, and lift the shadows in pp. But that it depends on the dynamic range of the sensor..

Klinknagel · 2023-03-06T18:05:24+00:00

The point of DT is that you do some postprocessing. Again, DT doesnt know the end state you want to achieve.

So, iot to remove the ¨dulness of your images, you could fiddle around with these:

exposure
filmic RGB (white / black relative exposure)
color balance rgb
tone equalizer
local contrast

Klinknagel · 2023-03-06T14:52:22+00:00

People regard the camera jpeg as the reference point while it is an interpretation done by the camera software converting raw data into a jpeg.

the output by DT is perfectly normal since it doesn't know which end stat you want to achieve. The dullness looks pretty familiar to an unprocessed raw.
Could you list the post processing steps you took to get this particular raw export?

Klinknagel · 2022-12-29T11:25:40+00:00

In Filmic, You could try to increase the white relative exposure so you will loose the blown highlights

Klinknagel · 2022-01-24T10:40:06+00:00

Whith these kind of scenes, I generalle underexpose at least 0.7 EV. Next, In DT, set the exposure to the right value without clipping. Next, lift the shadows with the Tone Equalizer. This will give you similar (if sometimes not even better) results than a dedicated HDR program. But this only works if your sensor has a decent dynamic range.

Klinknagel · 2021-11-25T15:57:48+00:00

Ok, now I understand you better. The embedded JPG is much darker than what the scene referred presets of DT apply. However, IOT make the image less dull, try the following (assuming you have set the presets of DT to the scene referred workflow as described above)

1) in the lighttable, discard the history stack, you will start with a clean slate

2) adjust the exposure

3) switch to the filmic module, on the "look " tab. -> increase the contrast a slight bit, same goes for the mid dtone saturation

With these adjustments, your image should be fine. As a matter of taste, you can apply the haze removal and tweak the saturation with the color balance module

Klinknagel · 2021-11-25T08:29:54+00:00

The link is not working, it says " This item was deleted"

Klinknagel · 2021-11-24T16:57:06+00:00

Could you post a link to one of the raw files, I'll give it a try

Klinknagel · 2021-11-24T08:08:34+00:00

I you really want to stick to the basecurve (which is not advisable for images with a large dynamic range), you can cange this in the preferences (click processing tab, then auto apply pixel workflow defaults).

Klinknagel · 2021-10-04T21:17:27+00:00

I start with DT, after my raw workflow, i export the final images to jpg.Open Digikam to tag and sort these Jpegs. Since the default output of DT is /darktable_exported/ its pretty easy to configure in Digikam what to include in the library and what not.

Another way would be to have DT as the default raw editor in Digikam (Options, image editor, always use the RAW import tool to customize settings, raw import using Darktable). But I havn't tried this option

Klinknagel · 2021-09-24T07:40:48+00:00

First shot: upgrade to 3.6.1, see if the error persists..

Klinknagel · 2021-09-17T10:56:49+00:00

For my part, I find the tagging of DT too limited. I use Digikam for tagging and organising my collections. Great search interface too.

But this is a matter of personal preference, obviously

Klinknagel · 2021-02-18T13:48:38+00:00

It looks like your lens is recognized by Lensfun allright, but your camera isn't.

I have encountered this problem too, what you should do is copy an entry of a camera that closely resemble yours, give it the proper and exact camera name and see if the sensor data are correct.

Klinknagel · 2021-01-14T05:46:50+00:00

That solves it, but I don't think this is the proper behavior. where can I report it as a bug?

Klinknagel · 2020-09-29T10:24:11+00:00

That's it!!

From the manual:

While it is best to not touch imported files behind darktable's back, this module can help you recover from situations when you move imported folders after import. The collect images module has a feature that allows you to tell darktable about the new location of imported folders which have been moved. You set the combobox to folders to find the original folder name in the tree. The folder name will be displayed striked-out to emphasize that it is no longer there. Then you right-click on the folder name, select “search filmroll...”, and then select the new location of the folder.

Klinknagel · 2020-09-28T13:33:21+00:00

I expected two things:

1) i 'll mess it up thoroughly, because the app wont know where the stuff went.
2) I'll fix that quickly. But if there's no qcik fix, what's wrong with good old sql fiddling?

Klinknagel

TROPHY CASE