Product Feature Suggestions

Could someone please tell me who i can post or send comments to about feature enhancements/suggested improvements too? Thanks.

Use either one of these links.
iPod Feedback.
iTunes Feedback.

Similar Messages

ITunes User Feature Suggestions

I think it would be beneficial for Apple and the users to have a dedicated thread
for User based feature suggestions ,So with this in mind I hope you add this as a sticky or ad this as a category all it's own .

A built in album art/pdf. viewer : As Music makes it's change more and more over to digital distribution artists are making the art/packaging available in.pdf and ,or embed in the mp3's themselves however the user "experience" in this is laking .
A built in viewer for the "digital booklets " and embedded art would add that missing streamlined sexy appeal we mac users are missing and accustomed to .

Keyword Bugs and Some Keywording Improvement / Feature Suggestions

Tagging Bugs and Some Improvement / Feature Suggestions
Please excuse where I should use the word Tag or Keyword or vice versa!
1.       BUG?    If a tag synonym is added or changed then all affected photos should be marked for re-publish. I do not think this currently happens.   Should this possibly be considered a bug?
2.       BUG?    When viewing a smart collection in a Flickr publish service and a new tag is added to a photo it is correctly moved to the “requires re-publish” section.   However … the thumb selection in the grid moves to the next photo, the loop view remains on the photo just tagged and the key wording still reflects the just tagged photo.    The selection shown in the grid appears to be wrong.      When working quickly this can result in tagging errors as the user looking on the grid believes he is working on the next highlighted photo in the grid.      This is surely a bug?
3.       BUG?      A minor point and I realise this is probably not the correct way to do things … but a double word synonym entered with quotes for example “Ice Climbing” will create two tags “Ice” and “Climbing” at the flicker end of things.    Removal of this synonym and forcing a re-publish does not delete these two tags at the flicker end of things.    I may have miss-understood, but perhaps it is best for LR not to allow quoted tags?
4.       SUGGESTION      An easier and more powerful way to review tagging of current photos should be provided whereby it is possible to clearly see the current tagging of a photo and have immediate access to the keyword list at the same time to make corrections.    Having both the Keywording and Keyword List panels open in Library mode results in a lot of up and down scrolling for me and is a slightly inelegant UI in my opinion.   I would suggest it should at very least be possible to have the tags viewable in Loop info as an option - so long as no truncation is made and all tags visible.    Ideally a better way should be sought.
5.       SUGGESTION      It would be very useful when reviewing tagging to select to show all photos in the currently selected folder or set which do not contain the selected tag.    Note, I don’t think this can be easily achieved by using a keyword filter and selecting all keywords and unselecting the tag of interest as the pictures may have many tags.    The same might be performed by textual based searches but this is inelegant and its slowness precludes a browsing approach.     For example – for me it would be useful to look at all my mountain shots in a trip which have not been tagged with “Glacier” and it will be immediately visually apparent where I need to make tagging corrections.    I would suggest a “Not” checkbox is made available on the top of each column in the library filter – this may also provide a great deal of power for other situations.
6.       SUGGESTION      It would be useful to allow a means of showing all pictures with a certain tag but which have not been tagged yet with any children of said tag.   For example all pictures tagged with Glacier which I have not yet named the glacier by introducing a relevant child tag or selecting an existing child tag.    A similar situation occurs for wildlife and potentially many other scenarios … I would like to use a tag “Butterfly” which I can quickly use on my first pass… and then do the identification and child tagging on a second pass using appropriate filtering.   This allows for a step wise or “top down” approach to tag classifying things in a workflow.    I appreciate this can be achieved (as I do now) by using a child tag called “Unnamed butterfly” or “Unnamed Glacier” but it seems more powerful, elegant and generically applicable to be able to filter on a “not tagged with a child” basis.
I apologise if I have missed the point on some existing functionality on any of these points and welcome any suggestions.

This is a great post.
I couldn't have written it myself better.
I'm also in dying need of Korean input as I can't communicate with my Korean friends.
But I second every point.
I hope the tech teams are reading this.

How do i submit a product improvement suggestion

How do I submit a product improvement suggestion for the iPhone?

