As newbie, I need to achieve a result as in ACR

I guess you mean the other right :wink:

4 Likes

Well, I don’t use LR, I find it so uncomfortable. I use ACR, which uses the same API as LR, but differently. ACR offers me a nice starting point - according to my taste.
Regarding the software… There are technical guys and simple users, who don’t need such refined details. They need simple controls, as a few sliders… This is the reason why powerful tools are not easily adopted these days, and thinking to those simple users needs consistent efforts, with the gain of having an increasing user base. This is the story of Linux, Linux DE’s and lots of free/open software. In time, the first impression remains in their heads and won’t come easily to use software that made them suffer once.
Now, what I have struggle with here, was, in part, the unresponsiveness of the edit boxes and made me think they have no effect. Some timer to decide the user have ended editing some value and start applying it would be nice.
On other hand, to help the migration, also my case, some profile for the initial automatic processing, with a very close result to some common commercial tools used these days, is very useful. You give to the new users something familiar that makes them stay. Just my two cents…

@msdobrescu Here’s what I would do:

Open the raw and apply neutral profile:

As it’s overexposed I set the exposure compensation to -1:

Adjust the white point until it looks so:

Then increase it by 0.01 (press the +) to remove the pinkish tint:

Enable Highlight reconstruction:

Now the details are partly back in overexposed regions. Let’s have a look at CA which you can see here:

And remove it:

Then a bit of sharpening, first without sharpening:

Then with sharpening:

Maybe Local Contrast, first the before view:

Then the after view:

Further adjust to your taste…

4 Likes

Wow! Thanks for the detailed instructions!

1 Like

@heckflosse Could you elaborate on what you are doing with white point? I think people would benefit from that.

2 Likes

@msdobrescu The fact, that I had to adjust the raw white point, means that the white level for your camera is probably not correct in RT. Can you provide some completely overexposed raw files from your camera using filebin.net and post the link here?

I did something, which usually should not be necessary if the white point for the camera in RT is correct. If the white point from dcraw or camconst.json is too large you get this pinkish tint when applying negative exposure compensation. In this case the white point was too low, means, to recover as much highlights as possible, I increased it by reducing the value of the white point correction adjuster until it was too much (pink) and then increased the adjuster value again by 0.01.

I have only some in the same place and having the same camera settings. Does it help?

Well, we can try. If there is at least a small completely overexposed region in the raw, it could work. The larger the region the better.

I lost my rock. In pilot training, the joke was that you held a rock in your right hand to remember which way… :smile:

1 Like

Right is where the thumb is left :wink:

2 Likes

There’s no entry for the Canon 400D in camconst.json; dcraw.c has it, and the white value is 3726. That’s what libraw reports in its metadata.

When I open this image in rawproc, all three channels saturate at 4056.

@msdobrescu There is a file camconst.json in your rt installation folder.

Open it with an editor (not with notepad.exe) and insert this lines

    { // Quality C
        "make_model": [ "Canon EOS 400D" ],
        "ranges": {
            "white_max": 4018
        }
    },

after

// Canon mid-range DSLRs (Rebels)

Edit: hold please. there is something wrong.

Thanks, done, but remember, I’m on Sabayon Linux, will be overridden at update time (this is a rolling release distro).

It will be included in dev branch of rt

Ah, learning in progress: what did you do to arrive at that number?

I basically followed this instructions: RawTherapee/rtengine/camconst.json at dev · Beep6581/RawTherapee · GitHub

@msdobrescu As the entry above was wrong, here’s the fixed one

    { // Quality C
        "make_model": [ "Canon EOS 400D DIGITAL" ],
        "ranges": {
            "white": 4018
        }
    },

Thank you so much, this improves things a lot!

New white level pushed to dev

Edit: I used the more progressive wl by @ggbutcher because it worked fine

2 Likes