Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Darktable

darktable.org

Post reply on HN
Print view View original

141–150 of 183 posts

Re: Darktable

#141

Post by pmarreck »

qurren wrote: post #138
pmarreck wrote: post #136

Earlier quoted context omitted.

There's quite a difference in my experience between "using coding AI tools" and "using coding AI tools _well_", especially when it comes to editing code.

Doesn't really matter in this case. Doesn't matter enough for people to pull out their wallet. You can re-fork from clean OSS and re-implement any time while you sleep, using whatever AI subscription you already have.

I think you overestimate the number of photographers who are also comfortable with CLI tools, because doing this via web-facing UI's is quite less capable currently

Re: Darktable

#142

Post by blutack »

qurren wrote: post #114
lionkor wrote: post #34

I've been using darktable for a while to edit my RAW photos. The amount of features, viable workflows, and in general the quality of the software is baffling for a free product. I would happily pay 200 bucks or something per year to use this, it makes all other RAW editing software obsolete. I can only recommend it, and there's nothing missing for me, even for editing thousands of RAW photos with presets, different s…

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…

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

Re: Darktable

#143

Post by qurren »

pmarreck wrote: post #141
qurren wrote: post #138

Earlier quoted context omitted.

Doesn't really matter in this case. Doesn't matter enough for people to pull out their wallet. You can re-fork from clean OSS and re-implement any time while you sleep, using whatever AI subscription you already have.

I think you overestimate the number of photographers who are also comfortable with CLI tools, because doing this via web-facing UI's is quite less capable currently

Those photographers you speak of (95%) are using Lightroom and Photoshop and you wouldn't be able to build a fork business for them. The 5% who use Darktable are likely comfortable with CLI tools.

Re: Darktable

#144

Post by jollymonATX »

pmarreck wrote: post #119
qurren wrote: post #114

Earlier quoted context omitted.

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…

I now have a business idea: Curated Open-Source App Forks. Would you pay to have access to a service which tweaked the open-source software you use just enough to make it much more useful to your workflow, and automatically updated it over time? (I'm not just talking about a one-time fork; I'm talking about a subscription to get access to a maintained fork that stays current with upstream, fixes any conflicts, does t…

Nope

Re: Darktable

#146

Post by MoonWalk »

IgorPartola wrote: post #135

I guess I am in the minority but I did not have a good time with Darktable. I used it for a few years and then had to hold my nose and transition to Lightroom. On decent hardware (MacBook Pro that was only a few years old) it was dog slow. But the worst part was transitioning from their version 2 to version 3 of the workflow or whatever they called it. None of my old photos would render correctly after that and half…

You are in good company. I went into Darktable enthusiastically and with willingness to learn its workflow.

What I found was crippling bugs and a piss-poor UI. I've even gone back to it after a few years to see if I'd soften my stance, but nope: It blows.

Part of my beef with it is discussed below; people are acknowledging that it sucks at organizing (and, I submit, browsing). But it purports to do it, so you waste time wrestling with its ineptitude.

Re: Darktable

#147

Post by vegetarianarian »

ryanjshaw wrote: post #31
drdexebtjl wrote: post #23

To me the killer feature of Adobe’s offerings in this space is backwards compatibility. You can open a very old Lightroom library and the reprocessed photos look exactly the same. The way they do it, unfortunately, is by maintaining every previous version of the processing pipeline. How do the FOSS alternatives handle this? If I was designing a raw engine I would try to store the high-level code for the processing pi…

Killer feature is intuitive UX. Using DarkTable was an exercise in frustration for me. In darkroom mode you can’t navigate to other photos with cursor keys. Since the cursor keys do nothing else I have no idea why the aren’t bound to the nav. You have to double click on a photo to select it, one click does nothing so again I have no idea why not just bind single click to select. Then it recenters the entire row on wh…

That's a legitimate complaint as a newcomer, but the darkroom navigation hotkeys are backspace and space.

Re: Darktable

#149

Post by l8rlump »

lolc wrote: post #78
e12e wrote: post #6

See also: https://ansel.photos/en/

I used Ansel for a while, and I agree that Darktable is suffering from feature creep. Ansel right away had some usability improvements. But the amount of regressions introduced was wild. The anger you can read in the messaging was apparently also employed to cut code, and things got flaky. In the end some features I used stopped working in all releases I tried, and I went back to Darktable. Maybe Ansel is stabilizing…

Yes it is stabilising, IME. I’d recommend trying again.

Re: Darktable

#150

Post by epihelix »

qurren wrote: post #137
c7b wrote: post #130

Earlier quoted context omitted.

Stupid question, if there's an old version that you liked, couldn't you just keep using that version?

It's a pain in the ass to maintain when it has dependencies on older stuff while I upgrade the rest of the system

Well, you shouldn't need to maintain - just compile a static linked binary and you should be good for the rest of your system's life.

But more practically - I've been using darktable for well over a decade, and it's remained backward compatible with my old styles. If you like the older modules, they should still be there, and you should still be able to apply your old styles the same as always.

My own problem is that darktable keeps improving, so much so that I want to reprocess all my old photos again :/

Post reply on HN