Live data from Hacker News

Ansel

ansel.photos

41–50 of 167 posts

Re: Ansel

#41
post #27

Somewhere very recently I encountered a quote from Ansel Adams, in which he seemed to anticipate that "electronic" photos would be the next big thing, in (IIRC) 1980. Wish I could find that again. Seemed remarkably prescient.

It was in Playboy (May 1983) https://petapixel.com/2022/07/30/ansel-adamss-interview-with... “There’s no end in sight. Electronic photography will soon be superior to anything we have now. The first advance will be the exploration of existing negatives. I believe the electronic process will enhance them. I could get superior prints from my negatives using electronics. “Then the time will come when you will be able to…

"I wish I were young again!"

Ah, the oft-repeated refrain of those who never stop learning.

Re: Ansel

#42
post #8

This is the work of a former "darktable" developer (Aurélien Pierre) who decided to fork the codebase and go it alone. He has strong opinions about the correct way to do things. I like some of the cleanup on the UI that he has done. For now, Ansel and darktable are compatible in terms of the underlying database. So you can easily switch back and forth between them. If the fork diverges significantly, it would be more…

> "Ansel is what Darktable 4.0 could have been if its developers were not so busy turning it into an usability nightmare. Ansel is a Darktable 4.0 variant where 30.000 lines of poorly-written code and half-broken features have been removed, and 11.000 lines rewritten : it runs faster, smoother, uses less power and requires less configuration. Enjoy an app focusing on getting work done and stability."

Shots fired!

Re: Ansel

#43
post #10

Oof. Looking at the "Transitioning from Darktable" page ( https://ansel.photos/en/doc/special-topics/from-darktable/ ), the author is extremely disparaging about Darktable developers. Very off-putting, even if some of the changes seem sensible. [edit] Make that quite a lot of the changes, actually, including getting rid of some really dangerously bad bits of UI design. Still dislike the guy's attitude but I've got to…

This guy basically changed darktable from a shitty Lightroom clone to something truly unique very recently, and his approach is highly divisive among the users.

Yeah, having read the article linked above [1] I see his point - it definitely looks like he's put in an enormous amount of work for the project, and I can see where his frustration comes from!

To me, Darktable has a 'feel' of a highly technical editor for people who really care about colourspaces etc, and although I hardly know anything about colour I rather appreciate that. It's interesting to note that almost all the modules that contribute to that 'feel' are written by Aurélien.

[1] https://ansel.photos/en/news/darktable-dans-le-mur-au-ralent...

Re: Ansel

#44
> On the following picture, I made the styling, the make-up, the lighting, the shot, the editing, the retouching, the software color filters, the documentation to use them, the website to talk about them in 2 languages, and even the colorspace used for saturation adjustment. You will find very few people with this kind of full-stack understanding of light and color able to also write efficient computer programs and read academic research papers on applied mathematics. Yet, you will find a lot of image editing applications and a lot of guys trying…

Jeez, wish I had 1/10th of the confidence of this guy

Re: Ansel

#45
post #8

This is the work of a former "darktable" developer (Aurélien Pierre) who decided to fork the codebase and go it alone. He has strong opinions about the correct way to do things. I like some of the cleanup on the UI that he has done. For now, Ansel and darktable are compatible in terms of the underlying database. So you can easily switch back and forth between them. If the fork diverges significantly, it would be more…

I admire his work.

But as a Darktable user, I found the implementations of strong opinions frustrating because I value actual workflow above potential technical superiority.

Display referred worked fine for me because the important work happens before the shutter is clicked. The skill I want to develop is fixing things in the lens not fixing them in post.

Breaking changes suck.

But again open source developers don’t owe me anything.

Re: Ansel

#46
post #8

This is the work of a former "darktable" developer (Aurélien Pierre) who decided to fork the codebase and go it alone. He has strong opinions about the correct way to do things. I like some of the cleanup on the UI that he has done. For now, Ansel and darktable are compatible in terms of the underlying database. So you can easily switch back and forth between them. If the fork diverges significantly, it would be more…

I tried to use Darktable coming from Lightroom, and I have seldom felt as stupid. I just couldn't grasp how Darktable worked.

Re: Ansel

#47
post #18

Earlier quoted context omitted.

> Anyone know what happened to the Darktable project? Are you referring to the fact of there being no releases in the last year or so? Edit: Ignore the above - it's incorrect.

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.

Yeah. My mistake: I somehow overlooked those.

Re: Ansel

#48
If you're using nix, I was able to make a build from the darktable derivation[0] modified to use fetchgit (since he hasn't made a github Release since December) and `s/darktable/ansel/g`.

    src = fetchgit {
      url = "https://github.com/aurelienpierreeng/ansel.git";
      rev    = "f7669af89a71882ebad15982d698b8df7e6c6ce8";
      sha256 = "sha256-FI6dKUrmtTG7DIV0MmY6XdqlUpqdt7boKuXKU6CywjA=";
      fetchSubmodules = true;
    };
[0] https://github.com/NixOS/nixpkgs/blob/nixpkgs-unstable/pkgs/...

Re: Ansel

#50
post #8

This is the work of a former "darktable" developer (Aurélien Pierre) who decided to fork the codebase and go it alone. He has strong opinions about the correct way to do things. I like some of the cleanup on the UI that he has done. For now, Ansel and darktable are compatible in terms of the underlying database. So you can easily switch back and forth between them. If the fork diverges significantly, it would be more…

I admire his work. But as a Darktable user, I found the implementations of strong opinions frustrating because I value actual workflow above potential technical superiority. Display referred worked fine for me because the important work happens before the shutter is clicked. The skill I want to develop is fixing things in the lens not fixing them in post. Breaking changes suck. But again open source developers don’t…

I don't disagree, I spend a lot of effort thinking about things at exposure-time. I think the thing that sold me on scene-referred is that I started conciously thinking about the kind of data I was capturing. It's often the case that the display medium, or its artistic representation, has a much lower dynamic range than the sensor in the camera, and so there are a number of things you can do to get the most data possible when capturing to leave yourself room for expression at presentation time.

What this gives you isn't necessarily the ability to "fix" things in post, but the ability to decide how you want your image presented in a certain medium or format when "developing". Even master photogs like Ansel would take liberties when developing to realize their vision from the negatives they were able to capture.

Post reply on HN