Wow, gorgeous! Thanks!
I’m running windows 10 & manjaro atm. In Windows, dt 3.0.1 works really nice, thx again!
In Manjaro, atm i work with the latest git release from AUR and i want to “downgrade” to the official release. Searching for 3.0.1 manjaro in google links to the archlinux packages site where the package is updated and shows version 3.0.1.
Pacman on my manjaro installation only finds 3.0. I already updated pacman but still 3.0.1 is nowhere to be found.
I’m new to arch / manjaro, may anybody help me what i am doing wrong?
Thx!
Might be worth checking if your mirrors are up-to-date (update /etc/pacman.d/mirrorlist to match /etc/pacman.d/mirrorlist.pacnew if it exists and then uncomment the mirror(s) you want to use).
After that, run ‘pacman -Syyu’ (I think the second ‘y’ forces the mirror to update)
1 Like
Thx. That has not changed anything. But i found the “Download package” button on the arch package site, now i have 3.0.1. Unfortunately some edits from 3.1 git do not work, “mask version mismatch”. But i am running manjaro as my second system and only do some “testing”, so no problem. Maybe i just stick to the “official” releases in the future 
That would be the curved gradient mask in 3.1. I got stung by that one and will have to wait until 3.2 to get back onto the stable version
The module vibrance uses Lab and tends to darken colors a lot (which is weird because the Lab space should precisely allow to avoid that).
The vibrance in basicadj is an algo I have designed. It works in RGB space and is just the same algo as the saturation, but with a penalty applied on already-saturated pixels. The dev who put it there tested its hue preservation property, and it’s fairly hue-invariant. Of course, it will darken blue a bit (no saturated blue can ever be percieved bright, that’s how our perceptual system works, just like dark yellow is actually more muddy than yellow), but for some reason, it darkens less than the Lab vibrance.
2 Likes
You will release a 3.0.2 to install that fix in our computers, right?
Yes, but no date yet.
Hi everyone, just upgraded from 3.0.0 to 3.0.1.2 on Mac Os X and all the camera presets on denoise (profiled) module disappeared. Am I the only one experiencing this issue?
Thank you for your great work.
UPDATE: my fault, I’m an idiot, camera profiles are still there, sorry guys. I just got fooled, I’m just moving my first steps in digital post-processing and with DT, forgive me.
I don’t see any camera presets on this module. Using good words is easier to be sure we understand what you mean. There’s module presets and camera profiles, two different things, on this module.
Said that, I will suppose you talk about module presets. Presets (for example chroma and luma ones) have been removed because they were related on old version of this module (so before 3.0 updates). As they are no more useful (not adapted to new algorithm) they were removed in 3.0.1 update. This is not an issue but a one fixed.
I’m a newbie moving his first steps in post-processing and, my fault, I checked under module presets, while, as you correctly pointed out, the camera profiles are under “profiles” and I confirm they’re still there. I’m really sorry, thank you so much for spending time answering to a n00b.
Mistakes happen! Welcome to the community.
Thanks a lot.
No problem, my answer was just a statement. Welcome here !
Another basic embarrassing beginners question:
I like to adjust exposure with a value that looks similar to the camera exposure because I often do +1 or +2 when the light is a bit low. I then do -1 or -2 in exposure to get the correct light (with less noise, hopefully).
What is a better module, exposure or basic adjustments ? The 3.0.1 basic adjustments has vibrance as a bonus, very attractive.
Can I set the -1 etc in filmic RGB , seems not, or?
You need to choose whether you want to use basic adjustments or filmic (don’t use both at the same time). If you want to use former, use basic adjustments module to adjust exposure. In the case of filmic, you can use the exposure module to set exposure (or otherwise set the mid grey point in filmic itself)
Darktable 3.0.1 is much more reliable than 3.0.0 (windows version). The center view and/or the thumbnail had a tendency to go black in darkroom mode when adjusting the tone equalizer mask. Apparently, this and other “blackout” problems has been eliminated……
. Great work!
I think that darktable.org should be updated to download and install 3.0.1.
3.0.1 looks and runs terrific, and built very easily under Debian Linux.
(if this isn’t the right place to post this, I’ll apologize in advance) I’m not sure if there’s a bug, or I’m doing something wrong - I’m trying to pick a different Nikon lens under “Lens Correction”, and the list of lenses doesn’t scroll - I can’t scroll to the lens I want to correct for. It’s listed in slr-nikon.xml (the LensFun database), but I can’t see it in the Darktable list because the list is so long.
Using the arrow keys I can get to lenses that I can’t see, but I can’t see the actual choice until after it’s been selected.
It’s ok on my side. It’s probably Gtk related so which Gtk version do you have ?
(in case my reply email didn’t get to you)
I’ve got the dev packages for both 2 and 3 installed. However, if I do an ldd of the darktable executable, I see:
libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x00007fcafd753000)