BUGS in Lightroom 1.0

Ok, I'm already working a month of 2 with LR. So far, I like the app very much, if it was not for al those bugs!
I encountered following things: Anybody else with these bugs?
* sorting order; sorting on edit time instead of capture time
* exporting photo's, LR keeps exporting the same photo (with other photo's selected) only changes after restart
* Rejected Flags set with shortcut "x" don't stick (only when you apply them with right-click menu),grrr
* quick Slideshow" always take the basic ugly theme, not my custom one
* I'm sure there are plenty more ;-)
b

I've just discovered the same as the first point. I'm not sure what the difference is, but I have some photos taken with the same camera but imported at different times, and when it should show in order of capture time, it shows some from Dec 2006 first, then all the rest from May 2006 through to Jan 2007. I've checked the metadata and they are all correct. This is viewing with the folder selected.
PS. With the photos all being from the same camera and using sequential numbering, if I select to sort by filename they display in the correct order.

Similar Messages

Bug in Lightroom 3 - Folder Browsing Selecting Incorrect Text Case

I seem to have stumbled upon a bug in Lightroom 3. I was at first wondering why, when I had Auto Import enabled, no images were appearing in the Lightroom Catalog, even though they were being copied to the _Inbox folder which I created on my QNAP NAS to contain them. However, after the import had finished, I would Sync the folder and there they were.
This was very confusing until today, when I noticed a seemingly identical folder in the Folder dialog shown in the first image. This one *was* receiving the Auto-Imported files as well, except that this one was updating the Lightroom catalog correctly.
What is the difference between them? The second (working) Auto Import folder has the folder 'files' in lower case. This causes Lightroom to see them as different. Presumably this is for Unix support. This is logical. The QNAP NAS device is Linux based after all.
However, when I tried to correct the folder path entry in the auto-import dialog, it displays the 'files' folder in the wrong case (lower) even though both the QNAP folder browser and Windows Explorer display it with initcaps as 'Files'. See other images below demonstrating this.
So I'm stuck. As the Lightroom Auto-Import folder browser displays the folder in the wrong case, Lightroom will always see this folder as two different folders, even though they're the same. I can't rename the folder in lower case, or I risk losing all the Lightroom edits I've carried out against thousands of images in the folder named as 'Files'. Anyway, I *WANT* it named in upper case - this is an Adobe bug, not a QNAP or Windows bug.
See that Windows sees the folder name with initial capital:
See that the QNAP file browser sees the folder name with an initial capital:
See that the QNAP share manager sees the shared folder in upper case:
See that the Adobe Browser sees it in lower case for some inexplicable reason:

Thanks for your post and sorry you're also experience this two-folders-in-LR but only-one-at-the-Finder-level problem.
It looks like I've finally solved this problem, but I suspect I did so the hard way ... if I even understand where in the process things were fixed. As previously posted, when I tried to "move" one folder in LR into the other, LR got confused and deleted the entire contents of one of them! This was the existing one I had been using. Thousands of photos gone! I searched the hard drive and even used disk recovery software but, no, they had vanished. I luckily retrieved these photos from a backup drive, so that's good, but it makes one nervous to fiddle around with this particular problem.
Anyway, BEFORE I imported the new photos from the back-up drive, I first deleted LR prefs and in the process stumbled upon old LR prefs from LR2 and LR3 Beta. Cleaned them all out -- including LR prefs -- and wondered if that had anything to do with the problem. Then rather than Import>Copy the photos, I worked at the Finder level and copied them into position in the <2010> folder, retaining the month and date folder structure. This is at the Finder level. Then in LR, I used Import>Add and the photos properly were added to the existing <2010> folder (the newer of the two that was still there after the disaster ... the new one that LR is intent on importing into). It all works now.
Hope I've written that so you can follow along. Don't know if that will help you in your situation. If you have questions, please let me know.
Good luck, but don't work without a backup, OK?
Best,
Bradley

Rather significant BUG in Lightroom 3.0-3.2

