Lightroom 4.3 import bug

Why is an image imported into Lightroom 4.3 significantly lighter than the same image displayed in Windows Photo Viewer at the same time and on the same screen?
This basic problem also applies when using an external editor such as Elements 11 where the image is returned much lighter than what appeared in Elements.

Thanks for your reply.
I take your point about windows Photo Viewer but what about Elements 11? Also if the two versions of the image were displayed on the same monitor at the same time would that not invalidate the need for screen calibration?
As perhaps a better demonstration of the problem, if I export an image to a jpg with "add to this catalog" checked the added jpg is returned significantly lighter.

Similar Messages

Lightroom 1.3 Import Bug

I have a Nikon D200 and typically shoot in RAW + JPEG mode. I upgraded to 1.3 on my laptop a few days ago, and have just done my first import. I was puzzled by only seeing JPEG images in the catalog after doing an import. I deleted them all and tried again, confirming that yes, the CF card had both JPEG and RAW files on it. The import again only showed me the JPEG files. I did the import a third time, this time *unchecking* the box for "Don't Re-Import Suspected Duplicates". Surprise, it worked: I can see both the JPEG and RAW images (I've always had the "Treat JPEG files next to raw files as separate photos" option checked off).
I've always had the "Don't Re-Import Suspected Duplicates" box checked and it's never caused this problem in previous versions.

Hi Melissa. I'm using a Delkin ExpressCard 54 CompactFlash adapter with a Delkin 8 GB UDMA memory card in a Dell XPS M1330. My camera is a Nikon D200 with all the default settings. I'm shooting RAW + JPEG BASIC.
The path to my images on the CF looks like this under Vista:
F:\DCIM\103ND200
I made the mistake of doing a Lighroom import, then deleting the folder on the CF card before confirming that Lightroom had all the images - Lightroom has never mis-imported on me before, but since updating to 1.3 I'm seeing this frequently. Luckily I ran some memory card "photo unerase" software and was able to get back all my NEF images. It was a sinking feeling though thinking I'd lost them.
I've since done another import, which only copied over the JPEG files. I deleted all the images off the hard drive using Lightroom, then did another import, and without changing any of the settings it grabbed the JPEG + NEF files this time. My next import got both file types as well, though this time I opened the preview portion. Not sure if that had an impact, seeing the NEF files being selected. When the files didn't get imported it was an auto-import pop-up...when they DID get imported it was from a FILE > IMPORT FROM DEVICE. Not sure if that has any bearing.
Let me know if you need any other information. I hope this can get nailed down soon. I'd so more experimenting myself, but I'm on vacation and really need to get down to processing my images. ;-)

I believe I found an import bug in LR 5.4

I believe I've uncovered an import bug in Lightroom 5.4 under Mavericks. I noticed a folder with 19 photos and videos, but LR was only showing 18. So I tried synchronizing the folder, and still only 18 were found. So, in the import screen I unchecked "Don't import suspected duplicates", and it still would not import. So, I removed the folder containing the photos from LR, then re-imported them, and still only 18 photos!
So, the .jpg file listed here will NOT import into LR regardless of my efforts. The mp4 imports just fine. It seems like a bug pertaining to files with the same name but different extensions, or something similar. Here are the file names:
bernie3_blue_baby_shopping_walmart-09-2.mp4 - IMPORTS OK
bernie3_blue_baby_shopping_walmart-09-2.jpg - WILL NOT IMPORT

I’m not sure it’s a bug but rather by design. For example if you do external editing from Lightroom in Photoshop the word Edit is automatically added to the tiff or PSD file with the same name. Simply change the file name for the jpeg and it will import. LR does permit jpeg and raw files with the same name but it requires enabling in the prefs. I assume there is no similar pref setting for videos, as they would always be numbered separately when importing directly from a camera card; so the situation would never usually arise.

Lightroom will not import my photos. It did up to a week ago. I have changed cards and cameras (both worked two weeks ago). I can import the photos to Picasa and iPhoto

Lightroom will not import my photos. It did up to a week ago. I have changed cards and cameras (both worked two weeks ago). I can import the photos to Picasa and iPhoto. I get the following error message:
Some import operations were not performed.
The following files were not imported because they could not be read [followed by a list of the files I wanted to import]
Thumbnails show up. LR just will not import them.
Any idea what is going wrong?

If the Import button is not clickable, that means that Lightroom thinks you have no new photos to import (one possible reason is that they are duplicates)
So, you need to figure out why Lightroom thinks that. The way I would do this is to search your Library module for at least one of the photos, by file name. To do this, you would follow all 4 of these steps in sequence:
Click on All Photographs in the Catalog Panel on the left of the Library Module
Turn off all Filters (Ctrl-L or Cmd-L once or twice)
Expand all stacks: Photo->Stacking->Expand All Stacks
Search for one or more of the photos using the Filter Bar (press backslash), search by File Name

