A git question.
I have
But I still get a Gb of darktable/src/tests/integration
I was expecting that would not happen. Was I expecting too much?
A git question.
I have
But I still get a Gb of darktable/src/tests/integration
I was expecting that would not happen. Was I expecting too much?
Hey, quick question
I have a FujiFilm X-T30 III and I see that there is a bug ticket for supporting the camera. I see that its status is done but not merged into stable.
Which branch should I pull to get this unstable version while waiting on 5.8 where it seems to be targeting its stable merge? I couldnāt find a nightly or pre-5.8 so I was hoping someone could point me to the right spot.
You can find it by using tags
Release Darktable nightly build 20260808 Ā· darktable-org/darktable Release Darktable nightly build 20260808 Ā· darktable-org/darktable Ā· GitHub
I have no idea if it solves your issue but here it is
Has darktable changed its default behavior when it comes to carrying over exif info when exporting images? Maybe something got messed up in my config, but images starting from a few months ago started being exported without exif data. I understand I can create a preset and so on, but was just wondering if this default was changed.
I have a problem that Darktable doesnāt export the star rating randomly. Iāve never figured out what could be the problemā¦
Did you verify that the boxes for EXIF and metadata are checked in the export module preferences?
I think itās a bug in master (not a surprise of lateā¦), even if I check them, upon restart itāll forget the settings and export without exif. Based on my exports, it has been happening for some months. Iāll open a bug report. It works fine in 5.6 from the arch repos.
The AppImage does not show the mouse-over tool tips.
Debian 13. happens with 5.6.0 and 5.6.1
Have no idea if that was the case before.
Sugestions how to fix or debug or further reading?
Check github to see if your problem is there, either open or recently closed, if not open a bug report
In addition to what @hatsnp said: 5.4.1 is not affected? You could try the nightly AppImage (if you do take care to use a different --configdir because it might affect your stable installation).
BTW thanks for your work on the docs translations
!
The answer is very simple and the question has proven to be stupid:
The key shortcut Shift-T does toogle tooltips on/off.
It was disabled on my system, by accident i suppose,.
.by accident I discovered that the very old module colour correction works really well after using the new colour harmony. The vector scope is really helpful here to saturate or slightly move the colours
So my stupid question is should I be using 15 year old module with a very new one? What risks are there to my processing? It made me realise that the colour harmony can be incorporated with other modules, particularly as a starting point
Sorry if this doesnāt read well but I was just excited to find an old module work so well with a new one
IMHO there is absolutely nothing wrong with using an old, āoutdatedā tool if it brings you joy and the results you like.
Also watching the vectorscope while playing with color correction is mesmerizing
- would make a great Windows Media Player visualization ;-).
Itās not broken or deprecated, itās just a simple module that comes after the tonemapper by default. Itās like the split toning module. It will change the colour of maximum white as well as dark shadows (of course you can protect them with parametric masks). But if you like the way it looks, itās fine.
In my opinion the color harmony model is more of a black box module whereas the color corrector is more manual, which I think is superior if you actually want have some control and thought into what youāre doing to the photo.
Darktable error messages are my favorite, like ā āfailed to allocate memory for thumbnail export, please lower the threads used for export or buy more memoryā ![]()
I can confirm buying more memory solved a problem with a similar message.
Iām occasionally getting something about graduated density has had an introspection error. ![]()
Yeah, I like that one, sounds very existential.
Is there a way to update an existing style? Or is delete+save the way to go?