Skip to content
Hubert Kowalski edited this page Apr 4, 2020 · 6 revisions

Getting new cameras to work with darktable

Every new camera means new things to explore for both camera manufacturers and software developers.

Open source software like darktable doesn't have direct connections with manufacturers to get specs and SDK before camera releases, so we have to depend on samples and data provided by users.

Here's all the steps involved in getting new cameras to work with darktable (and for older cameras to get better)

Raw format support

First step in getting new camera support is providing RAW image samples.

We are looking for shots that are:

  • Lens mounted on the camera, cap off
  • Image in focus and properly exposed
  • Landscape orientation
  • Base ISO

If your camera produces several types of RAWs (like different bit depths, compressed, etc) please do shots using all those types of exactly same content with same exposure params, settings etc.

The recommended content of sample images is photo of color target. That way we can get most of it and avoid any potential problems. Make sure sample images are not of people for legal reasons.

Photos have to be released with Creative Commons Zero (CC0) - public domain licence

Upload your samples to https://raw.pixls.us/

Also, check this thread periodically: https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri

White balance presets

In order to get your camera's white balance presets in darktable's white balance module, please follow the steps described in our white balance presets wiki

Noise profiles

darktable has a great denoising tool in form of denoise (profiled) module. In order to get the best possible results, a profile has to be created for every ISO setting of your camera.

Follow How to create camera noise profiles for darktable tutorial and send us resulting package by creating a noise profile issue on Github

Lens correction

Whenever you're shooting image, there are always imperfections in lens design distorting images slightly (or very) that need to be corrected. darktable uses lensfun library for lens correction in lens correction module and doesn't have own lens database. If your camera and lens combination is not recognized, try updating your lens database using:

lensfun-update-data

If that doesn't work, then maybe your camera/lens is too new. You can check lensfun lens coverage to see whether your lens is on the list.

If it isn't - follow creating lens calibration data for lensfun tutorial.

Base curve

the purpose of the basecurve is to make the otherwise scene-referred linear (linear raw rgb) color look good on your output devices.

in darktable we try to match approximately how vendors process their images by guessing the basecurves visually/manually. if your camera is not supported yet or you don’t like the result or just want to play with it, there is also a way to measure the basecurve from a raw and jpg pair.

To get best results, use similar pattern as in Noise profiles section for shooting sample image.

Remember to disable all "enhancements" your cammera offer and shoot using camera default image style (usually called "standard")

And finally - follow basecurves tutorial on darktable website.

Profiling a camera

To get almost perfect OOC-JPEG feeling out of RAWs automatically, it is required to create color profile.

First - you have to get yourself good color chart as usually typical ColorCheckers don't have nearly enough colour patches to be worth working with. It's best to get IT8 chart as a target. If you do have ColorChecker or something similar, the results might be acceptable.

Follow Profiling a camera with darktable-chart tutorial