I keep getting the error: "lightroom could not import this catalog because of an unknown error" when trying to import from a catalog?

I have around 400,000 photos of 15 years so given the high number, I organized all my photos into 6 catalogs to avoid potential problems. All the photos and the catalogs are in a 4TB Seagate external hard drive. I use Adobe Lightroom 5 and I use a PC with the latest Windows Office 2013.
I wanted to have a NEW Catalog of all my rated 1 Star+ photos of all the years in a single Catalog. So I created what I called Star+ Catalog and I was told the best option is to import a Catalog at a time and given that there is no means to filter importing only Stared photos, I would import all the photos and then delete all the UnStared photos. I did that for Catalog Year 2014 but at the end gave me the message: "lightroom could not import this catalog because of an unknown error". It actually had imported around 40k photos from about 50k total. I tried again and again and every time I end up with the same thing. I created another new Catalog and stared from scratch and the same ting happened: the ONLY EXACT 40k or so photos were imported and the rest were not!! When I imported Catalog Year 2013 of around 45k photos, it worked perfectly. But when I imported Catalog Year 2012 of 35k photos, the same thing happened!!
I then tried exporting the needed photos to a new Catalog and that worked. But then when I try to import them again from my Master *+ Catalog I get the same error again!!
I also tried creating a new Master *+ Catalog and tried to import the Catalogs of each year into it and the same error happened again!!!
Any advice: 1) on how to solve this? and 2) if there is a better and easier way to create this Master Catalog of All Stared Photos of All my Catalogs?

This is a duplicate thread - see here

How to solve the error: "lightroom could not import this catalog because of an unknown error" when trying to "import from catalog"?

I have around 400,000 photos of 15 years so given the high number, I organized all my photos into 6 catalogs to avoid potential problems. All the photos and the catalogs are in a 4TB Seagate external hard drive. I use Adobe Lightroom 5 and I use a PC with the latest Windows Office 2013.
I wanted to have a NEW Catalog of all my rated 1 Star+ photos of all the years in a single Catalog. So I created what I called Star+ Catalog and I was told the best option is to import a Catalog at a time and given that there is no means to filter importing only Stared photos, I would import all the photos and then delete all the UnStared photos. I did that for Catalog Year 2014 but at the end gave me the message: "lightroom could not import this catalog because of an unknown error". It actually had imported around 40k photos from about 50k total. I tried again and again and every time I end up with the same thing. I created another new Catalog and stared from scratch and the same ting happened: the ONLY EXACT 40k or so photos were imported and the rest were not!! When I imported Catalog Year 2013 of around 45k photos, it worked perfectly. But when I imported Catalog Year 2012 of 35k photos, the same thing happened!!
Any advice: 1) on how to solve this? and 2) if there is a better and easier way to create this Master Catalog of All Stared Photos of All my Catalogs?

OK, my starting point is that LR can happily contain 400000+ photos, and it's a mistake to create a 1 star plus catalogue as you suggest. Instead, I'd recommend you create a master catalogue of all your photos, which you can then query however you want - 2 star, or a certain keyword, or with "xyz" in the title etc.
If you are intent on going that way, you could try a slight change from what you've done so far. Instead of trying to import an entire catalogue and then delete no-star pictures, take the 2014 and 2012 catalogues and select only the 1 star photos. Then do an Export as Catalog for these items, and import the 2014-1star and 2012-1star into your new catalogue. That may get you past the problem images which I suspect are the problem.
If that doesn't work, or if you follow my initial advice, you're going to need to identify the image where the failure occurs. You may have a corrupt image file, and replacing it from your backup may be sufficient to resolve the problem. Alternatively, it may be a corrupt record in the catalogue, and in this case it may be sufficient to remove the image from the catalogue and import it again. You might try selecting everything in the 2014 catalogue and seeing if you can do an Export as Catalog, creating a clean 2014, and deleting 2014's previews folder might also get rid of a potential problem. Something else is to try the Export as Catalog for images 1-40000, then a second Export as Catalog for images 40002-50k.
So a few things you'll need to try, rather than a magic bullet, and a recommendation to change the underlying direction.
John

Lightroom 1.3 Import not automatic for card reader

Lightroom no longer opens Import window when card is connected, as it did with ver 1.2.
Preferences are set to "show import dialogue when card is detected".
When card is inserted in reader, Lightroom starts, but Import dialogue box does not appear.
I can manually open Import from Lightroom and import images.
When I click on "Adobe Photo Downloader" icon in Tray and select "Launch" it will start Lightroom but not Importer and says "no photos were found to import".

I'm seeing the same thing. I actually now have to open my card reader under "Import Photos from Disk" instead of "Import Photos from Device".

