Lightroom: How to mark images locally? (If LR3 then flags, if LR4beta then???)

  • 2
  • Question
  • Updated 8 years ago
  • (Edited)
In LR3 flags are local but in LR4beta they are global. Within a collection if I want to mark a few images, can that no longer be done? For example, perhaps I want to pair down a large collection and want to mark possible items for deletion, but I do not want to delete anything from the collection until I have gone through the whole collection; under LR3 I just set flags, then filter based on flags, then make my final decisions; but in LR4beta I don't see any easy way of doing this.
Photo of Philip T

Philip T

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 8 years ago

  • 2
Photo of john beardsworth

john beardsworth

  • 1231 Posts
  • 319 Reply Likes
Try using stacking, which is now local.
Photo of Chris Ogden

Chris Ogden

  • 33 Posts
  • 4 Reply Likes
This is essentially a duplicate/alternate posting of

Sorry to be late to the party. BUT, this "new" global flag behavior is REALLY screwing us (and other colleagues and our workshop students) up.

We have many collections that contain Client Proofing selections via the Picked/rejected flags. They often contain overlapping images. One client might want to order Image123 (so click "Select"), but the next client may not (so click "Reject"). Similarly, their "maybe's" are left unflagged.

With LR4 we can no longer allow this proofing (without a huge hassle of maintaining separate, little catalogs for each client/job/interaction/output type). Seems like a big step backwards.

Additionally, all the selection criteria we have in LR3 up until this point is wiped out when "upgrading" to LR4. This seems like DATA LOSS, which we'd consider to be a bug.

(Similarly, we have collections that contain output jobs that use Local Status selections (and ordering) for what was/wasn't included. Examples include various Calendars, Books, and even Gallery Shows. )

Pretty, pretty please can you make local vs global flag behavior a simple Preference? (if local was confusing folks, then global could even be the default).

Please don't go the way Apple seems to be heading, in "dumbing down" your products, and create a Lowest Common Denominator situation.