As I said, I read it on the internet.
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.
Sorry to bother everyone.
*** Many thanks for this latest version ***
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.
Ah, thanks, I see.
What new features are planned for dt 3.4?
Some of them are already highlighted in the release notes draft (a really work in progress documents): darktable/RELEASE_NOTES.md at master · darktable-org/darktable · GitHub
But there are many pull requests (upcoming changes) that are still to be merged/developed/reviewed/discussed… You can have an insight here (sometimes really technical, sometimes understandable by anyone): Pull requests · darktable-org/darktable · GitHub
Not much, 3.2 had many new features already. 3.4 will mostly concentrate on fixing some bugs uncovered after the huge 3.2 work. 3.4 will also have many speed improvements.
I also hope for an update of the user manual. Work has already been done on this part but there is some more work to be done.
A new tooltip was added to history items in the darkroom that shows each of the individual parameter changes within the module.
Excellent!
Great news! Are there any plans to add some documentation for the Tone Equalizer module? I have zero clue what sort of mask I need for a given task, nor how to achieve it.
I noticed this but its a bit distracting I might actually turn it off…I took a quick look and the info seemed cryptic…I guess I should pay more attention…likely the host of small numbers and my eye sight…
There are two videos, created by Aurelien Pierre (coder of the module), answering many questions :
dodging and burning with the tone equalizer
handle any dynamic range efficiently with filmic RGB and tone equalizer
Also trying out and experimenting with the parameters may help…
Yes, there is lot of work on the documentation at the moment. My plan is really to have a full documentation for 3.4 and we are very close from this target already 