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

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

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

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

@eylul I know you have many original workflows I have never seen elsewhere, your opinion ?

Show thread

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 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 : github.com/darktable-org/darkt

darktable boosted

The new filmic v4 highlight reconstruction in @darktable allowed the following photo to be salvaged, even though parts of the sky were completely blown out in the raw file.

darktable boosted

Inventing a new view to explain filmic curve as a scene -> display range mapping zone by zone for next #darktable. It should make it easier to get.

The clipping alert in 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.

The darktable user manual is largely outdated. Problem is it uses an esoteric kind of XML required by a brittle software stack (Saxon) to be compiled into HTML or PDF.
This complexity steers away many contributors.
But thanks to Chris Elston, @secretlifeofmatt and @paperdigits, it is being rewritten in Markdown with a better "tutorial" approach.
WIP : elstoc.github.io/dtdocs/
Contribute : github.com/elstoc/dtdocs

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…

Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!