LIGHTROOM: Merge Library and Develop modules

  • 2
  • Idea
  • Updated 7 years ago
  • (Edited)

This conversation has been merged. Please reference the main conversation: Lightroom: Integrate Library & Develop Modules

There is no good reason why they have to be separate other than "just because that was how it was designed in the beginning".

I must switch to library to
- go through individual pictures (because it is faster than doing it in Develop)
- browse pictures in a grid
- comparing 2 pictures
- bulk develop

I must switch to devlop to
- develop photo
- check adjustment history

Not to mention all the money Adobe is spending to maintain 2 different code bases with similar functions.
Photo of Jonno Wong

Jonno Wong

  • 3 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 2
Photo of Lee Jay

Lee Jay

  • 994 Posts
  • 137 Reply Likes
I've been asking for this since LR 1.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 391 Reply Likes
Gazoo eliminates the round-trip to Library module for relative adjustment (i.e. "bulk develop"), and some other things...
Photo of Babar_e


  • 138 Posts
  • 24 Reply Likes
Well that way the DAM part of lightroom would become a lot more complex

The library module is the DAM function of Lightroom and that is where i spent 70% of my time the remaining 30 is in the develop module
so getting ride of the library is a none-sense for me

but I agree the map and develop module would gain having at least the folders view, the collection view and the keyword filtering
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 391 Reply Likes
DAM part need not be *any* more complex. i.e. the goal is to be able to have Lr metadata panels more readily accessible whilst photo is undergoing development (and conversely, have develop panels more readily accessible whilst photo is undergoing library treatment), and avoid non-stop loading indicators when switching modules, etc...

IOW, if there was 0 delay and no loading indicators when switching modules (and Library histogram was same as develop, and..., then they would be "integrated" more or less, with almost *no* change to anything you are familiar with.

Summary: there are 9-zillion different ways to "integrate" library and develop modules, and in my opinion, Adobe should choose a way which has minimal impact to the UI that people presently know and love, since that would be easiest for them to do and easiest for users to adapt to, plus minimal changes to books&documentation/tutorials, web-info, ...

In my opinion, there is room for more optimization, once embarking on a truer integration, still - nothing to fear... - I'm pretty sure if they do it right, it will be a big improvement for everybody.