- 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

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.

Comments URL: https://news.ycombinator.com/item?id=43844287

Points: 5

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43756518

Points: 2

# Comments: 0

> 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]

[0] https://hr.cornell.edu/2025-hiring-pause

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 development.

It appears that Ansel is being developed more by direct commits from its main author. So let's compare the recent commits:

https://github.com/aurelienpierreeng/ansel/commits/master

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.

Here goes for darktable commits:

https://github.com/darktable-org/darktable/commits/master

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.

To semi-misquote Lewis Carroll: Which is better, a stopped clock or a clock which loses a minute a day? Carroll posits the former, as it is precisely correct twice a day. The trick, of course, is knowing for sure when those two times per day will be.

LibreOffice, it's a slippery slope... Next thing we'll be using the mouse and ditching the tiled window manager.

> We are adjusting our engineering priorities for RHEL for Workstations and focusing on gaps in Wayland, building out HDR support, building out what’s needed for color-sensitive work, and a host of other refinements required by Workstation users.

This is a long-standing and important effort [1] to make Wayland more plausible for image/video-editing.

[0]: https://lwn.net/ml/fedora-devel/20230601183054.12057.45907@m... [1]: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...

I sent Steve a fan email, and to my wonder, received a reply back. He struck me as a lovely guy, happy to correspond about the music and his general state of mind.

My memory is that an attraction of his column was that each was written from a different place, and described the adventures getting there, and being there. But then he got to the Florida Keys. And hung out at the Florida Keys for another column. And then hung out there for another column or so -- it was a pretty great place. And eventually, CompuServe dropped the column.

So nice to read the article on Steve Roberts, and fill out a bit these memories. Perhaps somewhere out there, someone has also written a memoir about CompuServe in its pre-Internet 1980s glory?

One way to think about it: Today's LLMs require incredible outlays of capital and processor power (and crews of folks with doctorates), such as billion dollar companies can provide. But how is that different from what Intel brought to commodity CPUs in the '90s/'00s, or what Nvidia brought to GPUs in the '00s/'10s? Or even what Cisco and folks brought to networks?

Though we may never design an artisanal CPU/GPU/router, we get to work with them every day to make things, and to communicate. These LLMs can be that for us at this moment. Let's go out and enjoy them, and see what we can make within their (vast) domain-specific capabilities.

[takes off rose-tinted glasses]

Not to be petty, but I see that to all appearances Smith is not, having given "Catmull, Edwin" about half a page of index entries. (The cover identifies Smith as "Cofounder of Pixar. And that there are index entries for "Pixar, origin and cofounding of, cofounded by Ed Catmull and Alvy Ray Smith" as well as for "Pixar, origin and cofounding of, not cofounded by Steve Jobs".)

> The only thing is that color management for Wayland is progressing and far from being completely done. Even if work is quite slow, things seems to go in good direction. For correct and complete Wayland color management, we just have to wait again.

Blender itself seems to be color-profile aware: https://docs.blender.org/manual/en/latest/render/color_manag....

Here is an issue tracking work on Wayland: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m....

There's a nice site which is parallel to this work which summarizes issues/goals: https://gitlab.freedesktop.org/pq/color-and-hdr

Here is parallel work on this in Sway: https://github.com/swaywm/sway/issues/1486 And parallel work in KDE: https://bugs.kde.org/show_bug.cgi?id=439135

I can't find any reference to color management in the Blender meta-issue at https://developer.blender.org/T76428. For X11, I believe applications would have to manually determine the color profile of the display holding the current window, then query colord or and X atom to determine the profile. The application would then manually do the colorspace conversion. Does querying colord and making an in-application conversion works for Wayland until Wayland becomes colorspace-aware? Or if there are more wrinkles?

https://thismoviedoesnotexist.org/movie/in-the-land-of-oz-th...

Which reads like a bad translation of a bad translation. Like the the old joke about the AI program which was supposed to translate "The spirit is willing but the flesh is weak" from English to Russian to English, and after the roundtrip came up with "The vodka is good but the meat is rotten."

On the other hand, the market for stock photography was already decimated by the internet. Where previously skilled photographers would create libraries of images to exemplify various terms and sell these as stock, in the last decade or so, an art director with the aid of a search engine could rapidly produce similar results.

I had a teacher who was known as a master printer. Students would ask, "How can I make a truly archival print?" His answer: "Show me something you make worth keeping, and I'll tell you."