Ok, I have found a really annoying bug in Lightroom. It was not there in 2.0, but is in 3.0 and 3.2. (I use the MAC version)
When in the library module, if you select a number of images and switch to the survey view. You cannot mark individual images as rejected. I have tried the following.
1. Highlight an image and hit X and ALL images are marked rejected.
2. Zoom in on an image and use arrow keys to switch between images and mark X, ALL images are rejected.
3. Actually click on an individual rejected flag under a single image, and again. All images in the survey view are marked as rejected.
Other instances of this bug:
-You can click on a rating on any individual image and it works fine, however if you hit the number of the rating, (4 for instance), then ALL images are ranked as four stars.
-If you either click on the color rating or hit 6-0, then ALL images are flagged with a color.
This bug effectively ruins survey mode. In previous versions survey mode was a great way to pull up images that are similar and to go through them, if you wanted to reject one, you would hit X and only that image was rejected... Now, there is no good way to rank and flag images in survey mode... The ONLY way it works is to click on an individual dot under an image to rate, but don't hit the number, or it will apply to all selected.
I can see it doing this if you are in the normal Grid or Loupe view, then it should apply to all selected, but survey mode should not behave this way. Please go back to the way it was in previous versions.
Thanks

In previous versions activating Auto Sync required the use of a modifier key and even then was only available in Develop module. However, following representations it was added to the Library module. A switch was added to the Synchronize button and an enabling command added to the Metadata menu. These so called improvements were intended to make the feature more discoverable and flexible. Unfortunately, they also make it more easier to screw up multiple images whilst leaving the wondering what they did wrong.

Bug in Lightroom 3 Develop window?

When working on a JPG image in the main Develop window the image displays fine until I make an adjustment on the right hand tool pane.
As soon as I move one of the sliders the image turns jagged and blocky - only correctable by viewing 100% and back again (clicking to magnify and zoom back out again). The problem re-occurs every time you make another adjustment.
I'm using an Intel 2.8GHz iMac on OS X 10.5.8 with 4GB RAM. Lightroom 2 never had this problem so it must be something in my LR3 upgrade.
Has anyone else experienced this problem too? Any suggestions as to what might be the cause appreciated.
Thanks,
Nathan

