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

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 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).

Beware though that it tends to not abstract away a lot of technicalities, if you dig deep enough you may encounter exotic terms like “illuminant”, “demosaicing method”, “green equilibration”, “CAM16”, “PU”, “nit” and so on, but I personally love it for that even while I am still learning what half of it all means.

I’d say the only major lacking feature of RT is support for HDR output, which hopefully will be coming by way of PNG v3 and Rec. 2100 support.

I like this one its simple and easy to use

May I ask why choose to shoot raw given simplicity and ease of use are priorities?

Those are certainly not mutually exclusive! The point of shooting raw is not to painstakingly tweak super-technical details, it’s to get processing latitude to make photos the way you want. Often that involves simple adjustment of shadows, highlights, saturation and so on, applied to a large number of photos in bulk.

The priorities are mutually exclusive: delegating scene data conversion to in-camera engine grants you the most simplicity and ease of use at the expense of control; the territory of technical details grants you the most ability to make the photos looks the way you want at the expense of simplicity. You dial one up, you dial the other down.

For example, your choice of demosaicing method can make a tangible difference in finer details: some methods would make them less noisy (better for some styles), others would better preserve finer details (better for other styles). Abstracting it behind one “more detail—less detail” slider isn’t going to work because “detail” can mean a multitude of things, of which sometimes you want one and not the other, and inventing new sliders with user-friendly but inscrutable labels a la “brilliance”, “texture”, and so on, can only get you so far.

There are shades between simplicity vs. control, of course, and so I am curious to know the answer from the horse’s mouth so to speak: to what end they choose to compromise simplicity.

It’s a case of diminishing returns. Shooting raw is a huge and obvious improvement if you want to post-process in almost any way. Conditional on that the workflow should be as smooth and simple as possible. Abstract controls like "clarity" are fine if the result of adjusting them is tangible and almost always does what you want. Giving the user lots of knobs that hardly have a visible effect (let alone a desired effect) is not an improvement.

Almost no professional photographer will care about the intricacies of the demosaicing algorithm, or the choice between a dozen different denoising modules, and Lightroom is entirely correct in not giving you a zillion knobs to adjust things that have no effect on image quality except in the rarest of cases. In 99% of cases the controls that matter are:

* Basic exposure/shadows/contrast etc

* Curves/levels for more control if needed

* White balance

* Cropping, obviously

* Cloning/healing brush

* Simple knobs for sharpening and NR

* Level/perspective adjustment

* Lens aberration correction (most of the time no manual input needed if the lens is in the batabase)