Sporadic failure dng conversion

I've recently upgraded from Windows XP (SP3) to Windows 7 Ultimate 64 bit. At the same time I upgraded from 2 gb of RAM to 4 gb. Since the upgrade I've been experiencing random errors in DNG conversion. I usually convert to DNG inside Lightroom 2.5 by selecting the files to be converted and then use the command Library...convert to DNG. This process randomly freezes/hangs. I've tried using the standalone DNG converter from Adobe (5.5), but this results in random errors of DNG conversion (about 10 % of files fail conversion). The RAW files I'm trying to convert are from a canon eos 350 d. I've never had an issue using Windows XP. I've tested the RAM with Windows Memory Diagnostic - no errors are reported. I'm not experiencing other issues.
I would appreciate feedback. Has anybody experienced similar issues? Any ideas as to what could be causing the problem?

I solved my problem - it was caused by a conflict between Lightroom 2 and the virus software Eset Nod32. After uinstalling the latter, I have not experienced issues with DNG conversion.

Similar Messages

DNG conversion fails sporadically with Get Photos From Camera

Camera: Canon 40D and 5D
XP SP2
CS3
Bridge 2.1.1.9
ACR 4.4.1
DNG Converter 4.3.1
Importing my files to Bridge using the Get Photos from Camera (GPFC) option results in sporadic DNG conversion failure. There's no pattern, just a lump of files that don't get converted at the end of the process. It's very frustrating because I have to manually go back and find the files that failed and use GPFC option again. Even then sometimes it fails again!
I'm attached to using the GPFC option instead of the standalone DNG converter because GPFC lets me automatically make a backup file to another disk and adds a template. But even when I use DNG Converter to import the files off my card, DNG fails for some of the files. Purging the cache only works half the time and for some of the files.
Is there any solution to the GPFC problem? I've seen people have similar problems, but with no real conclusions...
Any ideas? Thanks in advance.

Ramon,
No, I have tried purging/refreshing before and it doesn't help, because the un-converted CR2 files are just skipped over and put in the same destination folder as the successfully converted CR2 files (to DNG). I thought it might be a memory issue, but I never have any other applications open. As a test, I purposely opened some other applications to see if MORE CR2 files would be skipped, but the amount of files skipped was still random.
My "DNG Conversion Settings," accessed through the Get Photos From Camera dialogue, is set to:
Jpeg Preview: Medium Size
Compressed (Checked)
Preserve Raw Image (Checked)
Embed Original Raw File (UN CHECKED)
Could some of my Edit>Preferences>Cache options be overloading things and causing skips? I use the default settings because I wasn't confident with messing around with the cache.
Thanks

DNG conversions not opening

I dusted off an old Toshiba laptop that has a copy of CS4 Photoshop and the newest DNG Conversion software (v8.8). Pointed the DNG at a folder of RAW files (Olympus ORF), converted them, opened them in ACR and saved the files that are now .dng files in Bridge...but CS4 won't open them, says it doesn't support this file type. How can Adobe Photoshop not open an Adobe file type? I thought DNG made all RAW files backward compatible for Photoshop going back to the beginning of time. Any ideas, suggestions, solutions?

I got a couple of sample raws and converted them on the mac side using the 8.8 dng converter and they seem to open on both photoshop cs4 on mac and windows xp
Did you check to make sure both your photoshop cs4 versions have camera raw installed and are updated to camera raw 5.7?

DNG Conversion Fails in Camera Download

I've been using Photoshop CS4, Bridge and ACR for about a year. I was sold on the Adobe rationale for converting to DNG and have been doing so using the convenient check box on the Photodownloader screen. It has worked fine the entire time - until now. Suddenly that no longer works: although the DNG conversion box is checked Bridge only downloads the raw NEF files and reports at the end that it the DNG conversion failed on all of the photos that were downloaded.
So - here is what I've tried:
- Rebooted my Windows XP computer ( dual core - which has 4GB of RAM). Same results - no conversion
- Reinstalled Photoshop CS4 - and everything on the disk. Same results - no conversion
- Downloaded version 5.7 of Camera Raw (just found out there is a 5.9). However that seems to only update camera profiles - and doesn't change the version that displays on the Camera Raw preferences menu: 5.0.0.178. Same results - no conversion.
- Finally I downloaded the free DNG converter. It works, but I would much prefer to have the download program work
Any clues to solving this will be greatly appreciated.

Film4Now wrote:
…version 5.7 of Camera Raw (just found out there is a 5.9)…
??? !!! Where?
Film4Now wrote:
… the version that displays on the Camera Raw preferences menu: 5.0.0.178…
That proves you did not install 5.7 correctly and you failed to remove the old 5.0 plug-in.
Wo Tai Lao Le
我太老了