Nwrfc 0.0.5 with important bug fix!

I have just pushed version 0.0.5 of the new gem to rubygems.org (you can also access the latest repo at GitHub).
0.0.5 introduces an important bug fix in Table#each. Previously only the first row would continuously be returned. Now you can actually treat a Table like an Enumerable!

To quote Metalink Note 161818.1 (Oracle Server (RDBMS) Releases Support Status Summary)
"Terminology Used in this Article
Patch Set
*Patch sets are cumulative. For example, 10.1.0.4 includes all the fixes in 10.1.0.3 as well as new fixes for 10.1.0.4.* "

Lightroom won't import

i took some photos this morning and lightroom won't import them. i can view them on my sd card but not when i go to import new photos

FAQ: What information should I provide when posting, or What do you need to know to solve my issue?

Why won't Lightroom 4.4 import my Nikon D7000 NEF RAW files?

Why won't Lightroom 4.4 import my Nikon D7000 NEF RAW files?
I even downloaded the latest Adobe DNG converter and converted all the NEF files to DNG then tried to import to lightroom - it didn't even recognise them??? What the...

Keith_Reeder wrote:
It's not a "wrong" error message - it's true, as far as it goes, and it's completely unrealistic to expect error messages to be fully diagnostic - they're a starting point.
Not wrong?
Let us have a look at the error message:
"The following files were not imported because they could not be read"
This clearly gives the user the impression that there is a reading error where you want to copy the files from. Is that the actual error?
No, the actual error is that the file could not be written at the destination.
It is possible that it is not factually wrong because Lightroom first make a failed copying attempt without giving an error message, then still assumes that the files have been copied and tries to import them, and THEN makes a failed import attempt from the destination and gives the error message. But that would never be anyone's first guess when they experience that error message.
A much better error message would be: "The following files were not imported because they could not be copied to the destination folder."

Lightroom could not import this catalog because of an unknown error.

OS 10.5.8
(gb mem
I have recently exported a catalog from my main database (on a mac) with about 700 photos. Including negative files
We opened the catalog on a PC machine in the same version of lightroom. 3.5 camera raw 6.5. The images were given new keywords and then exported as a Catalog including Negative files.
The original catalog has been deleted from the main database on the Mac.
The Catalog with the new keywords saved across the network to the Mac.
Permissions are open to everyone on the folder the Catalog is in.
When I try and import the catalog in lightroom I can see the thumbnails,
However get this message. I’ve lost many hours trying to get the catalog bak into the main library.
I can open the catalog on its own in Lightroom, just when I try and import the catalog I get the bellow message.
I’ve tried importing saving to a new location
Importing not moving the files
Lightroom could not import this catalog because of an unknown error.
I see others have had similar problems however do not see a clear answer.
Has anybody a solution?
Thanks Patrick

I'm having this issue as well, and honestly I've *never* been able to get "import from catalog" to work. In my case I have a catalog created on my Windows 7 laptop in LR3.5. I've copied it to an external drive, plugged it into my PC running Windows 7 with LR3.5. And I get the "could not import this catalog because of an unknown error" message.
I've confirmed every image in the catalog I am trying to import is accounted for and isn't "missing". There are no duplicate images between the exported catalog and the one I'm trying to import in.
Thoughts?
Neil

IDML Import Bug?

Hi All,
Just wondering if anyone can reproduce what appears to be a CS4/CS5 IDML import bug.
I typed
11
22
33
44
55
(first 3 digits in bold) then tagged "22" as an XML element before exporting an IDML file.
When the IDML file is imported, I get
11
22
33
44
55
(all digits in boldface except for the trailing 2.)
The problem seems to be on the import side of CS4/CS5 since the exported IDML looks okay to me:
<ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/$ID/NormalParagraphStyle">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>11</Content>
 
 </CharacterStyleRange>
 <XMLElement Self="di2i7i6" MarkupTag="XMLTag/Story">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>2</Content>
 </CharacterStyleRange>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 <Content>2</Content>
 </CharacterStyleRange>
 </XMLElement>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 
 <Content>33</Content>
 
 <Content>44</Content>
 
 <Content>55</Content>
 
 </CharacterStyleRange>
</ParagraphStyleRange>
Comments anyone?

Hello Larry,
i am the developer of the IDMLlib http://idmllib.com/ a Java library which is able to read/modify/create IDML.
I have also noticed some strange behavior regarding the importing of IDML, where the order of elements affect the parsing of the IDML in CS4/CS5.
My first thought was, i have created an invalid IDML, but the IDML Relax NG compact schema is very explicit, order doesn´t matter.
The best example i have at hand, which is very easy to reproduce is the TabList. A valid tablist attached to ParagraphStyleRange for example looks like this:
<TabList type="list">
 <ListItem type="record">
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 <Position type="unit">144</Position>
 </ListItem>
</TabList>
If you change this by moving the Position to the top, which is no problem regarding the schema which doesn´t enforce a strict order of the elements:
element Alignment { enum_type, TabStopAlignment_EnumValue }&
element AlignmentCharacter { string_type, xsd:string }&
element Leader { string_type, xsd:string }&
element Position { unit_type, xsd:double })
So if you change this example to this, and reimport the IDML into CS4/CS5 INDD the <Position/> will not be parsed and you wont see a TabList
<TabList type="list">
 <ListItem type="record">
 <Position type="unit">144</Position>
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 </ListItem>
</TabList>
If you export this again as IDML the <Position/> if set to 0
I circumvented this problem by forcing the creation of TabList Items with a constructor that will only allow to create TabListItems with all values present and therefore i can force the order of the created childs. But i think this will not be the only problem where parsing doesn´t do what it is supposed to do.
There has been a posting from a guy complaining about different import results regarding the attribute order of IDML element:
http://forums.adobe.com/thread/637711
I will try to reproduce the behavior you decribed.
Cheers, Andreas

