aurius_paskevicius

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

gisela_m_cerutti

16 Messages

•

222 Points

8 years ago

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

rob_cole_2221866

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.

8 years ago

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.

8 years ago

rob_cole_2221866

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.

8 years ago

steve_sprengel

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.

8 years ago

greg_priestley

8 Messages

•

146 Points

Am I reading this right - they've gone from "weeks", to now part of the regular cycle which will be 3 months? That's ridiculous. We're all supposed to implement work arounds because Adobe is too lazy to fix a critical bug? Lightroom is supposed to save us time - not create more.

8 years ago

madmanchan

Employee

•

629 Messages

•

11.5K Points

The delta between public builds is typically "weeks" because in addition to the final dot releases (roughly once every 13 weeks) there are the public Release Candidate (RC) builds which fall in between those.

8 years ago

greg_priestley

8 Messages

•

146 Points

The only public builds I've ever seen Adobe publically release before are the release candidates and final releases. The RC's are generally 3-5 weeks before the final releases. Given we are 4 weeks in with LR5, the RC at earliest would be at least another 4 weeks away based on the historical timelines. Hardly "weeks" - I call that "months", especially from when the "weeks" comment was first made. Very very very disappointed in Adobe for leaving us high and dry.

8 years ago

madmanchan

Employee

•

629 Messages

•

11.5K Points

Your point is well taken, Greg. I am trying to move things along as quickly as I can, but please understand this is not my decision alone and I can't promise anything in terms of timeframe.

8 years ago

greg_priestley

8 Messages

•

146 Points

Eric, I appreciate that, but it seems like all the feedback is falling on deaf ears at Adobe. How do customers get to talk to the people who make the decisions?

The lack of a clear statement as to when is the most frustrating part. Everyone speculating doesn't help. But I've got 10's of thousands of images that were affected (astroimaging timelapses). It is a major time waste for me to try and work around for something the product should do (and used to do!). If a clear statement from Adobe was "It will be fixed in 2 weeks" then I would wait. If a clear statement from Adobe was "Next release on usual timeframe" then I either need to work on other projects for the next few months, or save out all my metadata for images and re-import 10's of thousands of them back into LR4, and then re-export them all out again with a working version. But in the mean time we all sit in limbo land parsing forums looking for a light at the end of pain and suffering that has been inflicted upon us.

8 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

Is there a way to bootstrap export filters (post-process actions) into web module, or exports initiated programmatically via plugin, i.e. using LrExportSession object. If so, then it would be possible to better work-around for the mean while.

8 years ago

gisela_m_cerutti

16 Messages

•

222 Points

8 years ago

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

rob_cole_2221866

4.5K Messages

•

76.3K Points

Yes - just resizing using Lr/Mogrify (and NOT Lr) will fix the problem with noise reduction and dev-module sharpening, but not output sharpening - granted, you can enter a little sharpening for output too. Such has been rolled into a turn-key plugin: Lr50 Export AutoFix which has the advantage of auto-detect / pass-through in case fix is not needed, and auto-fix in case fix is needed.

8 years ago

gisela_m_cerutti

16 Messages

•

222 Points

But I can only use the "LR / Mogrify 2" without problems, right?

8 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

I recommend Lr50 Export AutoFix to minimize the potential for problems.

8 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

8 years ago

BEWARE: There is a bug in the latest version of ImageMagick's mogrify (6.8.6) - images are coming out untagged, so export as sRGB unless you have an older version (6.7.3 is ok).

gisela_m_cerutti

16 Messages

•

222 Points

So when I use mogrify export only with sRGB color space?

8 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

Recommended solution: use an older version of ImageMagick (which includes mogrify utility) if possible. e.g. 6.7.3.

Links:
* Source code: http://www.imagemagick.org/download/w...
(not sure where the mac equivalents are).
* Binary installers: http://mhonarc.veidrodis.com/image_ma...

If not possible, then yes: export with sRGB color space - this is not a perfect solution (because untagged images may not be handled exactly the same as true (and properly tagged) sRGB images), thus the recomendation above, but it's better than nothing (e.g. better than AdobeRGB, at least until this bug is fixed).

NOTE: Authors of ImageMagick are aware of this problem and may have fixed the problem in latest beta release (source code only) - fixed binary release should be available soon.

Note2: another option is to manually assign an icc profile after exporting. Note: do not convert profile, just assign the correct one (as exported) - e.g. Photoshop or NX2 can do this.

