CR2 to .dng

Since my CR2 image files will open in Camera Raw, I am confused as to why I am converting them to .dng files.

99jon wrote:
The other big advantage of a DNG workflow is that you don’t have to keep upgrading the software every time you get a new camera. DNG is totally backward and forward compatible.
You may have to upgrade the DNG Conversion software when you get a new camera. However, the upgrade is free.

Similar Messages

CR2 to DNG. Any loss of quality or funcionality?

Hi.
So, the same questions arise with me but I can't get a definitive answer...
1. Adobe Bridge CS3 (and I presume CS4 as well) will "Convert to DNG" upon importing from your card reader. It's a simple checkbox option. Will this function convert 5DMK2 CR2 files to DNG properly or do I need to use the standalone Adobe DNG Converter because only Bridge CS4 will do it right?
2. If I process a CR2 file in ACR and make adjustments, then convert the CR2 to DNG, what happens to my edits saved in the XMP sidecar? Does it come along for the ride or is the XMP file now ignored forever?
3. Are there any features/benefits/downfalls in converting to DNG first then processing it in ACR? Anything that a CR2 file offers that a DNG file does not? Is there an ACR function that is now grayed out or something?
4. Is the quality of a DNG identical to the CR2 file? Same file size too?
5. Will presets I've created in ACR to run against CR2 files also run against DNG files?
6. If I convert a CR2 file to DNG and open it in, say DPP, then make changes such as sharpening and noise reduction, then open that DNG in ACR, are those changes seen or ignored?
7. People have said "Convert to DNG. Who knows how long you will be able to read CR2 files." I'm not sure how this statement holds water -- the DNG format was only released in late 2004. It's not a long-standing standard. I could make the argument that both CR2 and DNG files have an equal chance of becoming obsolete or changing drastically. Thoughts about this?
I've worked with raw files and a 40D for a long time now and my workflow is great for me: Import into Bridge --> Edit in ACR. If I get the new 5DMK2 I would hate to lose this functionality and I'm willing to upgrade to CS4, but why bother if CS3 Bridge's "Convert to DNG" function will convert it upon import, or if the new DNG Converter will do a whole directory in a few minutes... but I need to be sure that I don't lose any quality or functionality by doing this... and, if I decide to convert a whole year's worth of CR2/XMP files to DNG for long-term compatibility reasons, I need to be sure that all my XMP edits come along for the ride. If not, that's hundreds of hours of work gone... I might as well export to hi-quality JPG.
Thanks,
-Dave

> It's a shame that an edited CR2 file contains the edit information embedded in the file instead of within an XMP DPP can store the adjustment in a parameter file, but other raw processors would not recognize that. > Many times I'd like to use, say, DPP to apply NR and Sharpening, but I'd like to use ACR for the rest You seriously misunderstand how this works. We are talking about i parameters for the raw processor. Here is a crop from the XMP parameters: <PRE> xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/"> <crs:RawFileName>40D01784.CR2</crs:RawFileName> <crs:Version>4.5</crs:Version> <crs:WhiteBalance>Auto</crs:WhiteBalance> <crs:Temperature>2850</crs:Temperature> <crs:Tint>+21</crs:Tint> <crs:Exposure>-1.20</crs:Exposure> <crs:Shadows>1</crs:Shadows> <crs:Brightness>+10</crs:Brightness> <crs:Contrast>+50</crs:Contrast> <crs:Saturation>+15</crs:Saturation> <crs:Sharpness>50</crs:Sharpness> <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing> <crs:ColorNoiseReduction>0</crs:ColorNoiseReduction> <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR> <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB> <crs:VignetteAmount>+20</crs:VignetteAmount> <crs:VignetteMidpoint>50</crs:VignetteMidpoint> <crs:ShadowTint>0</crs:ShadowTint> <crs:RedHue>0</crs:RedHue> <crs:RedSaturation>0</crs:RedSaturation> <crs:GreenHue>0</crs:GreenHue> <crs:GreenSaturation>0</crs:GreenSaturation> <crs:BlueHue>0</crs:BlueHue> <crs:BlueSaturation>0</crs:BlueSaturation> <crs:FillLight>0</crs:FillLight> <crs:Vibrance>+15</crs:Vibrance> <crs:HighlightRecovery>28</crs:HighlightRecovery> <crs:Clarity>0</crs:Clarity> <crs:Defringe>0</crs:Defringe> <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed> </PRE> LuminanceSmoothing and ColorNoiseReduction are the parameters for noise reduction. If DPP would do the parameters in this or some other but metaformat, ACR or other raw processors could interpret the setting. However, the result would be ACR noise reduction. In order to get the DPP noise reduction result, you have to convert the raw file in TIFF or JPEG by DPP.

