Lightroom color export problem

Hello there. When I export a photo in lightroom it does not export the photo with the same colors as in lightroom. It loses some of the warmth, and that not very helpful. The problem might very well be in lightroom, because when I convert to black and white the picture still has a slight yellow-ish color to it, but when exported it becomes regular black and white. I've tried all the export color settings and that doesn't help. I have also checked if there is a filter that applies when importing, but there don't seem to be. What do you guys think?
I've just exported and open the photo on the left.

You see that the histogram also has a slightly yellow tint?  That's because you have a corrupted monitor profile.  You can confirm it using these instructions: http://members.lightroomqueen.com/Knowledgebase/Article/View/1137/188/how-do-i-change-my-m onitor-profile-to-check-whether-its-corrupted

Similar Messages

  • Lightroom Color Space Problem.

    Hello,
    I am processing my photos in Lightrrom. The histogram in Lightroom looks ok without any clipping, but when i export them to AdobeRGB or sRGB (for web) the photos have clipped shadows or highlights or both. I belive that the problem is that the histogram in lightroom reflect the data of the photo in ProPhoto RGB, and when you export to a narrow color space the clipping happens.
    Is there any way to fix this? I will always have clipping if i export to AdobeRGB or sRGB? What do you do to not have this problem?
    Beside of the clipping problem. The diferece between the histogram in the develop module in Lightroom and the histogram of the exported photo in AdobeRGB or sRGB makes that you don't know what the exported photo will look like, is like working blind. I don't know about you guys, but for me the is a big problem. Well, maybe if you work all in ProPhoto RGB this is a little issue.
    I would appreciate a lot any help or comment that you could give me.
    Thanks, :)
    Marcelo.

    Another thing I sometimes do is to save the development settings (save metadata in metadata menu) to file in LR, and then open the RAW in Camera RAW. In camera RAW the histogram reflects the color space you set, so you can optimize the development settings there. Then I close Camera Raw, which updates the xmp file (or the stuff written into the dng) and in LR do read metadata from file, which will apply the changed settings. This does the trick typically.

  • Photoshop Edits Import into Lightroom, Color/Noise Problems

    Hello!  When I edit photos in Photoshop (CS5), it looks completely different when I save it/re-import it into Lightroom.  The color is usually way off, and there tends to be a significant amount of noise in the imported version.   Tiffs v. Jpegs makes no difference.  I read in another forum that someone else said he only has this problem with his Canon 7D files.  My files are all Canon 7D.  Would that be a Canon problem to solve, or Adobe?  I'm attaching a screenshot of an image I had just saved in Photoshop, and then how it appears when it automatically re-imported back to Lightroom. Thank you for any help you can provide.  It's killing me to work so hard on my images, just to have them look completely different afterwards.
    Thanks, Heather

    Looks like you are applying a preset, have set camera defaults, or have enabled auto-tone. In Develop, all sliders should be at zero for tif files. You probably have a large amount of shadow fill dialed in. Go into your preferences and make sure to uncheck "apply auto tone adjustments" Also reset all default camera adjustments in the same dialog. Then hit reset on the file in develop.

  • Lightroom 4 exporting problem

    Hi,
    I have been using Lightroom for years without any problems.
    Today I had a problem exporting editing images to DNG. Lightroom will only export the original unedited versions to DNG. If I export to JPG I get the edited versions, but it will not export the edited versions to DNG.
    Any help much appreciated.

    Hi Victoria,
    even when I import the exported DNG into a new LR 4.3 catalog, it doesn't pick up the corrections that were made by the original LR 4.3 catalog to the DNG... This is the first time I'm encountering this... The jpegs, tiffs etc do have the corrections applied, just not the DNG... very weird.  So basically I cannot detach my DNG's from the LR 4.3 catalog at the moment...

  • Lightroom jpeg export problem

    I exported about 300 photos into jpegs from Lightroom.  They all showed up very dark in Windows photo viewer.  They look great in lightroom but each photo had an upward arrow on it and the following dialog box came up saying: The metadata for this photo has been changed by another application.  Should Lightroom import sedings from disk or overwrite disk settings with those from the catalog?  What is happening and how do I fix it?

    Same here with LR 5.5. Just generated a few hundred jpegs to further process them in web applications for some online albums. One example is a QNAP NAS that has to generate smaller jpegs. It was working perfectly with LR5.4 and all older versions of LR. But as soon as I exported jpegs from LR 5.5 only grey rescaled images with some "noise" are depicted/generated. Had to go back to LR5.4 and it is now working as expected.
    Adobe: Please do not try to fix something when it is not broken and get a fix for the "fix" ASAP. This is not acceptable for the prices we pay as we are not talking about freeware or shareware where somebody is programming in his free time. Most likely these guys would have already posted a fix for the issue.
    Do your homework and please do it fast!

  • Lightroom (ACR 4) color management problems

    Lightroom (or ACR 4) has some color management problems. When I develop a DNG into Photoshop (sRGB) everything looks great. Then I proof colors for the web (monitor RGB) the reds become oversaturated. I don't see this problem when I develop the same DNG using Bridge (ACR 3).
    Any picture that I develop using LR that looks great in Photoshop, becomes way too red when published on the web.
    Whats going on here?

    I have confirmed this finding using Photoshop CS3 beta - same problem in converting to the web - too red!

  • Lightroom 2 Export Color Issues

    I had been using LR 1.4 without a problem. I don't use LR to print I used Qimage. I am noticing that I cannot get bad colors when exporting to jpg and printing with Qimage.
    I don't have a profile issue, that I know of. Qimage allows printing a CR2 file direct now and the colors are perfect.
    I must be missing something. Since using LR2 the colors on exports are all off.
    Is anyone else experiencing any problems like this?
    David

    Thanks for the feedback. I am not sure if this is fully correct but:
    I tweaked a test CR2 in Qimage and printed directly from Qimage (good colors) After I went to LR2 and played with the same image and printed in LR2 (bad colors), exported to jpg (bad colors) and printed the jpg in Qimage (bad colors) Went back to LR2 and pressed reset in LR2 and stared over from scratch. (output good again - print and export)
    I am not sure but I don't think Qimages RAW changes are non-destructive to the RAW data. I am going to post message in Qimage forums, but MAYBE that messed up the CR2 file until I clicked on Reset.
    Any thought?? I will post my answers from Qimage forum.

  • Lightroom 5.5 jpeg export problem

    I am using jAlbum to create photo albums on the web with images exported with Lightroom. Since I am using Lightroom 5.5 for the export I am get an error message whenever I create an Album with jAlbum which says "inconsistent metadata read from stream". As jAlbum uses Java the Java version may aslo matter. I am using the latest Java update from  Oracle on a Windows 7 Professional x64 machine. With images exported with Lightroom 5.4 there is no problem. Also changing metadata options in Lightroom's export dialog  did not help.
    Is there a known problem with the Lightroom 5.5 export?
    Wolfgang

    Same here with LR 5.5. Just generated a few hundred jpegs to further process them in web applications for some online albums. One example is a QNAP NAS that has to generate smaller jpegs. It was working perfectly with LR5.4 and all older versions of LR. But as soon as I exported jpegs from LR 5.5 only grey rescaled images with some "noise" are depicted/generated. Had to go back to LR5.4 and it is now working as expected.
    Adobe: Please do not try to fix something when it is not broken and get a fix for the "fix" ASAP. This is not acceptable for the prices we pay as we are not talking about freeware or shareware where somebody is programming in his free time. Most likely these guys would have already posted a fix for the issue.
    Do your homework and please do it fast!

  • Lightroom 4.1 export problem

    Lightroom 4.1 will not export a deleloped image.  I have the metadata to new file set to automatic and I get no error mesage.  All my new exported files are the same as the original.  I need a detailed discription of what boxes need to be checked or unchecked and where to find them.  Something as simple as saving changes so that I might use them in another app should not be so difficult- version 2.7 worked fine so what's up with 4.1? 

    Still no luck... I just purchased a licence for my demo version- I was hoping not to have to do  a 1.1Gb download and/or redo my my catalog- is this required?
    Date: Sun, 17 Jun 2012 00:37:57 -0600
    From: [email protected]
    To: [email protected]
    Subject: Lightroom 4.1 export problem
        Re: Lightroom 4.1 export problem
        created by ssprengel in Photoshop Lightroom - View the full discussion
    Are you saying that LR4 is exporting over the top of your exiting images, or that it is not exporting anything?   To test whether you can export anything, try exporting to a subfolder under your originals, instead of new names in the original images folder, which I think is what you’re saying you’re attempting: On the Export panel, all the way at the top, make sure to set Export To: to Hard Drive. Set the Export Location – Export To:  value to Same folder as original photo. Put a checkmark next to Export Location – Put in Subfolder Enter in “output” into the Export Location - Put in Subfolder: textbox. Uncheck the Add to this Catalog unless you really want to include the output of this experimental export in the catalog. Set Export Location - Existing Files to Ask what to do, so LR will indicate if it’s trying to overwrite the same files, again, which it should if the output subfolder is empty. Uncheck the File Naming – Rename To: so the files aren’t renamed. At the bottom change Post-Processing – After Export to Show in Explorer Click the Export button and see what happens.  It should do the export then open up Windows Explorer on the output folder you specified.    Before doing any of this, it might be wise to make a screenshot of your current Export settings, the Export To and File Naming sections at least, which you can both post here and use to reset things back from what I’ve specified, above.
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4498854#4498854
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4498854#4498854. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Photoshop Lightroom by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Lightroom Colors do not Match Windows

    I have spent hours and hours trying to figure this out to no avail.
    Dell u2410 monitor
    Colormunki
    Lightroom 4.3
    Windows 7
    I have gone through and calibrated the monitor according to Colormunki directions.  It says it's saving a profile that windows and all of my programs will use.  If I process a photo exactly as I want then export it srgb profile to my desktop and open with any other windows program it's significantly more pink.
    I've looked through all of the advanced tab settings in color managment in control panel, but it's super confusing.  How do I make what I'm editing to in lightroom match what I see in windows?
    BTW...I had this problem before I calibrated the monitor as well, which is why I calibrated it.  Actually it looks like windows views changed, but lightroom colors don't look any different than before profiling.
    I'm so frustrated, this shouldn't be this difficult.  I need to output some photo's to print in the next day or two and I now they are going to be messed up because I can't see the correct color.
    Thoughts?

    The effect produced by ColorMunki and similar tools consists of two independent parts: calibration and profiling.
    Calibration is the process of adjusting your monitor/video card hardware to make it "as perfect as possible", i.e. to make your monitor and video card to display sRGB colors as accurately as possible by using their respective hardware adjustment capabilities. For monitor that involves adjusting brightness, contrast and independent RGB channel gains. For video card that involves loading so-called "color lookup table" (LUT) with more-or-less finely tuned values. Since calibration is a hardware adjustment, everything you do during calibration will affect all software running on your system, regardless of whether it is color-management-aware in any way or not. As long as the software sends sRGB data to the monitor, that data will be displayed more accurately after more accurate calibration.
    However, with a typical monitor and/or video card calibration can only produce a roughly accurate results. It cannot make your monitor to work as a perfect sRGB device. There's simply not enough precision and/or flexibility in monitor controls.
    So, this is where profiling comes into play. Profiling is perfomed after calibration. Profiling records all deviations from "perfect sRGB" your calibrated monitor still has, and stores these deviations in a color profile. Later, any color-managed software will pick up that profile. By using the data stored there, color-managed software will be able to dial-out any color imperfections your monitor still has after calibration. For example, if your calibrated monitor is still greenish, the profile will say that it is greenish, and the software will automatically dial-out some green from the image data before displayng it. The combined effect of the image data being "de-greened" by software and then "over-greened" (by the same amount) by the monitor will produce ideal (non-greenish) display.
    However, only color-profile-aware software will use profiles and perform such adjustments to counterbalance calibration imperfections. All other (non-color-managed) software relies on calibration and calibration alone. So, in the above example, non-color-managed software will display greenish pictures while color-managed software will display the pictures perfectly.
    Apparently, this is something that happens in your case. When you used your ColorMunki, did it ask you to use your monitor's RGB controls to adjust the channel gains independently in order to arrive at some white point? Does white look white your monitor or does white also look pinkish?
    What your can also do is forget for a second about profiling software. Open your monitor's control panel and adjust it manually to your liking. Dial out any pinkness by using RGB controls (or use some standard preset). Adjust brighness and or contrast to the point where they "look good" to you. You may use some test picture and adjust the monitor manually to the point where the picture looks good to you.
    Now, once you finished that, you can start the ColorMunki software and use it to profile your monitor only. Profile only. No calibration. Do not adjust anything, regradless of what ColorMunki tells you to do. Keep the current settings on your monitor and make ColorMunki to generate a profile for it. That way you will get the look you like in non-color-managed software while at the same time getting accurate display from color-managed software.

  • PLEASE HELP - COLOR SHIFTING PROBLEM on output NTSC monitors

    http://www.smmlv.com/testproject/
    Above is a link to a layered photoshop file that has a USA map and over a dozen network overlays used in a section of our video. I animate each layer on sepeartely in the video and have noticed a major problem recently, the color of the art does not hold true to placement. I created the art originally in Illustrator and then converted the file to Photoshop at 640x480, 72dpi. This has always worked perfectly in the past to display and animated artwork in FCP.
    Right now, in FCP I am using the NTSC DV 3:2 frame size, and the compressor of DV/DVCPRO - NTSC. I have a JVC Profressional DV deck that hooks up through firewire and sends S-Video to my monitors. This setup has always given me a great picture even though it is not completely upcompressed. Using these settings and this art, the color lines on this map in red, light blue, yellow and purple all have a "color shift" to the left about 5 pixels. It makes it appear that the line is where it is in the file, but the color overlaying the line is offset to the left 5 pixels and transperant to about 50%. This occurs only when viewed on some TV's and NTSC monitors and projectors. The strange thing is, some monitors display the color aligned almost perfectly on these maps and other monitors and projectors show this "digital halo" of color shifting really bad. If I take the layered network overlays in these colors and color tint them to black or grey, white, light green, or even light orange, they no longer have the color shifting and the detail is perfect.
    Is there any way to fix this problem? I have tried duplicating the sequence and setting the compressor to 8bit Uncompressed, and while my captured footage is not this compression, in theory the art should render at this higher resolution setting. This did nothing to solve the problem.
    I also have tried using different Broadcast safe and Y/C corrector filters with different results. The Y/C filter allowed me to reposition the color problem and thus removing most of the problem, but also removing most of the color. Nothing else has allowed me to seemingly move the color into the proper possition.
    What is causing this color shift on the displayed NTSC image?
    In FCP 4.5 I can see my rendered video in the program viewer screen and besides the pixel compression appearing on the lines, overall the video looks great paused or even better when playing. Then you view it through my deck onto my Pro Sony NTSC 19" color monitor and it also appears great, with a slight color halo to the left of these colors, but the color in the lines are there. If you are a few feet from the screen and know what you are looking for you might see it, but doubtful. Then you view it using the same signal on a 17" Samsung TV and the color shifting makes the map and other art, like the clients blue logo, look horrible, with each color line appearing twice and offset left from each other as if you had double vision. Normally I would think it is the TV causing this, but then we tested this same movie on 2 differnt projectors. The $700 Epson projector displayed everything beautifully, again with only the slightest color halo to the left, but then the Panasonic $4000 projector made everthing in these colors look double vision again. What is going on???
    One more thing to keep in mind, my color bars also show this problem with these colors as well as shot footage of these facilities. There are tall red poles in the shots and everything displays fine except for the red pole color looks like it's glowing off the pole to the left.
    PLEASE tell me there is a solution to this.

    I have tried Degaussing, using filters, changing cables, and testing other monitors and systems on these monitors, everthing I can think of to solve the issue. Is it FCPo or is it the monitors?... or is it a signal strength thing. Can monitors and projectors shift color when the signal is read from a DVD or Mini DV Deck? Is there a fequency difference (Ie: 75mgz or 80 mgz) that might be causing the shift in some monitors and not so badly in others. But if this was true, how would some DVD's (like Baby Einstein DVDs that use really bright colors) display red and blue perfect using these same player and monitor, while my projects is shifting color? Doesn't that rule out the signal from the DVD player if other DVD's do not have this issue?
    I have uploaded the original art used, an exported .jpg file from the FCP timeline and sample photos of 2 different monitors to show to show this problem as best I can. http://www.smmlv.com/testproject/
    Someone out there must have had this problem before. There's no way a color shift problem like this with Mini DV has gone on this long without someone seeing it.
    One last thing about what I have tried... I do understand that with editing in Mini DV instead of uncompressed or HD video I lose a bit of resolution (4:2:2) and I see this compression occuring in some of the areas in the video where these problems persist. But, I did remake the art and rerender this project in an 8bit uncompressed settings and then displayed that up on the screen and I get the same color shift. I keep going in circles trying to find the culprit that is causing the delema.
    PLEASE HELP! There are large tours going through our facilities daily and the large screen projector is displaying this problem as well. Let's just hope they don't notice and that their TV's at home or office does not display it on our final DVD's made.

  • I would like to use slideshow in lightroom to export my video as a full screen 1920x1080 video with text overlays.  I am using text overlay in lightroom as it reads from the metadata that is easy for me to input in the library screen.  When i export from

    I would like to use slideshow in lightroom to export my video as a full screen 1920x1080 video with text overlays.  I am using text overlay in lightroom as it reads from the metadata that is easy for me to input in the library screen.  When i export from lightroom slideshow and choose the 1920x1080 resolution the end product is a very small video in the middle of a black background.  i have double checked and do not have any borders turned on.  Another option would be to export from the library but lr mogrify does not seem to put text overlays on video either.  Any input would be welcome.

    I dont understand anything you said in your post.
    Do you have a specific question about video production?
    The forums are for individual technical or creative issues that users have with video production. I am sur someone will be able to help you, but and to get a response it is best to ask a specific question.
    Is this about a technical problem you have or something about setting up a web site? If its the latter this is the wrong forum.

  • Export Problem in LR 3.5

    Hi folks,
    I have been working with LR 2.7 for a while now and was happy with it.
    PC - Win XP - LR3.5
    Photo's stored on external hard disk (K:)
    The RAW captures of a Nikon 3100 I recently won were not being recognized/imported by LR 2.7 and I installed the 3.5 version to see if it was any better. I would have to buy it anyway by the time I switch to Win7. In 3.5 the Raw files were imported, the settings of 2.7 were nicely taken over but now and I cannot export the files I have worked on to the K: drive of the external hard drive as I used to do with 2.7.
    I get the message 'The folder could not be found' though it is set in the Export Window and I am looking at it in Win Explorer.
    The original RAW captures are on the D: drive but that was always the case with 2.7 as well... I am doing it exactly as I used to with 2.7.
    I tried with a photo from an older folder of my usual camera and everything works fine there.
    The problem seems to be only with the Nikon files. Now I start wondering if there is something with raw format of this Nikon camera that is putting LR in a twist...
    Anybody any ideas to help me out?
    Thanks and grts
    Nil

    @ web-weaver:
    Of course they go to a different folder and they also get different
    titels/names once processed in LR. The originals are always RAW (NEF) and I
    export them as jpg or tiff files depending on what more I will do to them.
    @ ssprengel:
    I get the message when I have renamed the file in the export window, set
    the folder it has to go to and hit export.
    In the 2.7 version I got it already when I tried to import.
    As I said, this only happens with the Nikon (NEF) RAW files. With the
    Olympus (ORF) RAW files I have no problem at all and had no problem in LR
    2.7 either.
    I cannot see anything wrong in the Export panel nor in Preferences.
    Plug in is Metadata Wrangler and has been updated to the latest version >
    no joy...
    I tried import/export with jpg files and no problem there.
    Yesss! Got it! What I had overlooked was a question mark next to the folder
    in Library (sooo small). A rightclick and telling LR where it was solved
    the problem. Strange, though, as it has never done this before... the main
    folder and the path are still the same as the ones that work perfectly with
    Olympus exports... just a different subfolder named Nikon and another named
    Test... Also strange that if I started off with jpg, it was no problem
    either...
    Anyway, thanks a lot for shaking my senses for me
    Nil
    2011/12/10 web-weaver <[email protected]>
       Re: Export Problem in LR 3.5  created by web-weaver<http://forums.adobe.com/people/web-weaver>in
    Photoshop Lightroom - View the full discussion<http://forums.adobe.com/message/4075999#4075999>

  • Why does Lightroom color not match when editing in Photoshop CS3

    I just started Using Lightroom 4, the only version of lightroom that I have used. Short version, saves me heaps of time. But I went to edit more in photoshop and noticed that the color is dramatically different. I have Photoshop CS3 (10.0.1)and the color space is ProPhoto to match lightroom. If I make edits in lightroom, say removing dust spots, it shows in the photoshop version. It seems that on the shadow side is where it really shows. My workflow would be to import as original RAW in lightroom 4 (canon 1d mark II) and go about editing. Right click to edit in Photoshop CS3, and this is where colors go crazy. Then if I save the file with no edits done in Photoshop and compare side by side in lightroom, they are completely different. What is causing the drastic difference?
    These are screenshots where in the left screenshot the original image is the dark image and the lighter is what it looks like when opened in Photoshop. The compare in lightroom on the right screenshot is what it looks like when I saved the file from Photoshop. So how does opening in Photoshop, then hitting save change the image? If i make the edit in lightroom then export the jpeg and open in photoshop, I get the appropriate color, exactly the same as my original lightroom raw. 
    My external editor settings in lightroom are tiff, prophoto colorspace.
    photoshop preferences are to preserve embedded profiles.

    Just to make sure we're talking about the same thing, when you "Edit in" Photoshop CS3, it should give a warning dialog that says the version of ACR in Photoshop isn't compability, with the option "Open anyway" (won't work well) or "Render in Lightroom" (which should be fine).  Or, if you've created your own "Edit in" preset, you should get the option "Edit a copy with Lightroom Adjustments". 
    So long as you've chosen "Render in Lightroom" or "Edit a copy with Lightroom Adjustments" (depending on how you've edit up "Edit in...") then colour should be OK. 
    Colour options in PS should be something like:
    Check all the "Ask when..." options, just to make sure you get warned of mis-matches.  And I suggest the RGB policy should be "preserve...". 
    And the final thing: to be sure of no colour mis-match, you need a calibrated/profiled monitor (with a hardware tool like Spyder, ColorMunki, Eye-One etc).  When there isn't a monitor profile containing a colour space (which needs a hardware tool, generally) then different programs can make different assumptions and display the same image differently. 

  • "Lightroom has encountered problems reading this photo."

    ***** UPDATE July 17, 2013 @ 9:16 am Central Time (UTC -06:00)*****
    After Creating a fresh catalog I have been able to clarify the issue a bit. This error appears to only show up in Folders exported as Catalogs. Particularly when I try and open that exported catalog.
    I suspect there is a problem with the way Lightroom 5 is exporting these catalogs. I didn't have this issue with LR4.4, but it shows up any time I export a folder as a catalog within LR5, regardless of whether or not it is exported from an upgraded catalog or a fressly created catalog.
    It looks like fixing the problem is going to be time consuming, but not impossible. So far I have confirmed that these files - reported as throwing this error by Lightroom 5 ("Lightroom has encountered problems reading this photo .... You will not be able to make adjustment to this photo.") - can be imported into a new/existing catalog by multiple methods without carrying over the errors displayed in the exported catalog.
    This is frustrating and adds additional steps to my workflow, but isn't undoable. Of course it would be nice if LR5 worked as correctly and exported folders as catalogs without throwing errors when those new catalogs were opened...
    Is anyone else seeing this problem when they open catalogs created by "exporting a folder as a catalog"?
    ***** Original Post *****
    I'm really confused. I am consistently getting this message on certain exports, but not others...
    When it happens:
    1) "Export this Folder as a Catalog" from a specific folder within my Working Catalog
         Select the location
         Select "Export negative files"
    When I open the NEW Catalog - ALL the photos reflect this error message: "Lightroom has encountered problems reading this photo .... You will not be able to make adjustment to this photo."
    When I go to the Develop tab it displays "There was an error working with the photo" over the photo, but I can edit it... When I close the catalog and re-open it, the changes don't reflect UNTIL I go back to the Develop tab, then the thumbnail will reflect the change. But the system still insists that it has a problem with the file...
    2) The same thing happens when I export the file from my Working Catalog as an image of the same format - be it tif, dng, or psd, or RAW files. Not sure what I was refering to here (can't duplicate today - July 17).
    When it doesn't happen:
    When I export the file to the auto import folder for my Portfolio catalog (original format). This seems to work...
    Why am I so confused? Because all of these catalogs are located on the same drive (which is different than the drive my Working Catalog is on). When they are auto imported to my Portfolio catalog they seem to work, but everything else throws an error sinse I upgraded to LR5!
    My System:
    Windows 7 Pro SP1 (fully up to date) 64-bit
    Intel Core i7 CPU 950 @ 3.07GHz
    Installed RAM: 12.0 GB
    My Lightroom 5 Working Catalog doesn't seem to be having any problems...
    This problem is frustrating enough that I may go back to LR4. I can't have my archived files compromised...

    Suggestion to all who encounter problems like this: if you've installed 3rd party memory cards (ram), go back to your original ram, or at least the brand of ram that your computuer came with.
    Long story, short:
    I had the same error message in LR5.  It only happened with several images in a given import.  If I deleted all of the images from the import and reimported the images, a different set of images would have the error message.  The images that originally had the message would no longer have the problem.  I deleted and reimported several times while observing the same behavior. 
    Not only did lightroom give me issues, but Bridge had problems reading the files, and the previews of the problem images would not show up in Finder (Mac speak).  This ruled out, to me at least, that it was a software issue.  I went out and purchased a new card reader and had the same problems.  I tried a different card with different images and got the same problems. 
    After I contacted Adobe, they had me upload two files with the error, and they said the files were corrupted due to faulty hardware.  I took my mac book pro (13in early 2011 w/ 10.7.5) to the apple store and they ran a diagnostic test amoung other test and we came up with nothing.  Everything seemed to be good on the hardware side.  After some research the Rep. asked me about my ram (memory cards).  I had in the past installed two 3rd party cards to boost my ram from 4GB to 8GB. The rep. suggested that I go home and test the issue with the original ram my computer came with before we go any farther.  So far, I haven't had any issues. 
    I hope this helps,
    Josef

Maybe you are looking for

  • SMARTFORMS field in STRING format

    Hi! <b>Is there limitations when using data type STRING in connection with SMARTFORMS?</b> I'm trying to send a text field (581 digit long) into an XML file. It is declarated: AVVTEXT     <i>(text field, can be 0-2004 digit)</i> data type <b>STRING</

  • Analog distortion and digital's lack thereof

    Djokes wrote: "analog is distorting - without a doubt - tape decks were like compressors in a way and that is what being simulated by e.g. mcdsp or crane song... However, using no eq or tape deck - the distortion is minimal.... but analog is distorti

  • JDeveloper Code Editor doesn't do ClearType font anti-aliasing

    I can't seem to get the Code Editor in JDeveloper (11.1.1.5.0) to do ClearType sub-pixel font anti-aliasing. Everything else in the IDE is doing proper sub-pixel anti-aliasing, it's only the Code Editor that's not doing it. It's doing "normal" pixel

  • Is there a 64-bit gdb for Solaris (I need both x86 and Sparc)

    I'm looking for publicly available versions of gdb for both SPARC and Intel. I'm the current developer of the NetBeans gdb module and we've had bugs filed that our Solaris users can't debug 64-bit applications. I've built a 64-bit gdb but its trying

  • Next Button

    Hi I've make a report that show one only row, when I run as portlet and I press the Next button it's OK, but when I'm running it in a page if I press Next button to show the next record it gives me the following error: ORA-06502: PL/SQL: numeric or v