Apple does not accept input from the general public. They advise AGAINST it.
http://www.apple.com/legal/intellectual-property/policies/ideas.html
Apple or any of its employees do not accept or consider unsolicited ideas, including ideas for new advertising campaigns, new promotions, new or improved products or technologies, product enhancements, processes, materials, marketing plans or new product names. Please do not submit any unsolicited ideas, original creative artwork, suggestions or other works (“submissions”) in any form to Apple or any of its employees. The sole purpose of this policy is to avoid potential misunderstandings or disputes when Apple’s products or marketing strategies might seem similar to ideas submitted to Apple. If, despite our request that you not send us your ideas, you still submit them, then regardless of what your letter says, the following terms shall apply to your submissions.
TERMS OF IDEA SUBMISSION
You agree that: (1) your submissions and their contents will automatically become the property of Apple, without any compensation to you; (2) Apple may use or redistribute the submissions and their contents for any purpose and in any way; (3) there is no obligation for Apple to review the submission; and (4) there is no obligation to keep any submissions confidential.
PRODUCT FEEDBACK
Apple does, however, welcome your feedback regarding many areas of Apple’s existing business. If you want to send us your feedback, and we hope you do, we simply request that you send it to us using the form found at www.apple.com/contact, or you can choose from the many other listed areas for your feedback. Please provide only specific feedback on Apple’s existing products or marketing strategies; do not include any ideas that Apple’s policy will not permit it to accept or consider. It’s just one more way that Apple can learn how to best satisfy your needs.
Feedback and Information
Any feedback you provide at this site shall be deemed to be non-confidential. Apple shall be free to use such information on an unrestricted basis.

Who do you contact with Aperture feature suggestions?

Who do you contact with Aperture feature suggestions?
Anybody have Joe Schorr's email address?
Photographer Brian Fischer, Atascadero CA
[email protected]

There's a "submit feedback" menu item in Aperture itself. Use that

Backlighting Feature Suggestions?

Where the heck is the iPod feature suggestion area?
There definitely needs to be separate backlighting controls/timing for running on battery power and running on AC/DC/USB power.
Powered example: when I'm plugged into my car connection, which is powered, I want to be able see the display. Would be nice to do that without scrolling through the menu everytime. The display is impossible to read dark.
Battery example: when the iPod is in my pocket, backpack or whatever running on battery power, it doesn't need to remain backlit long. I can't see it anyway.
Seems like options to set for each type of power would be useful to most users.
I primarily listen in my car and via the home stereo. I rarely run on battery power/headphones.

I don't want to have to manually set the backilight setting for whatever condition I am using the iPod. It should be smart enough to know when it is connected to a power source and when it is not.
When it is connected to a power source I want the opition to set it to "Always On" and when I am on battery I want it to automatically set to a specified amount of time (i.e 5 seconds).
I also like the option of having it cycle on for a few seconds when the song changes.
Dell Windows XP

What security products are suggested for scrubbing rootkits from a Mac? There are good articles on similar repair for PCs and it makes me want to see if I can save this machine. It's in forensic recovery right now so I myself have not done anything yet.

What security products are suggested for scrubbing rootkits from a Mac? There are good articles on similar repairs for other makes online. I would like to investigate whether a machine can be truly scrubbed or if it's best to retire it. I haven't done anything yet as it is a candidate for more extensive forensic recovery.
Also, I am not sure if various malicious spoofing and cloaking tricks (making Wi-Fi appear off when it is on, hiding unauthorized sharing/remote access, falsifying System Preferences preference panes, etc.) are resolved by a thorough drive erase or are more similar to APTs?
Finally, is there any emerging information regarding APT hiding places other than the recovery partition? I have heard mention of the EFI, for example, but it seems unproven and unlikely. Some people have also mentioned the RAM.
This is an upsetting topic to some people, including me, so I appreciate circumspect, measured responses. Thanks! And don't try to answer all my questions if you really just want to comment or answer one. All thoughts are appreciated.

Hi, Lincoln,
A straightforward question. You are correct in recognizing the difference between tentative conclusion and certainty. Here are our main reasons:
1. Incoming items noted on the console (or console sub logs) and Activity Monitor after defenses are overcome, and which are brought in by an unwelcome remote user, often have a process name and the word "kit." (Bear with me.) We soon observe the process is under attack, from terminal evidence and soon, decreased or lost functionality of the process. The terminal generally reports alteration of specific kernel behaviors. A simple example (that may or may not be accompanied by kernel changes and may simply alter permissions) is modifying Disk Utility such that key uses are unavailable. You can see how an attacker might value disabling partition views, mounting and permission repair. In retrospect, DU might not be a root alteration. I was thinking that its relation to fsck flagged it as a possible ring 0 item. I may need to know core parameters of a good example to pick strong ones.
2. Incoming folders hidden for possible later use contained bundles of similar root kits, including some not applicable to Macs. From what I have read from reasonably credible sources, root kits are sold and traded both singly and in bundles.
3. Root kits are a logical next choice for our attackers, as various prior techniques hindered us but did not paralyze us.
4. One of the most authoritative articles I found was about PCs not Macs. I noted the assertion, undocumented, that an estimated one million computers are infected by root kit manipulations, and underscored that the kits can be used by people with low computer skills.
5. MacAfee lists root kits (by description, not name) as a top pop five threat prediction in the coming year, though again, the emphasis is on PCs.
Linc, I am trying to show a spectrum of observations and info that have shaped my thinking. To retrieve better captured evidence requires significant legwork at this time, but it is something I am willing to do if you can be patient. Understand this long attack has been like a natural disaster to us.
I have not linked a few articles of interest because I forget if that's allowed. If so, I'd be glad to.
After reviewing this partial answer, you may form another hypothesis. If so, please share it. I am comfortable with my position but not clinging to it.
Thanks for your interest. Looking forward to your thoughts.
Oh, yeah: some material is out for analysis, so we should have credible opinions pretty soon. Not positive exactly when.

Where To Post Product Feature/Improvement Suggestions

Hi,
I have a bunch of suggestions for product improvements and new features (mostly security-related) that I would like to send to Apple development teams. Do I post it in the discussion forums or do I e-mail it to Apple ? If I have to e-mail it, what's the address ?
Thanks

Hi bartron2007!
Go here Product Feedback.
And note "Please read Apple's Unsolicited Idea Submission Policy before you send us your feedback."
ali b

FAQ: If I make a feature suggestion, will I see it in the shipping product?

Adobe is always eager to hear what users think and feedback will be considered for future versions of Photoshop.

If you have an Apple router now providing your wireless network, you could add another....like an AirPort Express, for example....to "extend" the signal wirelessly and provide more coverage.
This is always a bit tricky, because the AirPort Express would need to be located where it can receive a strong signal from the main AirPort wireless router.
For example, if you need more wireless signal in a bedroom at the end of the house, you would locate the AirPort Express about half way between the main AirPort router and the bedroom.
On a side note......only the print function will work when you connect an All-in-One device to the USB port on an AirPort, so connect the All-in-One using wireless for full functionality.

How do you make an itunes feature suggestion to Apple?

I'm trying to find a place to make an itunes feature suuggestion to Apple, but all I seem to be able to find is a "request music" link...
If this is the only place, then here is my suggestion...
I am a video editor and I use itunes to play my music, but also to audition sound effects and production music tracks. But when I do a shuffle play of my entire library, I don't really want to hear these sfx and songs (or the audiobooks I've taken from an audiobook CDs).
Therefore, I think it would be useful if there was some kind of "flag" that said "this is not a song" or "don't include in shuffle".
Alternatively, what would be great for me, is if itunes could have multiple libraries, then I could have a normal music library, a sfx and production music library and an audiobook library.
Anyway, I guess I can dream.
Chris.

The iTunes feedback is confusing indeed. I use the general Feedback page to report bugs and to do suggestions.
They assure that the messages will be read, but you won't get a reply.
As this is a user-to-user forum, it is highly unlikely your suggestions will be read by Apple employees (except moderators).
You can exclude songs from shuffling by checking 'Skip when Shuffling' in the 'Options' tab of the Info window (Get Info of a song; shortcut: command-I)
Unfortunately, you can only do this song by song.
Using this script, you can enable/disable 'Skip when Shuffling' of all selected songs.
You could put the songs/sfx in a playlist, select them all (command-A) and run the script.
To run multiple libraries, you can choose between these two applications:
iTunes Library Manager and Libra.
Although not real instant switchable libraries, both apps. can create multiple 'iTunes Library' files, which enables you to have separate libraries for all kinds of files.
Hope this helps.
M
17' iMac fp 800 MHz 768 MB RAM Mac OS X (10.4.7) Several ext. HD (backup and data)

New feature suggestion: Graphic Pitch Adjustment

Hey all -- Digital Performer user here, but soon to make the move to Logic (as soon as the new desktops come out in 2008). There is just one major time-saving feature I am missing in Logic, and I thought I'd post it here. I've also sent this suggestion to Apple .
That feature is the ability to graphically adjust audio pitch. Digital Performer has, for a couple of years, had the ability to analyze pitch on any audio as soon as it's recorded, and then allow users to graphically adjust it +*right in the audio track*+. I'm an owner of Antares' Auto Tune plugin, which has graphical adjustment ability, but it's a real pain. Also, it's a plug-in, and not inherent right in the audio track. Here's a link to the page for that feature at MOTU's site:
http://www.motu.com/products/software/dp/features46/pitch-automation.html
Again, this feature is a huge time saver, and something I really can't do without.

So that's basically Melodyne Plugin but built right in the track view. Would be handy I suppose - I've just come from SONAR which has it's own version of this (called V-Vocal) but it's not quite so integrated as the DP example you linked to.

When will you release the next version of Strobe? + Feature suggestions

Thanks for a really excellent,solid and well thought-through video player.
I'm just curious on when the next version will be released. What kind of features are planned? A public roadmap would be really nice to have when developing around this player.
My suggestions would be:
Simple JavaScript API
An optional loader graphic while the media element is being retrieved/determined. (Instead of the miss-aligned buttons and completely black screen)
Possibility for the user to retry playback if RTMP connection fails, (media element not found) instead of locking the player, currently forcing the user to reload the browser.
Remove the pause button on live streams and replace it with a stop button. (When DVR is not supported obviously)

Hi,
Thank you these great suggestions! We will definitely consider these for our future roadmap. A couple quick answers to your questions:
We are shooting to release the next version (v1.5) of Strobe Media Playback (SMP) in December.
One of the key features of SMP 1.5 is a JavaScript API for creating player controls. We've actually just released a sprint drop that includes this feature, and the source can be downloaded here and the specification can be found here.
Some of the other planned features for SMP 1.5 include Multicast support and an HTML5 fallback engine. (Please note that these are just planned and not committed features.)
We have just added support for an FMS 3.5.3 feature called Stream Reconnect to OSMF 1.5 (release currently scheduled for early November). In the event of a network connection loss, this allows the player to continue to play out the buffer while it attempts to reconnect to the network. Would this suit your needs? We will likely eventually add this to SMP as well.
Any other questions or feedback, please let me know.
Thanks!
Cathi
Product Manager, OSMF and Strobe Media Playback

"vi is not executable" built app - product feature request

OK, here's what I want for the next version of LabVIEW. Forget a real implementation of OO. Forget about making XControls so that you don't need a PhD to program them. Forget about a real polymorphic control (down all you who say "variant!"). Here's what I want for the next feature of LabVIEW.
I want the run-time engine to give me a better idea of why a built application won't run. The generic "This VI is not executable. The full development version of LabVIEW is required to fix the errors..." is meaningless. If the VI works just fine in the development environment, and it builds without errors, why does it not run? If there's so many reasons, how is one supposed to track it down?
I've been using LabVIEW since version 2 on a Mac, so I like to think that I know what I'm doing with it. Yet, whenever I run into this I feel helpless because I have NO information! This is frustrating beyond my ability to put into words. And please don't tell me to look at this article or this other article in your KnowledgeBase. Been there, done that. In one situation I tracked the problem down to a VI. Couldn't find ANYTHING wrong with it. So, I created a new VI, copied the block diagram over, and saved the new VI over it. Rebuilt the app, and presto, the app worked. Do you know how long it took me to track it down to that VI? About half a day. Was there ANYTHING that gave me a clue as to the problem? Can you say rhetorical question?
I'm posting this here in the hopes that enough people get my grief, and head over to the Product Suggestion Form to hopefully make this pipe dream a reality. Power to the people!
Now, back to figuring out why my latest built application won't run. Guess what I'll be doing for the next half-day or so.

smercurio, i can't help you, but i'm with you, maybe that makes you feel better.
i upgraded a LV-app i created originally with 7.1 (this was the best LV ever, in my opinion) to 8.20. i was forced to do that because of the 64bit feature of ms tickers. it took me about 4hrs to create a project to generate an executable, after several LV-crashes during editing. finally i managed to get the project working (compiling took about 10 mins, with the 7.1 app builder about 1 min!! same code!!!), and then there was this error message: "error blabla in VI blubblub", and the VI was part of the vi.lib! so what to do?
KB: no answer!
discussion forum: no hits!
i found a post in the forum about another error code, but the same scenario. workaround was to disable the "remove as much as possible" option in the advanced project settings.
result: size of executable increased about 100%, while execution speed decreased about 50% compared to the 7.1 version, though all of the "code enhancement features" of 8.20.
now i'm thinking of switching back to 7.1 and to workaround the limits of long execution times with 32bit tickers.
i'm a big fan of LV, and i'm dealing with it since 1998, not for fun, but as a professional programmer. but 8.2 is a real step backwards in quality in my opinion. i think this has to be said to make 9.0 better!
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Feature Suggestion / Request: Ability to live preview websites instead of screenshots

