Re: [darktable-user] darktable 4.0.0 released
On Mon, 4 Jul 2022 at 11:09, Terry Pinfold wrote: > I have looked for this UCS 22 colour space in the input color profile > module and I tried to find information in the latest user guide, but I > don't see it anywhere. Is this just something that is hidden from the user > or is it something I should be selecting somewhere. > It is used internally within the colour balance RGB module, not as a pipeline working colour space. If you go to the masks tab in color balance rgb, you'll find an option "saturation formula" which selects whether to use the new UCS colour space or the previous Jzazbz colour space. It is documented in the user guide: https://darktable-org.github.io/dtdocs/en/module-reference/processing-modules/color-balance-rgb/#saturation-formula Regards, Matt. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] darktable 4.0.0 released
" Introducing the darktable Uniform Color Space 2022 The darktable UCS 22 is a perceptually uniform color space designed from psychoperceptual experimental data specifically for the purpose of artistic saturation changes, as performed in the *color balance RGB* module. It uses a brightness-saturation scheme that compensates for the Helmholtz-Kohlraush effect (accounting for the contribution of colorfulness in perceived brightness) and allows an efficient gamut-mapping against pipeline RGB at constant brightness. It will make the saturation control in *color balance RGB* better behaved." I have looked for this UCS 22 colour space in the input color profile module and I tried to find information in the latest user guide, but I don't see it anywhere. Is this just something that is hidden from the user or is it something I should be selecting somewhere. Thanks Terry On Sun, 3 Jul 2022 at 03:05, Pascal Obry wrote: > > We're proud to announce the new feature release of darktable, 4.0.0! > > The github release is here: [ > https://github.com/darktable-org/darktable/releases/tag/release-4.0.0](https://github.com/darktable-org/darktable/releases/tag/release-4.0.0) > . > > As always, please don't use the autogenerated tarball provided by > github, but only our tar.xz file. The checksums are: > > ``` > $ sha256sum darktable-4.0.0.tar.xz > 1416f8f59717e65a6220541aaa12eacca93888ce5176f2c9ab6c17b9cc53cc2d > darktable-4.0.0.tar.xz > $ sha256sum darktable-4.0.0.dmg > addab784af18bafa303340e754c00084c126e61c3d5b93006f8e6d602f838203 > darktable-4.0.0.dmg > $ sha256sum darktable-4.0.0-win64.exe > d0e09efb2f74beae9f5387a296d366c160d9fb87e571c9559c53cd0111b7b955 > darktable-4.0.0-win64.exe > ``` > > When updating from the stable 3.8.x series, please bear in > mind that your edits will be preserved during this process, but the new > library and configuration will no longer be usable with 3.8.x. > > You are strongly advised to take a backup first. > > Important note: to make sure that darktable can keep on supporting > the raw file format for your camera, *please* read [this post]( > https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on > how/what raw samples you can contribute to ensure that we have the *full* > raw sample set for your camera under CC0 license! > > Since darktable 3.8: > > - Almost 1600 commits to darktable+rawspeed > - 586 pull requests handled > - 123 issues closed > > ## The Big Ones > > The following is a summary of the main features added to darktable 4.0. > These features > are described more fully in the user manual and accompanying blog post. > > - Color and exposure mapping > > A new feature in the "exposure" and "color calibration" modules allows > you to > define and save a target color/exposure for the color pickers, in order > to > match any source object in the image against an arbitrary target > color. This can be used to perform white balance > (chromatic adaptation) against non-gray objects of known color, or to > ensure the color consistency of an object across a series of images. > > - Filmic v6 > > Filmic v6 introduces new color science. This change removes the > mandatory desaturation > close to medium white and black and replaces it with a true gamut > mapping against the output (or export) color space. This allows for more > saturated colors, notably in blue skies. > > For users who still prefer the "desaturated highlights" look, > you can still do this by disabling chroma preservation, but v6 adds a > hue handcuff to prevent the traditional hue shift that comes with this > method (where saturated blue skies degrade to cyan and saturated red to > yellow). > > This gamut sanitization is the third and last to be added to darktable, > which now has a fully-sanitized color pipeline from input (color > calibration), > through artistic changes (color balance rgb) to output (filmic v6). Users > can now color-grade pictures safely in the knowledge that invalid input > colors can be recovered in the least destructive fashion possible early > in the pipeline, and valid colors can't be pushed out of gamut along the > pipeline. > > Note: If modules are applied after filmic in the pipeline, they > don't benefit from this gamut mapping and rely on LittleCMS2 (if > enabled) at the final export stage, which does not gamut map as it > should, and probably never did. > > - Guided laplacian highlight reconstruction > > A new "guided laplacian" method has been added to the "highlight > reconstruction" module. This uses an iterative and multi-scale wavelet > scheme to extract valid details from non-clipped RGB channel(s) if any, > uses these details to guide the reconstruction of clipped channels, and > finally > propagates the color gradients from neighboring valid regions using > edge-aware color diffusion. This limits color bleeding through edges > (preventing green leaves from bleeding color in the
Re: [darktable-user] darktable 4.0.0 released
Greetings, Tried to download the installation and getting following error. Basically followed the steps at https://software.opensuse.org/download.html?project=graphics:darktable=darktable for Ubuntu 20.04 Get:8 http://download.opensuse.org/repositories/graphics:/darktable/xUbuntu_20.04 InRelease [1,533 B] Err:8 http://download.opensuse.org/repositories/graphics:/darktable/xUbuntu_20.04 InRelease The following signatures were invalid: EXPKEYSIG 040524A84C70D8B5 graphics:darktable OBS Project Reading package lists... Done W: GPG error: http://download.opensuse.org/repositories/graphics:/darktable/xUbuntu_20.04 InRelease: The following signatures were invalid: EXPKEYSIG 040524A84C70D8B5 graphics:darktable OBS Project E: The repository 'http://download.opensuse.org/repositories/graphics:/darktable/xUbuntu_20.04 InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I've installed from this site before and don't remember encountering this issue. Do I need to do something else? Regards, Niranjan On 7/2/22 09:50, Pascal Obry wrote: We're proud to announce the new feature release of darktable, 4.0.0! The github release is here: [https://github.com/darktable-org/darktable/releases/tag/release-4.0.0](https://github.com/darktable-org/darktable/releases/tag/release-4.0.0). As always, please don't use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are: ``` $ sha256sum darktable-4.0.0.tar.xz 1416f8f59717e65a6220541aaa12eacca93888ce5176f2c9ab6c17b9cc53cc2d darktable-4.0.0.tar.xz $ sha256sum darktable-4.0.0.dmg addab784af18bafa303340e754c00084c126e61c3d5b93006f8e6d602f838203 darktable-4.0.0.dmg $ sha256sum darktable-4.0.0-win64.exe d0e09efb2f74beae9f5387a296d366c160d9fb87e571c9559c53cd0111b7b955 darktable-4.0.0-win64.exe ``` When updating from the stable 3.8.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 3.8.x. You are strongly advised to take a backup first. Important note: to make sure that darktable can keep on supporting the raw file format for your camera, *please* read [this post](https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw samples you can contribute to ensure that we have the *full* raw sample set for your camera under CC0 license! Since darktable 3.8: - Almost 1600 commits to darktable+rawspeed - 586 pull requests handled - 123 issues closed ## The Big Ones The following is a summary of the main features added to darktable 4.0. These features are described more fully in the user manual and accompanying blog post. - Color and exposure mapping A new feature in the "exposure" and "color calibration" modules allows you to define and save a target color/exposure for the color pickers, in order to match any source object in the image against an arbitrary target color. This can be used to perform white balance (chromatic adaptation) against non-gray objects of known color, or to ensure the color consistency of an object across a series of images. - Filmic v6 Filmic v6 introduces new color science. This change removes the mandatory desaturation close to medium white and black and replaces it with a true gamut mapping against the output (or export) color space. This allows for more saturated colors, notably in blue skies. For users who still prefer the "desaturated highlights" look, you can still do this by disabling chroma preservation, but v6 adds a hue handcuff to prevent the traditional hue shift that comes with this method (where saturated blue skies degrade to cyan and saturated red to yellow). This gamut sanitization is the third and last to be added to darktable, which now has a fully-sanitized color pipeline from input (color calibration), through artistic changes (color balance rgb) to output (filmic v6). Users can now color-grade pictures safely in the knowledge that invalid input colors can be recovered in the least destructive fashion possible early in the pipeline, and valid colors can't be pushed out of gamut along the pipeline. Note: If modules are applied after filmic in the pipeline, they don't benefit from this gamut mapping and rely on LittleCMS2 (if enabled) at the final export stage, which does not gamut map as it should, and probably never did. - Guided laplacian highlight reconstruction A new "guided laplacian" method has been added to the "highlight reconstruction" module. This uses an iterative and multi-scale wavelet scheme to extract valid details from non-clipped RGB channel(s) if any, uses these details to guide the reconstruction of clipped channels, and finally propagates the color gradients from
