Local adjustments is in dev

[dngimage]

@Wayne_Sutton,

Thanks for confirming.

[jdc (Desmis)]

@dngimage @Wayne_Sutton

Yes there was a bug…crash due to “Laplacian” not used in inverse…
I thik it is solved in branch “Local_ch”

Local ch - Curve C=f(H) in Color and Light

Jacques

[jdc (Desmis)]

I just merge this change
jacques

[Wayne_Sutton]

Thank you, it works well and is very useful.

[jdc (Desmis)]

@Wayne_Sutton

Thank you
I just push 2 commit for all the curves in “color and Light”

Now, you have “references” (hue, luma, chroma) draw in each curve. I think it will help
jacques

[Wayne_Sutton]

@heckflosse

Also the step pyramids are in non locallab wavelet code as well. I will change them to more continues pyramids next days…

@heckflosse Will the changes affect the way the Edge Sharpness module in Wavelet Levels behaves and in particular this?

Wayne

[heckflosse (Ingo Weyrich)]

@Wayne_Sutton

and in particular this?

I don’t think so

[jdc (Desmis)]

@Wayne_Sutton

I think in all cases, its better…
Ingo replace a step pyramid, by a smooth pyramid…
The differences are small, but nevertheless it is better

Other thing
I found an old bug, in calculation H (LcH) use to hue reference to H (HSV) (uses by GUI curves), this differences leads to wrong values display…
I have fixed this (bad) behavior)

Jacques

[dngimage]

@jdc,

The Dynamic Range Compr. & Exposure” with inverse problem is gone.
C’est parfait maintenant.

Thanks

[nosle]

Some questions about highlight recovery and local adjustments (among others)

RT controlling highlights, differences between various tools

I photograph outdoor scenes and typically under expose to keep detail in the sky/clouds. To massage the scene into typical dynamic range I can sort of use two approaches (there are more) Use the exposure get the main subject visible and then claw back highlights using: a. Highlight Compression b. Graduated filter c. Color toning (with luminance mask) d. Local adjustments (dyn. range compr. or tone equalizer) Selectively raise all but the brightest tones. I find that from 1. above o…

[betazoid (Anna)]

Played around a few times with local adjustments and I think it’s really nice…

[betazoid (Anna)]

So local adjustments will be in the next stable release which will be released when? I am guessing it will be Version 6.0?

[jdc (Desmis)]

Since the last commit (130fbb8 - Aug 10, 2020) many improvements have been made by Ingo @heckflosse , Pierre @Pandagrapher and me, and with advice from team members

• speed-up and code improvment ( especially the “wavelet” part)
• rename the “normal” and “expert” complexity levels to “standard” and “advanced”
• add complexity level “basic” : “basic” is simpler than “standard”, in particular, no mask, no curves…

jacques

[CranberrySauce]

Is Spot the only type?

Like freehand curves and bruishes aren’t in the dev local lab build?

[Wayne_Sutton]

@CranberrySauce

Is Spot the only type?

The idea behind the original commercial spot concept was to have a quick and easy way of doing local edits without having to use brushes, lassos, magic wands etc., to create selections . It is the same idea behind RT-Spots which use their own algorithms and offer more flexibility:

• There are two shapes available (an ellipse and a rectangle), which can be adjusted asymmetrically around the spot itself.
• You can control the detection mechanism within the shape to allow for more precise selections
• You can associate parametric masks with the RT-Spot to refine the selection in difficult cases.

There is a description in Rawpedia under Local Adjustments (the translation is still work in progress). Local Adjustments - RawPedia

Hope that helps

[CranberrySauce]

@Wayne_Sutton

The idea behind the original commercial spot concept was to have a quick and easy way of doing local edits without having to use brushes, lassos, magic wands etc., to create selections.

It feels really over engineered and oddly different from all other tools out there.

I always end up going back to Lightroom or ART and using the Brush tool with soft edges, takes about 20 seconds on complex shapes and great for about 80% of situations.

Compare this to, trying to fiddle around with selection using “sliders” which assume there is something in common like color to filter on.

Hmmm… still think there should be a brush option like the ART fork.

[Wayne_Sutton]

@CranberrySauce

oddly different from all other tools out there

The original U-Point concept as used in the the Nik Collection (c) was also quite different from the usual approach to local editing. However what suits one person may not suit another , which is why we are lucky to have so many options.
Personally I find RT-spots quick and easy for simple edits such as lifting the shadows on a face, adjusting skin tones, doing selective denoise and sharpening etc. etc.

@CranberrySauce

It feels really over engineered

The interface has three options: Basic, Standard and Advanced so it can be as simple or as comprehensive as you want.

[JackH]

I have been a big fan of the U-Point approach since I first used it in Capture NX2 (then in PS via nik), so if RT-spot is similar I am a happy camper.

[mikae1]

So excited — I’ve been waiting years for this!

Is it possible to try it out now on macOS (without building from source)? Can’t find macOS among the automated builds.

I like the Lightroom brush, but I’m also in love with the u-point concept in Snapseed (also used CaptureNX long ago). A combination of both is probably the best, but I will hold my comments before I’ve tried out the RT implementation of this concept.

[Rick]

@Wayne_Sutton

The original U-Point concept as used in the the Nik Collection © was also quite different from the usual approach to local editing.

I +1 this comment. Nik continues to be the only FOSS application that I use, and that’s due in large part to U-point. It’s nothing short of sorcery.