LR and DNG conversions from NEF

Just received a batch of Nefs and corresponding dng conversions from a client. I immediately noticed that there was a serious white balance difference between these pairs--LR shows the Nefs at 5600 and the dngs at 7100. Is this typical. I have worked with dngs a few times, but this is the first set of images that I have seen with side by side conversions. Is this typical? Neither the dngs or nefs have been previously edited. I don't normally work with dngs--only when a customer insists.
Very curious about this WB difference. Any explanations from the color gurus here? TIA

I was aware that the numbers were relative and would likely be different, but in this case the images are visibly very different--I just gave the numbers to indicate what LR saw them as. When the difference is between 5600 (NEF) and 7100 (dng) one sees a big difference between the cool NEF and the warm dng on the screen. This difference is seen systematically in a batch of about 75 images. LR shows no metadata differences except the WB reading. Could this have resulted from a dng conversion in an older dng converter?

DNG conversion fail and Photoshop will not open my NEF files (Newbie question)

Two part question. First, I just recently installed photoshop CS4 to my (windows vista) computer and I go to upload NEF photos to bridge and I check the box that says "Convert to DNG" and when it finishs uploading it says "Files successfully copied, However, DNG conversion failed." It says it everytime and I don't know what to do about that.
Second part: I try to open my NEF files in photoshop it says "Could not complete your request because it is not the right type of document." I am using a Nikon D90 and I don't know if that has anything to do with this. I apologize if this question is in the wrong forum, I am new to this and I thought maybe camera raw had something to do with this at least.
Thanks for any help

You need to update your Camera Raw plug-in to either version 5.2 or 5.3RC, as well as the new DNG converter. They are available on the Adobe download page, and there are complete instructions for installation available there.

Embed Original Option for DNG Conversion

I have switched over my digital workflow now to DNG. I would love to see Adobe add an option to embed the original RAW file to it's DNG conversion in Lightroom. I was hoping that someone from Adobe would read this and take this suggestion into consideration...if not in v1.1, maybe in a future version. Thank You!

Ok, I am a novice here, but I am wondering:
What is the advantage to embed the original RAW into a DNG?
I believe I understand the value of the DNG: that it provides a single format for RAW data that simplifies the job software needs to do to render the RAW data, rather than needing to translate a zillion file formats. Also it removes the need for sidecar XMP files. OK, that sounds like good things.
So, assuming one already has a good backup of the RAW stowed away somewhere, and also assuming that the RAW-to-DNG converter is competant to do what it is supposed to, Why would one want the RAW embedded in the DNG?
One other question: would embedding the RAW file double the size of the DNG?
Thanks

"There was not enough memory" error, DNG conversion.

I have CS4 and I like to convert my files to dng, however, I can't seem to do it on multiple raw files, because after fifty or so, I get the message, Incomplete because 'There was not enough memory.'
I originally thought this may have had something to do with Bridge and trying to save way too many files through acr in bridge, since bridge is a bit of a ram hog at times and has cache issues, so I tried using the Adobe DNG Converter standalone application, and the same thing happened.
I am trying to convert just over a thousand images, NEF, about 15M each. I have several hundred gigs of HD space, GeForce 8600GT video, 2G ram, WinXP SP2.
I track my actual memory usage and adobe dng converter has never used more than 6MB of memory.
Anyone know why I can't convert my files?

I want to try to reproduce this problem, a few questions...
Which version of the DNG converter did you use (the latest is 5.5)?
What camera produced the NEFs?
What NEF settings did you use, if any, compressed, uncompressed, 14-bit, etc.?
What DNG conversion settings did you use?
Did the NEFs already have settings (XMP sidecar files?). If you did have settings, what kind of settings, just basic adjustments, or did the settings also include localized corrections, spot heals, etc.?
Thanks,
David

Did my NEF to DNG conversion work properly?

I had read that when I convert to DNG in Lightroom (v4), the file sizes will drop by about 20% (I checked the check box for compression). I'm converting from a batch of 16-bit NEFs I created when scanning slides using the Nikon LS-5000 scanner. Those scans and files were created with Nikon Scan 4.0. After doing the conversion in Lightroom, the DNG file sizes are around 3MB-17MB. The original NEF files were about 135MB. Where in the world did all my data go? I'm concerned that the conversion to DNG threw away a ton of the original data. How is that much of a reduction possible? I'm hoping that there wasn't some catastrophic problem during the conversion, as I also checked the check box to delete the originals after the conversion is finished.
The image quality seems to be okay when looking at the DNG files in Lightroom.
Thanks,
Jay

