RAW impages lose color, clarity, detail when importing.........

I use Canon's Professional Digital Software [OEM] to process RAW images from my 21 MP camera. Incredible color, sharpness and Clarity. Color is shot in sRGB and as part of processing, I sharpen, adjust color temperature, set exposure, etc.
When I import into LightRoom 2.7, the photos load beautifully, then one by one the photo is rendered losing color, clarity, etc. ....... Yes I saved all RAW image adjustments to the original RAW file as part of my processing using Canon's software to my hard drive with a unique folder name, then import from that folder. I like LightRoom as I can edit muliple images rather than one by one in PhotoShop.
I've checked all my settings, etc. so as to understand what is going on. Lightroom is incredible and I'm anxious to see 3.0. So, has anyone else experienced this? I can't help thinking that LightRoom has become corrupted or ?????
Isn't the original *.jpg or RAW image supposed to import exactly as read? Any comments?

Question Answered: YES and I understand the "How" this happens. Guess I'll have to import only HiResolution JPG files from this point forward.
Brad Snyder
Moderator
Senior Member
Posts: 4631
Location: Port Deposit, Maryland USA
Primary OS: Windows
OS Version: 7
Memory: > 4 GB
CPU Cores: 4
Video Brand: ATI
LR Version: 3.0 BETA
Printer: HP
Camera: Canon
Why did Lightroom 'ruin' my photo?
« on: March 16, 2008, 01:27:34 PM »
Updated August 12, 2008 to include references to DNG Profile Editor and Camera Matching profiles.
Updated December 23, 2008 to note Lr 2.2 automatically installs the Camera Matching profiles.
By far the most common question asked on this Forum is: "I took a beautiful picture! It was perfectly saturated and color balanced, and I loved it. When I imported the RAW file into Lightroom, I saw my beautiful picture for 5 seconds, and then Lightroom ruined it, and turned it into a bland muddy mess. Why?" The picture you see in LR is exactly the picture your camera sensor recorded. It's likely that you are used to seeing the preview on the camera display. That preview is not your RAW file, but a JPG which has been processed by the electronics inside your camera. Or, you may be using your camera manufacturer's proprietary RAW conversion software. That software has a post-processing advantage in that it can utilize proprietary 'secret' information embedded in RAW files, which is undocumented and unavailable to third party programs such as LR and ACR. Additionally, most third party viewer/browser applications show you the embedded JPG preview rather than the actual RAW file contents. In fact, LR itself shows you that preview for a few seconds at first, until it has time to render a preview in accordance with your current develop settings. When you import your RAW file, none of that proprietary in-camera processing is applied by Lightroom. To a certain extent, you have to do it yourself. That is the purpose of Develop Presets. It takes some getting used to, and some practice, and some homework to achieve consistently good results. The amazing flexibility of Lightroom comes with some costs in terms of effort.
Now for another slightly confusing concept.
As part of configuring a new camera for LR or ACR, the Adobe engineers create two import profiles for daylight and tungsten lighting conditions. Your import will be treated with a mixture of those two profiles which attempts to match your lighting conditions. To take advantage of this default processing, you need to apply the default develop preset, which is unfortunately named "None". Well, not exactly, but that's the preset option you need to choose if you want the default processing. To confuse matters a little further, there is a sample preset, called "General - Zeroed", which sounds to most people as what they want. "Give me the picture my camera took, with ZERO changes!" Alas, that particular preset simply sets all of the Develop sliders to zero, which is rarely the correct choice for photo processing.
Why would anybody choose to forego the sophisticated in-camera processing? The only way to take advantage of that is to save an RGB pixel-oriented format, typically JPG. Unfortunately, in applying that processing to the JPG, the camera makes many decisions which become 'locked-in', and unchangeable with post-processing. Fortunately, it's often possible to take advantage of both worlds. Many cameras offer a RAW+JPG save mode. Don't forget that the in-camera processing is a fundamental compromise between the manufacturer's engineering and marketing departments. Which achievable vision will sell more cameras? Your artisitic vision is what matters in the end.
Why would anybody choose to use Lightroom for RAW conversion with its inablilty to use the proprietary data available to the camera manufacturer's software converter? Many users cite ease of use, overall sophistication, and better fit to workflow, among others. That's an individual choice. The main concept to glean from this tip is that:
"Lightroom provides a marvelous flexibility in post-processing photos. But, akin to many tools for the dedicated craftsman, it comes with a cost in terms of learning curve, and a much broader requirement for thoughtful practiced input."
With the advent of Lightroom 2.0, Adobe also released the DNG Profile Editor in beta, along with beta versions of the standard Adobe camera profiles. In addition the available profiles include 'camera-matching' profiles which are specifically designed to allow LR2 to match the in-camera 'picture styles' available from Nikon and Canon cameras. This capability is revolutionary in a 3rd party product, and will go a long way toward addressing the issues discussed in this article. Find further information on the product here: Profile Editor At present, Adobe has committed to providing the beta and subsequent Version 1 as a free utility for the photographic community.
With the advent of Lightroom 2.2, the revised Adobe standard profiles, and the camera matching profiles are automatically installed, and are available in the Camera Calibration panel, lower Right Hand Panel in the Develop module. LR = Adobe Lightroom
ACR = Adobe Camera Raw
« Last Edit: December 23, 2008, 08:31:36 PM by Brad Snyder »
Logged
.....brad s Win7x64, i7 2.7 GHz, 6GB

