Skip to main content
This topic is closed to new replies. Start a new post to keep the conversation going.

133 replies

areohbee
Legend
Jul 8, 2013 2:05 PM UTC
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.
Translate
MadManChan2000
Adobe Employee
Adobe Employee
Jul 8, 2013 1:23 PM UTC
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.
Translate
Inspiring
Jul 8, 2013 3:56 AM UTC
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.
Translate
areohbee
Legend
Jul 7, 2013 10:40 PM UTC
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).
Translate
areohbee
Legend
Jul 3, 2013 12:29 AM UTC
I recommend Lr50 Export AutoFix to minimize the potential for problems.
Translate
Jul 2, 2013 8:45 PM UTC
But I can only use the "LR / Mogrify 2" without problems, right?
Translate
ssprengel
Inspiring
Jul 2, 2013 8:04 PM UTC
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.
Translate
areohbee
Legend
Jul 2, 2013 7:15 PM UTC
I'm surprised this bug wasn't considered critical enough to fix sooner than next dot release, but thanks for clarifying the time frame.
Translate
areohbee
Legend
Jul 2, 2013 7:12 PM UTC
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.
Translate
Jul 2, 2013 7:05 PM UTC
Will it work if I just use plugin "LR / Mogrify 2" just to resize? Thus the bug does not occur?
Translate