Ad
Ad
Ad
Pages: « 1 ... 3 4 [5] 6 7 ... 19 »   Bottom of Page
Print
Author Topic: What are you wishing for in LR5 ?  (Read 69978 times)
Rhossydd
Sr. Member
****
Online Online

Posts: 1989


WWW
« Reply #80 on: December 29, 2012, 04:54:31 AM »
ReplyReply

none of them made the screen larger than using TAB.  Roll Eyes
That depends on the screen state you start from.
E- forces a single image to the screen in loupe mode as large as possible > shift tab- removes all panels, both at the sides and top and bottom > FF makes the application full screen with no window controls or menus.

Yes, Fred's right, one keystroke to do all of this would be nice, but it won't seem so important to people working with big screens.
Logged
stamper
Sr. Member
****
Offline Offline

Posts: 2874


« Reply #81 on: December 29, 2012, 05:12:41 AM »
ReplyReply



Yes, Fred's right, one keystroke to do all of this would be nice, but it won't seem so important to people working with big screens.
[/quote]

but you would have to pick the viewing mode first which would mean more than one keystroke? In develop mode I don't see a better solution than TAB? Wink
Logged

john beardsworth
Sr. Member
****
Offline Offline

Posts: 2888



WWW
« Reply #82 on: December 29, 2012, 05:13:03 AM »
ReplyReply

"Care to elaborate further?" It's irony. Was it not patently obvious 4 keystrokes wasn't what Fred suggested? Wow, the world was crying out for that fact to be pointed out. Hence the line from Pulp Fiction.

Just try your tab suggestion when you are in grid, loupe or compare view. On its own, tab is insufficient as it will only hide the side panels - the top and bottom might remain visible, the menu and application window too. So depending on how many of these are shown when you want a single image as big as possible, you could currently need as many as 4 keystrokes to get to a full screen.
Logged

Rhossydd
Sr. Member
****
Online Online

Posts: 1989


WWW
« Reply #83 on: December 29, 2012, 05:34:04 AM »
ReplyReply

but you would have to pick the viewing mode first which would mean more than one keystroke? In develop mode I don't see a better solution than TAB? Wink
No, I think Fred's idea is one single keystroke to bring an image absolutely full screen with no interface clutter at all. Hopefully flip flopping back to where you where with a second press.
It really could be a more comprehensive solution than tab which still can leave a lot of screen clutter.
Logged
john beardsworth
Sr. Member
****
Offline Offline

Posts: 2888



WWW
« Reply #84 on: December 29, 2012, 05:41:45 AM »
ReplyReply

A single keystroke would be helpful, though I'd be happy enough to lose the impromptu slideshow and re-use its Ctrl Enter / Cmd Enter.
Logged

Anthony.Ralph
Newbie
*
Offline Offline

Posts: 43



« Reply #85 on: December 29, 2012, 06:30:04 PM »
ReplyReply

How much bigger can the screen get using your suggestions rather than TAB. I tried your suggestions - Rhossyd was correct about the four keystrokes - and none of them made the screen larger than using TAB.  Roll Eyes

Well, shift|TAB minimises all four panels and *does* make the image fill the screen (more or less, subject to the crop shape of course), with the FF expanding the images to full screen mode. Certainly bigger than just TAB.

The E John mentions just puts the image into loupe view and would apply even with just TAB. If we want to work our fingers to the bone we could go LL as well, to activate 'lights out' mode as well :-)
Anthony.
Logged
Phil Indeblanc
Sr. Member
****
Offline Offline

Posts: 1111


« Reply #86 on: December 29, 2012, 07:18:12 PM »
ReplyReply

Have you tried LL?
Works good enough for my needs. Fit or Fill, and its zero clutter.

I don't find use for my needs to fill the screen edge to edge.
Logged

If you buy a camera, you're a photographer...
alan_b
Jr. Member
**
Offline Offline

Posts: 82


WWW
« Reply #87 on: December 29, 2012, 11:33:03 PM »
ReplyReply

I've seen this mentioned before, and it trips me up often:

A Quit confirmation/cancel would be helpful.  On a Mac, it's easy to hit Cmd-Q when aiming for Cmd-Tab to switch applications.
Logged
hjulenissen
Sr. Member
****
Offline Offline

Posts: 1704


« Reply #88 on: December 30, 2012, 02:22:42 AM »
ReplyReply

The big selling-point of Lightroom for me is that is minimize the tedious, monotone actions needed by me to develop large series of raw files into good-looking, well-organized digital libraries. My suggestions are primarily in order to improve on this main benefit.

