Live data from Hacker News

Darktable

darktable.org

21–30 of 183 posts

Re: Darktable

#21

I highly recommend people try out Capture One. After using Lightroom for years, switching to Capture One a few years ago felt like someone turned the lights on. Far and away the best photo and media mangement software I've ever used by at least two orders of magnitude, and reasonalbe license cost and generous free tier.

If Capture One or any other buy-once commercial offering worked at all under Wine (or, in a dream land, had a Linux build), I would happily pay for it. But unfortunately, I've had no luck getting either Capture One or DxO PhotoLab running on Linux.

I struggle with Darktable's workflow, but it works without issue on Fedora with Wayland (including with my monitor's color calibration), so I'm sticking with it for now.

Re: Darktable

#22
post #18

I highly recommend people try out Capture One. After using Lightroom for years, switching to Capture One a few years ago felt like someone turned the lights on. Far and away the best photo and media mangement software I've ever used by at least two orders of magnitude, and reasonalbe license cost and generous free tier.

Private equity owed proprietary Mac and Windows exclusive. No thanks.

Want the best software for editing photos? No thanks, I'd rather use inferior open source solutions. Go Gimp

Re: Darktable

#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 pipeline in the metadata for each file such that it could be reproduced reliably across software versions and even forks. Like a sequence of shaders.

Re: Darktable

#24

I highly recommend people try out Capture One. After using Lightroom for years, switching to Capture One a few years ago felt like someone turned the lights on. Far and away the best photo and media mangement software I've ever used by at least two orders of magnitude, and reasonalbe license cost and generous free tier.

Not getting into which solution is better, but Capture One is at least 50% more expensive than Lightroom. It's a material difference.

Re: Darktable

#25
post #9

https://github.com/aurelienpierreeng/ansel

I haven't heard of either, but have been hoping for a replacement for Aperture for years. Having no knowledge of the history here, reading the `ansel` github page sounds like the developer has some animosity towards `darktable`. Does anyone have any experience with both? Or more knowledge of the history here?

If you’re looking specifically for an Aperture replacement, Nitro[0] was created by the person who led the Aperture, iPhoto, RAW Camera and Core Image engineering teams, as well as the imaging team for the Mac version of Photos.

No subscription cost either.

[0] https://www.gentlemencoders.com/nitro-for-macos/

Re: Darktable

#26
post #18

Earlier quoted context omitted.

Private equity owed proprietary Mac and Windows exclusive. No thanks.

Want the best software for editing photos? No thanks, I'd rather use inferior open source solutions. Go Gimp

Darktable is top class.

Re: Darktable

#27

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…

Foss alternatives generally handle this by either not changing the format too much or by making old versions available to download in perpetuity and then you can manually upgrade your decades old library at your leisure. I'm really glad they don't spend their already limited resources on trying to handle every possible old library file under the sun, as long as you've got incremental upgrades working you've got a path. And if you are not using it on timescales that would allow for incremental upgrades you are not the ICP anyway so they've made a good engineering decision.

Re: Darktable

#28
post #17

Ditched Adobe Lightroom 10+ years ago in favour of Darktable and never looked back. It was the first FOSS software, which showed me how green the grass can get.

Pretty sure Darktable only supports openCL and not Metal for MacOS. OpenCL is unsupported for M1/2/3/4/5, which makes RAW file processing, batch workflows, basically everything, unusably slow. Unless something has changed in the past few months, Darktable is dead on MacOS with no fix in sight.

I used Darktable on Mac yesterday

Re: Darktable

#30

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…

>How do the FOSS alternatives handle this?

In the same way, because there's no other way. Darktable in particular contains previous versions of the color pipeline. Every RAW software does that.

Post reply on HN