Another option is to use Lr50 Export AutoFix in non-mogrify mode (i.e. without mogrify), at least for now...

8 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

8 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

8 years ago

piotr_rojewski

5 Messages

•

102 Points

7 years ago

Still no noise reduction in jpeg export with resizing to 1200! v5.2 Need help here!

rob_cole_2221866

4.5K Messages

•

76.3K Points

Are you sure you're using Lr5.2RC, and not Lr5.0? (v5.2 has not been released yet).

7 years ago

piotr_rojewski

5 Messages

•

102 Points

Yep, Youre right it is 5.0 ver. :)

7 years ago

madmanchan

Employee

•

629 Messages

•

11.5K Points

7 years ago

Hi Piotr,

What camera model are you using?

piotr_rojewski

5 Messages

•

102 Points

7 years ago

Hi Eric,
I'm using 5D mark III

madmanchan

Employee

•

629 Messages

•

11.5K Points

7 years ago

Hi Piotr,

Can you please provide me with an example 5D3 image where the NR isn't correctly being applied on export? You can send it to madmanchan2000@yahoo.com (dropbox, yousendit.com, etc.). I would like to run this file through one of our internal tools to check what may be going wrong here.

Thanks,
Eric

piotr_rojewski

5 Messages

•

102 Points

7 years ago

Sure ,sent.

piotr_rojewski

5 Messages

•

102 Points

7 years ago

Yep, Youre right it is 5.0 ver. :)

rob_cole_2221866

4.5K Messages

•

76.3K Points

Oops ;-}

7 years ago

madmanchan

Employee

•

629 Messages

•

11.5K Points

Ah, that would explain it. 5.0 had the bug. It's fixed in the Release Candidate of Lr 5.2 (and of course the final version of Lr 5.2 will also have the fix). That'll be out very soon.

7 years ago

gisela_m_cerutti

16 Messages

•

222 Points

When the patch is released? The upgrade from Adobe LR will automatically by Adobe Creative Cloud?

7 years ago

mdshirajum

6 Messages

•

100 Points

7 years ago

This issue is still present in release 5.2!!!! See the pictures edited using 5.2.

Couldn't you fix this small thing in last 3 months!!!

madmanchan

Employee

•

629 Messages

•

11.5K Points

7 years ago

Are you referring to the sharpening or the noise reduction, or both? It's not clear to me what you're demonstrating with the above two example images. Can you please clarify?

mdshirajum

6 Messages

•

100 Points

the first pic is the exported jpg and 2nd one is the screenshot in 'develop' mode. see the exported image is MUCH softer than the 2nd one! very frustrating! and I am using 5.2 by the way!

7 years ago

madmanchan

Employee

•

629 Messages

•

11.5K Points

Questions:

1. At what size are you trying to export the image?
2. Are you applying output sharpening when doing the export?

7 years ago

mdshirajum

6 Messages

•

100 Points

exporting 1:1 and not using output sharpening. By the way, 'At what size are you trying to export the image' question seems kinda funny! I paid for the software and it should be able to do the SIMPLE task of 'sharpening' at EVERY SIZE!!!!!!

7 years ago

hans_van_eijsden

32 Messages

•

820 Points

No problems here, fortunately.
But why don't you stay nice? We're all humans, doing our best, making mistakes. Not machines.

7 years ago

steve_sprengel

Champion

•

2.6K Messages

•

33.7K Points

I have a question about the sample images, just above: they appear rather small, in the 400x600 range. Are the attached images cropped screen-shots of photos viewed at 100% zoom or are they reduced down to a small size before the screen-captures were taken? If they underlying image was not at 100% then the Develop module sharpening is an estimate and can be off.

As far as the LR 5.0 bug not being fixed, it was only a problem if the images were resized down to 1/3 of their original size or smaller, and it was also a problem with output-sharpening not being applied since these appear to be exported at 100% and with no output sharpening, then what you're seeing isn't the 5.0 bug.

7 years ago

mdshirajum

6 Messages

•

100 Points

sorry if i was rude! Mistakes are acceptable, but I am a bit frustrated to see that they are taking SOOOOOOO long to fix this simple problem!

7 years ago

gisela_m_cerutti

16 Messages

•

222 Points

I think the same.

7 years ago

mdshirajum

6 Messages

•

100 Points

and to add on that, pls don't bring "We're all humans, doing our best" in this forum. This is a forum related to a business product. We pay for the product, we DESERVE the service. Are they going to refund us cause it's not performing as it should? If not, then pls KEEP your emotion with you!

