darktable 3.0.2 released

We’re proud to announce the new feature release of darktable, 3.0.2!

The github release is here: https://github.com/darktable-org/darktable/releases/tag/release-3.0.2.

As always, please don’t use the autogenerated tarball provided by github, but only our tar.xz. the checksums are:

$ sha256sum darktable-3.0.2.tar.xz
6abaf661fe9414e92bdb33b58b98ef024ccf6132b7876abaf0751ec2109f36fb darktable-3.0.2.tar.xz
$ sha256sum darktable-3.0.2.dmg
b71dab1b4f0ad796055f6d725a82913ad08f609de6ca96d65dbe6ffbeecb6416 darktable-3.0.2.dmg
$ sha256sum darktable-3.0.2-win64.exe
2702b553acd09250f923f6e39d71d3c0f4ba0f81801c9c1ea55466bcf1ffab42 darktable-3.0.2-win64.exe

When updating from the currently stable 2.6.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will not be usable with 2.6.x any more, so making a backup is strongly advised.

Important note: to make sure that darktable can keep on supporting the raw file format for your camera, please read this post on how/what raw samples you can contribute to ensure that we have the full raw sample set for your camera under CC0 license!

Changes since 3.0.1

New Features And Changes

  • Better UI for the blend modes which are now grouped by category.

  • Ctrl+Click can be used to rename a module instance.

  • Allow larger vignette scale.

  • Add pseudo preset in whitebalance to keep user’s modifications.

  • In crop&rotate module it is possible to allow only vertical composition change using the Shift modifier when dragging the crop area and horizontal one using the Ctrl modifier.

Bug fixes

  • Fix color peaking mode in culling mode.

  • Fix single expanded module in some cases.

  • Fix a watermark issue that could crash darktable.

  • Fix issue with gradient mask rotation in some cases.

  • Fix upward compatibility support in base adjustment module.

  • Fix some MacOS full-screen mode issues.

  • Fix issues on some Lut 3D files.

Base Support

  • Fujifilm GFX 100 (compressed)
  • Fujifilm X-Pro3 (compressed)
  • Fujifilm X100V (compressed)
  • Nikon COOLPIX P950 (12bit-uncompressed)
  • Nikon Z 50 (12bit-compressed, 14bit-compressed)
  • Olympus E-M1MarkIII
  • Panasonic DC-S1 (3:2)
  • Panasonic DC-S1R (3:2)
  • Panasonic DC-TZ91 (4:3)
  • Panasonic DC-TZ95 (4:3)
  • Panasonic DC-TZ96 (4:3)
  • Panasonic DC-ZS80 (4:3)
  • Sony ILCE-6100

White Balance Presets

  • Canon EOS 77D
  • Canon EOS 9000D
  • Nikon COOLPIX P1000
  • Panasonic DC-GH5
  • Olympus E-M1MarkIII
  • Olympus E-PL6
  • Olympus TG-5
  • Samsung NX1

Noise Profiles

Translations

  • Catalan
  • Czech
  • Danish
  • German
  • European Spanish
  • French
  • Hebrew
  • Hungarian
  • Italian
  • Japanese
  • Norwegian
  • Dutch
  • Polish
  • Russian
  • Slovenian

Share this on: Twitter | Facebook


This is a companion discussion topic for the original entry at https://www.darktable.org/2020/04/darktable-302-released/
18 Likes

Did negadoctor make it into this release? I don’t see it mentioned in the release notes.

Only one way to find out. :wink:

There are two ways. One way is asking here :wink:

I have 3.0.2 installed, the invert module looks the same as in 3.0.1

I had to lookup what negadoctor is, certainly something to look forward to in the future:

2 Likes

The better way ist to look here: https://github.com/darktable-org/darktable/tree/release-3.0.2/src/iop
negadoctor wasn’t included

No negadoctor will be for a major release.

2 Likes

Seems also the input color profile fix didn’t make it to this release. Is some minor release planned?

Going from 3.0.1 to 3.0.2 seems like a minor release already (notwithstanding the major work that’s been put into it of course :wink: )

1 Like

I wasn’t being lazy. I was on mobile and won’t be at my computer for a couple of days. I had thought Negadoctor was planned for the next minor release as I believe Aurélien had said in another comment, so thought I’d quickly ask on here. @Pascal_Obry has kindly answered with what I wanted to know.

This is probably a case of terminology. Generally (at least for open source projects), the versioning is as follows:

M.m.b

where M = major release
m = minor release
b = bugfix (or “dot”) release

Major releases contain large changes to the functionality and potentially new capabilities, possibly breaking backwards compatibility and changing the user interface significantly. Minor releases are improvements to functionality and possibly some new capabilities, but not significant enough changes to the way the system works to warrant a major release. Dot releases contain bug fixes and small improvements to existing functionality.

Of course, the boundaries between these release definitions are quite subjective. But these are the generally accepted definitions in my experience.

4 Likes

@europlatus Sorry about that, didn’t mean the snark. Was in the middle of something so I probably shouldn’t have responded until I verified the facts myself.

For future reference, follow @MStraeten’s advice. This is the method I use. I also downloaded dt. Even if it is a point release, it contains bug fixes and incremental updates, both which are useful.

1 Like

Hi, looking good. Any word on Canon CR3 support? This is the only thing keeping me from going fully Linux. Must be a bugger of a thing to get working compared to the new Fuji and Nikons that seem to get pretty quick support

Cheers

ongoing task, not that easy since canon doesn’t provide any informations. See https://github.com/darktable-org/rawspeed/issues/121

1 Like

The most common variant of this convention is called Semantic Versioning: https://semver.org/

There are several other version number strategies to be aware of. Some projects (notably, the Linux kernel) will introduce major features or breaking changes in a minor release after a period of testing or deprecation, rather than making all the changes at once in a major release.

2 Likes

I can now open ILCE-6100 raw, but with an error that says " color matrix not found!"

That seems to be correct. Have a look at darktables camera support section (ILCE-6100 is near the bottom):

You might want to consider supplying RAW samples for this camera:

Great thank you for the link, I loooked into it. I dont see ILCE 6100 on the list but ill assume an old request. I looked at the menus on my ILCE 6100 and could not find any bitrate options. all

raw files have the same resolution regardless of any other settings including aspect ratios that is

6048 x 4024

does that leave me with sending 1 raw file taken with kit lens and tripod, set to iso=100? thanks!

Don’t forget that we are looking for:

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

and we are NOT looking for:

  • Series of images with different ISO, aperture, shutter, wb, lighting, or different lenses
  • DNG files created with Adobe DNG Converter
  • Photographs of people, for legal reasons.

Just add your link to a “6100” RAW file at the bottom. Google drive is good for file links.

1 Like

https://drive.google.com/drive/folders/1OyCnlRMY-2cywRnYPFhAxaRui6lcC9li?usp=sharing

a set of almost same photos taken within a minute, just in case… in the zip, the same files, again.

@Dave8 please upload them to https://raw.pixls.us

1 Like