I have done a fresh install of Lightroom 3.0 on a "new" PC. I use a dual display (1600x1200 + 1280*1024)
Same bug !
I have made Snapshot's of my lightroom.
No bug (picture)
With bug (picture)
These files (2 JPG's) in one Zip archive

Bug with Lightroom 4? - Big problem in the keyword list!!

Hello guys,
I am Rafael Rojas, a nature and landscape photographer. This is my first post, trigered by a quite bothering problem I am having with my LR...So hello everybody!
I upgraded to LR 4 a week ago. Today I realized many of the keywords I have installed in Lightroom do not appear on the keyword list (basically all keywords after the letter S). Moreover, half of the keywords which appear on the list are not editable: that is, I cannot assign them to the selected image (by clicking on the left box), or I cannot double click them or right click them to get the Edit panel. All the rest of keywords (those which appear on the list on top), can be edited and there is no problem.
When I export the keywords as a .txt file (in metadata, export keywords) I can see that all the keywords are there. When I try to write some of them on the box LR recognize them and adds them automatically. However, I just cannot see them on my keyword list or just cannot edit them.
The reason I want to edit the keywords is because many of them got desactivated while upgrading (something more people have reported). Right now, I cannot send my images to my stock galleries, since many of my important keywords are not active, and I just cannot edit them...
Can you help me please?
thanks so much!!
rafael

Well, 64 bits.
And yes, it seems when I erase one keyword, the list "shows" one more below...so it seems the problem is related to a certain limit in number.
That would be still a problem I could live with, the big problem tough is that many of the keywords got "deactivated" alone by Lightroom (see problem here described http://www.backyardsilver.com/2012/02/strange-behavior-with-capitalized-keywords/) and that means I NEED to edit some keywords which are really important and which are not active. Otherwise, when I export the images those keywords are not embedded...
Any thoughts?
Rafa

Figured out a Bug with Lightroom 2

Now just how to get it to Adobe so they can fix it.
Okay, I used to have a problem with the first version of 2.0 where I would assign color labels to pictures that would be B&W, special tweaks, etc. When I would edit in photoshop, then save back to lightroom, they would not retain the color label. This has been fixed in 2.1. Today while editing, I would be going back in forth all day long and all of a sudden it happened. My edited file was not in my color category. Finally after about 5-6 times, I realized what I was doing. When in photoshop, I would run certain actions for certain color effects. If I did not like the particular action, I would hit F12 to revert back to the original. After finding the effect I wanted, I would save back to lightroom. I guess for whatever reason, when you hit revert in Photoshop, it strips the color label info. Seems kinda weird. Anyone have any thought on this?
Thanks,
Toby

Hi Jazzey ,
were you able to get your data . I apparently have a similar problem a really need the data in my computer . Let me know how things went with you and whether you were able to solve the problem. That would be a great help to me as I am clueless of how to proceed. Thanks in advance.

Serious bug in Lightroom printing

I was wanting to spread a panorama print over two pages, and because the printer does a larger margin on the bottom of the page, I needed to flip the image to have its join (halfway) on the top of each printed page (bear with me!). So, to do this, I flipped the image along vertical and horizontal axis, and dragged it so that on one printed page it would print the left side of the image, and on the other printed page, it would print the right side of the image. The "left" side is the flipped image. I have the "zoom to fill" option selected (as I want it to fill the available vertical height), "rotate to fit" off, as I don't want it rotated or fitted.
So, in the Print view, I have a resulting display that is showing me a flipped version of my panorama, with just a half of it visible, and a non-flipped version (the original) with its half displaying in the area LR defines as the printable crop on each page. I've repositioned the photo so that I see which parts I need to print on each page.
When you go to print the flipped image, despite it showing correctly on the screen, it doesn't print what I see on the screen, but rather it prints the other end of the image that is cropped off the display'd print area!
I tried making a "real" (not virtual) copy, same problem.
I tried printing to a PDF and also having LR directly print to a JPEG, and had the same result.
I ended up having to take the image into photoshop and save a copy of the pano, crop it to the half of the image I wanted to print, and bring that back into LR and print it - I had still flipped it in LR to print it, but as I'm printing "the whole image" now, it printed fine.
So, there is something really broken in the LR printing, I don't know if it is the display crop of LR that is not being applied when you print in ANY situation, or if the display crop of the printed area is not being applied properly only when an image is flipped horizontally.
Thanks
William
ps: I can' provide screen shots if the description is too convoluted!

Because you appear to have an urgency with your problem the best course of action I can recommend is to file a TAR with support with your test case and ask for a fix to your problem.
Thanks -- Jeff

Edit Date bug in Lightroom 5?

When I create a smart collection with "Edit Date is Today" in LR5, I get my entire library as a result. The same in LR4 returns the expected results.
Is this broken in LR5?

I described briefly in my first post, but to recap:
Use AnyFilter (plugin):
I just tried it - edit dates are logged as numerical values (in seconds), but you may be able to glean something from it.
In my case, it hangs before finishing the whole catalog - still, you only need so many photos to discern a pattern..
Rob

BUG! lightroom 3.4.1 Adjustment Brush Doesn't Show It's "Button" Anymore

Adjustment Brush Doesn't Show It's "Button" Anymore:
I installed the update for 3.4.1 and warm re-booted my computer.
The button that you saw after painting (releasing the mouse button), is no longer there.
There is nothing to hover over to see what area you painted and if you Close the brush, and reopen it, the button does not appear.
HALP!

Disregard my second message about not understanding your email reply.
I thought I had to hit "H" to see a link -on the email- to confirm my registration.
I didn't realize it was your answer.
Since I had just installed my 3.4.1 update and the default on my installed version of LR, and since my 'pins' have never been hidden, the 3.4.1 default of hiding the pins was a problem and is likely to fool a lot of users that hadn't read about hiding those pins yet. Shouldn't the installation of -any- new version, pick up the defaults currently in LR? That is an issue.
We're good now.
Thanks for the response.
Michael

Still no fix for two annoying Lightroom 5 bugs

I'm very disappointed that Adobe still hasn't fixed two of the most annoying bugs in Lightroom 5. The first is the issue with full screen mode. Unpredictably, the screen will occasionally become trapped in full screen. The only way I know to escape is to quit the software, restart and hit Shift F. The second, even more annoying issue is that, when moving from image to image or going to Loupe view, images will often open blurred. This can usually be fixed by moving back and forth between images.
I have these bugs on a Macbook Pro Retina and an iMac running Maverick and on a Mac Pro running Lion. They occur with Nikon and Fuji JPEGs and RAW files.

I'm encountering the very same issues on Windows 7 x64 with Canon and Sony RAW files. So it looks like a general LR problem.
I have a second monitor plugged to my notebook and when the screen turns off after the inactivity period, the secondary LR screen is moved to the primary monitor with no possibility to move it back, even if the second monitor is turned back on.

Lightroom bug with GPS in raw files with XMP

I'm quite sure I've stumbled upon a bug in Lightroom. I look in my XMP file and I see my GPS info:
38,53,25118N
77,1,90390W
But in lightroom, it loads the coordinates as:
+58° 52' 25.00", -82° 14' 53.00"
Now I was thinking something was just wrong in the XMP file, so I load the same image in Bridge and I see the correct GPS information. So I know it's a problem with Lightroom.
I searched the forums and haven't found anyone else reporting this bug. So now I'm kind of stuck. Can anyone confirm or deny this behavior? I'm processing hundreds of images from my last vacation and I am really stuck here because I can't continue until this is fixed and the chances of it getting fixed any time soon seem pretty slim.

After hours of painfully trying everything imagineable, here is what the problem is:
I downloaded the images to my PC using Downloader Pro (Breeze Systems) and initially viewed them with Bridge. Using a Windows XP in French. Apparently Downloader Pro used a comma instead of a period. Bridge understands it this way, as it's just a separator. However LR does not.
To fix it, I had to delete all my images from the library, then by hand modify each XMP and change the comma to a period. Then reimport into LR. I tested this on a few images and it works. Now I'm off to do the rest of the photos of my trip.
I'll report this to Breeze Systems as well, as I think it actually originates on their end. It'd be nice if LR could still read it like Bridge does. It seems LR is more strict and that's the problem. This could be considered a bug by LR as well since instead of ignoring the GPS coordinates or giving an error message, LR seems to calculate it and ends up being way off. For example, I was shooting in washington and all my photos showed up as being in North Dakota, Canada, South Dakota, etc.

Lightroom 5.2 Heal Brush Bug

Guys -
It appears that there's a bug in Lightroom 5.2, with the introduction of the "feather" parameter which results in images being produced in an earlier version to not render correctly. As far as I can tell, the "default" feather parameter does not match the previously used (uneditable) value. The default value is now 75, which results in my images being completely screwed up, with the healed areas not healing as expected, leaving areas exposed, etc. The only way to fix this, as far as I can tell, is to go to every adjustment point and set it feather value to something different (I've been using 0). For complex edits, this is a real pain.
To be frank, I'm absolutely flabbergasted that this made it through QA and into the production code. Am I missing something?
Added more clarification to "Screwed Up". ;)

