Self-portrait, Before/After, of a full beauty edit performed on #darktable 3.4.

See (in French) the editing process by Minh-Ly, the model in the picture, guided by her husband, a darktable's developer : https://www.youtube.com/watch?v=gH1gRQ3Und0

darktable is now in feature-freeze state for version 3.4 planned for Christmas day. Translators can now take over (for supported languages, see https://github.com/darktable-org/darktable/blob/master/po/LINGUAS - only German and French have 99% complete translations).

It has been a truly crazy month. So much work… Stay tuned for more news.

Dear users, a glorious patch submitted in June to make the masking and blending fully scene-referred-compliant (and unbounded) is currently being reviewed for merging in #darktable 3.4.

We would like to take this opportunity to declutter and remove the output masking parameter, which nobody seems to use. Does anyone has a case to make against this ?

PR : https://github.com/darktable-org/darktable/pull/4688

The clipping alert in #darktable use to be a bit misleading, showing any RGB channel of any pixel out of the [0.1 ; 98] % range. Indeed, such clipped pixels could be the result of overexposure and/or oversaturation, and many users overreacted to this (pic. 1).

We introduce 2 new clipping modes: luminance (for pixels too bright/dark - pic. 2) and saturation (for pixels oversaturated for their luminance, aka out of gamut - pic. 3).

These will make diagnostics more relevant.

#darktable 3.4 will let you define exports size directly in pixels (as in 3.2 and before) but also from the physical printing size × printing DPI.

Long-asked feature…