/* consumer-style features */
+ Facial/Motif recognition would be great. I'll happily tag my first 100 pictures, but if those faces are recognized in other pictures, why not suggest the same tag?
+ Instead of presenting an import as a chronological list of 100s of images, I'd like some smartness in presenting the "likely" good shots first. Focus/camera-shake, over/under-exposure, open/closed eyes etc.
+ Some modules seem overly constrained. Why do I resort to MS Paint occasionally for simple things like putting two images side-by-side in an image, instead of wading through endless options in the LR book module with seemingly pointless e.g. margins enforced upon me?
+ an iOS/Android lightroom-"light" app. Should give access to catalogs shared on a NAS, the ability to search and view images in a UI familiar to LR users. Additional points for being able to rate and tag images on the device, but no need for the full develop module, and images could be pre-rendered by the PC/Mac to jpegs if necessary.
+ Ability to keep source folder (sub) structure when exporting.

/* enthusiast features */
+ 2nd monitor should zoom in on an area defined by the active AF points. I see myself manually doing this all of the time to check focus of e.g. eyes in portraits
+ The ability to combine images into one edited logical image (HDR, side-by-side, layers, etc)
+ add "skin tone" to the wb picker
+ The possibility for true raw histogram and exposure correction (switch early stages of processing pipeline to camera native "colorspace"?)

More snappiness, exploit GPUs if that makes sense. Enthusiasts may have 8+ cores, 256-bit SIMD, large and fast flash drives. How well does LR exploit this? How well will it in the future?

-h
« Last Edit: December 30, 2012, 02:41:20 AM by hjulenissen » Logged
Stephane Desnault
Jr. Member
**
Offline Offline

Posts: 69


« Reply #89 on: December 30, 2012, 04:06:46 AM »
ReplyReply

@hjulenissen

+1 on all your suggestions - Image recognition software today is definitely smart enough to find common defects like camera shakes and red eyes - taking advantage of that should be part of the library features to pinpoint shots with or without likely issues, and we should be able to correct them semi-automatically in the develop module (without being forced to do it obviously).
Logged
Rhossydd
Sr. Member
****
Online Online

Posts: 1989


WWW
« Reply #90 on: December 30, 2012, 04:16:25 AM »
ReplyReply

Enthusiasts may have 8+ cores, 256-bit SIMD, large and fast flash drives. How well does LR exploit this?
It's not a question of if it exploits this sort of power, it absolutely needs it. LR will use every morsel of performance in your hard drives when searching and scrolling in the library, similarly CPUs hit 100% utilisation regularly in the develop module and if all other parts of the system keep up will keep all cores at 100% when exporting big batches of files.
But yes the GPU sits doing SFA, whilst the rest of the system is trashing away.
Logged
Rhossydd
Sr. Member
****
Online Online

Posts: 1989


WWW
« Reply #91 on: December 30, 2012, 04:19:30 AM »
ReplyReply

To get back to the original post;
Most of this was discussed when LR4 was first released and ultimately discussions like this here are pretty futile. Although they do have a habit of revealing that many people want features that are already available, but they haven't discovered them yet.

If you want something added, tell Adobe directly. Unfortunately the system for doing this isn't as convenient as it could be, each individual suggestion has to be made separately which is tiresome and awkward if some requests are dependant on others.

With respect to the OP's five requests;
I don't want "automatic" anything. In my experience auto features just get things wrong or not quite right, so I don't want resources wasted on things I'll just switch off.

Below are the suggestions I've sent to Adobe since LR4 was released;

General
A global history option; A list of what files have recently been written to in or used and in which module.
Use the GPU power of high end graphic cards.

Library module
This module is almost perfect but there are two areas where significant improvements can be made;
Keywording:-
1. Significantly increasing the number of the keyword suggestion options (buttons). This would ideally be user configurable to account for different screen sizes.
2. Increasing the number of keywords allowable in a set and increasing the number of buttons to accommodate this.
3. Having the option of a third keywording panel. This would allow suggestions/recent/sets to all be easily accessible.
4. The ability to select and add a complete set of keywords with one click.

Develop module

The ability to split the colour temperature control to give different values in different tonal ranges (shadows/midtones/highlights)

Local adjustments:-
Adjustment Brush;
Move “show selected mask overlay” option to mask control drop down box. (like ACR)
Add buttons to change overlay colour (maybe two pre-configured options). (like ACR)
Add HSL range of options.
Gradient Mask;
Add overlay provision as above.
Add HSL options.
It would also be nice to partially erase areas of the mask using the adjustment brush.