Similar Messages

Color profile off when importing motion proj into FCP

Color profile off when importing motion proj into FCP. Is there a way to set the profile?
I deleted preferences in FCP.

No, profile do many things. It is a color space. It allows different apps and systems to view colors the same. Also fcp typically works in a tub color space not rgb.

Raw files become dull and lifeless when imported

i have an isue with the fact that i spend time setting up my camera for the rite white balance and exposure to get a quality image that might use some spot removal in post but thats about it, to have the images become dark, dull and lifeless in lightroom when imported. when i try to bring the color back its just not the same. why is this happening and how can i fix it. i am glad that i saved the files elsware first, the raw images look fine in other sofware its just lightroom that is doing this. here is an screen shot of the same image side by side the one on the left is raw exactly how it lookes in camera with canon software and the one on the right is in lightroom. at first it looked the same but 2 seconds later it was dull and imo ugly.

You lack a basic understanding of what a Raw file is and what it isn't. It is data from the sensor siphoned off the camera's pipeline immediately after it is converted from analog to digital data, a checkerboard of the intensities of light received by red-seeing pixels, green-seeing pixels and blue-seeing pixels. A record of the intensities only (greyscale) and not the colors. All the colors will be created by the camera further down the line, on the way to a jpg. The Raw can, at best, be characterized as a b&w image, dark and flat because it is linear. The later processing will also apply a Tonal Response Curve to make it brighter, contrastier and more vivid. Since the Raw has been pulled out of the camera before it gets a chance to do all this, it has to be done by the Raw converter - Lightroom in this case. But the camera needs to display on its LCD a review of the shot, so it does do the rest of what is needed to produce a bright and pretty jpg, purely for display purposes,and then embeds that jpg in the Raw file. When you view the Raw on an application that is not a converter, it shows you that jpg. Open the Raw in the converter from the camera maker and it uses the same processing as the camera to produce a very similar image to that jpg, a more or less finished product. But the initial processing done by LR is more restrained and moderate because it is assumed that if you shot Raw you will want to design your own personal processing, an expression of your taste, judgement and vision. By having defaults that add only minimal processing LR is providing a starting point that leaves the road open to whatever direction you want to take it. But if you don't want to make that investment, Adobe bundles with LR a collection of presets that will move the sliders for you and there are many hundreds more on the internet, both free and purchasable.

Raw and jpeg will not show when imported from camera

