darktable

I don't think your assessment of the DJI Mini thing is very fair. Sounds like they would be more than happy to accept a pull request and indeed there is an open one the maintainers are helping get merged [1]. Shame that the new workflow doesn't work well for your particular camera and setup - but I would encourage other people to try it, because it works great for mine. We know :-) It very much seems there is no dt developer currently interested in this sort of correction, i suppose none are using such devices. Just two reminders: Such "missing support for my camera" started me to get into darktable code. A lot of code to be reused is there, there are already some hints, just go ahead :-) Some comments above i suggested something ... :-) 1: https://github.com/darktable-org/darktable/pull/20467

I've used Darktable for almost a decade quite happily, but recently am moving off of it because they made one MASSIVE blunder with the new shitty color grading and white balancing tool that never gets any of my images right, all the tones are off, and it doesn't have sane defaults that renders things at least "almost correctly" at first go like the previous white balance tool did. It was way better a couple years ago with the vanilla "White Balance" and "Base Curve" tools. Darktable also cannot correctly color any of my DJI Mini Pro imagery. None. They all have really bad greenish hues. I haven't been able to publish any of my DJI images for 4 years now because Darktable won't fix it, and it's a known issue that they explicitly plan to not fix (https://github.com/darktable-org/darktable/issues/13319). I'm currently starting to love RapidR

I totally understand the point of view from maintainers. Review fatigue of low quality slop is a legitimate issue. The worst ones are fully autonomous AI agents looking for open source projects and adding random pull requests. But in some cases, I find a legit bug that needs fixing. For example, I want to get a particular program working in Wine/FEX on aarch64 [1], or I find a 12 second hang in Darktable [2]. The problem is that, as a software engineer working in a totally different discipline, I have no knowledge of the low level C code to fully understand what the problem even is, or how to fix it. All I want to do is to fix the issue and help other people avoid running into the same issue. Right now, on my machine, I maintain a set of custom patches to get everything working. But I am too dumb and ignorant to figure out how to create t

Darktable has a "neural restore" algorithm [0] in the development version (intended for midsummer release). Note: - It appears to be an out-of-band pre-processing stage (run the image through denoise to produce an intermediary TIFF), unlike most other parts of the program. - All AI features are gated behind compile-time flags which default to off. [0] https://github.com/darktable-org/darktable/pull/20523

That insane behavior around acting on the highlighted image instead of the selected image has finally been fixed: https://github.com/darktable-org/darktable/issues/16850#issu...

Fujifilm lossy compressed raw still isn't supported after many years [1]. [1] https://github.com/darktable-org/rawspeed/issues/366 And in my experience there has been lots of bugs with Fujifilm raws in darktable: [2] https://github.com/darktable-org/rawspeed/issues/354 [3] https://github.com/darktable-org/darktable/issues/18073 However, Fujifilm lossless compressed raw actually does a decent job keeping the file sizes down (about 50% to 60% the file size of uncompressed) while maintaining decent write speed during burst shooting.

> the while loop of death (source: https://github.com/darktable-org/darktable/blob/darktable-4....) shudder Yeah, I too wouldn't want to volunteer to contribute to a project which is OK with this.

FWIW, here is the recent merged pull requests from darktable: https://github.com/darktable-org/darktable/pulls?q=is%3Apr+i... At the moment, this is about a week's work by eight authors. Others cycle/in out, of course -- this is a spot sample. They range from bugfixes to performance improvements to documentation to translation work. All what one would hope for in a software project headed to its bi-annual release next month. There are many ways to develop, and it may be a bit cruel to compare a one-man show to a long-term international collaboration. But here are the recently merged pull requests from the software which is posted about in the blog post: https://github.com/aurelienpierreeng/ansel/pulls?q=is%3Apr+i... On the first page, I see about five authors offering PR's over the course of all of 2023 -- a much slower pace of community

Author has a blog post here, https://ansel.photos/en/news/darktable-dans-le-mur-au-ralent..., which exhibits some example code, for example, this: https://github.com/darktable-org/darktable/blob/darktable-4.... That's a far cry from what I'd find acceptable in any project.

4.2 dropped in December 2022. 4.4 was released in June 2023: https://www.darktable.org/2023/06/darktable-4.4.0-released/ 4.6 is slated for December 2023: https://github.com/darktable-org/darktable/blob/master/RELEA... Their release schedule has been remarkably consistent.