To make matters worse, with complex cloning/healing operations it is impossible to select points that are "behind" an area, meaning I have to move areas to get to the other points, then move them back. Awkward, to say the least.

Lightroom 5 can't import to a FIXED drive called A: or B: even if that's where your catalog is

This what I consider a bug for lightroom 5. It simply does not allow you to import to a fixed hard drive called A: or B: even if that is where the catalog was opened from and where all your other photos are stored.
Yes I know why... A: and B: used to be used for floppy drives back in the stone ages... however windows has allowed you to assign them to hard drives for decades now, and as time goes on, you are going to be seeing a lot of computer users who have in fact never heard of a floppy drive and have never even seen a floppy disk.. it's just something they heard about in history class.. if they weren't sleeping.
You will be getting more and more technical support issues when the following scenario happens...
I was running out of room for my data, so I went out and bought me a nice new huge drive... Installed the drive per the instructions and went to 'disk management' to add an additional drive to my system..   It eventually asked me for a drive letter, and A: was at the TOP of this list, so I used that...   then formatted the drive and all was great.. windows reports a fixed drive called A: with a ton of free space... so I moved all my lightroom data to A: and opened the catalog from A: and it started lightroom just fine.. and all my photos are there and this is great!    You can do everything with the hard drive being A: or B: so I'm done messing with it... well a few weeks or months go by, and I've long forgot about the install process and now I have 13 other applications using my A: drive and I finally have a break in my busy schedule so I go out and shoot some photos.. I get back, install my memory card in my computer and prepare to import my files to the hard drive where my catalog is...... but I CAN'T!!! A: and B: do NOT EVER show up in the lightroom list of drives... and WHY NOT??? I can't understand why lightroom can't import to something my operating system is reporting as a FIXED drive.     Now I have all this stuff on my huge drive called A: or B: and it's going to be a huge task to re-assign that drive to another letter because all these other applications will be looking for their stuff on A: or B: Ugh
Ok, so Adobe is trying to save us from ourselves and not allow us to try to import to a tiny disk that could not even hold one of our photos... uh... WHY? Just put A: and B: in the list if the operating system is reporting them and if someone DOES have a floppy drive, called A: or B: and they try to import something to it.... they will just get an error saying it won't fit... problem solved!    What is REALLY ironic is that lightroom WON'T EVEN RUN ON ANY MACHINE WITH A FLOPPY DRIVE IN IT!!!!    You could put a USB floppy drive on your windows 7 or 8 machine... but when you do that... it's NOT necessarily A: or B:... you can make it whatever you want... leaving out A: and B: doesn't help ANYONE at all.
Now, assume this user is in their early 20's... they have never ever seen a floppy disk, and could not buy one if they wanted to... which they don't... they just can't understand why this is happening.. why is my huge drive NOT in the list??? why is it not there? I don't understand this.
It should be noted that this also happens if A: or B: is a network drive as well.    Floppies have been obsolete for a long time, and in fact you haven't been able to buy a new computer with a floppy drive since 2005, and they were completely useless back then.. and B: drive has been useless even longer!
So, what has happened here... is leaving out A: and B: has just been carried over from decades ago when it was probably a good idea... and no one has even looked at changing it.   People do have problems with this though, but it won't be fixed until someone says something... So I'm saying something. fact:    A: and B: are NOT reserved for floppy drives anymore.. they have not been for a very long time fact:    No one will ever plug in a floppy drive ever again.
fact:   Windows has allowed network drive and fixed hard drives to be A: or B: for decades
fact:   You SHOULD be checking the operating system to see if a drive is fixed or removable and what it's capacity is... not making assumptions about the drive configuration
fact:   As time goes on the the more and more people who have never heard of a floppy disk increases, this WILL become more and more of an issue.
fact:   There is no reason to NOT be using A: or B: for network or fixed hard drives... and our software should allow us to do so.
fact: I want my 4TB drive to be B:!   but I have to settle for it being WAY down at T: because I've used all the letters down to S: already... heck my usb 3.0 card reader alone takes up 4 drive letters.. and I'm used to them where they are now.   I also want my RAID box to be a network A: drive.. putting it right there at the top of the list!
I'm settling for other letters, at the moment.. I actually moved my nearly useless DVD burner down the list.. do you all realize even DVD's are becoming obsolete??? why burn a measly 5GB on a DVD that is so fragile and easily scratched... when you can just write files on a 128GB flash drive? (yes there are even 512GB flash drives available now) It's only a matter of time before NO one will have ever heard of or seen a CD, or DVD disc either!

