Another Lightroom 3 bug

Occasionally, I insert a card to import and get the message that LR cannot import because card is unreadable. I try to read the images from Bridge, and there they are, all images can be opened without any drama. Images can also be read and downloaded if I use Finder (Mac OS X), or any other software for that matter. Used to happen at least once a week on LR3, but never on the previous versions.
I thought this bug was fixed in LR3.2, but today it just happened again. Very annoying and frustrating. Eventually, after several tries, Lr will budge and import the photos from the card.
Also worried because Lr3 has been corrupting images for me when converting to DNG.

EricKeithScott wrote:
I again suggest you get a life and do something with your family. I do not use LR for any fun. I use it for work and only work.
This is a pretty funny group of sentences.
Yes, I use LR at work (I do wind energy research and use it for engineering photography):
I use LR at home for family pictures:
I use LR for pictures I take while on vacation with my family:
And I use LR for pictures of my own fun with my own hobbies, such as R/C aircraft:
And planetary photography:
Among others...
I'm sorry you aren't having any fun with photography.

Similar Messages

BT Cloud, another curious bug

Another curious bug to add the the BT Cloud chamber of horrors.
BT Cloud somehow decided on the Web Interface that my main device contained two separate top levels, 'D' and 'd'.
Most things I had backed up from my D drive showed up under 'D', with just a few under 'd'.
On the PC client, everything showed up under 'd'.
The extra 'd' was a bit irritating on the web interface, and none of the files saved in it was significant, and so I decided to delete it in the web interface.
Result:
1: 'd' correctly deleted in the web interface (they seem to have fixed the bug where you couldn't delete folders in the web interface)
2: 'd' deleted from what shows up in the PC client. As the PC client never showed anything under 'D' but everything under 'd', when I look at my main device it now shows 'This folder does not contain any files.'
3: All the files still showing up correctly under 'D' on the web interface
4: PC client still knows what it is trying to back up from the D drive:
- the auto-backup folders show up correctly when I look in 'Add to Backup' (usability bug: 'Add to Backup' doesn't admit to what path it thinks they are from)
- it correctly backs up new files added to these auto-backup folders
- it still knows about the backed up files if I look under 'All Files'; and remembers correctly what directory they came from. (usability bug: but not easy for the user to see what directory they came from)
5: No files actually deleted from my PC.
I don't trust BT Cloud at all yet, so I am only experimenting and waiting till it is ready as a backup solution. Meanwhile, all my files are backed up elsewhere. I didn't trust BT Cloud not to make an even bigger silly and delete lots of my original files; I trust it even slightly less now.
BT Cloud still has the makings of something that might be useful eventually, so I still keep hoping and trying ....

Hi Sjtp,
Thanks for the feedback. I will make sure the cloud team get this useful info.
Cheers
Sean
BTCare Community Manager
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry that we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

ANOTHER Lightroom 5 Bug??

This is another bug that I had during the Beta which I hoped would have been solved. It is difficult to reproduce but happens frequent enough to be a real pain.
Using the adjustment brush or gradient tool, I can apply settings to photos. Then when I switch to a new photo, I can select the brush or gradient, but I cannot apply it to the photo. Nothing happens when I paint or drag gradients. I can select and deselct the tool as many times as I want and even switch between tools. Only way to get it working again is to restart Lightroom.

True.... except that in the Beta it was more the gradient tool causing this issue and now it is mostly the adjustment brush. I am not ruling out the fact that it can be something on my side... Could be a plugin or something causing this too. Once I can replicate the problem I will post the steps - but for now I am just keeping an ear out to see if anyone else have this issue.

Lightroom bug: activation state of brush adjustment lost

Since the introduction of Lightroom 2 through 2.4 there has been a bug in the operation of the local brush adjustment. It's as follows.
Start or edit a local brush adjustment so that the little activation bullet (radio like button) appears. Toggle before/after by typing . When returning the after view (after/before/after) the local brush bullet is no longer active, thus forcing me to reselect it. The behavior is especially irritating when I'm zoomed in so the active brush indicator not view (scrolled off). I am then required to zoom out so I can find it and click to reactivate it, then zoom in to continue my editing. I see no reason why the active brush should not remain active between toggling between after/before/after with "\". I prefer to do my before/after viewing with the full frame rather than one of the split pane views because I want to see as much of the image as possible. I've reported this issue directly to Adobe a few times with no response or fix.
p.s. while I'm at it (I'll repost in feature requests). The location of the brush adjustment indicator corresponds to where the mouse down first occurred. I should be able to move the indicator to where it's more convenient after placing it, regardless of where the brush strokes occur. For some images I have a number of local adjustments in the same region. They become crowded, making it hard to distinguish one brush indicator from another.

Hi
Good point, but does not work on all density settings, noda.

Lightroom Bug: with GoPro Hero4 Silver Lens Profile, crop settings do not sync properly in Lightroom 5.7.1 when Constrain To Warp is checked

I was having a bit of difficultly in getting crop settings to properly sync in Lightroom 5.7.1 (running on OS X 10.10.1) when Constrain to Warp was checked. This appears to be a bug in the latest version(s) of Lightroom that include(s) the GoPro Hero4 Silver Lens Profile settings. I'm working with a lot of files from a GoPro Hero4 Silver camera shot in the time-lapse / interval timer mode. All of them are horizontal with the same resolution (and dimensions). I've tried various sequences to get this to work in terms of using Auto-Sync, resetting the settings on all images except one and then copy and pasting settings, etc, though the crop is not properly syncing regardless of what I do.
Here's are instructions of how to duplicate this issue (there are some extra details/steps here, though this should be clear enough to produce the same result):
     1. in the Develop settings for a single selected image, go to Lens Corrections, click to Enable Profile Corrections (in the Profile tab), and then pick the GoPro Hero4 Silver Edition (Adobe Profile) if it is not automatically chosen for you (if you are using files from a Hero4 Silver camera). After this, click on the Manual tab, and set the Scale setting to 76. (as you will see, you now have the full horizontal width of the image that was getting cropped off, though you do see white around the edges that have been warped/shaped to correct the fisheye distortion)
     2. Press the R key (or click on the Crop Overlay tool just below the histogram). Change the Aspect option to Custom. Click to unlock the lock next to it (this seems to re-lock after setting to custom even if it was locked before). Place a checkmark next to the Constrain To Warp option. (At this point, you'll see the image gets cropped back to an approximately 4:3 ratio and the full horizontal width is not included in the cropped area) Click the upper right most corner of the crop area and drag as much to the right and top as it lets you go. Do the same for the lower left corner, dragging it as far to the bottom left as you can go. (Now, you will see that your cropped area is the maximum rectangular width and height you can select without getting any of the excessive white area) Click the Close button (or press R again) to leave the crop overlay tool.
     3. Press G to go back to the grid of images. Make sure the image you just adjusted the settings for is the only one selected. Right click on it, go to Develop Settings, and click Copy Settings. Click Check All on the window that appears and then click Copy.
     4. De-select the image you were working on. Select multiple other images in the grid. Right click on one of these, go to Develop Settings, and click Paste Settings. (at this point, you will see their aspect ratio has become more panoramic than the 4:3 aspect ratio the images previously were)
     5. De-select these images. Select one of these image, and then press D to go to the Develop settings for this image. Press R to go to the Crop Overlay tool. Here you will see the bug where the crop was not properly copied over from the first image. The selected area is smaller than the full width and height available to crop.
It seems that the bug is that Lightroom is only copying the aspect ratio (and the other settings), but not the actual crop selection.
I just thought of a workaround that I've tested and can confirm works (and will also work in a slightly different workflow than above). In step 1 above, for the Model (and Profile), manually pick the "GoPro Hero4 Black Edition" or the "GoPro Hero3-Silver Edition". If using the "Hero3-Silver" setting, the Scale (also in step 1 above) need only be set to 79 (rather than 76 for the Hero4 profiles). By picking one of these Lens Profiles and doing everything else the same as the other steps above, the crop settings do copy and paste properly. This does also appear to work properly when selecting the "GoPro Hero3-White Edition" Lens Profile, with a Scale setting of 75, which yields a slightly more rectilinear image (with a wider aspect ratio -- almost, but not quite 16:9).
While this isn't too big of deal as it does work by picking one of the other lens profiles (and the Hero4 Black Edition profile appears to make the same exact correction to the image), this was incredibly frustrating last night to notice that some files had the proper horizontal field of view / crop and others didn't, and other users may experience this or not even notice their crop is not copied properly (as, depending on one's composition and image, it's not extremely obvious with such a wide view).
I hope this discovery helps someone else and provides feedback for Adobe to correct this issue in the next version of Lightroom 5.
On a separate, additional note for Adobe: Please allow the crop overlay tool to "crop" an image to a size that is larger than the original dimensions of the image. This would allow for one to retain maximum original sharpness in the center of the image when using the Lens Profile tool to correct, or "de-fish" a lens, without having to scale the image down with the Scale option on the Manual tab of the Lens Corrections settings. For example, when I do the above process selecting the Hero3-White Edition profile, my final image dimensions are 3840 by 2257 pixels, reducing the size of the image in the center by 25%. If the tool allowed one to crop/scale a larger image size, and I kept the Scale option of the Lens Corrections settings at 100 rather than 75, my final image dimensions would be 5120 by 3009 pixels (larger than the 4000 by 3000 pixel dimensions of the original image which the tool now limits me to). Yes, the edges would be a little softer but the center would retain the original detail. (this is essentially what the Calculate Optimal Size button found in the Hugin open source software does, when using it on a single image for lens transformations/corrections)

Can you zip up a few of your GoPro images, upload them to dropbox.com and post a share link, here, so others can experiment with them, or do you mean this issue is global to all camera models?

Lightroom bugs with Windows Vista

I'm having difficulties with one of the file navigation controls in LR running under Windows Vista. The control that pops up with the import (choose files) function works fine, but the control that pops up with the add folder or create new library function misbehaves and causes LR to hang.
I've logged a ticket with Adobe, tried all the standard workarounds (run as administrator, re-create preferences etc.), but to no avail. I think it is a bug.
Has anyone experienced this? Any solutions out there?

What I've seen is that if you try to import from a card reader using the LR downloader, you get a list of files on the card and a message saying that they could not be imported. This also apparently damages the LR database because you cannot import even from a folder on the computer until you delete the database and create a new one. It happens in XP compatibility mode for me too. Otherwise, I have had no troubles using LR on my Vista machine. I can import from a card using another program's downloader and then import the folder into LR for editing.

I have a dual monitor setup. When I paste develop settings from one image to another, Lightroom switches the active window.

Strange problem. Lightroom 5.5. Windows 8.1. Dual monitor setup.
I'm processing a large batch of photos. I have Monitor #1 set as my main develop window, with Monitor #2 set only to display a larger version of the image I'm working with. If I copy the develop settings off of one image and try to paste them onto another image, Lightroom will switch from Monitor #1 to Monitor #2 as the main develop window, and will not display anything on Monitor #1.
If I then try to paste develop settings onto another image on Monitor #2, LR will then display a larger version of the image I'm working with on Monitor #1.
To work the way I want to, I have to continually drag my develop window back to Monitor #1 every time I try to paste develop settings onto a new image. How can I make this stop?

I just tried what I think you’re saying you’re doing and I don’t have the problem with LR 5.5 on Windows 7 SP 2.
Does the same thing happen whether you use the key shortcuts vs the Settings / Copy/Paste options on the menu?
I ask this because if you’re using the keyboard shortcuts, maybe you have some display-manager program that has bound itself to the Ctrl-Shift-V (paste settings) to the function of move-to-other-monitor which would do at least part of what you describe.
You can also test this theory by doing a Ctrl-Shift-V with an application other than LR as the active window and see if it moves. I suppose Ctrl-Shift-C might also play into it so try both of these hot-key combinations with a program that isn’t LR.
If none of this sheds any light on the situation, then give a more detailed description of the low-level functions you’re doing to accomplish the copy-paste of settings, so someone else could replicate the steps exactly.
Specific detailed steps, like:
left-click on source photo’s thumbnail in the filmstrip
press Ctrl-Shift-C to copy the settings
click Check-None
enable the white-balance and calibration checkboxes
click Ok
left-click on destination photo's thumbnail in the filmstrip
click on Settings / Paste Settings in LR’s menus to paste the settings to the selected photo

Weird Lightroom bug

This bug has existed for a number of Lightroom versions, starting from 1.4. After working with a lot of images and using the shortcut menu extensively (right-click menu), right-clicking will suddenly stop working, and so will many shortcut keys. For some of the shortcut keys, bizarre behavior occurs. For example, CTRL+Z will cause a particular preset to be applied, rather than performing an undo.
The only "fix" for this problem is to restart Lightroom. Any ideas on what's going on?

Lightroom RC3.5 is what brought me here. Wanted to see if the issue had been addressed. It's not mentioned but I guess I'll give it a try.
As far how to reproduce I think the original poster nailed it. Just work in LR for awhile and it starts to do exactly what was posted. Closing LR and restarting does fix it until it starts acting up again.

Lightroom bugs: full screen mode and import

I'm considering buying Lightroom, it's quite impressive for a v1.0. But there are some troubling bugs I've run into on my 2nd or 3rd day of use.
Platform: Vista Ultimate, Lightroom 1.0, P4 2.8ghz, 1.5 GB mem + 2 GB ReadyBoost.
- Full screen mode is broken? I switched into full screen mode, and then back into normal mode. But now when I minimize the app and alt tab or click back into it, it's back in full screen mode. So I put it back into normal mode, but it goes back to full screen the next time I return to it. Very annoying. It's not just when I minimize it. If I change window focus *at all*, it sets itself to full screen mode.
- Import from camera doesn't work. When I attached my Canon 20d and selected Import from 20d, it said "Could not find files" or something. I had to import through Canon EOS Viewer.
Both of these features are a pretty basic part of workflow, so I'm surprised they're broken.

There are know issues with Vista which isn't supported yet. Also import has some issues to be resolved.
The read me has some of this noted.

Have i found another big bug? from 2nd monitor profile bug to Exp panel bug

Well 2.0.1 is out and i was hoping for a fix for the second monitor color profile bug ... but no, not yet.
But guess what .. i think i have found another little treat.
Ok here we go, click on the Exposure, Recovery or Black Point sliders (but don't move them), notice anything?
On my system as soon as you click, the shadows block up. Take your finger of the button and they shadows go back to normal.
Next .. click and slide, when the button is down... blocked shadows again, release the button and shadows open up.
This also happens in the White balance panel.
Also we still have the tint slider problem, click it and it jumps the tint.
The exposure and white balance problem only happens in full screen mode.
It happens on my second monitor when running in mirror or alternate (or any other of the settings)
If i press the F key and go full screen on my macbook pro, the same thing happens on the macbook's screen.
Press the Z key to zoom to 100% and the problem goes away on either screen.
But get this ..... click any of the sliders in the Enhance panel before going to the Exposure panel (you don't have to move them), then go back to the exposure panel and...EVERYTHING FINE.....whaaaaaaat.
So now i have a second monitor with dodgy colors and an exposure panel glitch.
Thought this was an update!!!
Anyone else got this problem?
Oh, just to add, i have deleted pref files, deleted aperture altogether, re-installed 2.0 and 2.0.1, rebuilt library, tried on another library...all with no joy.
Sigh
Mike
rebui

System is macbook pro 2.4 4gb ram, formac 2010 second monitor.
Leopard 10.5.2
pro app 4.5
Seems that i am not the only one with this problem, not many out there... just a few.
Couple of links
http://forums.dpreview.com/forums/readflat.asp?forum=1017&thread=27043649
http://www.flickr.com/groups/aperture_users/discuss/72157604042773520/
Mike

Another Minor Bug in SQLDev

I discovered another minor irritant in sqlDeveloper.
Steps to recreate the bug:
1) Create table t ( n1 number); (table created)
2) insert into t values (1); Commit; (Record Committed)
3) Goto Explorer on the left pane and click on the table to view the table t on the right (table will be displayed with a single column); Click on the data tab to view the data.
4) Alter table t add (n2 binary_float); (Table modified)
5) insert into t values (10, 10); Commit; (record committed)
6) click on refresh button to view the data.
You would expect to see two columns and two rows of record. But you would see only one column and two rows of data.
7) click on columns tab and click on the refresh button. (Two columns are displayed).
8) now go back to data tab; you would still see only ONE column and two records. Clicking on refresh does not display two columns
Only alternative is to close the tab and click on the table t again. You can now view the records with two columns
Version: 2.1.1.64
OS: Linux
Database: 11g
-- rsrini

