The 3.2.0 build had a couple of problems that the dev team deemed serious enough to warrant a correction before public release. Although the 3.2.0 build had not been publicly announced yet, some people may have downloaded it already, so the safest course was to issue the corrections as a maintenance update, 3.2.1 (and it seems they removed the 3.2.0 tag from the repository to prevent anyone from accidentally downloading that broken build).
So, the public announcement for “Darktable 3.2” will be on the 3.2.1 release. If any further emergency corrections are required, then I expect they’ll reluctantly issue a 3.2.2 build, but in practice I think the devs will now focus on getting Darktable 3.4 ready for Christmas, and any non-critical fixes from now on will be delivered in the Christmas release.
Would you mind explaining what the difference is, just in a sort of big picture way? I don’t know which one to install, and will this replace my current released installation? Or can I use it to update the 3.2 version I have been installing from the zip files?
Most of the added 3.4 stuff is listed here: current OSX Build - #98 by MStraeten
Both build are for testing purposes only, so backup your darktable settings and xmp files before using it. While the release 3.2. tag might be quite stable - fundamental changes are very unlikely, the 3.4 contains several work in progress stuff. So there might be changes until Christmas breaking edits done with earlier development builds.
Then I tried replacing my dev version by copying the darktable folder to my J drive and changing the bat file used to start the dev version. I started it the new version, and it looks like this:
Both installations are set to run elegant-grey. I’ve looked at preferences and don’t see a setting to account for the different look. Moreover, in the second installation, clicking on an image doesn’t select/highlight it. When I double-clicked on one, it opened in darkroom, but upon returning to lighttable, it looks like this:
You have to look for your personal config files, not for the files of the installation. In linux you find them in ~/.config/darktable in windows I don’t know.
On darktable 3.2 and dev versions, check before preferences dialog window and see which theme is used and if modify theme with css tweaks below is checked (if yes, start by unchecking it).
On what you made, you have an issue with a CSS personal tweak and especially a path issue. darktable don’t find the correct CSS on your dev version, that’s why you have that awful GUI.
When I read directions for installing the dev version, the post said rename darktable.exe to make sure there was no confusion, and of course, use that name in your bat file. I did the same thing with 3.2.1. Bad idea! Once I changed the name back and the bat file to darktable.exe, dt ran just fine.
I think I’ve built the right version, it says it’s 3.2.1, e.g. there’s a search in shortcuts, e.g. there’s a “user modified” preset in white balance. However there’s still a checkbox for basecurve presets in settings - I read this has been removed.
There’s a checkbox to ‘auto-apply per-camera base curve presets’ which should only be used in combination with the ‘display-referred’ pixel workflow defaults. It’s the latter option that replaces the ‘auto-apply base curve’ preference.