I scanned at the full resolution (4000dpi, I think) of the LS-5000. The DNGs all appear to have their full original resolution, 5782x3946. This was one of the first things I thought about, too, but the resolution doesn't appear to have been changed any.
Jeff, upon re-opening the Convert Photo to DNG dialog box, I see that I did check "Use Lossy Compression." I spaced. I belived I was telling it to use lossless compression (I was assuming that no compression would have been used otherwise). So the conversion makes them into a high-quality JPEG, basically (but still 16-bit)? If I don't check that, will the DNG conversion use lossless compression, or no compression at all?
These slides are from a few decades to several decades old, all shot by my dad. I'm wondering if I would even see any degradation from using the lossy compression option. 135MB per image seems WAY beyond what is necessary to maintain the quality of these slides, so I would like SOME compression, but don't want to see any clearly visible signs of quality loss. Any words of wisdom welcome.

DNG Conversion - preview size

In lightroom when converting files to DNG on the pop-up screen is the Choice: Size of the Preview file: Large, Medium or Do not create.
1. what is the file size for large and medium?
2. What is the impact of NOT creating a preview? When I've tested NOT creating a file I can still open the file in my lightroom grid and loupe view. I can also view it in Windows vista Preview when right clicking on the image file on my hard drive.
3. Where do these "Previews" come into play?
4. Also, I have noticed that if I convert a JPEG file to DNG the file size is about 4x larger. Should I reserve DNG for only my raw files such as my .mrw and .cr2? Has anyone else observed an increase in file size after DNG conversion?
5. What is the deal with DNG anyway? I havn't seen the big manufactures like Canon with the new EOS-1D Mark IV and Nikon's new D3s,include the DNG as a file format selection on their cameras. What do they know that I don't, about DNG?

1. what is the file size for large and medium?
Medium is screen sized, the other option is full sized, not large.
2. What is the impact of NOT creating a preview? When I've tested NOT creating a file I can still open the file in my lightroom grid and loupe view. I can also view it in Windows vista Preview when right clicking on the image file on my hard drive.
Lightroom generates it's own preview. It's just handy for portability, so how the file looks is available to programs that can't understand the internal settings.
3. Where do these "Previews" come into play?
Lightroom will use them in Library intially. Like I said above, it's handy for other programs for managing and printing with the Lightroom settings, especially with a full sized preview.
4. Also, I have noticed that if I convert a JPEG file to DNG the file size is about 4x larger. Should I reserve DNG for only my raw files such as my .mrw and .cr2? Has anyone else observed an increase in file size after DNG conversion?
You should. The JPEG doesn't get converted to a Raw, it's just convenient to have all DNG. The increase happens because Lightroom removes the JPG compression AFAIK.
5. What is the deal with DNG anyway? I havn't seen the big manufactures like Canon with the new EOS-1D Mark IV and Nikon's new D3s,include the DNG as a file format selection on their cameras. What do they know that I don't, about DNG?
Nikon and Canon have proprietary information in their Raw files. Yes it's rather a pain when they release a new camera. Sticking to a DNG format would really help with this, if they came on board. DNG is just a way of providing a common Raw format.

Is DNG conversion during Tethered Shooting Possible?

Previously, using a Canon 5D MkII and lightroom 2 I could shoot to a hot folder which Lightroom would watch, convert the images to DNG and add them to my catalog.
I love that Tethered Shooting is now part of Lightroom but unfortunately I can't seem to find anywhere to set up a recipe or parameters for the import and can only convert the files to DNG in post.... bit of a waste of time isn't it?
Am I missing something.... I sure hope there will be more options in tethered shooting in the final release. I have had to use Capture One to do Tethered shooting on Jobs but hate that I can't import the corrections into Lightroom. I was really hoping to circumvent C1 and save a bunch of time.
If it's not there, please add DNG conversion on the fly and keep my files in LR rather than C1