Intermittent "Unsupported image format" message with either CR2 or DNG

I am seeing "Unsupported image format" messages once files created by a Canon EOS 1Ds Mark iii (+stored in Canon's CR2 file format or when the same file is converted to Adobe's DNG file format+) have been imported into Aperture.
Some files will import and be viewable. However, most of the time the files are not viewable. This occurs even after updating Aperture to 1.5.6.
Is anyone else seeing problems with CR2 or DNG files created by Canon EOS 1Ds Mark iii?
Has anyone see a solution?

I think Support is confused with the Canon camera models.
10.5.1 supports 1D Mk III, but only 1Ds Mk II.
(http://docs.info.apple.com/article.html?artnum=306835
http://www.apple.com/aperture/raw/cameras.html)
I don't believe that 10.4.11 supports anything that 10.5.1 doesn't support. In fact, the docs at http://docs.info.apple.com/article.html?artnum=306297 say "Adds RAW image decoding support for the following cameras: Panasonic Lumix DMC-FZ50, Leica V-Lux 1, Olympus E-400, Olympus EVOLT E410, Olympus EVOLT E510, Canon EOS 40D" (the 1D Mk III came in the 10.4.10 update.)

Color change in RAW file from CR2 to DNG

I recently got a new Canon camera, the 60D and when converting from the CR2 file format to the DNG format using the latest 7.2 version of DNG Converter I notice a color change between the original image (CR2 file) to the new DNG file. Once I open it into Camera RAW (version 4.6 with CS3) the color issues go away and if I save it as a JPEG the color issue is no longer a problem but if I were to resave the DNG file to another DNG file it reverts back to the color changed view in MacOS. Is this something that I need to be concerned with for future use of the RAW files or is it a display issue in MacOS and iPhoto. The DNG file also shows the color change in iPhoto. Below are the two screen caps.
RAW CR2 file straight from the camera
Converted RAW CR2 to DNG using DNG converter
This issue only appears to occur in preview mode or in iPhoto.
Thanks,
Nathan

Try changing the CAMERA’S color-profile settings from sRGB to Adobe RGB or from Adobe RGB to sRGB, switch to the opposite one, and see if the previews are any closer for new CR2 you convert to DNGs. The theory is that the preview is in terms of the camera Color Profile setting (sRGB vs Adobe RGB) and when the image is converted to DNG that profile is lost for iOS to see, and it is defaulting to the wrong profile.
In the end , what matters is how Camera Raw converts the file.
Also DNGC 7.3 is the latest version: http://www.adobe.com/downloads/updates/

AE stopped to open cr2 and dng files, PS still works

Hi
I have a mac book pro 16gb OS 10.9.2 and worked over 6 months with AE and Photoshop CS6 opening and working with cr2 (Canon 5dmk3 raw) and dng (converted from magic lantern) files.
all went well. For no apparent reason (maybe any kind of update?) my AE does not recognize these files anymore. They just show up grey and not selectable in the open/import dialog.
I can still open them using photoshop with the well known dialog box for raw files. so somehow the raw importer seems to work? Tried adobes dng converter 8.4 but converted files do still not open.
Did someone encountered the same problem and found a solution? Thanx very much for your help!
Roger

See this:
http://helpx.adobe.com/bridge/kb/acr-84-bridge-cs6-metadata.html

Canon CR2 to DNG issue. DNG files too big!

I'm experiencing what I believe may be a few issues whilst converting from Canon CR2 RAW files to the Adobe DNG format.
(Camera is Canon 5D Mk2)
For example, I have a folder containing CR2 RAW files which size = approx' 410MB. But when I perform the DNG conversion to a new folder, the total file size of that folder containing the converted DNG images is over 800MB! Does this sound correct?
I thought converting to DNG reduced the overall file size of the RAW image somewhat?
For info, I'm using the latest version of the converter with no JPEG preview or embedded original RAW file selected.
THANKS

When converting to DNG, is "Embed original Raw File" selected?
If it is, it will double the size of the DNG file.
I have not seen any reason to select this option, and the only time that I have seen reference to it (in Better Digital Camera, I think), it was suggested that this option be turned off.

Converting CR2 to DNG via script?

Hello,
I want to create a script which converts several CR2 files as DNGs (later to create a drag'ndrop-button for this script).
It's not possible to record this steps/these steps. Probably because of the "Camera Raw" module which Photoshop uses after opening a CR2 file.
Thanks.
Carlos

You might be better using the stand-alone free DNG converter from Adobe..
http://www.adobe.com/products/dng/
With this you can do a folder of raw files.
You could even create a batch file do do the convert IE:
Create a .bat file with something on the lines of..
For %%a in (c:\CR2\*.cr2) do "C:\Program Files\Adobe\Adobe DNG Converter.exe" -d c:\DNG %%a
This will process all cr2 files in Folder C:\CR2 and convert them to DNG putting them in C:\DNG
Another possibility would be to create a script passing the command line to the app.system() command (CS4/5)

ACR conversion of CR2 to DNG = 14-bit Not 16-bit :Why?

If I open one of my Canon 5D Mark II CR2 raw files (several in different folders and taken at different times were tested) in ACR (7.2) and save it as a DNG file (with no ACR edits) Bridge shows the DNG as being a 14-bit file whereas if I save it as a PSD file it has a 16-bit depth. Exactly the same thing happens if I convert the CR2 file to DNG using the Adobe DNG Converter (7.2 version). You might answer that as a raw file, it does not yet have a bit depth because it has not been rendered, and the 14-bit description really has no meaning. But if that is the case then Bridge's reporting that all my original CR2 files are 16-bit is also meaningless.
Why is there a difference in the reported, and presumeably actual, bit depths?
Interestingly, if I then open the "Bridge reported"14-bit DNG file in Ps (CS6) and save it as a PSD, the new PSD is shown, presumeably correctly, as being 16-bit.
Please help a poor confused soul.

Andrew_Hart wrote:
But that can't be the whole story.
Well, as it relates to Bridge, is is...as Eric said, the bit depth reported to Bridge is non-standard unless the file has been processed as DNG.
Andrew_Hart wrote:
So if the DNG shows the correct bit depth stored in, as you say, "the standard TIFF header location", why can't the CR2, now rendered as a TIFF, do the same?
Because...Bridge isn't reporting the correct info (which I tried to explain and you seem to refuse to accept)...
Andrew_Hart wrote:
This logic seems to me to be strengthened further by the fact that, as we all know, there is no viewing of a raw file without rendering. So when viewing a preview/thumbnail of a DNG in Bridge, you aren't actually viewing the DNG at all, you are viewing a preview/thumbnail of something which has been demosaiced, had a tone curve applied to it, et cetera, namely, I presume, another TIFF. If that TIFF can report its correct bit depth to Bridge, then why not the TIFF rendered from the CR2 as well?
Because, well, the headers are not standard and Bridge kinda reads the wrong thing with many raw/rendered files (unless you convert to DNG).
Not sure why this is so hard to understand...Bridge is a browser app that tries (but often fails) to display the "right thing". But often can't due to the file's metadata.
This really is not a thing to dwell on...you may think there is a tempest is a teapot, but it means nothing. Again, these are not the droids you were looking for (do you even understand the reference-Google it).
This whole thing is a red herring...you may as well give it up. Seriously, you are not getting anywhere here...raw is raw and you should generally ignore Bridge for most reports...because, well, Bridge isn't accurate because the standards for reporting bit depth are not standard...that's what is causing the differences. [Edited to keep this thread a friendlier place.]
Message was edited by: TerriStoneCHL

Failure to convert CR2 to DNG

I am not able to convert my CR2 files to DNG.
DNG converter is saying there is an error parsing the files.
what does this mean?

Walt,
I suppose it is a matter of what you become accustomed to doing. I have a shortcut to my CF card on my desktop. All I do is double click on that shortcut, highlight all of the raw files and drag them to the DNG converter. Then I specify the folder on my hard drive where I want the DNG files to be saved. That's all there is to it. Sometimes, when the images are more important to me, I will save the original raw images to a DVD. But a lot of the time I don't even keep them. But then, that is the way I have chosen to work.
There are more reasons to upgrade to Photoshop CS3 besides just getting support for a new camera. ACR in Photoshop CS3 has been significantly enhanced. There are a number of new controls. But in order to get all of the changes it will be necessary for you to download the latest version of ACR. New controls for added in ACR 4.1. And then the cameras are continually added. It is a good idea to check for updates often to make sure you have the latest.
Another alternative that you might want to consider is Lightroom. This Adobe product has all of the same controls that ACR 4.x has, as well as some other nice features. A lot of people prefer using Lightroom. On initial purchase, it is quite a bit less costly than Photoshop, but would probably cost you more than it would cost to upgrade to Photoshop CS3. I prefer Photoshop. But there are trial versions of both programs that you can download and try for 30 days to see what you think.
In the meantime, my suggestion would be for you to try the DNG converter. You can start working on your raw images immediately. There really aren't that many hoops to jump through. At least give it a try. You will still have your original raw images and you can at least evaluate the workflow. The DNG converter is usually packaged with the latest version of ACR. All you have to do is copy the DNG converter to your desktop and just forget about the rest. Try a conversion and try opening them with what you have just to see if it works. But I can tell you that once you have an opportunity to use CS3/ACR you will feel extremely restricted when you have to revert back to CS2 for some reason.
Just one last thought. Some have expected they can save money by purchasing Photoshop Elements because it uses ACR. But many of the new controls are not available in Photoshop Elements even though it uses the very same plug-in.

Convert CR2 to DNG/JPEG

When converting *.CR2 (Canon D600) to DNG and Jpeg have vertical white areas on the picture.
What is cause?
I use Lightroom, Photoshop and Adobe DNG converter
The CR2 is good in the Viewer on the PC to Win 8.1.
When I use Contenta software converter to JPEG then is result good.
Via Adobe products is not good.
Operating system Win 8.1

Hi,
Which version of photoshop, lightroom and the dng converter are you using?
Which operating system?
Do you see the vertical white areas in both lightroom and photoshop?
Could you post a scrrenshot?

Is there a "one-touch" way to convert to my existing library to DNG?

Is there a "one-touch" way to convert to DNG?
My Aperture library currently has three types of files: JPEG files taken with point-and-shoot camera going back for years, (ii) RAW (NEF) files made with a Nikon D60, (iii) RAW (CR2) files made with a Canon G9, and (iv) RAW (DNG) files I have shot recently.
I am interested in converting all the non-DNG RAW files (NEFs and CR2s) into the Adobe DNG file format. I understand that the format has a smaller file size (than the original RAW file) and that it is "lossless" (unlike converting to JPEG). So, in addition to "standardizing" my file-types, it will also reduce my overall library size (in GBs).
So, the question is: is there a way to take my existing Aperture library and, through some (hopefully free) combination of scripts and programs, convert all the RAW files to DNG automatically and without having to export each one from Aperture and them import it again. That is, I want a solution that will look at each file and ignore the JPEGs and DNGs, (ii) convert the NEFs and CR2s into DNG, and (iii) move the original NEF/CR2 files to a folder (just in case)?
This is not an problem going forward, because I can easily just import as DNG to begin with ... but its an issue for a few thousand images in my library.
Any ideas? Also, anyone think this is a crazy bad idea?
Thanks,
~B

Do you find that using Aperture to "import" the pictures (e.g., using the import function on Aperture and pointing it at your memory card) gives better results than using the DNG converter to "import" (e.g., by selecting the camera memory card and saving the conversions to disk, then importing those DNG files into Aperture)?
Not the way it works. The camera memory card does not have conversions on it, it has RAW (or JPEG) image files.
IMO generally most useful to help keep drives underfilled and fast (drives slow as they fill) is to manage by Reference ("referenced images") as in the workflow outline below where Master images can live anywhere. However with small changes similar workflow could be applied to Managed Masters.
I feel pretty strongly that card-to-Aperture or even camera-to-Aperture handling of original images puts originals at unnecessary risk. I suggest this workflow, first using the Finder (not Aperture) to copy images from CF card to computer hard drive:
• Remove the CF card from the camera and insert it into a CF card reader. Faster readers and faster cards are preferable, and Firewire is much preferable to USB2.
• Finder-copy images from CF to a labeled folder on the intended permanent Masters location hard drive.
• Eject CF.
• Burn backup hard drive or DVD copies of the original images (optional recommended backup step).
• Eject backup hard drive(s) or DVDs.
• From within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location." This is called "referenced images." During import is the best time to also add keywords, but that is another discussion.
• Review pix for completeness (e.g. a 500-pic shoot has 500 valid images showing).
• Reformat CF in camera, and archive originals off site on hard drives and/or on DVDs.
Note that the "eject" steps above are important in order to avoid mistakenly working on removable media.
Alternatively, does anyone actually use (or recommend) Nikon-branded software for any step in this process? If your camera shoots JPG (as all mine did till a few months ago), it does not matter ... but does the RAW thing change that equasion?
Yes RAW changes the equation. Folks who want the very best NEF conversions will use Nikon Capture NX2 but the interface *****. Personally I find Aperture very good for the D2x.
Good luck!
-Allen Wicks

What is the use of preview JPEG embedded in DNG?

I tried converting a CR2 file to DNG, choosing different size JPEG preview, including full, medium and none. The converted DNG file all look the same when I open them in LR3. So the image we see in the library and develop module is not the JPEG embedded in DNG??? What is the JPEG preview used for then?

I never was able to see any preview in Windows 7, whether I use Canon's CR2 or DNG.
You need WIC codecs for the given format. If you have the codecs installed Vista/Win7 will be able to display thumbnails in Explorer and previews in the built-in preview apps. As far as I know there are free codecs available from manufacturers for most raw formats (Nikon, Canon, DNG), but most (all?) are 32-bit only. There's a commercial third-party 64-bit DNG codec available.
So what application on Windows 7 takes advantage of the preview exactly?
I use the free IrfanView. It does use embedded previews from all raw files, both proprietary and DNG. It can be configured to demosaic too.

Convert RAW Files in Your Aperture Database to Adobe DNG Files

The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files. In the example below I am assuming that your Aperture Library has ARW and CR2 files. These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library). The steps are:
1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu. From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
2. Drag the "Masters" folder out of the Package and place it on your Desktop. The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files. Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc. In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above). The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above. Do NOT put the .DNG files in your search criteria. Select all the files found in the search and move them to the Trash. This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
7. Select the Finder Window containing the Aperture Library Package Contents.
8. If there is a file called "ApertureData.xml" then open it with a text editor. Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search). Make sure you cover all the file types incorporated in your particular system. Save the "ApertureData.xml" file.
9. Traverse to the Database/apdb directory. Select the "BigBlobs.apdb" file and open it with a Hex editor. In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/). Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex. In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window. In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search). Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files. Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish. This process works because:
1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source. Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source. In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.

