LightRoom6 Must have!

[ErikKaffehr]

Which one?

BR Erik

Interesting idea.

[jjj]

The one directly above it. If it had been any other post, I would have quoted it.

[nik]

Speaking for the .1% here;

- Fix tethering and make it fast. Hell, fix it in LR5 - it's so broken right now it's unusable due to it's instability (loses camera connection constantly regardless if it's on a laptop or a desktop). Also, how about being able to create multiple folders beforehand and then select the desired one as your "capture-to" folder? And be able to re-select the folder as a "capture-to / shoot-to" folder by right mouse clicking it? Instead of having to type it's name in again (current implementation) ? C1 borrowed ideas from you, why not borrow from them?

- The ability to color folders would be nice.

- Lastly, a biggie, multi-user Catalogs.

[JRSmit]

Speaking for the .1% here;

- Fix tethering and make it fast. Hell, fix it in LR5 - it's so broken right now it's unusable due to it's instability (loses camera connection constantly regardless if it's on a laptop or a desktop). Also, how about being able to create multiple folders beforehand and then select the desired one as your "capture-to" folder? And be able to re-select the folder as a "capture-to / shoot-to" folder by right mouse clicking it? Instead of having to type it's name in again (current implementation) ? C1 borrowed ideas from you, why not borrow from them?

- The ability to color folders would be nice.

- Lastly, a biggie, multi-user Catalogs.

+1 on the tethered shooting plus Multi-folder
+1 on the Multi-user catalogs, including the option for secure access across the internet.

[hjulenissen]

I might have 5 different virtual copies of the same file, edited for different purposes. It would be nice to (more easily) be able to distinguish them at a glance (while rendered as a small tile). If one was last printed on glossy photopaper, while the other was exported as sRGB JPEG, cannot this infomation be presented in a way that lets me choose the file that I am most probably searching for instead of having to inspect them more closely?

-h

[Eric Myrvaagnes]

I might have 5 different virtual copies of the same file, edited for different purposes. It would be nice to (more easily) be able to distinguish them at a glance (while rendered as a small tile). If one was last printed on glossy photopaper, while the other was exported as sRGB JPEG, cannot this infomation be presented in a way that lets me choose the file that I am most probably searching for instead of having to inspect them more closely?

-h

+1 on this.

[David Jilek]

I agree! I'm so tired of wasting time switching back and forth all the time!
I would also love to be able to  have preset carry over  from a previous image while shooting tethered.

[tomrock]

If you want a preset to automatically apply when shooting tethered, change the default for that camera to your preset for the duration of the shoot. Change it back when you're done.

[sertsa]

Add grain to the adjustment brush, or add a slider sort of like the mask in sharpening that varies the grain by value.  Film grain is not uniform but varies, as is it often looks fake.

Extrapolating this out to pie-in-the sky (Ideally combined with an earlier suggestion to let all the adjustment tools work together - gradient, brush, radial filter) - when selecting the mask tools allow all the adjustments to be used with the masking tools.  The small panel that pops up would be eliminated and the look of the entire right panel would change (different color?) to indicate global adjustments vs being in a masked mode.

In the slideshow module bring back the toggle to require/not require a preview before the slideshow will run.  It is frustrating to watch Lightroom crank away before it will start the slideshow, never had a problem with them being built on the fly before, and if there was a slight stutter between images occasionally it is better then the long wait before.  I should be able to decide which is preferable.

[Scott Hargis]

I'd like to see a voice memo feature added. While in the field, I sometimes shoot an image that's going to have a very small, very specific role in the post-processing, and it'd be nice if I could click a button, dictate a quick memo to myself about what that image is for, and then have a little badge show up on the thumbnail so that days (or weeks) later I'll know that there's a memo associated with that image.

[Rory]

I'd like to see a voice memo feature added. While in the field, I sometimes shoot an image that's going to have a very small, very specific role in the post-processing, and it'd be nice if I could click a button, dictate a quick memo to myself about what that image is for, and then have a little badge show up on the thumbnail so that days (or weeks) later I'll know that there's a memo associated with that image.

You sure you cannot do this now?

