Lightroom 5 - Output Sharpening and Noise Reduction not working.

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

|> "We'll fix this."

Are we talking 5.1, or 5.0.1?

i.e. days or months...

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

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

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

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

You have set a deadline for this?

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

Yeah!

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

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.

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

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

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.

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.

okay!

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.

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

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.

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.

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.

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.

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.

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.

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.