Live data from Hacker News

Darktable 4.0

darktable.org

111–116 of 116 posts

Re: Darktable 4.0

#111
post #40

Earlier quoted context omitted.

AppImages are only as self-contained as the author put effort into making them self-contained. There's also upper limits to how self-contained they are. While some terminal and bitmap only X11 app can be compiled as static binaries, anything that depends on system libraries needs to be compiled with an older version of glibc. The best example is libGl (GLX or EGL) for hardware 3D acceleration or libvdpau for hardware…

Interesting. Yeah it seems like the solution for digikam on my solution was something like unpack the app image and recompile something and I’ve not had the time to mess with it. I hope the maintainer can release a fixed image at some point. I really like that app!

Wouldn't another option be to use the system package [0] or is the version too old? Or use the Flatpak [1] (or NIH-flatpak [2]), which is probably a better fit than AppImage for GUI programs that sit on top of a heavy toolkit.

[0] https://packages.ubuntu.com/search?keywords=digikam

[1] https://flathub.org/apps/details/org.kde.digikam

[2] https://snapcraft.io/digikam

Re: Darktable 4.0

#112
post #19

Let's see if this changed anything. But my previous experience with editing Sony RAWs on Rawtherappe and Darktable wasn't good. The color science is missed up in Darktable and in Raw therappe, I just couldn't get something decent out. I would be editing for an hour and end up with a weird looking image, while in lightroom I would be done in 10 minutes. People might say that I'm just used to lightroom but I'm not, I w…

I shoot Sony and use Darktable exclusively. I think your problem might be the base curve module and its default "Sony" preset, which looks like garbage. Try setting it to "neutral", it should look a lot better (presets are under the little arrow next to the "base curve" header). The base curve presets, if I understand correctly, aim to make the photo look similar to the out of camera JPEGs. In my opinion, they look l…

DxO is good shit, the only raw editor that ticked all the intuitive UI/UX boxes for me. Must have been through 10+ trials. The open source options in particular could do with some UI love

Out of curiosity what stops you from using dxo for everything?

Re: Darktable 4.0

#113

Let's see if this changed anything. But my previous experience with editing Sony RAWs on Rawtherappe and Darktable wasn't good. The color science is missed up in Darktable and in Raw therappe, I just couldn't get something decent out. I would be editing for an hour and end up with a weird looking image, while in lightroom I would be done in 10 minutes. People might say that I'm just used to lightroom but I'm not, I w…

I've had a similar experience, especially with skin tones. The out of camera jpegs can be a little aggressive in making skin and grass colors "pop", but they still beat Darktable (even with significant tinkering).

I totally agree, after hours of editing, i still wouldn't match the JPEGs by the camera, while in light room you start with thr same look as the JPEG even if it s a RAW file, And I would reach my desired looks in few minutes.

Re: Darktable 4.0

#114
post #19

Earlier quoted context omitted.

I shoot Sony and use Darktable exclusively. I think your problem might be the base curve module and its default "Sony" preset, which looks like garbage. Try setting it to "neutral", it should look a lot better (presets are under the little arrow next to the "base curve" header). The base curve presets, if I understand correctly, aim to make the photo look similar to the out of camera JPEGs. In my opinion, they look l…

DxO is good shit, the only raw editor that ticked all the intuitive UI/UX boxes for me. Must have been through 10+ trials. The open source options in particular could do with some UI love Out of curiosity what stops you from using dxo for everything?

But it doesn't support Linux, which is the main reason people use RT and DT

Re: Darktable 4.0

#115

Earlier quoted context omitted.

It's the busiest developers who would be interested in receiving PRs. If they go unanswered for six months, it is a clear signal that there is something stopping else them from action.

> It's the busiest developers who would be interested in receiving PRs. Depends on the PR. Bugfixes sure, but new features mean more work for the maintianer in the future.

It is also an opportunity for someone to feel involved and eventually join the group, perhaps even become a maintainer.

Speaking as a project maintainer that is starting to see some traction: I'd love to see people coming with PRs for features. It would mean a big amount of validation.

Re: Darktable 4.0

#116

Really glad there's advanced open-source tools like darktable and RawTherapee. I've switched back and forth between RawTherapee and darktable for a few years now. I prefer the UI and workflow or RT, but dt has better performance on my machine. And RT has this strange longstanding bug where the image is extremely blurry during editing, and only becomes clear after exporting. According to a github issue, a workaround i…

I'm also glad it exists but have never figured out how to use it on MacOS. I believe I somehow imported my entire /pictures folder at some point, producing many thousands of images in a film roll; I just downloaded 4.0.0 and have spent some time trying to figure out how to reset the film roll, or darktable altogether. Or how to create a new library. There's no typical top toolbar on MacOS. In clicking around, I've se…

fwiw - darktable 3.8.1 runs for me on macos 10.13.6 (2011 17" mbp) and macos 10.15.7 (2013 27" iMac). App launch takes some moments on both, but responsiveness and performance is fine+ once running. Imports (without copy) works well enough for me. The *collections* and *film rolls* I've imported from non-local sources (NFS, SMB, ssh/sftp) 'complain' with a strikethrough on re-launch, but the thumbnails and metadata remain present locally even when disconnected.
Post reply on HN