I am doing a OCA degree in digital photography using aperture 3 . I have been asked to take Raw and J pag , open up in the program I use. And not the differance and the make changes.
I have 1d MK III and 7 d I cannot get both file types to show side by side.. Some one tell me how to do this please. I must have clicked , ticked something , that I cannot find to put right again.

As always, start by copying the images on to a folder on the hard drive and then backing up the folder. Never import directly from camera or card into Aperture or any other images app.
Then since this is an exercise not a batch workflow, simply rename the RAW and JPEG versions of one image and separately import each renamed version into Aperture. The two should each be Masters, one from the JPEG original and one from the RAW original.
Note the JPEG may initially "look" better on the (relatively low resolution) display due to in-camera presets like sharpening, etc. not present in the RAW file. However the RAW file contains much more image data, is much more editable and is capable of making superior (relatively very high resolution) hard copy prints.
HTH
-Allen Wicks

Camera RAW: NEF - JPG color dessaster

Hallo...
I use PS CS4 on my Mac. Normally I use Camera RAW to convert my D90 NEF-files to JPG-files without using Photoshop.
In Camera RAW look all colors great. When I convert the 12Bit-Raw-files to 8Bit-JPG's all colors look sad and gray.
Where is my mistake??
In the export-dialog it's not important if i set 16-bit export or 8-bit export - the colors look like crap!
The only workarround i found is to rise the saturation and dynamic for 15-25 points. Is there no better way?

If you are saving to JPG directly out of Camera RAW and not enhancing further in Photoshop then you should probably save as sRGB, especially if you are putting the JPGs out for people to see on the internet.
What could be happening is that you’re saving as ProPhotoRGB or AdobeRGB but the viewer you’re using to verify the colors is not doing color-management properly so it is interpreting the colors as if the JPG was sRGB even though it’s not.
If you are going to be editing in Photoshop then keep the colorspace in ACR as 16-bit ProPhotoRGB and do the conversion to 8-bits and sRGB in PS just before saving as JPG.

Menu background lose color when import to dvd sp

i create psd then flat it and save as tif and jpeg and even psd files. Both look good but when import to DVDSP, the color lose. Any suggestions? save png file?

Russ
Can't thank you enough.
I had been away from FCP and DVD SP for awhile and that can cause a loss of memory.
Your answer triggered my brain to export the finished project in FCP as a QT movie to my external drive and from there to DVD SP.
I also have forgotten most of the French I once knew as well.
Again....much appreciated, Russ
Dan

Horizontal colored bands appearing in imported raw files

I just now started to have mostly magenta horizontal lines or bands appear in imported a Sony Nex 7 ARW files. When opening the same file with Sony’s raw converter or DXO Pro, the bands are non existent. I have noticed that sometimes but not always, the bands will disappearing in LR after I examine a photo by clicking on it to enlarge a selected area and the loading finishes. Exported photos will have the bands. Also, If I first open the files with IDC or DXO, the file will then import into Lightroom without the bands. I have run diagnostics on the SD card and the hard drive with no errors showing up. Running LR5.4 on a Macbook Pro. I’m totally confused. Any enlightening comments would be greatly appreciated. Thanks.
These artifacts are exactly like those in the post : Why do I get Colored bands on some images in LR4 and LR5, but not in Aperture?

I have the EXACT same problems when importing .RAF files from my Fujifilm X-T1 via a USB card reader (USB 2.0) on my MacBook Pro 13" Retina (late 2013) with OS X 10.9.3 in Lightroom 5.4. (I did not purchase the X-T1 until after I updated to 5.4, so I can't speak of whether this happens in other versions of LR)
I second sevenc's suggestions that this is NOT a hardware issue - I have tried 5 different SD cards, all formatted either on my computer or in the camera, reformatted several times (low-level format) and it STILL happens! Never with the JPGs, only with the RAW files.
However, doing a straight file copy from the SD card (in the card reader) to the hard drive before doing the import works fine - no artifacts!
Ditto if I use the internal SD reader (an internal USB3.0 connection) on the Macbook, no purple bands.
It is apparently unrelated to the OS, since this is happening both in Windows and OS X. I have posted a more detailed acccount here:
Lightroom 5.4 - "glitches" on my RAF->DNG conversions from X-T1 - Fuji X Post Processing - Fuji X Forum
One of the members of that forum has seen the same happening with Panasonic RAW files, but only when an external USB drive was connected at the same time.
When the external drive was disconnected, the images imported normally.
BTW, my Canon files import just fine, using the same SD card, the same USB card reader and the same computer - no glitches....
The most likely thing happening (my opinion) is that the Lightroom import process somehow interferes with the USB connection. It doesn't really make sense, because I am sure Lightroom uses the standard OS I/O file routines, but it seems to be the most likely issue. Is there a chance LR uses its own code for reading files off of external drives.
Other software (Aperture, Preview, Image Capture, Raw Photo Processor 64 or PhotoNinja) can import fine, whether the card is in an external card reader or not - no artifacts.
I have seen it the same issue described with Panasonic files on LR 4, so it does not seem to be limited to LR 5.4
Re: Why do I get Colored bands on some images in LR4 and LR5, but not in Aperture?
Anyone care to shed light on the issue and what could be going on here ? It seems the more obscure raw formats are affected (Sony, Panasonic, Fujifilm) and that Canon/Nikon users do not experience it (at least I haven't found it described online).
This is a serious bug, because unless you do a re-import of the RAW/RAF file, the image data is permanently corrupted. It is not an issue of corruption of the embedded JPG preview , it is the RAW file itself. Once it has been imported by Lightroom, it displays the artifacts in other programs as well (Aperture, Preview etc)
Trying to convert the image to another format, e.g. TIFF, JPG, BMP the artifacts are still there.
I hope this is taken seriously by Adobe, as it is a critical issue for those of us who are affected. I can work around it by copying the files to my hard drive first, but it shouldn't have to be this way....

Color space conversion problem when importing JPEG's

Hi,
I'm currently playing with the trial version of LR. While importing JPEG's with different color spaces (sRGB and Adobe RGB) to LR I've noticed a strange effect: There is a small but noticable difference in color, depending if the JPEG was previously saved in AdobeRGB, or sRGB. All the images I've tested so far should not contain critical colors that exceed normal sRGB. When opened in CS2 both versions of a JPEG, AdobeRGB and sRGB, typically look perceptually identical, no matter if I leave the sRGB image to sRGB, or convert it to the working space (AdobeRGB). Also my color-managed image viewer behaves as it should. So I don't think it's a matter of the different color spaces.
Looking at the imported images in LR I would say that the AdobeRGB image is correctly converted while the sRGB image suffers from a slight reddish cast, most noticable in skin tones. The effect is not as strong as if I would load the sRGB image into CS2 and skip color conversion to my working space (AdobeRGB).
The sRGB versions of the JPEG's were obtained from the AdobeRGB JPEG's using CS2 for conversion.
Anyone else here experienced a similar problem? Is this a bug in the xRGB-to-ProPhotoRGB conversion of LR, or a feature?
/Steffen

Hi Uli,
thanks for pointing me to your thread. I followed the discussion with great interest. Actually, I think the effect I am describing here is of different nature and a LOT stronger, at least for the type of images I've tested.
I did some more experiments yesterday with interesting results:
1) When I export a processed RAW from LR to JPEG or PSD, no matter what Color Space (I tested AdobeRGB, sRGB and ProphotoRGB), and re-import those JPEG/PSD's to LR, they look absolutely identical to the RAW I started with. Also, at first glance, they look similar when opened in CS2, but only because I tested with color images. I can indeed see small differences when testing with B/W, as you described in your "Color management bug" thread.
2) When I change the color space of an PSD or JPEG inside CS2 (I used the default setting 'relative colorimetric') and save it to JPEG and then import this JPEG to LR, colors are far off. The strength of this mostly reddish color cast depends on the color space of the imported JPEG, strongest for Prophoto, less strong for Adobe and sRGB. Interestingly, when I convert the color space inside CS2 and save the result to PSD, it will display correctly when imported in LR. Another interesting side effect: the thumbnails of LR-exported JPEG's in the "Open" dialogs of CS2 and LR (I guess those are not color-managed) show the typical color-flatness for the Adobe and even more the ProPhoto version. For the CS2-converted JPEG's, all thumbnails look just a colorful as the thumbnail of the sRGB version.
3) Such an image which doesn't display correctly in LR will keep its color cast when exported again to a JPEG (not sure about PSD). So something goes wrong with the color conversion during the import of such CS2-converted images.
My explanation so far is that CS2 uses a slightly different way of coding the colorspace information in the metadata of JPEG's which somehow prevents LR to recognise the color space correctly.
Can you confirm this behaviour?
Steffen

When importing raw photos from Nikon D90 aperture seems to automatically adjust exposure darker. why? How can I stop this?

When importing raw photos from Nikon D90 aperture seems to automatically adjust exposure darker. why? How can I stop this?

This is typical of the default NEF RAW conversion of Aperture and the best thing you can do is set up a few presets to apply to all of your RAW images to get a tone curve and colors that is pleasing to you as a default. The in camera JPEGs / embedded JPEGs (that you first see during import) are treated to the Nikon "Picture Control" settings that are set on the camera - the RAW's as interpreted by Aperture are not.
I have written extensively and even have a few downloadable presets on my site - look for NEF...
http://photo.rwboyer.com/
RB

When importing Raw into A3, in what format is the picture displayed? Jpeg or tiff.

When importing Raw into A3, in what format is the picture displayed on the screen? Jpeg or Tiff ?

None of the comments you have gotten are particularly useful. The display is independent of format of the file. It's rendering is of the full pixels in the image file that you have imported, modified by any adjustments you have made, or not if you ask to see the Master.
Even if your Master was imported as a JPEG, as seen on the screen it would have been decompressed, and you would see all the pixels (that the screen is capable of). However, a JPEG may have lost some detail in the compression, but when decompressed has the same number of pixels as the equivalent uncompressed photo format -- but some of them may result from interpolation, and not be the original.
Ernie

I'm not good with computers or software. I'm trying to save a RAW Ai file I created. When I currently save it, the color or characters/size fonts are not coming up in the saved version. How can I save, and have all of my information

Not going with computers. Trying to figure out how to save Ai RAW file with colors/fonts etc. Currently saves, but does not have colors and font information.

When you say "Colors/Fonts" are not saved, I'm not sure what you mean. How have you determined they were not saved?
Also, not sure what a "RAW" AI file is. I assume you mean simply a native format .ai file.
.ai will save all font and color information. It does not "embed" fonts, but it saves what fonts were used and will call the correct fonts when reopened (assuming fonts are available on the system).
CC 2014 also has a "Package" feature that will collect assets (fonts and images) into a central folder for easy distribution.

When importing RAW files in Photoshop why does camera raw 8.6 only import 1 size?

When importing RAW files in Photoshop why does camera raw 8.6 only import 1 size from canon 5d mark iii, in older versions I used to be able to import the files as larger images. It use to have a number of options for the images size. The option now is smaller than the maximum size used to be.

You know what - I'm sorry
I'd had a crazy long all-nighter session sorting out images for a client, then decided - when I should have simply gone to bed - to set up the new photoshop. At the very start I made a silly mistake, tried to sort it out then decided to call it a day, responding to your remarks with the problem still in my head but feeling more and more tired.
Responded again to your comment earlier with the problem still in my head but not in front of me on the screen - however with a fresh head I just turned it all on, opened up PS and today could instantly see what was going on - Oops!
Thank you for being patient with a sleep deprived photographer who must have been getting annoying yesterday
I am officially embarrassed
M

What happens to Raw files when importing Raw+JPG from camera to Lightroom Mobile on iPad? Only JPGs are showing up.

Hey I am Brian, and I was wondering how Lightroom mobile works again as in when importing photos directly into iPad using the camera connection kit.? This is for IPad 2. I . Like when importing raw files. now I just did a photo shoot. and I just uploaded them into lightroom 5 on desktop. the raw files are being pushed as smart priviews acroos ipad and iphone. its kinda cool seeing cr2 file showing up on lightroom mobile. when its coming from lightroom 5. but what about coming from camera to ipad.?
I thought you can import a Raw plus jpeg into ipad and it shows up as a jpeg plus raw file. well its not doing that. shows up as just jpeg.
cant wait for next update of lighroom mobile.

With this version of LR Mobile we not support the direct RAW import.
You can vote for this feature request...Lightroom mobile: Ability to import raw files
- Guido

IPhoto: Retain modified date&time details when re-importing

Instead of having all my photos in just one iPhoto library, I am now moving out photos into separate iPhoto libraries to better manage my photos:
... Export photos from existing/old library
... Re-import photos into newly-created library
Some of my existing photos have modified date & time (result of not checking camera clock after a service!)
Is there a way to retain these modified details when exporting photos from the OLD library and re-importing them into the NEW library?
I am really hoping not to re-edit the photo attributes
Thanks in advance
Message was edited by: auroranight

I am using iPhoto 6.0.6 I do not know of any option "modify original photo". Other than 'batch change' there is no option.
You are posting in the iPhoto '08 forum and will get iPhoto '08 answers here - if you want iPhoto 6 answers it is best to post in the iPhoto 6 forum
I xferred the pics from my camera to a new folder on my desktop. The times are all correct in that folder.
Again - how are you seeing that the time is correct? iPhoto looks at the EXIF data and the finder looks at the file data - how are you seeing the EXIF data on the desktop? EXIF viewer - http://homepage.mac.com/aozer/EV/index.html - is a useful utility to have to see the EXIF data
You can create a fresh plist - that might be the issue but I doubt it - quit iPhoto and in the finder to to "your username" ==> library ==> preferences ==> com.apple.iPhoto.plist and delete it - launch iPhoto and reset any personal user preferences you have changed and if you have moved the location of the iPhoto library repoint iPhoto to it
LN

Develop settings when importing RAW + jpeg

When importing NEF files from my D700 I apply the landscape sharpening pre-set and am happy with the results. However on my Fuji X20 I import RAW+jpeg rather than just RAW, in this situation if I use the landscape sharpening pre-set sharpening is applied to the jpeg as well as the RAW resulting in the already sharpened in camera jpeg being grossly over sharpened. If on the other hand I use none for the develop pr-set no sharpening or noise reduction is applied to the jpeg and a minimum amount applied to the RAW file, more or less what I want except I want the higher landscape sharpening applied to the RAW files. Is there anyway to modify the built in pre-sets so that they only get applied to the RAW files when importing RAW+jpeg pairs?
Dave Rosser

I believe the answer is No, you cannot apply a preset at Import time based on file type.
What you can do is after you import, filter on File Type and set it to JPG and apply another preset that changes the sharpening settings of the filtered set of files, then go back and turn off the filter and work with both sets of images as you want.
To filter by File Type, you need to go to Library Grid, enable the filter bar with the backslash \ key if necessary, then select Metadata, and either change one of the existing filter columns to say File Type or add a new File Type column.
Once you have created and applied the filter, you can save it as a filter preset that can be applied by the filter preset selector at the very right and just above the thumbnail strip at the bottom, even in Develop mode.
You might make one for raw and for jpg in case you want to swap between the two, and if you shoot JPGs with more than one camera model, you can add the camera model to the filter criteria.

RAW impages lose color, clarity, detail when importing.........

Similar Messages

Maybe you are looking for