LR 4: Autoadvance happens before color labeling - labels wrong image

  • 2
  • Problem
  • Updated 8 years ago
LR 4: Autoadvance happens before color labeling - labels wrong image.
I opened a fairly large catalog (upgraded from LR3.) In Grid view, Autoadvance is ON, I arrow through images. When I press the label "Blue" button at the bottom, often the advance happens first and the *next* (not current) image gets labeled. Some of the images already had other color labels, in case that matters
Photo of Steve Weil

Steve Weil

  • 3 Posts
  • 1 Reply Like

Posted 8 years ago

  • 2
Photo of John R. Ellis

John R. Ellis, Champion

  • 4593 Posts
  • 1238 Reply Likes
Details on how to replicate the problem:

1. Make sure Photo > Auto Advance is checked.

2. Select a photo that already has a color label.

3. Press the button for a different color label.

This also happens in LR 3.
Photo of LRuserXY


  • 426 Posts
  • 41 Reply Likes
Is this perhaps related to ?

I can reproduce it here (Win 7 64Bit, LR3 64Bit and LR4 64Bit). By the way: I could reproduce this on a very small test catalog (7 photos) newly created in LR4. Note: The same happens with autoadvance OFF if you use shift+click on the color labels.

The same workaround as in the other problem seems to apply: Don't use the buttons, but the keyboard (keys 6, 7, 8, 9, unfortunately no keyboard shortcut for the last color). Shift+Key without autoadvance works correctly, too.

Like the other problem, this seems to exclusively affect the color labels only. The rating stars and pick/rejected do not seem to be affected.

Another strange effect is that if the bug "happens", the current photo (that was meant to get the color) is left with "no color" - the color it had before is gone. You can see this by auto-advancing through e.g. photos all labeled red, assigning them e.g. blue. If the bug happens, a photo without color is left behind.

==> Please fix this, Adobe (in LR 4.1 and 3.7). This and the other bug could mix up the labeling really badly without the user noticing it. I consider these two bugs to belong in the "data loss / data corruption" category, the same as the bug that lets LR3 tone curves disappear after conversion to LR4. IMHO they have to be fixed with the same high priority.