Very nice, I will probably join your efforts on the project.
RapidRAW: A non-destructive and GPU-accelerated RAW image editor
71–80 of 127 posts
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#72Earlier quoted context omitted.
It's not about not "feeling right at home". I've detailed this in other comments but it's just that DT has an abysmal interface and that the devs insist that it needs to be complex. This sort of hostile attitude is part of what spawned Ansel. I much prefer the control darktable gives me now. This is a bit of a myth. One of my complaints dealt with how unintuitive the sliders are. There's no additional control gained…
First, let me concur that Darktable is not great. I found it to be neither quite as simple as Lightroom, nor as powerful as RawTherapee, and severely lacking in documentation. > Another dealt with trying to set color temperature. There are two places color temperature can be set and they'll both conflict with each other. There are at least three colour temperature / white balance controls in RT; more if you count out…
The problems I listed were for Darktable. If you use the stock configuration and go into the "white balance" module you will get an error. If memory serves turning off the "white balance" module also leads to problems. Instead you're expected to go into the "color calibration" module. More powerful? Perhaps. Unnecessarily obtuse? Absolutely.
I tried Rawtherapee first as they actually sign their (macOS) app. Unfortunately it was too unstable to be useful.
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#73The 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.
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#74Earlier quoted context omitted.
It's not about not "feeling right at home". I've detailed this in other comments but it's just that DT has an abysmal interface and that the devs insist that it needs to be complex. This sort of hostile attitude is part of what spawned Ansel. I much prefer the control darktable gives me now. This is a bit of a myth. One of my complaints dealt with how unintuitive the sliders are. There's no additional control gained…
I try to daily drive Linux but can't find a simple / nice to use RAW editor. I had high hopes for Darktable but I was astonished how bad the GUI is. When trying to delete photo, it deletes the photo under the pointer, not the photo I selected... WTF ?!? And the whole app feels so complicated... Then there's forks emerging and the dev forces are diluted in multiples applications and Adobe continues to milk its users b…
Filmulator (I really need to fix the CI...)
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#75Why the decision to store edits in sidecar instead of the app’s library? I’m sure there’s pros/cons that were considered, so curious how the pros won out.
Sidecar files (like XMP) are the industry standard for non-destructive RAW editing - they maintain file portability between different apps and preserve your original files. Library-based approaches offer better performance and organization but create vendor lock-in and complicate backups.
That's why I love DNGs. No Sidecar file to lose! Just one file, and still non-destructive.
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#76In my opinion, a web based UI for something like an image editor is a bad idea. It will be slow and resource intensive.
It’s not "web" in a way you mean that, it uses rust and gpu processing very heavily, up to the point where it just launched by web browser and that’s it
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#77Earlier quoted context omitted.
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…
> 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.
The camera makes all those decisions even when shooting raw -- and there are stored in the raw file. So, by default, processing a raw file witout doing any tweaks will get you the jpeg you would have gotten.
My camera (Nikon) -- and I assume the others -- will even store both the RAW and the JPEG, so you don't even have to go through the automatic conversion step if you don't want to.
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#78Earlier quoted context omitted.
IME in photo post-processing, good UX, smooth multi-photo workflow and intuitive controls beat technical details every time. RawTherapee is better than Darktable. But that’s a pretty low bar to clear. There are reasons people pay for Lightroom.
Partner is getting into photography and I don't have the stomach to purchase some software. I threw darktable and rawtherapee on the table but without technical grit you get nowhere really fast. It's no my wheelhouse so they are mostly in there own.
Pixelmator pro is nice on the Mac, and it's a one time purchase, not even expensive. And CameraBag was not bad last time I tried it, also a one time purchase.
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#79Earlier quoted context omitted.
IME in photo post-processing, good UX, smooth multi-photo workflow and intuitive controls beat technical details every time. RawTherapee is better than Darktable. But that’s a pretty low bar to clear. There are reasons people pay for Lightroom.
Partner is getting into photography and I don't have the stomach to purchase some software. I threw darktable and rawtherapee on the table but without technical grit you get nowhere really fast. It's no my wheelhouse so they are mostly in there own.
I've been getting into photography lately too and running into the same question. There's no way I'm getting an adobe subscription. But I'm not sure what tools do I want to pick up instead. Apple Photos has gotten me pretty far, but I'm hitting the limits of what it can do. And my photo library is getting pretty big now - big enough that I want some software to manage where my photos live as well.
Re: RapidRAW: A non-destructive and GPU-accelerated RAW image editor
#80Why the decision to store edits in sidecar instead of the app’s library? I’m sure there’s pros/cons that were considered, so curious how the pros won out.
Its pretty simple to explain: Imagine you have your images in a folder and you rename this folder, without RapidRAW knowing this. It would fail to associate the edits with the image. Lightroom does it the same way. Or imagine you‘re editing on your computer and want to move to your laptop to continue editing - the edits would only be saved on the computer, if it‘s only saved in the app library.
My folders do not have a series of sidecars written by Lightroom. The edits are stored within Lightroom’s library. I have other programs that use sidecar files, but Lightroom does not. Maybe it’s a preference, but I’ve never looked. If I move/rename a folder Lightroom was looking at, it asks me to relink it when I next open Lightroom. It’s not an earth shattering situation to fix.