Probably the best place is here http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om . Not sure if it's taking new registrations though.
I'm a little susrpised that it's not possible, and I agree it's a bit silly in 2013, but my guess is it's one of those things that won't change for a while. They've probably played safe, and to be frank, whenever you break such old rules (eg 32 characters, case-sensitive filenames, punctuation in filenames etc) it's only a matter of time before you get bitten by something. I just wouldn't expect Adobe to spend much time on it - it's not as if they've nothing else to work on.
John

Lightroom 5.7 Reports that catalog running out of space. Drive has 185GB free.

I tend to leave Lightroom running in the background for days sometimes, allowing my Windows 7 Pro 64-bit system to sleep. The program is installed on a 240 GB SSD with 139GB free. The catalog is kept on a HDD partition of 230GB, that also contains a recent backup of several photo files, but with 185GB free. Looking through the discussions, I saw a comment that using CrashPlan in auto mode can cause this error message to come up, and I do run it that way. I know there's a problem in Windows with CrashPlan requesting VolumeShadowServices, but the backups are still being made and are accurate, so I haven't spent much time trying to resolve this.
When the catalog message shows up, it goes away and I can continue working. However, I usually stop and restart Lightroom. No change is seen in the space allocation on the hard drives. Is this a bug with Lightroom?

Geoff -
Although you're correct about the LR catalog, changing the backup app (CrashPlan) to no longer backup the catalog defeats at least part of my purpose. As would making it a manual backup. The best backups are those done without any further action needed on my part.
However, I did read a bit more about CrashPlan, and have changed it to not backup currently open files. It will check every hour and see if the file has been updated but is no longer open, and then back it up. This should fix the Volsnap and VSS errors on Win 7.
The question remains as to whether it will keep the LR catalog message from occurring. I am assuming that it's related to backups, but cannot say for sure at this point. I'll leave it open (against ManiacJoe's rec) and see if this still occurs.

Droplet not working correctly in Lightroom 4 Export

Having finally found time to understand how droplets created in Photoshop work I realised I could save a huge amount of time by integrating droplets into my workflow through the Lightroom export dialogue.
I will not regail you with the hassle I had with CS6 creating droplets to start with. My question here is how to get LR4 to export and run the droplet correctly. My export preset is set up to do the following.
Export the selected file (RAW files chosen in my instance) to a subfolder named Processed.
Save those exported files as PSD at full resolution and with -processed added at the end of the file
Run a droplet that I created and placed in the export actions folder on the newly created files.
Import the resultant files back into lightroom
Using some test images I was able to watch as the images were exported and photoshop CS6 ran the action on the files and closed them off. When I checked the images in lightroom however there was no sign of the action having run! I opened the files up in Photoshop to confirm this (The action should have created a number of layers)
I wasted the best part of a morning trying various droplets and droplet settings to no avail. It was only when i went into Bridge, to test the droplet from there, that I suddenly discovered what had happened. The droplet had run and the revised file had been created. Unfortunatley instead of saving the revised PSD file over the original in the subfolder it had in fact saved it back with the RAW files in the original root folder. Of course there was no way of realising this in lightroom unless I decided to sync that folder, which I had no cause to do.
I have gone over the setting in Lightroom and I'm convinced it should do what I am expecting. All the books state that Post processing is carried out after the files have been created so should be carried out on the files in their new location. It apears however that LR4 is carrying out this process DURING export so causing the droplet to save into the original folder location. Not what I want and totally useless to me.
In terms of the droplet and action. The droplet was set to save and close. I did originally have a save command in the action, as instructed in tutorials, but removed it to see if that was causing the problem. Neither option made any difference to the problem.
To me it does seem there is a bug in Lightroom 4 but i have not found anyone else reporting this problem so am I missing something or not interpereting the export functions correctly?

You cannot go back.
Have you tried a reset, restore to address your issue?

BUGS in Lightroom 1.0

Similar Messages

Maybe you are looking for