Dng converter damage

As part of my importing images procedure I have the freestanding dng converter (6.7.0.339) convert all my cr2 files to dng because, among other things, dng files are smaller than the cr2 files they derive from. Having downloaded and converted a batch of 2000 or so images from a recent holiday, LR4.1 complained that one of the images had suffered damage, which manifested as a small square area with multi-colored horizontal lines and blotches. The natural assumption is that the original cr2 was corrupt, but it wasn't. Maybe the converter had slipped up because it had a heavy load and I was doing other stuff on the computer while downloading. So I did the conversion again; and the selfsame damage occurred again, exactly as before. This would point to a bug in the converter?

How are you determining that there is no damage to the orginal file? Likely the damage is there, but the thumbnail you are looking at is the embedded JPEG that was generated by the camera and has little to do with the raw data that the DNG converter will use to create a new copy. Have you tried importing the original CR2 file into Lightroom and seeing whether you get the same reaction? If it works, try using LR to do the DNG conversion.

Similar Messages

  • Adobe DNG Converter 7.4

    I downloaded Adobe DNG Converter 7.4 to upgrade Elements 10 to accept RAW files from my Nikon D7100 but it won't. The reason given is: The file format is damaged or is in a format that cannot be included in Elements Organizer. It does accept jpg files from the same camera and same card. Can you help with this problem?

    You can convert a whole folder of raw images in one click. See this quick video tutorial:
    You Tube click here for DNG Converter tutorial

  • Lens Profile Deleted By DNG Converter

    I'm currently having to convert some of my Nikon .nef files into .dng files so that Capture One Pro 8 will read them.
    I'm using the Adobe DNG converter 8.7.1
    After the conversion the lens profile is no longer readable within Capture One Pro 8.
    I assume (probably wrongly) that the lens data is being deleted by the converter?
    Ideally I'd like to have Capture One read all of my .nef files but quite a few of them aren't readable due to (I'm informed) them being damaged. Photoshop and Lightroom can read these files but not Capture One!
    If I could find something that would repair the .nef files I'd be much happier due to the problems I'm getting with the dng converter.
    Thanks for taking the time to read my small rant...

    Ok, your second sentence is what I was asking. 
    What camera model? 
    For DSLRs, PS/ACR and LR use external profiles, so are not actually reading lens profile information from within the raw file, and instead or just reading the lens model information and matching up an external profile with the lens model.
    For mirrorless cameras PS/ACR and LR there is a built-in profile (not sure if in the raw or in the software) that PS/ACR and LR applies automatically and this correction cannot be turned off.
    I don’t know anything about how C1 works.  Do you know if C1 has external profiles or does it only apply conversions that are actually specified in the raw files, which woudn’t be more DSLRs. 
    I guess what I’m asking is about your terminology.  Is what C1 can’t see the lens profile information in mirrorless camera raws (if such information exists in reality, I don’t know) or is what C1 can’t see the lens model information that it would need to determine what lens profile to apply?

  • Can't open .CR2 files in PhotoShop CS5, Camera RAW or Adobe DNG Converter

    Firstly take note I shot these with a Canon EOS 450D (or Rebel XSi)...
    I see a lot of answers speaking about having the most up to date version of the Camera RAW Plug-in.
    I have a similar issue with my .CR2 files... I cannot open them in Camera RAW because it tells me that my camera model or make is not supported by the Plug-in, and so I was directed by other forums to just try converting the .CR2 files to .DNG. I already had the Adobe DNG Converter (version 6.5 I believe), so I tried this. It too told me that my files or camera make were not supported.
    However, I have always been able to successfully both open my .CR2 files AND convert them to .DNG. I had not updated anything on my camera nor on my Adobe programs and for some reason this last attempt to open RAW files failed me... I have no idea what change would have led to it. Luckily I shot in both RAW and Large JPG but I certainly don't want to rely on my JPGs of course... Any idea why this problem might have arisen now if it had always worked easily in the past?
    Thanks!

    Are these the same exact files you've opened before that you cannot now open?
    Or are they newly copied files (camera or CF card to computer)?
    Can you not open ANY Canon 450D files, even those you find online and download?
    What I'm getting at with these questions is to try to eliminate or suspect data corruption of the files on your disk.
    Exactly what versions of the various tools do you have, specifically (don't guess - go check)?
    -Noel

  • How do you stop DNG Converter from embedding Adobe's ACR default settings instead of custom settings?

    I notice that the new version of Adobe DNG Converter (8.6, and maybe earlier) appears to place Adobe's ACR defaults in the converted file.  Thus, the converted files open up in Bridge with an indication that they already have settings made, and, hence, ACR does not apply the custom camera settings.  One has to Clear Settings first in Bridge, then open in ACR.
    This behavior is new, perhaps to 8.6.  But it's presence defeats the purpose of having custom Camera Defaults.
    Is there any way to prevent DNG Converter from installing settings?

    ssprengel wrote:
    What do you mean by “custom camera settings”?  Do you mean you’ve changed the Camera Raw defaults for a particular camera and those aren’t being seen until you do a Reset?  Or do you mean some sort of Nikon-settings that Adobe never looks at?
    Also at what point in the workflow are you converting these files, just after copying them to your hard-disk and before touching them with any other Adobe software, or after they’ve been adjusted in Nikon software, or after they’ve been adjusted in Bridge/ACR, initially as NEFs?
    I mean my custom camera defaults that are set by the Save New Camera Defaults for a given camera.
    My workflow is to take my original raw files first into Adobe DNG Converter.  I then open the folder in Bridge.  At this point I notice that my original raw files remain unaltered (there is no "settings" icon in the top right corner – circle with two lines and up-arrows – in the image's thumbnail), but the converted dng's (otherwise untouched and unopened in ACR) have a "settings" icon.  When I open the original raw file in ACR, it opens using my custom camera defaults.  When I open the otherwise virgin dng in ACR, it opens using the Adobe defaults (the same defaults that would be employed if no custom camera default had been set).
    This behavior is new.  DNGs formed by earlier versions of the DNG Converter did not apply any settings to the converted file, and when they opened in Bridge, they were given the custom camera settings.
    In order to retain the old (and proper) behavior, I now have to take the just-converted documents into Bridge, select them, and immediately apply Develop Settings/Clear Settings.  That gets rid of the settings that have been installed by the DNG Converter (as well as the "settings" icon on the thumbnail).
    I notice there is a new feature in Adobe DNG Converter 8.6, namely, a panel-specific toggle between the settings and the default settings. This indicates to me the likelihood that Adobe has been making some alterations with the settings that is having unintended consequences.  It clearly is not proper for DNG Converter to be adding (installing) settings, because that prevents the custom camera default settings from being applied, and hence defeats the purpose of the custom camera default settings.

  • Hi,  I've just purchased and installed an upgrade from Lightroom 4 to 5.  It doesn't seem to handle raw files authored with a new Nikon D750 camera.  I spoke to the sales rep about this and he gave me a link to the 8.6 DNG converter page with instructions

    Hi,  I've just purchased and installed an upgrade from Lightroom 4 to 5.  It doesn't seem to handle raw files authored with a new Nikon D750 camera.  I spoke to the sales rep about this and he gave me a link to the 8.6 DNG converter page with instructions to download.  8.6 only works with Mac OS 10.7-10.9, according to the page.  I'm running Yosemite, Mac 10.10.  Please can you tell me my options?  Lightroom 4 worked beautifully with my older cameras' raw files so I would like to continue using the application.  What should I do?  How soon will Lightroom 5 be able to deal with raw files from a D750.  Many thanks, Adam.

    Until the next version of Lightroom is released, you need to use the DNG Converter version 8.7RC to convert your RAW photos to DNG and then import the DNGs into Lightroom.

  • CS5 DNG Converter for Nikon D750?

    Hi, Is there a DNG converter for CS5 for the Nikon D750?  I only see CS6 or CC.  Thanks!

    The DNG Converter 8.7 RC in the CS6 branch at Adobe Labs will work to make the new camera NEFs compatible with your older ACR plug-in for CS5. 
    http://labs.adobe.com/

  • How to make windows 8.1 compatible with dng converter 8.1?

    I have installed the DNG Converter 8.1 so that I can view/edit RAW files on Photoshop Elements 12, but Windows 8.1 states "the source folder does not contain any supported camera raw files".  I have an Sony Alpha 6000 (version 8.4), and have moved the RAW files into a folder on my C drive.  DNG Converter won't work even if I run it on Windows 8, is there no way to make Windows 8.1 compatible with DNG Converter 8.1? 

    From that faq:
    http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    I see that you need the DNG converter 8.4 to convert Sony Alpha 6000 raw files.
    Download that version of the DNG converter to replace your version 8.1.
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh for Mac
    Adobe - Adobe Camera Raw and DNG Converter : For Windows for Windows

  • DNG Converter 6.4 does not recognize any RAW files

    Hi,
    I have updated DNG Converter from 6.2 RC to 6.3 and 6.4. DNG Converter 6.2 RC from Adobe Labs recognizes all my RAW files (Canon PowerShot S50, PowerShot SX1IS, EOS 400D). The official releases of 6.3 and 6.4 do not recognize any RAW files of these cameras.
    I select a directory, where the raw files are located, but DNG Converter tells me that no files where selected. With 6.2 RC, I select the directory and everything just works fine.
    What's wrong with this picture?
    atb,
    MOS-6502

    Ahh, I forgot:
    System is Windows Vista Ultimate 32bit, patched up to date.
    atb,
    MOS-6502

  • How can I get the updates for Photoshop CS5 to download to my new Macbook Pro where I have already installed CS5 from my original disk? I have tried many times over 2 days. I was able to successfully download the current version of Adobe DNG converter.

    How can I get updates for Photoshop CS5 to download to my new Mac book pro where CS5 is already installed from my original disk? I have tried many times over 2 days. I get the same error messages re downloading error. I successfully downloaded the current version of Adobe DNG Converter & it installed perfectly. Help please!

    The Adobe auto updater is highly unreliable.
    You need to look for and download the update yourself and then manually apply it as per the detailed instructions on the download page:
    Adobe - Photoshop : For Macintosh
    ~~~~~~~~~~~~~~~~~~~~~~
    Please note that the Adobe Camera Raw plug-in must be updated separately, after you have updated Photoshop:
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh

  • What's the Difference in Conversions done with ACR vs. DNG Converter?

    As an experiment, on my PC workstation I just converted a set of 40 Canon CR2 files with both the free DNG Converter 6.5 and Camera Raw 6.5 (both 32 bit and 64 bit).  With Camera Raw, I dragged the files to Photoshop, then used the [Save Files] button and chose .dng format.  I chose "Medium" thumbnails in both cases.
    The DNG Converter and Camera Raw 32 bit took almost twice as long as Camera Raw 64 bit (56 seconds vs. 33 seconds).
    The .dng files produced by Camera Raw ended up larger than those by the DNG Converter, about 9% larger on average.
    A file comparison shows that the differences are all near the start of the file, and that the latter 80% of the data is identical in all three cases.
    The DNG converter files are more different from the Camera Raw files than the two different sets of Camera Raw files are from eachother.
    This leads me to ask these questions:
    1.  Why are the 32 bit DNG converter app and Camera Raw 32 bit plug-in so much slower than the Camera Raw 64 bit plug-in?  I have an 8 core machine, and in general don't see a 2:1 difference between equivalent 32 and 64 bit code.  It appeared by watching Task Manager that all of them were using more than one thread to do the work.
    2.  Are there any plans to release a (much faster) 64 bit DNG Converter for Windows x64 users?
    3.  Is there a practical / usability difference between the .dng files generated by Camera Raw vs. those generated by the DNG converter?
    -Noel

    ssprengel wrote:
    You can see how many CPU cores are being used by watching the performance tab with core performance separated, as long as nothing else much is going on.
    Not really.  Particular threads do not normally maintain a long-term affinity for particular cores, so the usage gets spread around as Windows does its multitasking stuff and what you normally see is just activity across the board, as seen in the screen grab below (that was DNG Converter running).  Only inasmuch as the overall percentage is higher than 1/n (where n is the number of cores) can we infer a certain amount of multithreading.
    And yes to both of you - every setting that I could find is perfectly consistent across the board, including compression.  And as I mentioned before, the embedded previews are coming out exactly identical, both in size and color.
    -Noel

  • Loupe in Bridge doesn't display DNG images created using DNG Converter correctly. Why?

    I have noticed recently an anomaly in Bridge when viewing DNG files that are created by converting my Nikon NEF files to DNG using the DNG converter. Specifically, when clicking on the preview image of a DNG file, in order to open the loupe, the 100% image seen in the loupe remain fuzzy, whereas when clicking on a preview of the original NEF file the 100% view in the loupe is sharp and clear.
    I am using DNG Converter version 4.6.0.3, and it also occurs when using version 4.4.1. I am using Bridge version 2.1.1.9.
    I have no reason to believe that Bridge is at fault, since the loupe function does work properly when viewing the NEF file. It would seem that there's a problem in the DNG conversion.
    However, despite this anomaly seen in Bridge, when I open the DNG file in Camera Raw, it is perfectly normal at 100% or any magnification.
    I have tried re-setting the JPEG review size in the DNG converter, but that makes no difference.
    What's going on here? I don't want to keep both the NEF and DNG versions, for reasons of space, but I'd like the loupe to work correctly. Help, please?

    Try to recreate the thumbnails for that folder.
    Use the latest version of the converter (5.4)

  • Adobe DNG converter is corrupting NEF files. The color is way off and it's not the camera white balance.

    I was using the converter for a few months and it was working fine. Now it will convert the files, but the color is really messed. I know it is not the white balance, because the same files convert fine to TIF files through Nikon's software. I am using this converter for Nikon d610 NEF files. Here's a sample DNG and the same image in TIF. Can anyone help? Thanks!

    When you use the DNG Converter to make a DNG from an NEF, the DNG Converter applies the default Camera Raw settings.  When I open your DNG it looks fine, but when you open it, it looks off.  That is because you've some how set your Camera Raw defaults to have a bunch of customized settings specific to a particular picture, instead of having them all be normal settings.  Below you'll see what Photoshop is saying the settings of the DNG-Converted-JPG are, with the non-defaults marked in bold.  The main problems are the WB being custom and a bunch of HSL setting changes.
    Here is what Photoshop reports that the JPG was created using:
          <rdf:Description rdf:about=""
                xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
             <crs:RawFileName>hug_8290_0215_1.dng</crs:RawFileName>
             <crs:Version>6.0</crs:Version>
             <crs:ProcessVersion>5.7</crs:ProcessVersion>
             <crs:WhiteBalance>Custom</crs:WhiteBalance>
             <crs:Temperature>5732</crs:Temperature>
             <crs:Tint>+26</crs:Tint>
             <crs:Exposure>0.00</crs:Exposure>
             <crs:Shadows>5</crs:Shadows>
             <crs:Brightness>+50</crs:Brightness>
             <crs:Contrast>+25</crs:Contrast>
             <crs:Saturation>-4</crs:Saturation>
             <crs:Sharpness>90</crs:Sharpness>
             <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
             <crs:ColorNoiseReduction>25</crs:ColorNoiseReduction>
             <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
             <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
             <crs:VignetteAmount>0</crs:VignetteAmount>
             <crs:ShadowTint>0</crs:ShadowTint>
             <crs:RedHue>0</crs:RedHue>
             <crs:RedSaturation>+11</crs:RedSaturation>
             <crs:GreenHue>0</crs:GreenHue>
             <crs:GreenSaturation>0</crs:GreenSaturation>
             <crs:BlueHue>+12</crs:BlueHue>
             <crs:BlueSaturation>+2</crs:BlueSaturation>
             <crs:FillLight>0</crs:FillLight>
             <crs:Vibrance>-6</crs:Vibrance>
             <crs:HighlightRecovery>0</crs:HighlightRecovery>
             <crs:Clarity>0</crs:Clarity>
             <crs:Defringe>0</crs:Defringe>
             <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
             <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
             <crs:HueAdjustmentYellow>+1</crs:HueAdjustmentYellow>
             <crs:HueAdjustmentGreen>+5</crs:HueAdjustmentGreen>
             <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
             <crs:HueAdjustmentBlue>-9</crs:HueAdjustmentBlue>
             <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
             <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
             <crs:SaturationAdjustmentRed>-2</crs:SaturationAdjustmentRed>
             <crs:SaturationAdjustmentOrange>+14</crs:SaturationAdjustmentOrange>
             <crs:SaturationAdjustmentYellow>+25</crs:SaturationAdjustmentYellow>
             <crs:SaturationAdjustmentGreen>+26</crs:SaturationAdjustmentGreen>
             <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
             <crs:SaturationAdjustmentBlue>+32</crs:SaturationAdjustmentBlue>
             <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
             <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
             <crs:LuminanceAdjustmentRed>+40</crs:LuminanceAdjustmentRed>
             <crs:LuminanceAdjustmentOrange>+13</crs:LuminanceAdjustmentOrange>
             <crs:LuminanceAdjustmentYellow>+3</crs:LuminanceAdjustmentYellow>
             <crs:LuminanceAdjustmentGreen>+15</crs:LuminanceAdjustmentGreen>
             <crs:LuminanceAdjustmentAqua>+3</crs:LuminanceAdjustmentAqua>
             <crs:LuminanceAdjustmentBlue>+4</crs:LuminanceAdjustmentBlue>
             <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
             <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
             <crs:SplitToningShadowHue>231</crs:SplitToningShadowHue>
             <crs:SplitToningShadowSaturation>32</crs:SplitToningShadowSaturation>
             <crs:SplitToningHighlightHue>45</crs:SplitToningHighlightHue>
             <crs:SplitToningHighlightSaturation>33</crs:SplitToningHighlightSaturation>
             <crs:SplitToningBalance>+74</crs:SplitToningBalance>
             <crs:ParametricShadows>-39</crs:ParametricShadows>
             <crs:ParametricDarks>-7</crs:ParametricDarks>
             <crs:ParametricLights>-15</crs:ParametricLights>
             <crs:ParametricHighlights>+14</crs:ParametricHighlights>
             <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
             <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
             <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
             <crs:SharpenRadius>+1.0</crs:SharpenRadius>
             <crs:SharpenDetail>25</crs:SharpenDetail>
             <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
             <crs:PostCropVignetteAmount>-24</crs:PostCropVignetteAmount>
             <crs:PostCropVignetteMidpoint>50</crs:PostCropVignetteMidpoint>
             <crs:PostCropVignetteFeather>97</crs:PostCropVignetteFeather>
             <crs:PostCropVignetteRoundness>0</crs:PostCropVignetteRoundness>
             <crs:PostCropVignetteStyle>1</crs:PostCropVignetteStyle>
             <crs:PostCropVignetteHighlightContrast>0</crs:PostCropVignetteHighlightContrast>
             <crs:GrainAmount>0</crs:GrainAmount>
             <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
             <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
             <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
             <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
             <crs:CameraProfileDigest>51B4314CF8312BA027EF3FC60481FB35</crs:CameraProfileDigest>
             <crs:HasSettings>True</crs:HasSettings>
    To fix the problem you're gonna need to reset your camera raw defaults:
    And then be careful when saving new camera raw defaults with the menu item just above, that your image has the camera raw defaults applied to it, except whatever small change you want to be the new default.

  • Bug in Adobe DNG Converter 7.2 RC

    Adobe DNG Converter 7.2 RC (for Windows) keeps missing files. When pointing it at a folder containing many raw image files to convert (and providing a different folder as the destination for the converted files) then it won't always find all the raw files. There are no files besides the raw image files in the folder ... umm, with the possible exception of the hidden Bridge cache files, .BridgeCache and .BridgeCacheT. The destination folder initially is empty.
    When this happens then I have to re-do the conversion, with the same source and destination folders selected and the Skip source file if destination file exists check-box ticked. Then DNG Converter will collect and convert the raw image files it missed in the first run. So far, I never had to perform a third run, but I frequently have to do two runs to get a folder's raw files converted. For example, in my most recent attempt there where 966 raw image files in the source folder (of the type Sony ARW, along with XMP sidecar files), and DNG Converter found 954 files in the first run and the remaining 12 in the second. The bug also occurs when the folder contains mixed types (Sony ARW and Leica DNG in my case). There is no error message or any other kind of hint that something is going wrong, so you have to check the result manually. The status line at the top of the Conversion Status window teling the number of files to convert will report the number found; if that's less than the number of raw image files available then you'll have to start a second run when the first is finished. It's easy to miss the problem, and then you may end up with some files not converted!
    So far, the bug inevitably occurs when there are many raw image files in the source folder—i. e. more than 400 (and up to 1,200). When doing several attempts on the same source folder then the set of missed files will vary, i. e. it's not always the same files that get missed. It is not even always the same number; the number of missing files varies between, say, 5 and 20, i. e. approx. 0.5 - 5 % of the number of files in the folder. It seems that if the number of raw image files in the source folder is small (say, less than 300) then the bug does not happen. In my last successful attempt, I converted 263 files of type Leica DNG, and DNG Converter found them all on the first attempt.

    ssprengel wrote:
    Does it matter what hard-drives the files are on, whether they are missed?
    No, it doesn't. There are two physical SATA hard-disk drives installed in my machine, and the error occurs no matter where the source files are. It also does not matter where the destination folder is. Usually it's on an external 3.5" drive connected via USB 2.0, but I also tried the internal drives, to no avail.
    ssprengel wrote:
    Does an older DNG Converter also miss files?
    Gosh! To my surprise, yes it does! I just tried DNG Converter 7.1, 6.7, and 6.6, and they miss files just like 7.2 RC does. They didn't back when they were current ... or at least, I never noticed.
    This seems to indicate that the culprit is not DNG Converter 7.2 RC but my machine. But then, my machine and the hard-disk drives (including the external 2 TB 3.5" USB drive) are the very same I am using for years now. I didn't change the operating system; it still is Windows XP SP3. I am also still using the same cameras as I always did for years now. The only significant things that changed recently (besides DNG Converter) are Photoshop 13.0.1 and Bridge 5.0.1.

  • Adobe DNG Converter can't recognize any files

    Hi All!
    I'm new here and would very  much appreciate help.
    I am running a Mac OS X 10.04.11 and would  like to open .CR2 files (native file from my Canon 500D) in PS4      / Bridge  CS4. My problem is that although I have downloaded the Adobe DNG Converter and Camera Raw 5.1  update as described  here: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4057,  the DNG Converter can't recognise any files at  all (they are greyed-out  when I go to select any folder). I also followed these steps from the aforementioned link (well at  least I hope I did it right, I found the reference to step 4 slightly  confusing):
    To install with Adobe Creative  Suite 4 or Photoshop CS4:
    Automated installation on Mac or Windows®:
    1. Select "Updates..." from the Help menu
    2. Follow the on-screen dialogs to download and  install the latest  available Camera Raw update  
    Manual installation on Mac:
    1. Exit Photoshop CS4 and Adobe Bridge.
    2. Open the Finder.   
    3. Navigate to the root of the local disk (not the user's home  folder).   
    4. Navigate to: (Please read directory carefully)
    Library/Application Support/Adobe/Plug-Ins/CS4/File Formats
    5. Move the existing plug-in to another location (for example, a new  folder on your desktop). Ensure you keep this version in case you need  to revert back.
    6. Copy the Camera Raw plug-in, Camera Raw, from the download  into the same folder as in Step 4.   
    7. Launch Photoshop CS4 or Adobe Bridge.   
    Is that version the right one for CS4?
    Only Finder and the Canon Software can preview my .CR2  files, Photoshop still gives the message: "Could   not complete  your request because Photoshop does not recognise this  type of file." and   Bridge only shows me a generic RAW thumbnail. This message also  appears in PS when I double-click on the  Camera-RAW.plugin. I also  restarted my computer,  but that didn't fix it.
    Can  anyone help me out please? I'd urgently need a solution.
    Thanks in advance!

    I now uninstalled the older 5.1 version and  instead installed the DNG Converter 6.3 separately and it works  perfectly.
    About the Camera Raw 5.6 update: I also downloaded the plug-in  (which I think should be the last version CS4 supports) and can now open  my .CR2 files in PS, Bridge previews them too. :-)
    Is it advisable to keep both, .CR2 as well as .DNG files? Why is it  that my .DNG files are lighter than the native .CR2?
    Thanks again!

Maybe you are looking for