Skip to main content
Adobe Photoshop Family

1 Message

 • 

210 Points

Mon, Jun 10, 2013 1:01 PM

Solved

Lightroom 5 - Output Sharpening and Noise Reduction not working.

Just installed Lightroom 5 final. Output Sharpening and Noise Reduction does not work. Whole story here:
http://forums.adobe.com/thread/1229132

Responses

946 Messages

 • 

13.8K Points

7 years ago

Noise reduction is working for me, but output sharpening at 1200 pixels (long edge) is not.

4.5K Messages

 • 

76.3K Points

Would you mind clarifying - is it the output sharpening that's not working, or is the Lr dev sharpening being dropped? - thanks.

I can not reproduce erroneous nr nor sharpening (output nor Lr dev) behavior, so this problem clearly does not affect everyone / every-photo equally... - either that or I screwed up my testing. But I checked using Beyond Compare's image comparison - not a single image bit of difference.

R

32 Messages

 • 

820 Points

7 years ago

The output sharpening seems to start working at 1791px long side. At 1790px long side, the exported files are identical, no matter which output sharpening I select.



Full 1:1 resolution here: http://www.hansvaneijsden.nl/test/lr5...

Employee

 • 

628 Messages

 • 

11.5K Points

7 years ago

Internally we've found the root cause of this issue. In a nutshell, images exported at less than 1/3 of their original size may not retain output sharpening / noise reduction settings. We'll fix this.

4.5K Messages

 • 

76.3K Points

|> "We'll fix this."

Are we talking 5.1, or 5.0.1?

i.e. days or months...

4.5K Messages

 • 

76.3K Points

Eric,

What exactly do you mean by "less than 1/3 their (original) size".

Are we talking "width x height", i.e. pixel count, or long dimension, or...

And is it "1/3 or less", or really "less than 1/3".

Thanks in advance,
Rob

946 Messages

 • 

13.8K Points

Long dimension. I don't know if it's before or after cropping.

4.5K Messages

 • 

76.3K Points

So, one dimension down, one to go.

It's original (uncropped) long dimension against ______ ?

That said, I've been having a hard time reproducing this issue - granted I've not done that much testing so far, is it expected to always happen (when resolution is low enough) or only sometimes?

Looks like nr is a "sometimes yes / sometimes no" kinda thing - is it the same for sharpening???

Rob

4.5K Messages

 • 

76.3K Points

After cropping, and since aspect ratio is preserved, either long dimension or short dimension can be used.

i.o.w.

long dim exported / long dim cropped < 1/3

or

short dim exported / short dim cropped < 1/3

R

1 Message

 • 

62 Points

7 years ago

Sur Lightroom 5, si vous exportez des photos en dessous de 1200 pixels en bord large, avec des fichiers de 5d mkIII pris à 3200 iso ou plus, la réduction de bruit de couleur est désactivée à la sortie !
On LR5 if you export a picture taken with a 5d mkIII at 3200 iso or more, resized with less than 1200 pixels on the long edge, the color noise reduction is deactivated on the final output...

This reply was created from a merged topic originally titled
LR5 noise reduction problem.

4.5K Messages

 • 

76.3K Points

hmm 1200 is *more* than 1/3 of 3200.

6 Messages

 • 

198 Points

7 years ago

you better release the fix quick, it is really disappointing!

16 Messages

 • 

222 Points

Yeah!

4.5K Messages

 • 

76.3K Points

7 years ago

I'm quite sure many people would like to know if the fix will be in the normal release cycle, or earlier. - is there any good reason to keep that a secret? do you really not know?

16 Messages

 • 

222 Points

I contacted support and they did not know the problem. Strange!

4.5K Messages

 • 

76.3K Points

The free tech support deals with issues of getting Lr up and running. - keeping current about various (operational) bug issues is not part of the service they provide.

216 Messages

 • 

4.8K Points

7 years ago

