Welcome Dialog

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.


Lightrooml: Process Version 2010 is unusable in LR4: Noise sliders details/contrast are inactive

5 Votes
Enthusiast ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

When converting from a LR3 catalog, as well as when switching back manually to PV 2010, the new noise sliders ("Details" for luminance and color, as well as "Contrast" for luminance) are not active and cannot be changed.

I have no idea if just the sliders are disabled or the associated development settings vanished, too (as it is the case for the tone curve).

LR4.0 64 Bit, Win7, tested with a RAW file from Canon 40D.
Bug Fixed
TOPICS
Desktop

Views

6

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Mar 29, 2012 Mar 29, 2012
There are many fixes in 4.1, we only explicitly call out the most serious in the release notes. But yes, this is fixed. :-) -Ben

Votes

Translate

Translate
8 Comments
Mentor ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

They all work just fine for me on PV10 on Canon raw files. I just tried it.

Can you slide the sliders or change the numbers?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

I can do neither. The three sliders and the numbers are disabled (greyed out).

Here is a screenshot:

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

Ah...the power of a screen shot.

I see the same thing (Windows 7 64). I have no explanation.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

I can confirm this. Same problem here with a catalogue converted from LR3. And: it does not depend on the camera maker. I see this problem with RAW files from Nikon D40 & D90, Canon 450D and Olympus E-PL1.

Seriously, I'm starting to wonder more and more, wth was Adobe thinking releasing Lightroom 4 so fast with such severe bugs. First, the issue with the point curve. Second, the terrible performance with converted catalogues from LR3 (as opossed to newly created catalogues). An then this.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

Addition: After some first superficial test and comparisons, it seems that when PV 2010 is selected, the noise reduction is indeed that of PV 2010, and that the detail/contrast values are correctly preserved (when converting the catalog from LR3, as well as when manually changing between PV 2010 and 2012). The "only" bug is that the sliders are inactive.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 08, 2012 Mar 08, 2012

Copy link to clipboard

Copied

I am able to reproduce this problem as well, and it is now filed in our bug database.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Mar 29, 2012 Mar 29, 2012

Copy link to clipboard

Copied

Apparently this has been "silently" fixed in 4.1 RC (not mentioned in "Fixed Issues").

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 29, 2012 Mar 29, 2012

Copy link to clipboard

Copied

LATEST
There are many fixes in 4.1, we only explicitly call out the most serious in the release notes. But yes, this is fixed. :-)

-Ben

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines