Lightroom 3.5 Annoyances

I just upgraded to Lightroom 3.5 for Windows and immediately noticed that a few annoyances; some from earlier versions are still in the newest version.
1. For some inexplicable reason, the file path for Lightroom 3.5 for Windows has an extra space between Lightroom and the version number. This appears to be new since I don't recall seeing it in previous versions. The file path reads "C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.5" instead of the standard "C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.5"
Why is this important? It may not matter for most users but since Lightroom cannot sort by file name extension when importing - to distinguish CR2 raw files from JPEGs for example - I created a custom "Send To Lightroom" command via the Windows Explorer context menu to send selected files to Lightroom's Import Dialog box. While editing the command to point it to the new install location I noticed that it didn't work and it took a bit of troubleshooting before I realized the path had an extra space.
2. When a CF card is inserted into a card reader the Autoplay pop-up box reads "Import photos using Adobe Photoshop Lightroom 3.0 64" even though we're currently at version 3.5. Ideally the Provider String Value should be updated with each new release but its been the same since the initial version of Lightroom 3.
3. This Autoplay Event Handler can be edited in the Windows Registry but for some odd reason the key is titled Lightroom3BetaAutoPlayHandler64 instead of Lightroom3AutoPlayHandler64 which would make it much easier to find when searching the registry.

Actually, the fact that there is an extra space in the path means that they did a remarkably bad job. Any programmer who makes that mistake should be justifiably embarrassed and any company that cannot catch that in QA/QC checks has completely failed at a fundamental task. It is something that can lead to problems on the user end, can complicate the Windows regitstry, and certainly can cause grief for add in developers, etc. Beyond those sorts of issues though, it raises an important question. If they missed something so simple (and easy), what does that mean for the integrity of the code where the real complexity is to be found? I have been a user and supporter of Lightroom since version 1 (and the previous betas) and this sort of thing shakes my confidence more than any bugs....
Stephen

Similar Messages

Lightroom annoyance - can't delete photos in collection view?

If I'm viewing a collection (which I am most of the time, because I don't want to be viewing "all photos" which is a mess), I'm unable to actually trash a photo. The delete key simply removes it from the collection. There's no way to actually delete a photo without viewing "all photos" then removing from there.
Isn't there some easier way to do this?

I guess it's a matter of preference. :) I leave the camera's original filenames as they are, I don't have time to rename them. I also don't care too much where the photos are.. I know all of them are inside my "Raw Photos" folder, and then each set of photos exist in folders organized by date. Other than that, doesn't matter to me where they are, I use Lightroom to organize them.
I'm glad someone told me how to delete a photo while in a collection, because that was driving me nuts!

Lightroom mobile performance and "previous" button issues

I am considering subscribing to Lightroom mobile for iPad so I decided to give it a trial run with 2000+ photos sync-ed (iPad 3, Nikon D7000 raw files). The performance is awful!
Browsing through the images is fairly decent. Flagging also does a good job and seems that export works fine, but that is as far as I would go in praising the app.
Downloading from the cloud for offline use takes time (for sure my internet connection's bandwidth is not the problem) and the app does not sync files for offline use when the iPad locks. I had to change the iPad lock settings to "never" in order to be able to download the full set of images. The iPad went from 50% battery to 10% just to download the files. That long it took, with the brightness dimmed to the minimum.
With all other apps closed on the iPad (and offline from CC), it takes 2 to 5 seconds for loading the adjustment values (not to render the image) when moving to a new image (all image info off: exposure settings and histogram).
When using basic adjustments and crop I have found it very difficult to apply the same settings to the next image. Simply the Previous button is inactive. Browsing back and forth seems to activate this button at random times. But clicking on it and selecting "Everything from previous" does not bring any settings. Neither the basic adjustments, nor the crop settings. Although the image seems to be re-rendering.
In this case above, once the "Previous" button is reactivated, clicking on it highlights the selection (e.g. "Everything from previous") but no settings are applied. The menu does not close. I can click on "everything from" or "basic tones from" and they get highlighted but nothing happens. The menu does not close. Extremely annoying.
Same thing for the Reset menu. Sometimes it works sometimes not. I have managed (again at random times) to reset the image to the import settings, browse back and forward to other images, return to the image and then apply the settings from previous photo successfully. But only if I wait 2-3 seconds after the "Previous" menu pops-up.
When I hit the Reset -> All menu and then Previous -> "Everything", the image seems to only receive distortion correction (applied on the desktop to all photos upon import). No other settings are applied (basic adjustments or crop).
When connected to CC, performance degrades even more as it seems that the app is checking for updated settings to the file. It adds an additional 2-3 seconds per image...
Is there a fix in the works for these annoyances? At the current stage of the app, I do not consider subscribing to Creative Cloud as the app is basically unusable for batch processing.
It would be best if the app would be optimised for batch processing as at the moment it seems as poor as the Photos app on the iPad (with some versatility in terms of the settings that can be tweaked). Any target date for a future update? My trial expires in 20 days or so and I am not impressed for now.
I am not bothered by the slow rendering of the images on my device (for sure the iPad Air would do a better job) but the user interface is extremely slow and unusable. I have managed to edit 135 photos in 2 weekend days (roughly 4 hours of use). Very disappointed.

Hi,
thank you for your feedback.
Previous... will only be active if the two images (previous one) and the present have different adjustments.
Some more answers inline:
In this case above, once the "Previous" button is reactivated, clicking on it highlights the selection (e.g. "Everything from previous") but no settings are applied. The menu does not close. I can click on "everything from" or "basic tones from" and they get highlighted but nothing happens. The menu does not close. Extremely annoying.
The Previous... menu will not close automatically once one of its options has been chosen. Btw. do the small thumbnails visually differ from another (Basic tones and Everything)?
Same thing for the Reset menu. Sometimes it works sometimes not. I have managed (again at random times) to reset the image to the import settings, browse back and forward to other images, return to the image and then apply the settings from previous photo successfully. But only if I wait 2-3 seconds after the "Previous" menu pops-up.
Reset to Import is only visible if you have done any changes to the image. When you mention that it sometimes doesn't work - is the problem that it's not enabled at all?
When using basic adjustments and crop I have found it very difficult to apply the same settings to the next image. Simply the Previous button is inactive. Browsing back and forth seems to activate this button at random times. But clicking on it and selecting "Everything from previous" does not bring any settings. Neither the basic adjustments, nor the crop settings. Although the image seems to be re-rendering.
It would be nice if you could give us some more info on this case. Since I have a problem reproducing this issue, could you please let us know if you have many applications in the background? How much free space do you have on your device?
Does a restart of the device help (in some cases it can)?
When I hit the Reset -> All menu and then Previous -> "Everything", the image seems to only receive distortion correction (applied on the desktop to all photos upon import). No other settings are applied (basic adjustments or crop).
Are you doing Previous->Everything this on the same image that you reset?
thanks,
Ignacio

Lightroom is not recognizing the files from my 7D mark II.

I just bought the Canon 7D mark II. I did a shoot Saturday and I'm trying to download the raw CR2 files into Lightroom. Lightroom is not recognizing them. What do I do?

anticandy wrote:
The other guy was a dick
Try to understand from another point of view:
Those of us who spend a lot of our time helping other users in this forum get mildly annoyed when another post comes up asking the same question just answered so many times.
I can see multiple posts with my eyes on the first page, and a search turns up multiple pages, so forgive me if I have a hard time believing you searched very hard (if at all).
So, I think the characterization as "dick" is unwarranted (not to mention vulgar & derogatory) - I answered your post, but did include a note of sarcasm and mild annoyance, which was my intent - I wasn't a dick, per se, but I'm glad the note of mile annoyance came through - consider practicing your search technique..
Rob

Lightroom 2.2 Develop Module Lockup Problems

I have a Windows XP SP2 system with the following specs:
AMD 64 X2 4400+ processor
2GB of Ram
Nvidia 6600GT Graphics (128mB ram)
NView shut off
3D settings: performance
Norton Internet Security 2009 with Lightroom, cache and image file types excluded from scans
The problem that I am experiencing is as follows:
When I am editing an image in the develop module, the Lightroom application will randomly freeze. When the application freezes, the title bar of the Lightroom application window will revert to the blue bar that is the default for the active window within Windows and the cursor symbol will switch to the hourglass and the Lightroom will be completely unresponsive. Sometimes, the problem will clear itself in 30 60 seconds time and the program will become operational again. But, on other occasions it will remain completely locked up and will require a forced shutdown and restart of Lightroom using Control-Alt-Delete.
This problem started with Lightroom 2.0 but occurred infrequently. With Lightroom 2.1 and 2.2, the lockups occur much more often. Also, I have had one instance where the computer completely locked and I had to do a forced shutdown of the entire computer with the power button. When I attempted to restart Lightroom, it complained about not being able to read the database and shut itself down. I started the application again and it came up but appeared to have reverted to an older database backup as I lost all of the edits that I had made during this working session.
I havent been able to determine any specific task that triggers the lock up but I am using the develop module and am doing tasks like selecting another image on the filmstrip, making an adjustment or selecting another tab in the develop pane.
I have updated my nVidia driver to the latest released version as I thought that this might help but I didnt see any changes following the update.
This problem never occurred with Lightroom versions 1.x and my system is very stable otherwise. I treated the temporary lockups as an annoyance but having the database not be readable after the forced shut down of the computer is extremely concerning to me.
I love the idea of Lightroom and plan to stay with it but I need help in resolving this issues. Thanks in advance for your suggestions.
Dave Mayfield

I have exactly same symptoms as Dave Mayfield.
Except I moved images to sub-folders and renamed them, from within Lightroom.
After it locked up, it did not show sub-folders in Library and all the images have question marks on them. If I show it where the file is in Explorer, it does not show any changes.
I Imported one folder and it could see the images in the folder.
Some were without any changes.
Some were the final edited configuration, but not change history shows in Develop. It is if it kept an Exported fersion.
HELP!
Jack Lane

Weird outline occuring in resized pics in Lightroom 1.x

Hi,
I have a question regarding pics that are exported in Lightroom. When I'm done editing, I click on the export button and change the sizing dimensions to 1000x1000 so that I don't have to open it up in photoshop again to resize it. Whenever I do this, it creates an odd outline around some parts of the pictures. Here's an example from last night
http://digitalremix.net/upload/uploads/1/ninja_2010.jpg
If you look at the rear exhaust tip, you'll notice a white outline around the edge of the tip. The same occurs on the ZX6R lettering on the side of the bike. The only way around this, is to export in the original dimensions and then resize again in photoshop, but that's an extra step I'd prefer to not have to do. One of my friends experiences the same issue with lightroom, using the same version as me, which I believe is 1.4. Is there any way around this?

Ah, the resize problem:
http://lagemaat.blogspot.com/2008/08/resize-artefacts.html
http://lagemaat.blogspot.com/2008/08/lightroom-artefacts-even-show-up-when.html
This has to do with Lightroom/ACR's scaling algorithm. There is nothing you can do about it but using a different program such as LR/mogrify or Photoshop to scale your images. It doesn;t show up in many images for me, but when it does, it is a major annoyance.

Problem deleting multiple keywords in lightroom 5

I am importing about 20,000 pictures from Flickr. they are all creative commons, and the end result will be the use of approximately 4000 of these in an online sign language dictionary.
I use Bulkr to import them and this process imports the tags as well as other information such as the photographers name and url. Many of these photos arrive with hundreds of tags, so that the total number of tags might be 20000 or more. I need to assign my own tags and delete all the tags that the photo arrived with. I use the lightroom batch delete to do this (the little minus sign at the top of the keyword list). i select a keyword, hold down the shift key and scroll down. the problem is that i cannot just scroll down to the bottom of the list. There appear to be unpredictable keywords that cause the shift-select process not to work. if i scroll back up and then carefully scroll part of the way back down, then there will be a point at which shift-select stops working and above that it works.
The end result of this is that it takes numerous shift-select-scroll down-select to delete everything so that what should take maybe 2 minutes takes 20 minutes or more.
The problem may be related to foreign language keywords especially chinese characters, but even what looks like a perfectly ordinary keyword can stop it. Two recent examples: travellers cheque and Київ. In all cases, the words can be deleted when i click directly on them. you just cant shift-select THROUGH them.
A separate annoyance that i will just grumble about is that i was forced to put these pictures in a separate catalog because there is always the risk that i could manage to delete my own keywords while batch-deleting everyone elses, and there is no simple way that i know of to undo this. with the separate catalog at least i wont delete all the keywords for my own pictures.

With respect to problems deleting multiple keywords: On Windows, since at least version 3, LR has had basic bugs when you have more than about 1600 keywords showing. (Hard to believe it isn't fixed by now.) A simple workaround for you situation is to filter the keywords one letter at a time and then select the subset of keywords that are showing -- e.g. filter all keywords with the letter "t", then all keywords with the letter "b", etc.
With respect to not getting the keywords into your catalog in the first place: You can define a Metadata Preset that will clear the keywords on import:

Runtime error R6304 Lightroom 5.3

Hi, I am getting a Microsoft Visual C++ Runtime Library error when I import photos into Lightroom 5. It is not allowing a clear thumbnail of the my photos
Can anyone help with this issue
Thanks
Dave

dj_paige
Sorry about that, early morning CA time and lack of coffee chagrin and annoyance at systems in general.
64 bit operating system
7.89 useable Gigs of RAM
There are perhaps 600-700 pictures installed on the computer in total, but I suspect the point is that the program does not even get around to asking where I wish to locate the photos but preemptively dismisses the suggestion out of hand.

Sharing color settings between Photoshop or Lightroom

Okay, I'll admit it! I'm partially red-green color-blind. It's quite common in males actually, so it's not that unusual. However, it does make it tricky while color-correcting skin-tones. I work for a wedding photography and cinematography company in Vancouver and have made a deal with the photographer --who also happens to be the owner of the company-- that him and I would collaborate on the color correction side of things. This is useful not only for my impairment, but also from a stylistic point of view.
Now here's the problem: He has never touched Premiere or After Effects. Now instead of going through step-by-step with him, and delivering hours of footage to him on a hard drive, and having to relink all the proxies, I figured it would make a lot more sense to give him a freeze-frame that he could edit himself. Like many small businesses in this industry, we edit out of our own homes, so driving from place to place is not only inconvenient, it's also unfriendly to the environment.
So I was mainly curious if there were a way for him to edit the freeze-frame in Lightroom or Photoshop, and then somehow export the settings so that I could import them back into Premiere. I know there are many similar tools such as RGB Curves that would be easier for him to use. Or does someone have another idea that might make this workflow more efficient? Wedding season will be starting soon to speed up turn-around before it's too late.
Thank you in advance!

I know you'll be shocked at this ... but over the years I've worked with a certain number of my pro stills peers who were perhaps a little set in ways that were ... um ... intractably set in them but shall we say, intriguingly unique? I'm sure this comes as such a difficult concept to grasp!
One of the problems that came in with digital was the concept that "we" can fix anything in post. White balance? Why bother ... simple adjustment in Photoshop! And this was something that was a nightmare when the only options in-cam were 8-bit Jpeg or Tiff files. So ... RAW got into the cameras and Lightroom and you could easily tweak entire batches in Lr ... again, why worry about WB in-cam?
Because ... it made post much faster and more accurate by getting into a much closer value on "loading" into Lr. After you've learned how to WB your camera manually and can do this quickly without even taking any gray cells ... it's so much faster over-all than "fixing" later.
Now ... take someone who thinks of usable color as an annoyance in shooting so it's a "fix in post" thing for ... something "acceptable" ... shall we say? Give them a DSLR that takes video, and voila ... we fix that in post also, right?
Oh my Heavens that's ... BAD. Because that person also will find making sure they have dead-on exposure a COMPLETE pain & waste of time. So the editor/colorist gets (typically) WAY under-exposed & way-off color video clips to match to the still images. DSLR video is far too "thin" in data-bits to bend much or it just completely breaks, totally different than DSLR still images these days. And you have to bend that stuff a LONG ways to look half-matching the stills!
So ... if you can't get this dude to modify procedures based on the absolute technical needs of producing professional work in video as well as stills, you have a difficult situation. And all my sympathies. I have my partner ... who I also happen to have been married to 40 years this June ... who 1) doesn't like to have to think while shooting and 2) has her ways to get good stills down pat without thinking. How to get new patterns built in? Well ... how about spending 3-4 sessions of an hour or more simply practicing the change-over from stills/video/stills/video? It's the kind of thing I do ... however ... chance of her actually practicing like that are not something I'm gonna hold my breath waiting for. Sigh. So ... she's done a bit, been disappointed ... and just doesn't do much with it. Which could help us a lot. Eventually, I'll move her along. Wish it wasn't such a hard slug.
Neil

Lightroom 5.3 Error message: Not enough memory

I have just installed Lightroom 5.1 and downloaded the 5.3 updates. When I press Import I instantly get a message: An Internal Error has occurred, not enough memory. There is nothing in it as yet, it was just installed.

dj_paige
Sorry about that, early morning CA time and lack of coffee chagrin and annoyance at systems in general.
64 bit operating system
7.89 useable Gigs of RAM
There are perhaps 600-700 pictures installed on the computer in total, but I suspect the point is that the program does not even get around to asking where I wish to locate the photos but preemptively dismisses the suggestion out of hand.

Lightroom CC reloading on editing TIF files

OK - another little Lightroom CC item I did not experience in earlier versions.
Library catalog settings set to record data to XMP file, as is my standard operating procedure. NEF raw file edits proceed as normally. However, on editing TIF files, such as those created externally via Silver EFX or what have you, LR constantly "reloads" the image after every edit (so it seems), and does not keep any of the edits made to the image on reload.
The workaround I found is to turn off recording data to XMP, however I prefer to have XMP data separate from the LR catalog.
Anyone else experiencing this issue?

Thank you! Yes, I have exactly the same problem. Since upgrading to LR6, touching almost any slider in the Develop module would cause the image to "reload". Worse, it would often "forget" my previous develop edits: even though they were listed on the History panel, they would no longer have any effect.
Great catch, noticing this was just for TIF files! I didn't make that connection. But as most of my edits involve a round-trip into either PS or Nik, I was almost always editing TIF files. As you suggested, I've disabled "Automatically write changes into XMP" in the Catalog Settings - and now it once again works properly. My first guess was that this had something to do with GPU rendering, but disabling the GPU had no effect on this problem.
This is potentially more than just an annoyance. As mentioned, such a "reload" event would often lose ALL of my previous edits (even though they were still listed in the History panel) and reset the image back to the starting point. That's actual data loss!

World of trouble with Lightroom

From what I've been reading, a lot of people seem happy with lightroom 1.0
It's giving me a world of trouble.
1. Sometimes it just crashes while importing a big folder of raw images. And when it doesn't crash, it takes forever.
2. I get outofmemory errors all the time
3. It seems unworkably slow...maybe I'm just not used to it.
4. When I'm importing from a memory card, there is no way to convert to .dng and have a full-sized image preview made at that time?
5. If I set a label in lightroom, using a .dng file, then later open the file with bridge, the label won't show up.
6. There are tons of interface glitches/annoyances. Like the annoying flaps on the side pop open when you don't want them to, then you have to wait for them to go away. When you use the key command to reject an image (X key), you can't just press (x) again to unreject it. You can't even do control-x or alt-x you have to get the mouse and click the stupid reject flag. And the flags don't show up in the loupe view...in fact there is very little info in the loupe view. So when you are looking at an image, you have to take your eyes away from it to see what the label is, what the flag is, etc.
I'm using XP x64...I don't know if this is a factor with the memory leaks and performance, but this really feels like beta software still. It doesn't feel like lightroom is ready for primetime yet!

It is quite obvious by now that the Lightroom modules when run on the PC platform, with the exception of the 'Develop' module, are pretty much broken and should be used minimally.
The 'Develop' module is great, I have NOTHING bad to say about it, but the modules around it pretty much stink. And virtually nothing about it has to do with the PC platform itself.
As I keep saying, I love the 'Develop' module, but the 'Library' module is so full of bugs and shortcomings that it is best avoided. Specially from a professional perspective... it may be adequate for amateurs and their needs, but the glitches and workarounds make it pretty much unusable as a professional tool.
I guess I should justify my statements:
a) File Ingestion - Downloading files is slow since it does a simultaneous import, which builds up the database and therefore is slow. When you have to download several cards with several hundred photos and do picks on deadline, you don't have time to be waiting around for Lightroom to build previews. Solution: Download using the OS drag and drop or a dedicated tool like "Downloader Pro", and do your initial selection and sorting with a separate sorting package of your choice. Only after you have whittled down the photos using a different tool should you consider importing into the Lightroom database.
b) File renaming. Again, amateur at best when compared to even a cheap tool like BreezeBrowser.
c) File organization, tagging, etc. Unless you generate 100% previews, it is unusably slow. You need 100% previews if you will be considering detail during your sort. And generating all 100% previews takes forever and results in a HUGE ligrary... if you are sorting JPEGs, you end up with a thumbnail collection larger than you original photo collection! So the solution is: IMPORT ONLY FINAL CHOICES INTO THE LIGHTROOM LIBRARY. Use Lightoom only for significant 'keepers'. Do your initial ingestion and sorting using almost anything else.
Once you get the actual photos that you want to adjust into the Library, and no more, then the program starts to really shine.
The stability is somewhat better on the Mac platform (I use both platforms), but the same issues of ingestion time, renaming, 100% preview building exist. They are part of the program core design.
(Slideshow and HTML generators are not even worth considering at this time, they are so limited when compared to so many other options available. I can not comment on the print module, since it does not do "print to File", provide soft-proofing, allow output to specific profiles, etc... so it too is fairly limited for 'pro' purposes, and utterly useless if you output to commercial printing systems.)

