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

Darktable 4.0

darktable.org

Post reply on HN
Print view View original

81–90 of 116 posts

Re: Darktable 4.0

#81

Post by t0bia_s »

saturn5k wrote: post #79

On several ocassions I've tried switching to Darktable or RawTherapee, but they never seemed to offer the practicality and ease of workflow that Lightroom has. They have tons of features and kudos for that, but when it comes to editing hundreds of photos, LR is the only choice for me.

Agree. To manage tousands pictures, LRC wins. DT and RT are full of features that are mostly pointless for professional use.

It has that linux philosophy - from nerds to nerds. But not for practical use unfortunatelly. No Fuji profiles, not many lens correction profiles, wired demosaic for X-Trans, not consistent UI, no native folder sync, no AI clone tool...

Re: Darktable 4.0

#82

Post by hef19898 »

humanlion87 wrote: post #46
hef19898 wrote: post #27

Earlier quoted context omitted.

Darktable is great! This year I restarted photography, ina serious manner, after quite some time. Serious as in I try to get beautiful pictures I could hang on a wall. I also started to do proper post processing, and darktable is quite handy. My dad used to be a pro photographer, now retired, and gave me crash course in RAW processing. Besides some handling differences between lightroom and photoshop he nothing negat…

Does your dad have any suggestion on resources/books that others can use to learn the same crash course he gave you? :)

Hevcertainly does, in fact besides years of experience he has quite a number of books at home. All in German so... If that's ok I can ask!

Re: Darktable 4.0

#83

Post by iasay »

sneak wrote: post #35
thg wrote: post #5

Earlier quoted context omitted.

> current biggest grip with dt... why are those damn arrows at the edges of the screen so tiny??? Expanding and retracting the side panels requires pixel-perfect accuracy on a ~20px target. I know I could use keyboard shortcuts, but my brain isn't wired for them yet. You can make them bigger through some CSS tweaks: https://docs.darktable.org/usermanual/development/en/prefere...

It's open source, you can change anything. The UI shouldn't be so annoying and hostile out of the box regardless. I reported this issue on irc years ago and the dev response was so hostile I abandoned trying to use it and never looked back. I pay Adobe $500/year for software that had been tested by users with developers silently watching.

Having tried to improve things on multiple projects and being ignored or got hostile responses I gave up on open source contribution.

I bought a Mac and use Lightroom and I’m happy to give them both my money.

Re: Darktable 4.0

#84

Post by iasay »

michaelmrose wrote: post #77
sneak wrote: post #35

Earlier quoted context omitted.

It's open source, you can change anything. The UI shouldn't be so annoying and hostile out of the box regardless. I reported this issue on irc years ago and the dev response was so hostile I abandoned trying to use it and never looked back. I pay Adobe $500/year for software that had been tested by users with developers silently watching.

Most projects have an issue tracker where one proposes changes or reports bugs. The IRC channel is labeled "Support channel for darktable" rather than "Tell the developer how they ought to better serve me for free" People have a finite slice of their life to give you for nothing. Putting specific suggestions on the issue tracker seems more respectful of their time.

I raised a ticket on an open source project about a defect. It was open for 6 months with no comment. So I fixed it and did a PR. The PR was still sitting there open after 6 months. More interesting PRs to the developers have been merged.

Attention and stewardship are not universal.

Re: Darktable 4.0

#85

Post by nuclx »

mikae1 wrote: post #63
nuclx wrote: post #29

I gave Darktable a try (never used Lightroom), and as an amateur, it is still kind of hard for me to achieve something better than the "out of camera" JPGs when post-processing RAW photos from my rather old Canon DSLR camera. I don't want to do elaborate stuff like working with masks / applying filters to sections of the photo only. Only thing I usually do is increase saturation, and, rarely, brightness/aperture. Sat…

> I don't want to do elaborate stuff like working with masks / applying filters to sections of the photo only. Only thing I usually do is increase saturation, and, rarely, brightness/aperture. You can't change the aperture after the image has been captured. I don't think you're the intended audience for darktable. Give https://filmulator.org/ a try!

What I meant was exposure compensation, sorry. Filmulator might be worthwhile to try, I'll check it out.