A rather involved method, David.
I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
I convert selected raw files this way - without manually patching the Aperture Library:
Export the originals of the raw images that I want to convert.
Run dng-converter.
Import the converted originals back, flag them, and move them to the project they came from.
Sort the project by capture date, so that identical images are show side by side.
Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
Regards
Léonie

Aperture lack of DNG support unfortunate

It's difficult to understand why Aperture does not offer support for Adobe DNG files.
DNG/RAW files are being used by some camera manufacturers that I work with, and they contain a wealth of metadata as well as the broadest range of image data, including "altitude", which is now very useful in my professional work.
This lack of support has forced me to go back to Lightroom, and to reconsider that application as my primary media catalogue and editing application.

A JPEG saved as a DNG isn't really a DNG file.
It is true that Aperture doesn't have "comprehensive" DNG support. It doesn't support linear DNGs, and it doesn't support some of the newest DNG extensions that Adobe has added (lossy compressed DNGs, etc.). I don't know the exact version of the spec that Aperture supports.
But do note that DNG is a lot of things. It's a fairly comprehensive spec that has many versions, with lots of different things. Aperture does support many DNG properties, but not all of them. If you want the latest, greatest, most comprehensive DNG support, then Adobe will have it, as it's their specification.
I personally just use the RAW files that come out of camera - whether they be NEF, CRW, CR2, or DNG. I _never_ convert my camera RAW files into DNG, because that actually strips some data (in my case, focus point informatin from CR2 files that Aperture can display, is removed from the converstion to DNG). There are many long-winded discussions on the "value" that DNG provides, and I don't subscribe to them. It provides no legay-proofness today that's unavailable other places.

