Almost 1600 commits to darktable+rawspeed.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! You are strongly advised to take a backup first. Library and configuration will no longer be usable with 3.8.x. Mind that your edits will be preserved during this process, but the new When updating from the stable 3.8.x series, please bear in You can find the link to the binary on the forum (a great place btw., you should check it out).We’re proud to announce the new feature release of darktable, 4.0.0!Īs always, please don’t use the autogenerated tarball provided by

Please report useful bugs in our bug tracker. We know it’s still buggy, but as a sign of goodwill and request for help in testing it we would like to ask you to give it a try. To cut a long story short, we are extremely pleased – albeit wary – to announce a very first official pre-alpha development snapshot for 64 bit Windows.

Eventually we became confident that the lack of Windows maintainership might be solved. Like some people before he managed to compile darktable on Windows and offered us the patches he had to do, but other than what we had seen before he stuck around, helped fix bugs and was open to suggestions how to solve things in a better way. Not just for the moment until all the patches got merged but for the foreseeable future.

The gist of it was that the real blocker for a Windows release isn’t so much a technical one but the lack of a person (or several) dedicated to maintaining it. Then two years ago there was yet another post regarding Windows. While I still stand by what I wrote six years ago, the times they are a-changin'. A long time ago there was a post about why we don’t have a Windows port.

Darktable windows 10