History
Add an indication of where in the history a “before” state is being shown from. (Emboldening the text of the state or an added asterisk would help this)
The ability to delete one edit from the history without removing everything since and/or the option to edit that history state. Surely not an issue with parametric edits ?


Book module

This absolutely needs the ability to work without templates, using custom layouts and custom sizes.
The ability to place text boxes freely anywhere on the page with any orientation.
The ability to save new custom layouts as templates.
A page numbering option.
Improved text handling.
A History panel.
The ability view other collections whilst working on a book and to drag images from any collection straight onto the page and have them added to the book's own collection.

Print module

The ability to place text boxes freely anywhere on the page (as above)


Plus fixing the bugs
Logged
hjulenissen
Sr. Member
****
Offline Offline

Posts: 1704


« Reply #92 on: December 30, 2012, 09:06:16 AM »
ReplyReply

It's not a question of if it exploits this sort of power, it absolutely needs it.
If LR is threaded by at most 2 or 4 or 6, then it IS a question if it exploits it. If LR cannot currently use more than 6 threads, it does not _need_ 8 cores (but one might argue, like you, that the software should have been written in such a way that it could use 8 cores more effectively. We dont know the low-level structure of the compute-bound algorithms in LR, though. Some problems are notoriously difficult/impossible to thread.)
Quote
LR will use every morsel of performance in your hard drives when searching and scrolling in the library, similarly CPUs hit 100% utilisation regularly in the develop module and if all other parts of the system keep up will keep all cores at 100% when exporting big batches of files.
But yes the GPU sits doing SFA, whilst the rest of the system is trashing away.
The question is if porting parts of the image processing to the GPU is worth it in terms of:
-Additional bugs (larger test-matrix, lower-level programming language, buggy GPU drivers)
-Slower development
-Algorithmic constraints due to limited GPU features

I do not claim to know what Adobe should do, but I think it is a relevant question.

-h
Logged
Rhossydd
Sr. Member
****
Online Online

Posts: 1989


WWW
« Reply #93 on: December 30, 2012, 10:25:31 AM »
ReplyReply

If LR is threaded by at most 2 or 4 or 6,
I see all 8 cores at full utilisation when importing/exporting and momentarily when doing CPU intensive tasks in develop.

Adobe have a decent track record of using GPU power in PS & PP so maybe different teams need to help each other.
Logged
Bryan Conner
Sr. Member
****
Offline Offline

Posts: 521


WWW
« Reply #94 on: December 30, 2012, 11:03:32 PM »
ReplyReply



5.  Ability to add custom keyboard shortcuts to presets (including cropping presets).



+1
Logged

ihv
Jr. Member
**
Offline Offline

Posts: 83


WWW
« Reply #95 on: January 03, 2013, 05:59:24 AM »
ReplyReply

Number 1 for me: healing brush (better yet content aware) in development module.

I believe this has also been requested by many in Adobe forums.




Logged
Tony Jay
Sr. Member
****
Offline Offline

Posts: 2157


« Reply #96 on: January 03, 2013, 06:10:13 AM »
ReplyReply

Possibly already requested:
An easy way to import and export collection sets as sets.

Currently the only way that I know to do this is as a catalog export/import step.

Tony Jay
« Last Edit: January 03, 2013, 06:34:46 AM by Tony Jay » Logged
Sharon Van Lieu
Sr. Member
****
Offline Offline

Posts: 382


Nantucket Landscape and Architectural Photographer


WWW
« Reply #97 on: January 03, 2013, 08:32:25 AM »
ReplyReply

I'm putting this in, hoping it is already in and I just don't know how. I would like the adjustment brush to work like dodge/burn in photoshop where you can choose to work on just highlights/midtones/shadows.

Sharon
Logged

Scott Hargis
Full Member
***
Offline Offline

Posts: 194



WWW
« Reply #98 on: January 03, 2013, 11:58:35 AM »
ReplyReply

How about the ability to generate a text file containing selected metadata for a group of images? I normally list out the file names of the images that I'm delivering (on the invoice, for example) and it's a bit tedious to have to type them out by hand. If LR could generate a list of the file names that I could then copy/paste into other documents, it'd be a great time-saver.
Logged

<a href="http://www.scotthargisphoto.com">Website</a>
john beardsworth
Sr. Member
****
Offline Offline

Posts: 2888



WWW
« Reply #99 on: January 03, 2013, 12:04:24 PM »
ReplyReply

Take a look at my ListView plugin, Scott.
Logged

Pages: « 1 ... 3 4 [5] 6 7 ... 19 »   Top of Page
Print
Jump to:  

Ad
Ad
Ad