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.
darktable has supported Fuji raws since 2014! It currently supports the classic "uncompressed" RAFs, as well as the newfangled "lossless" (compressed) RAFs. I do not believe that it supports the "compressed" (lossy) format. So setting "recording type" appropriately on your camera is necessary.
I'm curious where the notion comes from that there is no support for Fujifilm RAF files, as I see this in a cousin comment as well.
> Together with all of American higher education, Cornell is entering a time of significant financial uncertainty. The potential for deep cuts in federal research funding, as well as tax legislation affecting our endowment income, has now been added to existing concerns related to rapid growth and cost escalations. It is imperative that we navigate this challenging financial landscape with a shared understanding and common purpose, to continue to advance our mission, strengthen our academic community, and deepen our impact. [0]
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:
Page 1 of Ansel commits is by its mono-author from the last week. Page 2 takes us back to August. Page 3 back to June. I totally understand that good developers need to work carefully and sit on things, then release them in due time.
If we take a moment to page back to page 3, one can note that we're back to two weeks ago (rather than June). Steady work by a committed community matters. The log of work done is may be quite worth looking at, rather than incendiary blog posts.
What we're seeing here is one embittered ex-developer spending time/effort saying toxic things about their former collaborators in a public forum. At the same time the former developer is making a claim to such radical competence that they can somehow keep an open source project of considerable scope together -- one which until now was coded by generally at least half a dozen committed authors at any given time. The darktable project was originated by some quite bright folks. Others have cycled in/out over the years. Generally without too much drama. It's too bad to be giving so much attention to divisive claims.
A fair question. An easy answer is that I thought Lisp was pretty cool, and that the students were capable of it. And, pragmatically, I was experienced with it, unlike MaxMSP or Processing.
But there was something philosophical: I liked the idea of introducing them to the feel of fundamental computer science, rather than a nice layer over computers for artists. (And what artists actually use those nice layers?) I wanted them to experience an open source ecosystem (unlike Max), and I felt that the Java-base of Procesing was off aesthetically -- too many layers over the machine.
Thinking about the OP, I do wonder what it would have been like to teach coding-for-artists with Hypercard. One thing I love about Emacs Lisp is that it is only grudgingly visual. That it returns computers to something which sends output to a TTY. It gives people who have grown up with a GUI a vision of what computers were like before. I like that Emacs (and Lisp) are things with a history and touch on earlier eras of computer culture.
As an example, a decade ago I taught art students how to code. They had Macintoshes. I had them download Emacs then taught them Emacs Lisp. As insane as that sounds, it was interactive, easy to install, and interesting. They were able to write programs in the REPL after the first class. I wouldn't have dared to have put them in front of XCode or some equivalent IDE.
- 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