Welcome Dialog

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.


Lightroom Mobile - syncing to Lr mobile does not respect custom default Develop settings

1 Vote
Mentor ,
Apr 08, 2014 Apr 08, 2014

Copy link to clipboard

Copied

When I import 7D images to desktop Lr 5.4 I default with white balance As Shot, Clarity +12, and Vibrance +10. All other exposure values are set to 0. Lr 5.4 considers the image to have no develop settings.

When this image is synced to Lr Mobile I notice that the temperature and tint values do not match (e.g. 5750, +32 in desktop Lr but 5800, +21 in Lr Mobile). No adjustments have been made in either app. Furthermore, clarity and vibrance are shown as 0 in Lr Mobile but 12 and 10 in desktop Lr. I would think all values should match in either app. Lr Mobile seems to treat default develop settings in an odd way.

If I try the following I get more weirdness:

1. Import photo to desktop Lr applying develop defaults.
2. Sync to Lr Mobile. Values as explained above do not show identical values.
3. Make a dramatic tint adjustment (+150) on desktop.
4. Synced photo in Lr Mobile shows the change and shows identical values in both apps.
5. Click Reset in develop module on the desktop so image has default values.
6. Synced photo shows up on the iPad as visually similar to the desktop but the tint value on Lr Mobile remains as +150.
Bug Fixed
TOPICS
Desktop

Views

4

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jun 18, 2014 Jun 18, 2014
This is fixed in Lightroom 5.5, which is now available. Thanks, Ben

Votes

Translate

Translate
2 Comments
Adobe Employee ,
Apr 08, 2014 Apr 08, 2014

Copy link to clipboard

Copied

Hi Wolfgang,

Eew, that's a nasty one. Thanks for the bug report, I am able to reproduce this problem as well. I've entered the issue in our bug database and sent it to the engineers.

Also, I've edited the title of your post to describe what I've identified as the central issue.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 18, 2014 Jun 18, 2014

Copy link to clipboard

Copied

LATEST
This is fixed in Lightroom 5.5, which is now available.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines