Lightroom Classic V 12.4

[Rand47]

Adobe keeps hitting it out of the park, IMO.   In today's release (12.4) they've "fixed" (to my way of thinking) the curves panel that is available in the Develop Module and (more important) in masks.  I was disappointed in my long anticipated addition of curves to masks, in that the concomitant increase in saturation along with contrast was way over the top.  Now, when you are using an RGB curve (as opposed to either R G or B individually) there will appear at the bottom a "Refine Sat." slider.  100 is their current default in added saturation, and zero is no saturation added at all (like Luminosity mode in PS on a curves layer).  Hurrah!

Also, now in the HSL panel, if you are using the tat tool, if you hold down Alt/Opt while adjusting it will gray out all but the color range being affected.  Hurrah again.

And, there are also now the grain sliders for masks. 

Nice going Adobe!

Rand

[Rhossydd]

They've even noticed the book module and added a feature. Still lacking SO much, but let's hope it's the start of some more development for it.

I'd still like to see the HSL panel in masking.

[zobelaudio]

Yeah the new stuff is pretty dope, BUT...
When I opened my catalog with 12.4 soo many previews are broken, I have restarted countless times. Don't know what's happened here. Anybody else having this

[digitaldog]

What do you mean by " soo many previews are broken"?

[Rhossydd]

Anybody else having this

No, all correct here (W10).

Maybe a local display driver/profile issue.

[fdisilvestro]

Clipping indicators?

[Rhossydd]

Clipping indicators?

Unlikely as there are multiple colours on the example above.

[zobelaudio]

yeah, this is really strange and now that I've checked, my MBP does not do this with 12.4. only my older desktop mac.
I have regenerated 1:1 previews, but problem keeps coming back, files are ok, seems to be something with the catalog. I'll do further testing and report back.
cheers. Z.

[digitaldog]

First, try disabling GPU in the preferences (Performance). Any better?

If not, recalibrate and build a new ICC display profile; the old one might be corrupted. If you are using software/hardware for this task, be sure the software is set to build a matrix, not LUT profile, Version 2, not Version 4 profile.

If turning OFF the GPU works, it's a GPU bug, and you need to contact the manufacturer or find out if there's an updated driver for it. This is why disabling GPU is an option as more and more functionality moves to the GPU in newer versions of many Adobe products. Disable third-party graphics accelerators. Third-party GPU overclocking utilities and haxies aren't supported.

Also see: https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html

If the GPU and display profile isn't causing the problem, see:
https://helpx.adobe.com/lightroom-classic/kb/lightroom-gives-error-preview-cache.html

[zobelaudio]

thx for that Andrew. I'll look into this...

[mshea]

<I'd still like to see the HSL panel in masking.>

+1 for that!

[digitaldog]

<I'd still like to see the HSL panel in masking.>

+1 for that!

Be patient (enough said 😉)

[Rhossydd]

Be patient (enough said 😉)

Of course it will be added, it would be crazy not to. It's just disappointing that it's taking so long for such an obvious addition.

There's still lots of other obvious omissions that could(will) be addressed too. It's just tedious that the obvious additions don't get done to allow real innovation to happen.

[digitaldog]

Of course it will be added, it would be crazy not to.

"We all make basic assumptions about things in life, but sometimes those assumptions are wrong. We must never trust in what we assume, only in what we know." -Darren Shan
Someone here can post about this without a lick of an assumption.
Someone else can state 'of course' without any such knowledge (That is rather tedious.). 
 

[kers]

i often have a problem with transformation: After doing some things you cannot undo them by stting all parameters to 0.
you have to go back in history.
Lenscorrection is unclear with nikon-Z camera's... it uses the wrong correction to a Sigma lens stating it is a Nikon z lens with built in profile...
vignetting is unclear how it is handled etc.  a mess. It is what i disliked about DXO. a black box that you cannot control.
the latter is probably also Nikon's fault.

[Rhossydd]

i often have a problem with transformation: After doing some things you cannot undo them by setting all parameters to 0.
you have to go back in history.

It's very annoying when it happens. I don't use transform frequently, so forget to report the bug when it does fail.

I haven't seen LR use an incorrect lens profile yet, although it will sometimes fail to pick up the profile for some lenses for no apparent reason (often on lens/camera combinations that have been correctly detected in the past).
DXO does get it wrong sometimes, but the only way you know is either by seeing poor results or getting a warning it wants to download a profile for a lens you don't use. It was frustrating, but their lens profiles for most of my kit are only marginally better than the LR option.

[Michael West]

 
does anyone know why adobe removed the color and ratings etc in the " filmstrip " Development mode.

I thought it was displaying the same options in both modes but I must have been mistaken

[digitaldog]

does anyone know why adobe removed the color and ratings etc in the " filmstrip " Development mode.

They didn't.
But you might have:

[Michael West]

They didn't.
But you might have:

I found kit,   I'd been looking for "something" at the bottom of the filmstrip rather than in the upper menu.

[Chris Kern]

Adobe keeps hitting it out of the park . . .

The healing tool is also much improved.  I find I can now use it in areas of an image which in the past would have required a round-trip to Photoshop for Content-Aware Fill.  I'm impressed with how accurately the object selection works, as well.  It has reduced my reliance on the brush tool—often producing as accurate or more accurate a mask with much less effort.