FB3 Beta 3 - another organize imports bug

I'm getting lucky :-) Here is another organize imports bug in
FB3 Beta3...
If you have some simple hierarchy where base class defines
public (or protected) method, and sub class tries to override this
method you will encounter this bug. Let say that base class looks
like this:
package test {
import flash.display.Shape;
public class BaseClass extends Shape {
public function BaseClass() {
public function myMethod():void {
trace("In BaseClass.myMethod()");
and that sub class looks like this
package test {
public class SubClass extends BaseClass {
public function SubClass() {
super();
Now, if you try to override myMethod() from BaseClass and
start typing in subclass something like
override public function m
and use Ctrl+Space, FB will insert appropriate method but it
will also insert errorneous import statement like this:
import test.BaseClass.myMethod;
So you will end up with sub class which looks like following:
package test {
import test.BaseClass.myMethod;
public class SubClass extends BaseClass {
public function SubClass() {
super();
override public function myMethod():void {
Wrong import is correctly marked as error but issuing
"organize import" does not remove it so it must be removed
manually.
Regards,
Damir Murat
PS: Sorry for bad code formatting but there is no option for
inserting in-line code and attach code is a little bit
awkward.

Damir Murat,
Did you already file a bug for this? If not, would you mind
adding it to the public bug base so we can track the issue.
Thanks,
Peter

Address Book contact importing bug

Bug reproducing sequence:
1) Create any smart-group in the Address Book
2) Double-click that group's name to rename it
3) Command-Tab from Address Book leaving it in status waiting to enter new smart-group's name
4) Double click on any .vcf file to import a new contact into Address Book
5) You'd be forwarded back to Address Book with a window offering to confirm contact's import
Bug itself:
Pressing the Add button actually imports a new contact to the Address Book, but does not close this pop-up window. As a result you can create many copies of the same contact before you notice the problem and close this window pressing Cancel button.
Testing the same sequence on MacMini and iMac caused creation of many Unnamed contacts and did not import a new contact at all.

I found the solution in a different post in the community.
You need to go into yr address book on yr MAC. Edit each contact 1 by 1... Cut (Cmd X) and copy (Cmd V) each pix back in... When you synch yr MAC and iPhone again, pix miraculously appear in Contacts and when you get a call from one of them.
Not a fancy solution but works!...

Very Slow preview rendering for lightroom 5 on import

I am seeing very very slow rendering of preview images only when using the import function in lightroom 5. By slow, I mean for a shoot of 60 shots in raw, it could take 30 minutes before I can preview them all in the pane to see which ones I want to actually import. This was not an issue with lightroom 4. It is not an issue when using lightroom. Previews are fast there, even for images I've never pulled up before.
My hardware is a PC, with an intell i7 chip, and 16 gig of memory. My nvidia graphics card has the latest drivers.
I've seen a few others reporting this issue, so I'm trying to log it as a bug. Even though the dial up support text on the adobe lightroom says available 24/7, it now plays a voice recording that says only available m-f.
Brad

I'm having the same problem using Windows 7 (64b). I just took a shoot over the weekend for a significant birthday event. Now I can't load the photos. The work-around doesn't work as the program freezes before I get the chance to select the camera under "files".
I recently upgraded from 3.6 to 5 as I was also noticing a slowdown in the import function. That turned out to be a bad move I think. I also deliberately cleaned up the CF card and removed all my video recordings, as this seems to be reported as part of the problem, but to no avail.
This seems to be a pretty major bug to have in a major release that's been around for a while now, that I'm expected to pay for, and no sign of a resolution to date!
Cam.

Lightroom 4.3 import bug

Similar Messages

Maybe you are looking for