7 years ago

son_nguyen_2405250

62 Messages

•

1K Points

Nobody has this problem with 5.2 and you're the only one. Before screaming your lung out, shouldn't you check to see if you do something wrong? And more over the original bug was applied to image that is exported 1/3rd smaller.

7 years ago

rob_cole_2221866

4.5K Messages

•

76.3K Points

I agree with Hans: for everybody's sake - be civil, even though it's a product you paid money for...

That said, to 9X% of users, the bug (which is the subject of this thread) is fixed in Lr5.2. Worth noting:
* You must be using the final release - it's not fixed in the release candidate.
* Exported photos may be softer than in Lightroom unless you apply some output sharpening.

7 years ago

mdshirajum

6 Messages

•

100 Points

7 years ago

the first pic is the exported jpg and 2nd one is the screenshot in 'develop' mode. see the exported image is MUCH softer than the 2nd one!

gisela_m_cerutti

16 Messages

•

222 Points

7 years ago

Regrettably correction has not yet been released. When the customers of Adobe Creative Cloud will have an update for Adobe Lightroom?

steve_sprengel

Champion

•

2.6K Messages

•

33.7K Points

Are you saying you don't have the LR 5.2 update, yet, or that the output-sharpening bug in LR 5 hasn't been fixed in LR 5.2?

The recent post, here, is about something else, because the pictures were being exported at 1:1 and the LR 5.0 bug was for images exported at 1/3 the size with output sharpening enabled.

What problem are you talking about? There could be something new.

7 years ago

gisela_m_cerutti

16 Messages

•

222 Points

Exporting images with a size smaller than 1/3 of the picture. This has been fixed?

7 years ago

madmanchan

Employee

•

629 Messages

•

11.5K Points

Yes, this problem is fixed in 5.2. To get the update, just run Lr 5 and you should be notified about a 5.2 update being available.

As to the issue mdshirajum listed, this appears to be __unrelated__ to the bug being discussed in this thread. In fact, I am pretty sure based on the description given so far that this isn't a bug at all.

7 years ago

marcin_hakemer_fernandez_6233389

8 Messages

•

132 Points

7 years ago

Hi guys I'm using Lr 5.3 and still having these problems when editing a raw file from a lumix fz150... (noise reduction doesn't show up on any exports I make)

steve_sprengel

Champion

•

2.6K Messages

•

33.7K Points

Can you provide an example image with the problem, uploading to somewhere like www.dropbox.com, then post the public download link, here?

7 years ago

marcin_hakemer_fernandez_6233389

8 Messages

•

132 Points

Hi Steve, thank you for trying to help, here is the link: https://shared.com/f/buwxne29x4

There are three files there.
1. screenshot of the difference of the exported file and what I did in Lr
2. the original RAW file
3. the exported file (jpg)

7 years ago

marcin_hakemer_fernandez_6233389

8 Messages

•

132 Points

I also just noticed, that my library view also doesn't have the noise reduction applied... I wonder if I'm doing something wrong.

7 years ago

aurius_paskevicius

Lightroom 5 - Output Sharpening and Noise Reduction not working.

Responses

gisela_m_cerutti

rob_cole_2221866

gisela_m_cerutti

madmanchan

rob_cole_2221866

steve_sprengel

greg_priestley

madmanchan

greg_priestley

madmanchan

greg_priestley

rob_cole_2221866

gisela_m_cerutti

rob_cole_2221866

gisela_m_cerutti

rob_cole_2221866

rob_cole_2221866

gisela_m_cerutti

rob_cole_2221866

rob_cole_2221866

rob_cole_2221866

piotr_rojewski

rob_cole_2221866

piotr_rojewski

madmanchan

piotr_rojewski

madmanchan

piotr_rojewski

piotr_rojewski

rob_cole_2221866

madmanchan

gisela_m_cerutti

mdshirajum

madmanchan

mdshirajum

madmanchan

mdshirajum

hans_van_eijsden

steve_sprengel

mdshirajum

gisela_m_cerutti

mdshirajum

son_nguyen_2405250

rob_cole_2221866

mdshirajum

gisela_m_cerutti

steve_sprengel

gisela_m_cerutti

madmanchan

marcin_hakemer_fernandez_6233389

steve_sprengel

marcin_hakemer_fernandez_6233389

marcin_hakemer_fernandez_6233389

Helpful Widget

Tags