I am having a similar problem in 2.1.063.10. When I put in a filter I need to use the enter key and not the refresh button. Nothing happens to the data grid when I hit refresh button. When I enter a filter that causes no data to display, then blank out the filter and hit the refresh button, no data is displayed in the grid. Then I hit enter and the data grid is refreshed.

IMovie 09 voiceovers silent - another iMovie09 bug

Hello,
in addition to all the iMovie bugs reported, I now observe from time to time, that iMovie changes volume of the latest voiceovers on its own. I did the following:
1. I changed some things in my iMovie project. Especially I added some voiceovers.
2. I closed iMovie
3. I made a backup copy to another drive
4. I re-opened iMovie again
Result: Some voiceovers are randomly very very silent and the volume an not be changed anymore.
5. I check my backup copy on another Mac: Same result.
What happened? Who can support me?
Apple works always on new fancy stuff, but seems to forget the simple things.
Jürgen

Sorry to post again, but I can't find any other post about this problem. Have you found a solution for this. I have the same problem. Can't change the volume of voiceovers in some projects...... but had no problem doing it before.

Another keyboard bug

Hi,
While the "dead key" bug is still not fixed in LR2 (although already
reported in LR 1 and LR2 beta), there's another problem with the Tab
key.
I use the Alt-Tab combo under Windows to switch from an application to
another. If I use Alt-Tab to switch from LR to another app, LR ignores
the Alt key - which is currently depressed - and just see the Tab key,
and therefore it modifies the user interface layout accordingly (as if I
had hit the Tab key only) just before Windows switches to the other
application I have selected. Irritating.
It's another sign that LR installs its own keyboard handler, which is
far from being perfect (at least under Windows).
But the "dead key" bug is from far more annoying and I don't understand
why they are unable to fix this - but well, it's just affecting those
not having a US keyboard layout, so maybe it's not a problem for Adobe?
We are just paying more for less quality :-( .
Patrick
PS: For those who are not aware of it: The "dead key" bug makes
impossible to enter any character that requires a dead key to be
produced. For example, to enter " ê " on a french keyboard, you need to
hit " ^ " and then " e ". In LR, this yields " ^^e " instead of " ê ".
Same problem with other european keyboard layouts and other special
characters. So you have to use the old Alt + Code trick in order to
enter those characters (and you also have to remember these codes - very
modern UI, indeed).
I find surprising that a software that has reached this high level of
quality is still suffering from such a stupid bug that has been reported
since a very long time.

"*Tom*" <[email protected]> a écrit dans le message de news: [email protected].. > Hi Patrick, > > on my comp (Win XP Prof + SP2; PS CS3 + 10.0.1 + CR 4.5) in no problem > with Alt + Tab. It switches corectly to other apps. Hi Tom, I didn't say that it didn't switch to the other app. But before it does, LR acts as if I had hit the Tab key and therefore closes or opens the right and left panels. -- Patrick

Solo Track : another weird bug ?

Year after year, I find more and more annoying bugs in Logic Pro. This time it's the Solo Track button that act weird :
Take track with regions.
Activate the Solo button on that track.
Move a region from another track (that is not in Solo) to the Solo'ed track : this region WON'T BE PLAYED !!!
You NEED to un-Solo and re-Solo the track in order to include the new region...

I think I figured this one out. If you are soloing the regions, and you move a region that isn't soloed onto the track, that region will not become soloed. If you solo the track without any regions selected, then when you move a region from an unsoloed track, it activates....
I think. Don't have Logic in front of me right now to test.

Another Scrabble Bug

When the iPod is connected to an external speaker, For example, a Bose external amplifier/speaker for the iPod, switching music "off" actually turns the music off. This is good.
Um, not so with EA Scrabble for the iPod. When it plays its (annoying) background sounds, and one selects "off", it says, "uh uh, let me annoy you more fully" and turns the music back on.

I think i've found another bug with setBundledExceptionMode(true), this time regarding dates.
If you are using the oracle.jbo.format.DefaultDateFormatter then even with setBundledExceptionMode(true), a java.text.ParseException gets thrown IMMEDIATELY if the inputed date format is incorrect.
I got around this problem by subclassing oracle.jbo.format.DefaultDateFormatter and catching the java.text.ParseExceptionThis is not a DATE only issue. Formatting service as a whole currently sits outside of Bc4J runtime apis and thus "does not" honor Bc4J settings like exception mode etc.
JSPs need to "wrap" such exceptions and honor bundling of exceptions by going thru' the rest of the attributes. I'd log a bug for JSP code=gen for this.

Another Lightroom 3 bug

Similar Messages

Maybe you are looking for