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

RapidRAW: A non-destructive and GPU-accelerated RAW image editor

github.com

Post reply on HN
Print view View original

121–127 of 127 posts

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#121

Post by strogonoff »

account42 wrote: post #73
strogonoff wrote: post #16

The best raw image processing tool I know is called “RawTherapee”. It was developed by one or more absolute colour science geeks, it is CLI-scriptable, its companion RawPedia is a treasure trove of information (I learned many basics there, including how to create DCP profiles for calibration, dark frames, flat fields, etc.), and not to make a dig (fine, to make a bit of a dig) you can see the expertise starting with…

> you can see the expertise starting with how it capitalizes “raw” in its name (which is, of course, not at all an acronym, though like with “WASM” it is a common mistake). Language pedantry has nothing to to with photographic image processing expertise and if anything this would be a sign that the developers care more about being "right" than what users want.

I disagree; it shows understanding of subject area.

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#122

Post by strogonoff »

Mashimo wrote: post #69
strogonoff wrote: post #66

Earlier quoted context omitted.

It’s not binary is the point and the whole reason I asked the original commenter why put premium into simplicity and ease and then immediately violate that by shooting raw.

Do you understand him now?

Without him or her answering my question? Hardly.

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#123

Post by strogonoff »

igouy wrote: post #95
strogonoff wrote: post #65

Earlier quoted context omitted.

This tracks with my RawTherapee experience. I copy in base settings corresponding to the camera and the lens and then make tweaks. After a while often one of the pre-made profiles is good enough.

For example — Adobe\CameraRaw Sony SLT-A65 Adobe Standard.dcp ? DCP Tone curve DCP Base table DCP Look table

By “pre-made” I meant ones I have created previously, if that is what you mean.

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#124

Post by strogonoff »

inferiorhuman wrote: post #70
strogonoff wrote: post #54

Earlier quoted context omitted.

If you seek a GUI for managing/cataloguing photos, my advice would be to look for that and not a raw image processing tool that incidentally happens to also handle cataloguing (inevitably in a half-baked way). I have never seen Lightroom (or C1, for that matter) as compelling at all ever since I started using RawTherapee. Unlike, say, InDesign, which is legitimately a difficult to replace professional tool with incre…

my advice would be to look for that and not a raw image processing tool that incidentally happens to also handle cataloguing (inevitably in a half-baked way). Eh. No? Lightroom is a pretty darn good DAM. Maybe digiKam is at least as good, but I wouldn't know as it crashed the first time I launched it. I want to use my tools, not debug them. DT's asset management is, to put it charitably, an after thought. About the w…

Maybe Lightroom is okay for cataloguing, I cannot say because I have not used it this way extensively, but it is not up to par in terms of raw processing control in my view.

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#125

Post by rossant »

rossant wrote: post #21
TheDong wrote: post #15

Earlier quoted context omitted.

I mean, it's making 720px width jpg thumbnails using the CPU https://github.com/CyberTimon/RapidRAW/blob/fc21ede729b45d97... And then it's sending these thumbnails back from rust to javascript as base64 encoded strings, not using a shared buffer: https://github.com/CyberTimon/RapidRAW/blob/fc21ede729b45d97... This is the sorta stuff that native apps mostly don't do. They don't base64 an image just to send it to a dif…

6x sounds bad. Might be a sign of vibe coding?

I didn’t know the developer is 18. No snark intended. Great work. Slow or suboptimal code is common nowadays, and often it’s better to get it working before worrying about speed.

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#126

Post by Mashimo »

strogonoff wrote: post #122
Mashimo wrote: post #69

Earlier quoted context omitted.

Do you understand him now?

Without him or her answering my question? Hardly.

He, or rather we, want access to most of the benefits of editing raw files, but with an easy to learn UX. Even if it means giving up on the last 10%.

This concept is pretty common, not even limited to photography.

Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor

#127

Post by igouy »

strogonoff wrote: post #123
igouy wrote: post #95

Earlier quoted context omitted.

For example — Adobe\CameraRaw Sony SLT-A65 Adobe Standard.dcp ? DCP Tone curve DCP Base table DCP Look table

By “pre-made” I meant ones I have created previously, if that is what you mean.

I simply try to make "a pleasing picture" and I was trying to find a way to suggest that I'm surprised by how often that seems to be Adobe Standard.

I used to work the Exposure tab curves or Lab* adjustments but that no longer seems like a good use of my attention.

Post reply on HN