DNG Converter 5.6 crashes
I just downloaded the DNG Converter 5.6 Release Candidate for Mac. I have been trying to convert photo files from my Canon EOS 7D and the application crashes every time I try to convert. I tried converting them right from a Firewire 800 card reader. Then, I copied the files onto the computer and converting them from there: more crashing. I guess the beta could use a little more polish.
Can you please supply a 7D raw file that is causing the DNG Converter 5.6 RC to crash on your system? You can use YouSendIt.com and post the link here (or email it to [email protected]).
Similar Messages
-
I have had no success getting DNG converter 8.6 to work on a 64 bit Windows 8.1 system. As soon as I click on folder to select files the window grays out and locks up.
MartyHave you tried just clicking on the folder containing the raw files, but not double-clicking to open? That is what you have to do. I don't know if that's causing the error or not. But you just choose the folder. You don't open the folder to choose the files.
-
PS/Bridge not recognizing raw files - HAVE updated DNG Converter & Camera RAW
Had to re-install my Adobe CS3 due to hard drive crash.
Now that I have re-installed, Photoshop & Bridge won’t recognize my raw files.
I HAVE updated my Adobe Camera Raw (3 times in the last hour), and my DNG Converter (4 times in the last hour). Nothing works. Any ideas?If in photoshop cs3 you go to Photoshop>About Plug-in and click on the words Camera Raw, which version does it show?
Since photoshop cs3 can only use up to camera raw 4.6 and the EOS 5D Mark II requires at least camera raw 5.2, cs3 won't open those files directly without some help.
http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
The 4.6 camera raw plugin update for photoshop cs3
Adobe - Photoshop : For Macintosh : Camera Raw 4.6 update
You could use the 8.7.1 dng converter to convert the files to dng copies which then bridge should see and photoshop cs3 should be able to open.
Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.7.1
Camera Raw: How to use Adobe DNG Converter - YouTube -
DNG Converter 8.7.1 not converting RAW files. Windows 7.
DNG Converter is not recognizing any RAW files hence it will not convert anything to DNG. Tried the download a few times and different versions but nothing is happening. I just had the computer repaired and iI have lost the ability to convert CR2 and IIQ files. Previously, before the computer crashed I was able to do so. At the recommendation of the service tech, I went from Windows 8 to 7, since I hated 8 and other machines I work on are 7.
It probably is a simple fix but I have no idea what needs to be done. Please advise.update your lr to lr 5.7.1
your ps can still be updated, but i can't determine why you're showing an old cr and you've stated you've already updated ps to 13.0.1.3
Downloadable installation files available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
Photoshop Elements: 13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
Lightroom: 5.7.1| 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5
Contribute: CS5 | CS4, CS3
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'. -
DNG-converted 10D files too large, not recognizable in Aperture
[I've posted this message in the Adobe DNG forums after doing some searing around for an answer. I thought some others here might be doing the same thing and could comment]
While importing some of my older Canon 10D-shot images into Aperture, I noticed something curious about the DNG-versions of the files. They're much larger than I would expect and Apple's Core Image processor doesn't appear to be able to read them. For example, on one file the original CRW file is 5.3MB. The DNG conversion without the embedded original is 17.4MB. This is consistent across all my 10D converted files.
Apple's Preview app, as well as anything else based on the Core Image processing code, can't read the DNG, but it can read the original CRW. I know that Apple has botched parts of the DNG specification, but since the converted DNG is twice the size I would expect it to be, this seems like it might be a problem with the DNG converter itself. Anyone else seeing this with rev 3.2 of the converter?
BTW, the files open up in ACR just fine.
G5 1.8G SP, 1.5M RAM Mac OS X (10.4.3)Sorry for the noise. It turns out that my prefs had gotten munged overnight when the DNG converter crashed and had returned to one of my test configurations where I was converting the RAW files to linear. Aperture, as is well understood, doesn't handle the de-mosaiced format well at all.
This was user error. -
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 -
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 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-6502Ahh, I forgot:
System is Windows Vista Ultimate 32bit, patched up to date.
atb,
MOS-6502 -
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?
-Noelssprengel 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) -
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.
Maybe you are looking for
-
Hi, So I have had a macbook for a while and quite a bit ago I had a problem with iChat. It was unable to log me in one day, it would constantly try and try until I got the error that I had attempted too many times. I'm not quite sure what is wrong. I
-
I'm running Frame 8, unstructured, on Vista. Also running Distiller 8. I have a book file and was creating individual PDFs of the chapters doing Save As PDF on each chapter. After three weeks of doing this Frame starts to hang when creating the PDFs.
-
I'm using Studio 11 on Solaris 10 (sparc) and have come accross a linker warning. ztty.o is C code, compiled like this /opt/SUNWspro/bin/cc -Xt -KPIC -g -DSunOS -DZERROR_H -I/vobs/zplus/src/include/zcl -I/usr/dt/include -I/usr/openwin/include -c -o
-
CS2 camera raw plug-in no longer working
Issue description Summary: I currently have CS2 installed on my Dell desktop. In September, I noticed that I could no longer open raw files and I looked on the Adobe site, found the plug-in, downloaded it and all was well. Just the other day I went t
-
Change Materail PO text in PR/PO
Hello, I have maintained Material PO text in Material Master.After creating PR/PO it gets copied in PR/PO automatically. My requirement is after changing the Material PO text in Material Master it should get copied to the old PO which is already save