Runtime error in starting Lightroom

I receive the following message when I try to start Lightroom:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:...Files\Adobe\Adobe Photoshop Lightroom 1.2\lightroom.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Lightroom ran well for several days and then failed to open with the above message.
I have tried everything I know to do (uninstalled and reinstalled the application, restored the computer to a restore point before Lightroom was originally installed, etc.) and do not know were to go from here. Suggestions would be appreciated.
I am using Windows XP sp2 and have 4 GB of ram and 250 GB of hard disk space.
Thanks,
Cliff Culp

Aha! A fix! Please look at this...
http://www.adobeforums.com/cgi-bin
bob frost, "Help! Runtime error after Lightroom 1.1 install!" #10, 27 Jun 2007 6:54 am

Lightroom imports photos to wrong folder

I've been importing lots of photos from my hard drive into lightroom and been moving/renaming them in the process. I only got lightroom a few weeks ago.
This has worked fine but i've recently imported a few hundred photos off my iphone and doing the same thing - move and rename. The trouble is, these photos keep going into the 2009 folder, instead of the 2012 or 2013 folders that they should be. When i look at the photos, they have the correct name, and the capture date seems to be correct, its just lightroom keeps wanting to put them in the wrong folder by year. Does anyone understand why this might be happening?
naturally I want all my photos sorted into the right date folders as this is the way ive decided to organise my photos...

hmm so still not making sense. it keeps wanting to import my photos into the wrong destination. have removed all the photo from lightroom. how do i change it so it automatically puts the photos into the corresponding year/month they were taken..
I understand its something in the import settings/destination but cant seem to change this. not sure what parts of the import box your wanting to see Dj.
the structure now is my pictures/2009/21-7-09 then its creating new year folders and sorting them within this 21-7-9 folder..
can't see to change this?

I am trying to import developed images from LightRoom 5 in o Photoshop 6. I am receiving this message and the images will not open.....'Could not open scratch file because the file is locked, you do not have necessary access permissions or another progra

I am trying to import developed images from LightRoom 5 Photoshop 6 for further editing. I am receiving this message and the images will not open.....'Could not open scratch file because the file is locked, or you do not have necessary access permissions or another program is using the file. Use the 'Properties' command in the Windows Explorer to unlock the file. How do I fix this? I would greatly appreciate it if you would respond with terms and procedures that a computer ignorant user, such as me, will understand. Thanks.

Have you tried restoring the Preferences yet?

Lightroom 3.5 Annoyances

Similar Messages

Maybe you are looking for