This bug is also very annoying exporting web galleries, Cause there you always have picture sizes below 1/3 of the original size and any workaround (like exporting the affected pistures separately in LR4) causes a huge amount of extra-work.

Employee

 • 

628 Messages

 • 

11.5K Points

7 years ago

Rob, at present it looks like it will probably be "weeks". That's not the answer I want to give, and I'm not sure if it helps you, but there it is. :-(

4.5K Messages

 • 

76.3K Points

Thanks Eric - it does help some of us, to plan... - good luck with it.

4.5K Messages

 • 

76.3K Points

7 years ago

So, I'm thinking of a solid work-around, but I need to confirm precise bug behavior, if possible.

Could somebody confirm under what conditions the bug occurs, and under what conditions, exactly, the bug does not occur?

Thanks,
Rob

4.5K Messages

 • 

76.3K Points

7 years ago

Here's two workarounds for the meantime:

In cases when this bug bites (e.g. low-enough rez).

1. Use Lr/Mogrify (export without resizing in Lr's Image Sizing section, then downsize using Mogrify Resizing Options).
2. Use PreviewExporter.

R

4.5K Messages

 • 

76.3K Points

7 years ago

This will fix it right up, no fuss / no muss...

Lr5.0 Export AutoFix

16 Messages

 • 

222 Points

Will it work if I just use plugin "LR / Mogrify 2" just to resize? Thus the bug does not occur?

16 Messages

 • 

222 Points

7 years ago

This reply was created from a merged topic originally titled
Sharpness and noise reduction are not applied at the output..


Adobe Photoshop Lightroom is 5 problems in jpeg export. Sharpness and noise reduction are not applied at the output. Now, what to do!? Thus'm serious productivity problems.

Champion

 • 

2.6K Messages

 • 

33.7K Points

7 years ago

This is a known issue that Adobe has promised to fix for the next release, with a time-frame of "weeks". The specifics are that sometimes LR doesn't apply NR or sharpening when the output image is less than 1/3 of the original size.

As far as what to do, another forum user has created a plug-in that uses another LR plug-in, Mogrify that you'll also need to get, to do the resizing and output sharpening after LR is used to do the NR and capture-sharpening at full-size.

See the reply in the merged thread just above for a link to the "LR5.0 Export AutoFix" plug-in: http://www.robcole.com/Rob/ProductsAn...

4.5K Messages

 • 

76.3K Points

To be clear: Lr50 Export AutoFix does not need/use/rely-on any other Lr plug-ins.

Lr50 Export AutoFix can use another non-LR 3rd party application - ImageMagick (which includes the mogrify command-line utility).

Also, Lr50 Export AutoFix can be used without mogrify (and without anything else - i.e. completely stand-alone/independent), with some caveats.

16 Messages

 • 

222 Points

7 years ago

No employee of the company will express it?

16 Messages

 • 

222 Points

7 years ago

No employee of Adobe will bring us a reply and a deadline for resolution? We try to productivity problems with this failure.

4.5K Messages

 • 

76.3K Points

Eric Chan works for Adobe (see reply above). The answer is "weeks", which means not months, but not just days either. In the mean time, consider a work-around.

16 Messages

 • 

222 Points

okay!

Employee

 • 

628 Messages

 • 

11.5K Points

It will be fixed for sure in the next dot release. Although I can't give you a precise date of that release, we generally do releases 4 times per year, which means a release every 13 weeks or so. As Lr 5 was released in early-mid June, this should give you an idea of when the next release will be.

4.5K Messages

 • 

76.3K Points

I'm surprised this bug wasn't considered critical enough to fix sooner than next dot release, but thanks for clarifying the time frame.

Champion

 • 

2.6K Messages

 • 

33.7K Points

Not corrupting user data is the one time Adobe did a hurry-up double-dot release a few years ago.

LR not performing as advertised is not enough reason for a hurry-up release, especially if there are several other bugs to fix at the beginning of a major version series.