I know BrowserLab behind the scenes uses licenced operating systems to be able to offer so many different test combinations like Mac and Windows testing with various browsers, but I would like the ability to be able to interact with my sites and do things such as click elements that trigger modal boxes and other things like text input actions.
Is this something that will eventually happen? It's a bit of an inconevience to use the Firebug extension to test certain parts of my sites especially for actions like modal boxes and things that happen after certain events are triggered like logging in or Javascript validation on a login form showing errors to a user if they missed something.

We hear this request frequently, and understand why you'd want to be able to interact with a live page.
We have multiple datacenters for our browser server machines, which are shared by all BrowserLab users. These browser servers each handle dozens/hundreds of of screenshot requests per minute, from all of the users that are currently using the service. To support live testing, each user would have to have a dedicated machine that could only serve that one user while they are live testing. This would significantly increase the number of browser servers we would need to run the BrowserLab service, which of course would significantly increase the costs of running the service. Licensing restrictions are also a major factor when considering offering live testing. Combined, these factors mean that we're unlikely to offer a true live testing environment for BrowserLab.
We are considering some innovative new features that would allow you to achieve the results you're looking for, without having to dedicate a machine per user. We're actively exploring these as we plan the future of BrowserLab.
In the meantime, if you haven't already, consider taking a look at Dreamweaver where we've added some nice integration with BrowserLab. Dreamweaver has a feature called Live View, which is a fully featured WebKit browser built into the product. You can browse the pages you're creating, and drive them into specific states, then Freeze JavaScript. Once you have the page frozen in the state you want to test, you can send it to BrowserLab to see your page rendered in that state across all browsers. If you aren't using Dreamweaver, or prefer, you can use Firefox with Firebug and our BrowserLab for Firebug extension to achieve similar results.
If you absolutely must have live testing, you can find some online services that will rent time to you on their machines. I have tried many of these and generally found them to be expensive, and with their own issues. But if you have to have live testing, this may be a solution for you.
Thank you for taking the time to give us feedback. I hope this helps you understand our position.
Bruce
Bruce Bowman
BrowserLab product manager

Feature suggestions for Lightroom 3