[john beardsworth]

It can play voice notes recorded by the camera, that's all.

[JRSmit]

I might have 5 different virtual copies of the same file, edited for different purposes. It would be nice to (more easily) be able to distinguish them at a glance (while rendered as a small tile). If one was last printed on glossy photopaper, while the other was exported as sRGB JPEG, cannot this infomation be presented in a way that lets me choose the file that I am most probably searching for instead of having to inspect them more closely?

-h

You could use the copy name field to fill with its purpose, e.g.: SRGB JPG, Print. Also use the softproof create softproof copy, it adds the printerprofile used in the copy name. Typically you would use a vc in an outrput driven way, to achieve some form, size, color of b/w variant or what ever output objective you have.

[Remo Nonaz]

I'd like to see the ability to turn on  / turn off (preview) individual adjustment pins. Unless I've misses something, currently preview turns them all on or off.

[Dr Tone]

Performance improvements have to be number one for me.  Higher MP photos with a few localized adjustments can really bring LR to it's knees.  I think GPU acceleration would be a great start.

[Dan Glynhampton]

I think GPU acceleration would be a great start.

I'm not so sure GPU acceleration would do for Lightroom what you hope, as with most things in life it's not that simple.  Data has to be presented to a GPU in a very specific way, and the overheads of that processing can outweigh any benefits. Jeff Schewe explains it well (and more directly!) in this message.

[mlewis]

What I would really like is the ability to use the straighten ruler in the crop section when zoomed into an image.  Often I find it difficult to correctly draw the line when zoomed out.

[hjulenissen]

I'm not so sure GPU acceleration would do for Lightroom what you hope, as with most things in life it's not that simple.  Data has to be presented to a GPU in a very specific way, and the overheads of that processing can outweigh any benefits. Jeff Schewe explains it well (and more directly!) in this message.

Image processing should generally be well suited for GPU. Especially batch-processing many images. But doing algorithm X (well, i.e. accurately, stable and fast) on a hand-ful of GPU architectures, debugging, etc is more complicated than doing the same algorithm on x86. So how is this complexity going to be "paid"? By Adobe nicely hiring more staff? By Adobe redirecting algorithm development resources into GPU acceleration tasks? By Lightroom 6 having more bugs? By customers paying more for the product?

I am guessing that it should be relatively "easy" for e.g. Nvidia to port significant parts of the Lightroom pipeline to a recent generation Nvidia/CUDA GPU and making it produce equivalent output 2x or 10x faster than a recent Intel CPU for a demo. Making this into a robust software product that can be sold to customers of various hw configurations (and competence), making the software maintainable for adding features and fixing bugs, making money off of the thing, that is harder (I guess).

-h

[Phil Indeblanc]

I'm not so sure GPU acceleration would do for Lightroom what you hope, as with most things in life it's not that simple.  Data has to be presented to a GPU in a very specific way, and the overheads of that processing can outweigh any benefits. Jeff Schewe explains it well (and more directly!) in this message.

The bottle neck for most people that have just about all things updates ends up being the server or harddrive the file reads/writes to. It maybe worth it for some, as I consider it to have a "staging" drive. A large SSD drive to have all the projects/files your working on and then copy over to the server/main storage.  One thing that would concern me is the possibility of the SSD being bricked/wiped, as it isn't written on to the drive. So perhaps you have to save to the server move files to the staging drive, then move them back?  Not sure. I obviously havnt figured a way for this, but I think I would gain at least a couple hours if I could make things read/write faster. 

I for one get up and do something else while a 1-2gB PSD in max compatible mode starts writing.  I try and do this after major changes. So it breaks up the workflow a bit.

[Phil Indeblanc]

I have a NEW Must have....(along proper dual screen)

How many times do you have to edit something in PShop and then go back and forth with Synchronizing the folder to finally have it appear?

LightRoom needs a "HOT FOLDER". A folder that you can designate when ever you work on a project. The designated folder will be monitored and will automatically create previews for the folder gaining new files from outside folders. This would make LR more of a active DAM that you can cotrol, rather than a DUM DAM, ughmm.