Skip to main content
This topic has been closed for replies.

133 replies

MadManChan2000
Adobe Employee
Adobe Employee
September 9, 2013
Hi Piotr,

What camera model are you using?
Participating Frequently
September 9, 2013
Still no noise reduction in jpeg export with resizing to 1200! v5.2 Need help here!
areohbee
Legend
July 8, 2013
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.
Participating Frequently
July 8, 2013
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.
MadManChan2000
Adobe Employee
Adobe Employee
July 8, 2013
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.
Participating Frequently
July 8, 2013
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.
areohbee
Legend
July 8, 2013
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...
areohbee
Legend
July 8, 2013
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...
areohbee
Legend
July 8, 2013
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...
July 8, 2013
So when I use mogrify export only with sRGB color space?