Hi team,
Here's a quick summary of some ideas for LR3. Not sure how late in the dev cycle you guys are (we've seen one public beta so far, I would expect 2 or 3 before you go RTM, and features have not yet been frozen according to my reading):
* Perspective correction / Keystoning: This has been mentioned a lot here and on other forums - a no-brainer, especially considering that DNG 1.3 specifications allow for it
* Individual RGB channel control: Something that Capture One & Bibble 5 also have. It's time LR added this feature also, I think
* Soft-proofing: Hate to bang the drum on this one, but the LR interface could benefit from a readout of which colour space we're operating in for the current image, along with the ability to change this (I would think a simple drop down would do the trick, similar to the Tone Curve type). This is especially true on account of the fact that Library and Develop use different color spaces to display images (not a bug, a feature - but an obscure one at that)
* Layers: While I understand the LR team's resistance to layers as a concept (or at least calling it that, since the Adjustment Brush effectively - and very nicely - implements layers in a fashion), it would be handy to have. For example - let me rearrange the order in which Adjustments are applied. As a panel in Develop, this could easily be ignored by anyone not wanting to use (or who doesn't understand) Layers as part of their workflow. Leaving it out to "keep things simple" is not a good idea, IMMHO. After all, LR is targetted primarily at Pro Photographers and Advanced Enthusiasts - who should know how to use Layers, or at least be willing to learn!
* If not layers, then perhaps a list of Adjustment Brush pins in a scrollable list, so I can select them based on the adjustments I've made. Perhaps I could then re-order this list? The key challenge here would be how best to label each one?
* Selections / Adjustment Brush: Having Bezier, Rectangle, Ellipse and Free-form as selection options (along with the ability to invert these easily so I can do "Negative" selections where that's quicker) would be fantastic - this is something LightZone and Bibble both have
* Paint with Preset: At the moment, the range of settings I can apply with the Adjustment Brush is limited to a half-dozen or so. I can't paint White Balance, Sharpening (at least not with masking), Noise Reduction, or HSL adjustments, for example. This would give me lots of very granular control. It would be fabulous if we had a "Paint with Preset" option or a "Preset Brush" that let me create a Preset, then paint it on at various opacities (combined with the ability to invert selections, this would be extremely powerful).
* Blend Brush: An alternative to the Paint With Preset might be the ability to "Paint with another Image" over the current one. This might be useful for blending multiple exposures (e.g. to remove people in landscapes, or to do simple selective HDR blending from multiple exposures). Having the ability to set the "Blend Mode" (similar to PS's Blend Modes) might also be helpful. I imagine this new brush would work in a similar fashion to the current Adjustment brush, only it would be combining information from multiple images. It might be useful to have a "2-up" display similar to compare mode that shows the "Source" and "Target" images side by side (with the ability to zoom in and out)
* Grayscale Wedge: Would it be possible to have a greyscale wedge that could be displayed beside or underneath an image in Develop? LightZone has a fantastic implementation of controlling image Zone information using a simple point and click on the wedge. Well worth checking out. It would certainly make adjusting tones in the image a lot more intuitive for some people. I think this concept could be taken a step further.
* Luminosity Mask: The ability to "Auto Mask" an image based on its luminosity (i.e. which Zone an area falls into) would be way cool as part of the Adjustment Brush. That way, you could control individual zones easily. I imagine this tool would have 2 sliders: "Luminosity" (from light to dark) - which would determine the "target" luminosity to Mask; and "Threshold" which would determine the "Width" of the selection in tonal terms. Holding down the Option key on either slider would show a dynamically generated Mask overlay to help me determine which areas the Mask is applying to
* Color Mask: See Luminosity Mask above. Same idea, but based on Color. Perhaps a Color Picker tool would enable me to isolate a Color and create a Mask (which I could then refine using the Erase or AB tools if necessary). This would have HSL sliders to select the target color, and a "Threshold" slider to control the "Tolerance" either side. Again, using the Option key would give me a preview similar to the Sharpening / NR tools
* Perhaps the Selection Tools, Luminosity and Color Masks above could be combined into a "Smart Mask" panel (or panels) in the Adjustment Brush tool, making it more consistent with the current interface, and making it much easier to create masks with the Adjustment Brush
* Ability to Maintain Color Profiles inside LR, without having to restart. I use the X-rite CC Passport to generate Color Profiles at almost every shoot. It might be helpful to have an easy way to maintain these Profiles (and to share them like we can share presets!). At very least, add an option in Preferences to open the appropriate Folder so I don't have to go hunting for it.
While the early LR3 beta is encouraging, I do think it is missing many user-requested features, and features its "competitors" already have. In my view, Lightroom needs to stay ahead of the curve to gain market share.
Once again, congratulations on creating a fantastic tool in Lightroom. It just keeps getting better with every version (LR3 looks amazing so far for an early beta - love the improved demosaic sharpness and NR).
Hope these suggestions are helpful.
Cheers,
Matthew

Six changes that would be basic improvements - sorry if these look like bug reports, but they have lasted through all the updates and upgrades and I consider them to be overripe for improvement.
For mouse-heavy users it would be helpful to have a Grid icon in the toolbar in the Develop module, the same as appears in the Library module.
The consistency of having a Done button in all places that present a secondary work screen would make leaving those screens simpler.
When organizing folders, keeping the focus local after a Delete would be good, instead of the focus jumping up to a higher level as it does, requiring a search for your location. If you're making a lot of changes this can be time-consuming and frustrating. I know some other program do this, but not all and it's solvable.
When moving a folder of files, the last file doesn't get moved and could wind up in some random place if you don't suspect this and go after it to move it by itself. This seems to be unique to Lightroom.
In leaving Compare, it's not clear which image you're keeping because the filename isn't visible, only the rating (if used). Changing the rating to exit can disable the Done button. To get it back it shouldn't be necessary to swap the images. Why not use a more standard release action like the Escape key?
In LR 3.3, when using the noise reduction slider the option to update the whole filmstrip to use version 2010 is available only if the demonstration "compare" screen is retained with a box checked. If you uncheck that box, there's no way to get that screen back the next time, so the option to update to 2010 for the whole filmstrip at once is gone and subsequently requires one-by-one clicking to update. This could be simpler and faster.
I use LR every day and teach it, but I may have missed something so forgive my naming ills that have already been mentioned. Thanks for listening. DKD

Product Feature Suggestions

Similar Messages

Maybe you are looking for