.CR2 Files not recognized by Photoshop, Bridge, or iPhoto

I am a photographer shooting in Raw with my Canon Rebel T1i. I used to Import the images into iPhoto for editing and organization. But a few moths ago while importing the images (usually shows a preview of the photos) It just showed black... Then when i tried to edit the photos they wouldn't load. I can see the thumbnails inside of iPhoto but when I go to edit them... they wont load. So I tried to open the images using Bridge&Photoshop... I imported new images from my SD card into Bridge... the thumbnails of the images don't show up. It just shows white with a shutter on it... and it says 'file name'.CR2
When I double click on the images (supposed to open the image in Photoshop RAW ) Photoshop opens, looks like its about to start... then says "photoshop does not recognize this type of file."
Im not sure what to do... I've been looking around on different forums and it looks like I may be missing a Driver or some kind of Plug-in... But i dont know how to find out what Im missing or where to get it... Any help is greatly appreciated. Thanks!

Keith_Reeder wrote:
…or convert its CR2s to DNG using the free Adobe DNG converter.
Keith, Keith, Keith…
What part of not supported don't you understand?
If a camera is not supported by the latest version of ACR, it will not be supported by the free Adobe DNG Converter either.
ACR and the DNG Converter are always released in tandem and they support the same camera models.

CR2 to .dng

Similar Messages

Maybe you are looking for