Re: Darktable 4.0

#86

Post by rglullis »

iasay wrote: post #84
michaelmrose wrote: post #77

Earlier quoted context omitted.

Most projects have an issue tracker where one proposes changes or reports bugs. The IRC channel is labeled "Support channel for darktable" rather than "Tell the developer how they ought to better serve me for free" People have a finite slice of their life to give you for nothing. Putting specific suggestions on the issue tracker seems more respectful of their time.

I raised a ticket on an open source project about a defect. It was open for 6 months with no comment. So I fixed it and did a PR. The PR was still sitting there open after 6 months. More interesting PRs to the developers have been merged. Attention and stewardship are not universal.

What I usually do when I see promising projects and slow devs.

1. "This one issue is what is stopping me from using this product. Is this current method preferred by your users or do you have any other reason to not want to change?"

2. "The proprietary solution costs $X per month. Is there any way to sponsor development? I am willing to give $X/n (where n is whatever number you are comfortable with) per month to get this issue merged and to have some sort of prioritization when triaging issues.

3. Failing those: write a blog post and propose a fork. This is usually the quickest way to get a reaction from narcissistic developers.

Re: Darktable 4.0

#87

Post by kqr »

Darktable is amazing. It takes some getting used to after Lightroom -- it doesn't hold your hand as much -- but once you get past that, the tools surpass LR in the power they give the user.

Parametric masks, LAB curves, wavelet decomposition are very powerful ways to work with the raw stuff of images.

Re: Darktable 4.0

#88

Post by tomcam »

rglullis wrote: post #86
iasay wrote: post #84

Earlier quoted context omitted.

I raised a ticket on an open source project about a defect. It was open for 6 months with no comment. So I fixed it and did a PR. The PR was still sitting there open after 6 months. More interesting PRs to the developers have been merged. Attention and stewardship are not universal.

What I usually do when I see promising projects and slow devs. 1. "This one issue is what is stopping me from using this product. Is this current method preferred by your users or do you have any other reason to not want to change?" 2. "The proprietary solution costs $X per month. Is there any way to sponsor development? I am willing to give $X/n (where n is whatever number you are comfortable with) per month to get…

Maybe some of these developers are just, you know… busy.

Re: Darktable 4.0

#89

Post by berkes »

iasay wrote: post #83
sneak wrote: post #35

Earlier quoted context omitted.

It's open source, you can change anything. The UI shouldn't be so annoying and hostile out of the box regardless. I reported this issue on irc years ago and the dev response was so hostile I abandoned trying to use it and never looked back. I pay Adobe $500/year for software that had been tested by users with developers silently watching.

Having tried to improve things on multiple projects and being ignored or got hostile responses I gave up on open source contribution. I bought a Mac and use Lightroom and I’m happy to give them both my money.

There are loads of friendly and welcoming OpenSource communities.

I'm sorry you did not stumble into them, but instead in the few hostile ones. It's a pity that made you give up.

A general tip, I give to people wishing to contribute to OSS is to first watch from the sideline. Read issues, threads, subscribe to an ML etc. Then to ask. Don't just throw in PR or feature request, but ask: is this welcome? How do you work? Any particular details that you wish me to pay extra attention to (tabs, spaces, tests, documentation, design).

As a FLOSS maintainer myself, it can be very intimidating to have someone throw a PR at you that rewrites everything (it comes across as: you suck, your software sucks, but watch me fix all that), or that disregards things that I deem critical (tests, architecture) It is really hard to review it, without coming across as an arrogant bastard. And often software that I put on a back burner will require me significant effort to get back into. So merging a simple typo fix or dependency update might cost half a day, just to get the dev env back up.

Re: Darktable 4.0

#90

Post by rglullis »

tomcam wrote: post #88
rglullis wrote: post #86

Earlier quoted context omitted.

What I usually do when I see promising projects and slow devs. 1. "This one issue is what is stopping me from using this product. Is this current method preferred by your users or do you have any other reason to not want to change?" 2. "The proprietary solution costs $X per month. Is there any way to sponsor development? I am willing to give $X/n (where n is whatever number you are comfortable with) per month to get…

Maybe some of these developers are just, you know… busy.

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.
Post reply on HN