Right now, when tethered, Aperture is preventing files from being written to the CF card in the camera (which I definitely don't want)
You have no control over that behavior. It's the way Aperture works when you are shooting tethered.
If I understand your question, it sounds like you are trying to use Aperture as a replacement/supplement for the LCD on the back of your camera. If so, is there a HDMI output on your 5DMKIII? Maybe you could attach that output to a monitor as a solution.
Message was edited to add question about HDMI.

DNG conversion failed

system: Vista Ultimate x64 version 6 SP2, 8gb. ram, Video ATI Radeon HD 3600.
CS6 version 13.0.1, Bridge 5.0.2.4 x64, Camera raw 7.0.0.308
When trying down load files from D7100 with Adobe photo down loader, I get this message " files successfully copied. However DNG conversion failed" Last week the "blend if" from a layer in PS would not work and gave me this "could not complete request because of system error". I tried many things to resolve issue including uninstall & reinstall (CS6) using my disc. Finally deleted custom brush set that I'd got off the web and that solved the problem. I think I need a minimum of camera raw 7.4 to work with a D7100 and a maximum camera raw 8.3 to work with Vista. Adobe appication manager has been updated and says everything is updated. Photo help menu says it running 7.0. I tried removing the content of C;\users\appdata\local\adobe\aam updater\1.0 I tried to down load directly from Adobe down load list Camera Raw (7.4 then 8.3) no change. Tried another uninstall and reinstall, still the same. I seems like I lost something in the first reinstall.

You can try this camera raw 8.3 update and see if it works:
http://swupdl.adobe.com/updates/oobe/aam20/win/PhotoshopCameraRaw7-7.0/8.3.52/setup.zip
If not, this one should:
(read the whole page)
Adobe Camera Raw Help | Camera Raw/DNG Converter 8.4 on Mac OS 10.6, Windows XP, and Vista

DNG conversion 6.6 works on my XP system, but fails to see files on my Vista OS.

DNG conversion 6.6 works on my XP system, but fails to see files on my Vista OS. Same goes for older versions of DNG. I use the same setup of security on both systems.
Can anyone help?

Run an Apple Hardware test. That may provide a clue:
http://support.apple.com/en-us/HT201257
Note that an error free AHT is not definitive.
If you have all of your data backed up or an external clone HDD, I would try erasing the internal HDD, reinstalling the OSX and then upgrading the software to 10.6.8.
Ciao.

Error LNK1123: failure during conversion to COFF

hello,
I'm new to the sdk and I'm trying to open the sample projects to understand what's going on here,
the problem is that when i try to build the project(for example the SDK_File_Import project)
i get the error:
Error
1
error LNK1123: failure during conversion to COFF: file invalid or corrupt
why is that?
please help
thank you very much in advance
jony

Hello,
This topic is a bit old, but I have the same problem. My english isn't perfect so I don't understand everything in the pdf guide.
I just started, and I would like to build the Export project, which is in the Exemple directory. (I took the cs6 premiere pro release 2)
I did this part of the guide : "On Windows, to specify where you want the built plug-ins to go, set a user environment variable
(right-click My Computer > Properties > Advanced > Environment Variables > User variables)
called PREMSDKBUILDPATH to the desired path (e.g. “C:\Program Files\Adobe\Common\
Plug-ins\[version]\MediaCore\”)", and I also put the exemple directory on “C:\Program Files\Adobe\Common\Plug-ins\[version]\MediaCore\”.
Then, I opened the SDK_Exporter file with visual studio 2010 (from “C:\Program Files\Adobe\Common\Plug-ins\CS5\MediaCore\Examples\Projects\SDK_Exporter\"), and tried to debug it with the x64 debugger.
I obtained this error : "LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt"
May someone help me to build this?
Thanks for your help!

Sporadic failure of DNG conversion using Bridge

For the past 2 years I have been happily using the Adobe DNG (stand-alone) software to convert the NEF files from my D200. I routinely do this at "ingestion" as recommended in an article by Bruce Fraser. I have never encountered a single problem with this procedure. Recently I made a small change to my routine: In Adobe Bridge I chose File>Get Images From Camera. I specified the file type as DNG. After the transfer was completed a notice appeared to inform me that conversion to DNG had failed in xx images. This generally amounted to about 10% of the files in the folder, and in an apparently random manner. These files were copied over to my hard drive, but remained as NEF files.
Can anyone tell me why this may be happening? Is there a cure, or should I simply go back to my original method?
Thanks/Mike

Ramon,
Thanks for your reply and the information. The stand-alone dng converter is installed on my computer, but certainly not in the Adobe-prescribed default location. (Can you tell me where it belongs on a PC system running XT-home?) Presently it is not even on the same disc as the Adobe applications. Which makes it all the more puzzling why using Bridge to get images from camera results in converting most, but not all of the images to dng. I am running Bridge 2.1.1.9
What I find even more curious is that the coders of the software were thoughtful enough to present one with an information screen which appears after the transfer and tells you how many images failed to convert to dng. Suggesting that they anticipated this type of error but providing no explanation of why it occurs.
Thanks/Mike

Sporadic failure dng conversion

Similar Messages

Maybe you are looking for