Skip to main content
bitm07
bitm07
Inspiring
March 4, 2014
Answered

What new features in Lightroom 6 ?

  • March 4, 2014
  • 104 replies
  • 377681 views

With Adobe Photoshop Lightoom 6 expected to be released later this year, what new featured would you like to see in the new version ?.

      This topic has been closed for replies.
      Correct answer Geoff the kiwi

      Isn't it about time this thread was closed, and a new one opened for LR7?

      Bob Frost


      Robert Frost wrote:

      Isn't it about time this thread was closed, and a new one opened for LR7?

      Bob Frost

      Bit hard to know what to ask for in Lightroom 7 when 6 is not out yet....

      But quite happy to lock this...

      104 replies

      Show previous replies
      A
      aafisher
      Inspiring
      September 23, 2014

      Please add custom fields. Aperture has had this feature since version 1, and it is very useful for tracking things like copyright registration info, usages, licensing history, releases, restrictions, infringements, etc. As a professional photographer who licenses my images, I need to track some important things, and it's ridiculous to have to use an external database to track such things, when Lightroom already has an internal database engine.

      It's also nice to have a set of fields which will not be included with the file when it's exported along with all it's IPTC data. Some information is not appropriate to be included with embedded metadata.

      areohbee
      areohbee
      Legend
      September 23, 2014

      Lightroom does not have this feature built-in, but it can be provided by a plugin, e.g.

      robcole.com - CustomMetadata

      I know you want it native - me too.. - but the plugin is an OK work-around for the mean time, in my opinion.

      ~R.

      A
      aafisher
      Inspiring
      September 23, 2014

      Thanks for your response.

      However, I doubt that the Aperture to Lightroom migration tool that Adobe is working on will support the migration of custom fields if they are not part of the native application. This is what I'm waiting for before I migrate my 250,000 image library. It is simply unacceptable for me to lose all my custom field data that I built in Aperture. The only migration solution that I've been able to find that will even recognize the custom fields, will map all the custom fields into a single IPTC field, which is also unacceptable to me.

      Augestflex
      Augestflex
      Participant
      September 23, 2014

      +1 Facial Recognition

      Also better integration / publishing to existing Social Sites/Services such as Google+ Photos, Flickr, etc.

      sadmyst
      sadmyst
      Participating Frequently
      September 21, 2014

      More than anything I'd like a more robust version control. Or at least just a way of adding notes to a "notepad" I get from hovering over an image so I can tell which version it is and I can keep notes of what I've done to the image. (And no... Not in the library module. In the develop module.)

      I still want them to consolidate the library and develop modules though. Or consolidate all of them.

      Maps could be off to the side somewhere. It's so little used.

      Aperture had a near perfect integrated interface (except for the overdone database stuff) Do something like that!

      B
      bob frost
      Inspiring
      September 21, 2014

      Not by me it isn't! It's a great feature, enabling me to find my image

      locations from their GPS data. When you are touring out in the wild, it is

      not always possible to know exactly where you are. It is also great for

      giving talks, to show where images were taken. For me you could get rid of

      the web module and all the social interaction plugins.

      Bob Frost

      Rikk Flohr: Inactive
      Rikk Flohr: Inactive
      Participating Frequently
      September 21, 2014

      I Didn't say "get rid of them"

      When I said "off to the side" I meant they don't need their own module.

      I could explain why 80% of Aperture had better UI and UX than. 90% of Lightroom but it would be a LOT of typing. What I want to see is consilidation and access to as many functions as possible without having to change "modules." And if you think that would mean the program would HAVE to be slow...

      <points at aperture once again>

      Yes Aperture might have been 10% slower overall but not having to seitch between modules constantly spee the overall workflow up by at least 30% so the point is moot.

      Also Aperture didn't force a workglow order on you for efficiency. You could import, edit and organize all at the same time or "backwards" if you prefer.


      I think this is your quote:

      "2) The web panel is a joke. Either give us some real web tools or stop pretending you care about web and just get rid of it altogether."

      S
      Studio Las vegas
      Participant
      September 17, 2014

      Lightroom should have an option that does not re-organize key words in alphabetical order.  Photographers submitting to agencies have to put the most relevant key words first.  When we use LR to keyword it automatically alphabetizes, rendering it useless for this task.  All we need is a box to check to "leave keywords in order as they appear". 

      johnrellis
      johnrellis
      Legend
      September 18, 2014
      Lightroom should have an option that does not re-organize key words in alphabetical order. 

      A number of people have requested this.  Please add your vote and opinion to this topic in the official feedback forum: Lightroom: Better keyword management.

      S
      ShuckyD
      Participant
      September 11, 2014

      I would totally love to see Smart Collections that span catalogs.... reason is I have over 100k images in one LARGE SLOW CATALOG and it's because since 2006 I built my workflow upon Collections for all of my various genres of photos.  I do like to process on smaller catalogs like when I do work on my laptop and merge the changes with my desktop, but my main catalog is getting way too big and I wont see performance gains until this happens.  Then I would separate out years and not need to worry or remember which year which photos were in, etc.  Yes from the technical side it may need an additional repository/database, but that should be rather easy to do. 

      john beardsworth
      Community Expert
      john beardsworthCommunity Expert
      Community Expert
      September 11, 2014

      100k should not slow you down or force you to fragment control of your workflow into bonsai catalogues. I routinely work on one that is over 5 times that size, and the only thing that's slower is backing up, which is done in non-working time. See http://kb2.adobe.com/cps/400/kb400808.html and above all, optimise your catalogue every so often.

      J
      javieros
      Participant
      September 7, 2014

      +1 Face Recognition

      Subscription only to Lightroom would be helpful

      artministry
      artministry
      Participant
      August 28, 2014

      I would like to see integration of more image types -- specifically, Illustrator and PDF -- that can be opened as bitmaps. I would also like to see additional metadata search/cataloging ability as in Phase One Media Pro. Finally, I'd like to see complete metadata editing capability in Lightroom mobile -- this last would make my life much easier.

      A
      Ants Koel
      Participant
      August 28, 2014

      1. Although it has been stressed by other users before me, keep the stand-alone licensing possibility. Keeping backups off-site makes sense but not relying on daily operations.

      2. Simple inbuilt EXIF editor would be handy. I have a lot of manual lenses and editing aperture/focal length/lens model data straight in LR (not in external editors like Exif Pilot or similar) would be nice.

      B
      bob frost
      Inspiring
      August 28, 2014

      Hi ants,

      It is very unlikely that Adobe will allow editing of exif data in LR; it has

      made a principle of not touching raw files such as nefs. Although it has

      broken its principle by allowing editing of Capture Date in raw file - if

      you specifically check this in Prefs. And it doesn't mind chewing up raw

      files and turning them into DNGs. When is a principle not a principle??

      So using a raw editor such as ExifTool, or ExifGUI, or PhotoMechanic seems

      the only way in the immediate future, unless someone at Adobe has a

      'Damascene conversion'!!

      You should also note that Nikon has now adopted the principle of storing

      edits in sidecar files instead of in the raw file. It's new editor Nikon

      Capture NXD uses sidecars from what I read. That is a big change from its

      previous Capture NX2.

      Bob Frost

      sadmyst
      sadmyst
      Participating Frequently
      August 14, 2014

      Overall my basic wants are:

      1) Condense the Library and Develop modules into one module and make the panels smaller. (They are too big for laptops as it is anyway)

      2) The web panel is a joke. Either give us some real web tools or stop pretending you care about web and just get rid of it altogether.

      3) The print module needs to be more intelligent. Currently it's like a steampunk style printing press with gears and knobs.

      John_jcb
      John_jcb
      Participating Frequently
      August 14, 2014

      Some things I would like to see in LR and LR Mobile

      1.  The ability to mask areas I do not want impacted by the graduated filter.

      2.  The ability to import into a collection so that new photos would appear in LR mobile with no user action required.

      3.  The ability to take notes in LR Mobile and have them available in LR.  Would eliminate need for a notepad when reviewing proofs with a client.

      Show more replies
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices