Why do my RAW files appear different between programs?

I have rendered a series of three RAW images as an HDR file in Photoshop CC, saved as a 16-bit TIFF file, and imported it into Lightroom. The image appears different between the two programs. The Lightroom image appears to have some editing done already and is not nearly as flat as the image in Photoshop. I have made sure my Adobe software is up to date concerning both programs and the camera raw information that can be updated via Adobe.

The iPad stores the raw photo data, but displays an iPad optimized version of the original image in its place.
This image is usually an optimized JPEG image, so the quality will not be the same as the raw image file.

Similar Messages

TIFF & JPEG renders of RAW files appear different when viewed in Bridge

I am working with the demo of Photoshop CS6, with ACR 7.1. CS6 System Info will appear at the bottom of this post. Summary: AMD Phenom II x6 1090T, 16GB RAM, Win7-64bit, nVidia GTX 460 video w/1GB RAM, approx. 2.5 TB free space on multiple internal physical drives, Canon 50D, CR2 files. I have a camera profile generated through Profile Editor, and the monitor is calibrated with i-1 Match.
I have been practicing with the new Basic Panel controls (Process 2012). When I felt that I was getting the hang of them I started saving JPEG and TIFF files and noticed differences between what appears in Bridge and ACR. I worked on this for some time and searched out some other discussions in the Forum which seemed to talk about similar results. I have now tried Image Processor via Bridge, Save Image in ACR, and Open>Save manually in PS CS6. By whatever route, the TIFFs and JPEGs are different (lighter in the following examples, but this is not always the case), while PSD saves seem to be close, but not identical to the CR2 when viewed in Bridge or Photoshop. Here is a screen capture of Bridge thumbnails which show the differences.
I hope the labels come through legibly. The two images on the second row are CR2 and PSD respectively. What is really odd to me is that when I resaved the PSD file as a TIFF, the same sort of difference shows up in the TIFF. (See _MG_7960_via_PSD.tif above.) I have uploaded the CR2, its XMP, a TIFF and a JPEG on Sendspace (107 MB). I did this earlier in my experiments and regret that the file naming is not as informative as might be.
http://www.sendspace.com/file/t0lhko
I have run a few other ACR adjusted CR2 images through Image Processor and seen a variety of differences between the rendered files and the RAW versions. The differences seem to be in Exposure and Contrast. Most of these looked somewhat darker, unlike the examples above.
I will happily provide any other information on request. Thanks!
Photoshop System Info:
Adobe Photoshop Version: 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: AMD CPU Family:15, Model:10, Stepping:0 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 6
Processor speed: 3511 MHz
Built-in memory: 16382 MB
Free memory: 13415 MB
Memory available to Photoshop: 14766 MB
Memory used by Photoshop: 71 %
Image tile size: 132K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GTX 460/PCIe/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1200, right: 1920
Video Card Number: 1
Video Card: NVIDIA GeForce GTX 460
OpenCL Unavailable
Driver Version: 8.17.13.142
Driver Date: 20120515000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode: 1920 x 1200 x 4294967296 colors
Video Card Caption: NVIDIA GeForce GTX 460
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Serial number: Tryout Version
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Kieren\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
E:\, 770.4G, 644.1G free
K:\, 931.5G, 482.3G free
L:\, 1.82T, 854.4G free
H:\, 1.75T, 505.2G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   6,0,29,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   3D Studio 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.1
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Clouds 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Collada 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Embed Watermark 4.0
   Entropy 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Maximum 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mean 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Measurement Core 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Median 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mezzotint 13.0
   Minimum 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   MMXCore Routines 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Picture Package Filter 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Range 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Skewness 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Sumi-e 13.0
   Summation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   U3D 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Variations 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   WIA Support 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

Thanks very much for that lead, NormanPCN. I do have Auto Tone checked, though the rendered files in the example above do not have XMP sidecars. I will try unchecking Auto Tone even so, and post back when I see what happens.
Thanks again,
Kieren
EDIT: Bingo! I took Auto Tone off in ACR Preferences (in Bridge) and the non-RAW files immediately regenerated thumbs and previews. They now are indistinguishable from the PSD. There is still the very slight difference which I mentioned between the PSD and the CR2. While that seems odd, it is small enough to be relatively trivial.
Many thanks!
Thumbnail view w/o Auto:

I ran MacKeeper and demo'd my wife's iPhoto archive bigtime: RAW files appear corrupted and lotsa pix w/no thumbnails or "!" marks instead. Help!

I ran MacKeeper and demo'd my wife's iPhoto archive bigtime: RAW files appear corrupted and lotsa pix w/no thumbnails or "!" marks instead. Help!

Should I take it that recco'd means 'recommended'? Still have no idea what demo'd means in the context you use. I've often seem it as an abbreviation for 'demonstrate' but that makes no sense. The problem with idiosyncratic abbreviations is that other people don't understand them.
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD

Good afternoon ladies and gentlemen! My question concerns the impossibility to open RAW-files directly from the program Adobe Bridge. At the moment when you open a RAW-file from Adobe Bridge by double-clicking, RAW-file is opened only in Photoshop. In t

Good afternoon ladies and gentlemen!
My question concerns the impossibility to open RAW-files directly from the program Adobe Bridge. At the moment when you open a RAW-file from Adobe Bridge by double-clicking, RAW-file is opened only in Photoshop. In the settings Adobe Bridge - in "open RAW-files by double-clicking in Adobe Camera Raw» box is checked. When you try any changes in the settings Adobe Bridge system displays a message:
Bridge's parent application is not active. Bridge requires that a qualifying product has been launched at least once to enable this feature.
The entire line of Adobe products on my computer updated to the latest updates. Previously, a family of products Adobe Photoshop on your computer is not set. Computer - PC, Windows 7 Enterprises.

<moved from Adobe Creative Cloud to Bridge General Discussion>

Why the RAW files appear as exec files in CS4 Bridge?

I'm wondering how I can make my RAW files visible in CS4. I'm using the new iMac 10.8.3. Everything worked well in Tiger.

Canon 7D and 5D III
I believe you mean that only some files appear as 'exec', just a rounded rectangle icon with grey gradient and top left corn in green 'EXEC', the file extension shows '.CTG'. This is the file that sorts stuff on the CF card and you can safely delete this or simply ignore once the files have been imported on your computer.
If you check the file size of this icon you will see it has only a couple of 100 bytes, depending on the amount of files you have shot on one day or session so not even 1 kb while your Raw files will probably are around 15 or 20 MB in file size

Why does the bit debth of my raw file image different in my camera, in Brigde and in when opened in Photoshop?

I have a Nikon D700 12 megapixel full frame camera which has a 12 – 14 bit depth. I usually shoot images with the Nikon raw file format (NEF) with the color space setting at Adobe RGB (1998). When I select a photo to look at the details of the metadata in Adobe Bridge the bit depth is indicated as 16 and the color as RGB. Opening up the picture in Photoshop displays the long narrow detail line down the near the bottom of the screen. It indicates that the color is 8 bit but still Adobe RGB (1998).
Can someone please explain these fluctuations? This is still a NEF file I am referring to.
Thanks.

With Camera Raw open, you'll need to set the Color Space and Bit Depth is it to open as in Photoshop. See image:
Edit: Also, a raw file contains raw data - no embedded color profile. At least not that any programs, except Nikon's, will recognize.
Benjamin

D600 RAW files look different that D300 raw files

Please help me understand what's going on and more importantly, how to fix it.
RAW files from my D300 and my D600 look completely different. These are both NEF files, imported to Lightroom 4.2 using exactly the same import preset. I did NOTHING to either file, except that the D300 one was at 1/160 second and the D600 one was at 1/200 second, so I changed exposure on the D300 one by 1/3 stop so they would match. What I did was to shoot the D300 picture, then carefully changed the lens over to the D600 without moving anything, changed the D600 to DX mode to match the field of view and shot the same picture. The files should be essentially identical.
[b]This is from the D300:[/b]
[b]This is from the D600:[/b]
You will notice that the saturation on the D600 image is much higher. And it's much more yellow. The pictures were shot 2 minutes apart, from the same spot. Same lens, same camera settings.
First thing I did was to change the color temperature and tint to match: from 4150/+6 to 4200/+2. There was no visible change (I'm looking at them in compare mode in Lightroom on a calibrated monitor).
Next, I tried to change the D600 image to match the D300 one. I had to make substantial changes to both color balance and saturation of various colors, as well as contrast and black levels to get close. I'd give you absolute numbers but it varies from image to image. In this case, I had to drop the color temperature to 3500, for instance. The easiest way to do this was to use the white balance eyedropper on a grey area in the road.
I'm wondering if this is related to how LR handles the D600 NEF files. LR 4.2 says the D600 algorithm is 'preliminary'. Could this be part of it?
Anyone else here have a D600 and noticed the same thing?
Message title was edited by: Brett N

I'm not really good at using the right technical terms. Let me go back to basics.
Adobe came out with Lightroom 4.2 which has (preliminary) support for the D600. I installed it. I put the memory card from the camera into the card reader and Lightroom popped up because that's what I had set for the default for uploading photos. I told it which folder to store the image in (J:photos/2012-10/2012-10-05) and where to put a second copy (D:/px/lightroom import copies). Then I told LR to "save Current Settings as New Preset..." and I named it "D600 imports". Then I clicked "Import".
When I looked at the files afterwards in Lightroom, the sliders were all at zero except for the ones I noted before. I don't know why Lightroom chose 25 for the sharpening, but it did. Coincidentally, that's the same number it chooses for my D300 imports. I also don't know why it chose a color temp of 4200 and a tint of +4 (I was shooting on auto white balance).
Then I plugged in the card from the D300. I decided not to touch the preset (which still said "D600 imports") and I clicked "Import". The files went to the same folders and presumably, had the same sharpening and other slider levels applied.
Now when I look at the camera calibration in the develop module, under profile it says "Adobe Standard" on the D300 images and "Beta" on the D600 images, so Lightroom somehow knows which camera I used and sets itself accordingly.
At no time did my fingers ever leave my hand, and I did not modify, click on or even breathe on any of the Lightroom default settings. FWIW, my programming days are 35 years behind me and I'm a total non-tekkie user now. I wouldn't know how to 'hack' the D300 files if my life depended on it.
I know that conditions could have changed in the 98 seconds between the D600 shot and the D300 shot. Trust me when I say they didn't.
Regarding Noise Reduction: as far as I know, there are only two user accessible settings in the cameras: "Long Exposure Noise Reduction" and "High ISO Noise Reduction". Generally I have both of those on... but since these shots were at 1/200 sec and ISO 400, they wouldn't have kicked in anyway.
For WB, I used exactly the same spot on the road in both images. But you're right, I should use a grey target and I will next time.
To make the two pictures match as best I could tell onscreen (I changed the D600 image to match the D300 one), I had to change the temp from 4200 to 3500, the tint from +4 to +18, the exposure to -.33, shadows to -48, blacks to -19 (these are huge changes) and it still didn't look as good as the D300 image. It was 'harder' or 'crisper'. There was no mood, no softness to it. It's like looking at a "vivid" Jpeg vs. a "Standard" Jpeg, or a cooked HDR, if that makes any sense.
This isn't so much a complaint as a request for understanding, so that I know when I bring up an image, how to fix it. I shot a landscape and blew it up onscreen to 200%. I could see every leaf, every twig, every shadow's hard edge. That's not a bad thing, that's amazing: I just want to be able to control it.
Glenn

Why is my raw files from my Nikon D5300 completely overexposed in Apertue 3 but ok in View NX 2? Do I just have to wait for an update/patch from Apple?

Can anyone answer the above question?
Thank you.

Are you shooting RAW and using in-camera settings, like Active delighting in your Nikon? Then the RAW files will appear in Aperture very different from the JPEG previews that your camera is showing you, and also from the results in Nikon's own software.
Don't use in-camera setting, if you are shooting RAW, because Aperture will show you the naked RAW file, without any effects applied.
See Keith Barkley's user tip for a full explanation:
The Big Three: Setting your camera for the best Aperture RAW results
Just in case, that your images are not only overexposed but also desaturated , have a look at this thread:
Aperture corrupting RAW images

File appears different in arrange window and sample editor

I received a few AIFF files from someone Im working with: 24 bit, 44.1, same as I use. However, although they show up fine in the sample editor, in the arrange window they look clipped, as if they've been recorded too loud. This is making them very hard to edit. I've tried refreshing the overview in the sample editor, but with no success. Has anyone got any tips?

Does the file appear distorted visually, or does it also sound distorted?
In arrange, between the *Horizontal Zoom Slider* and the *Horizontal scroll arrows* you'll see a Waveform button with which you can adjust how "fat" the waveform is displayed. Clicking toggles it between the last setting and fully zoomed out. Clickhold to let the slider pop up.
!http://farm6.static.flickr.com/5179/5407362168_6d8e888c2a.jpg!

Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
Please help.
William

Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

Why are my raw files from my Canon 5D Mark III dim in Lightroom 4.3?

I am brand new to Lightroom, still reviewing various basic instruction videos, however I am adept in Photoshop CS5 and CS6. I have been able to import and move a file of jpegs but as I shoot jpeg/raw combo, the raw files were left behind in the original file. I can now bring them up, but they are dim and cannot appear to do anything w/them. I would like to move them to the file where I put the accompanying jpegs, but am having no success in finding an answer on how to do this. Nothing seems to activite to let me do this. Along w/this, I generally tend to work straight from camera raw files, the jpegs are generally not used, thus when LR encourages me to work on the jpegs, I'm not interested. I wish to process my raw files and only move to PS6 if I need to do some more intensive work. Can anyone offer a suggestion?

Here's my guess, based upon your description.
When the RAW photos are "dim", you are in the Import Dialog box, and the default operation of the Import is to not let you import a photo if it has been previously imported.
If that's the case, then you have misunderstood a basic operation of Lightroom. You import your photos once, and from then on, you access them via the Library Module, not the Import dialog. So, go to the Library Module and see if your RAWs are present or not.
Side comment: your workflow seems to be import then move. This is unneccessary, creating two steps for you when one will suffice. When you do the import, you also tell LR the destination where the photos should wind up (it's on the right hand side of the Import dialog box), and LR will do the import and the move in one step.

Why does my raw file show editing changes in the Organizer?

When I edit a raw (CR2) image and then save as a .tiff file and close, my original raw file also appears edited in the Organizer.
I have received advice telling me how to reset to default to get back my unedited CR2, but this is time consuming and I never had to do this in the past. How can I retain my CR2 in the Organizer after editing?

brevardlady wrote:
When I edit a raw (CR2) image and then save as a .tiff file and close, my original raw file also appears edited in the Organizer.
I suppose everyone expects the edits in the conversion of raw files to be shown in the organizer thumbnail... but that's your choice.
I have received advice telling me how to reset to default to get back my unedited CR2, but this is time consuming and I never had to do this in the past. How can I retain my CR2 in the Organizer after editing?
Instead of using 'Open', try using 'Alt Open'. The edited conversion is transferred to the editor, but the edits are not saved in the xmp sidecar filee. They are lost, and you are shown the default ACR settings, if that's what you want.

Why do G3 raw files show as "Unsupported Image Format" in Aperture?

I am moving towards shooting in raw, and as an experiment I imported some sample raw files from the publicly available text images on the Photography Blog. When I try to look at these images, I get a black screen with a warning triangle and the message "Unsupported Image Format". This happens for all the different raws, including some G3 raw files (.rw2). Oddly, it can read the EXIF metadata and has all the information about shooting settings etc. If I import the same files into iPhoto, it displays the images properly and allows editing, etc.
I have a workaround, which I've also tried with my Fuji X10 raws (still not supported on MacOSX), of running them through the Adobe DNG converter, and then looking at the dng files which seem to work fine. But it's a pain.
This has to be one of those simple "D'oh" things, but I can't see what I'm doing wrong!

Thanks Leonie, the second part revealed that I have been an idiot, although the behaviour is still surprising. The folder has a mix of DMC-G3 raws, Fuji X10 raws, and DNG files produced from both. For the Fuji X10 files, the DNGs produce images and the raws produce the "Unsupported file format" message. The latter is not surprising, the former a little surprising (as I've heard that DNGs only work when the associated raw works). The last two remarks don't directly address my problem (or perceived problem), but they perhaps set the frame for my expectations.
For the G3 files, when I look at it more closely, the G3 raws DO display correctly, while the G3 DNGs give "Unsupported file format". I had managed to fool myself into thinking it was the other way round (Aperture does rather hide the full file name).
So I was completely wrong, Aperture does support DMC-G3 raw, it's just it's DNG support that's a bit weird. However, it's on my side if I need to use X10 raws (via the DNG step). In fact so far I've given up the latter, as the noise levels are so much greater than in Fuji's in-camera JPEG conversion.
So, thanks very much for your help. Now I remember the first rule of system support: never trust what the customer tells you! (I know you're not really customer support, but I guess the same rule applies.) Thanks again

Why are my raw files being changed?

If I make changes in the Camera Raw window (i.e. change the exposure) and then "Open" it in Elements from the window, it applys those changes to the raw file, but the manual says "To open a copy of the camera raw image file (with the camera raw settings applied) in Photoshop Elements, click Open. You can edit the image and save it in a Photoshop Elements-supported format. The original camera raw file remains unaltered" - so why is it altering my original raw file?
Thankss

It isn't altering your file. Elements can't write to your raw file; it stores your changes in an xmp sidecar file, not in the original file. But if makes the reasonable assumption that the reason you made changes to your conversion settings is that you want to apply them. If you don't want to keep the changes when you open the file, then undo the ones you don't want to keep before opening the file into the editor. You are never opening your original raw file in PSE, just the converted copy.
To return to the basic elements conversion settings for the file, in the raw converter click the little lines to the right of where it says Basic in the converter window and choose Image Settings.
Here:
That's the mac version, but the location is the same in windows.

Why are my RAW files coming over grainy from Lightroom 5 to Photoshop CC

My images are transferring grainy over the last week. Any ideas why?

What camera raw file is it? Can you provide the EXIF data?
Here's the link to the possible answer:
Help! My RAW files are VERY grainy! :-(
I hope this helps.

Why do my RAW files appear different between programs?

Similar Messages

Maybe you are looking for