DNG converter question

I apologize for asking this question in this forum. But the DNG forum is not very active it seems. I have seen this problem mentioned in the past, but paid no attention to it and I can't find any of the references. I have no convert button on my DNG converter dialogue. Windows 7, DNG converter 8.4, 8 GB RAM. I have used this utility in the past without problems. I don't use it very often but was experimenting this morning

I posted a similar question quite a while ago, and what I learned was that Bridge has a DNG converter built in, but it's using ACR to read the file before it can convert. So you need ACR support for your camera.
AFAIK there's no way to point Bridge to a standalone DNG converter.
I suggested an updateable DNG converter plugin for Bridge, don't know why nobody listened...I thought it was an excellent idea
As for the metadata, you just have to try. I don't know if it can write metadata when it can't read the file.

Similar Messages

DNG converter questions

1. What is the recommended way to store images? Convert all to dng and discard the camera raw or keep both? If keep both I double my storage needs.
2. Under preferences there is a compression selection. I know it says lossless but is it really, and do many people use it?
3. Are there any other advantages to using dng over raw within the editing process?
TIA

1. If you are going to convert to DNG, you should keep the original raw images. Not all raw converters are capable of editing DNG files. As far as storage space is concerned, burn the original raw images to a DVD, or get an external hard drive. After a while you might realize that all your images are not needed.
2. If there is any loss of quality, I will be surprised if you will be able to actually see it. As far as I'm concerned, it is truly lossless. In my opinion most images are not so unbelievably priceless and irreplaceable that this should be of any concern whatsoever.
3. "Other" advantages? Is there really an advantage at all in the first place? That is my question. With my camera there is no reduction in the size of the image in DNG format. If you are using Camera Raw you don't have to concern yourself with XMP files because all the changes are stored within the DNG itself. But in Lightroom that isn't a concern because you only have XMP files if you specifically want them. So, I guess the real question for you is, is there ANY advantage to using DNG? Personally, I don't see any real advantage to converting.

Question about DNG converter in Bridge CS4

Hello,
I just installed Photoshop CS4, When I updated, it downloaded a hefty update (199 megs), so my setup now is:
Win XP pro
Bridge 3.0.0.464
Camera RAW 5.7
Photoshop CS4 11.0.2
My Camera is a Panasonic Lumix FZ150 ( 2011 vintage)
I have downloaded the Adobe DNG converter 6.6.0.261
Every thing seems to be working fine so far, except:
In Bridge when I "get Photos from Camera" the DNG conversion doesn't work. When I use the standalone converter it works fine.
From reading past material on this forum I am assuming this is due to the fact that Bridge is older than my camera, and doesn't recognize the format.
The questions:
1. Does Bridge have its own built in DNG converter that is not upgradeable separately?
2. If 1 is correct, is there a way to point Bridge to the location of the standalone converter so the work flow can be optimized.
3. Since Bridge is not doing the conversion, but only importing the files, does the "Apply metadata" section of that window actually do anything? Should I bother to fill in any of those boxes?
Thanks for any help.

I posted a similar question quite a while ago, and what I learned was that Bridge has a DNG converter built in, but it's using ACR to read the file before it can convert. So you need ACR support for your camera.
AFAIK there's no way to point Bridge to a standalone DNG converter.
I suggested an updateable DNG converter plugin for Bridge, don't know why nobody listened...I thought it was an excellent idea
As for the metadata, you just have to try. I don't know if it can write metadata when it can't read the file.

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

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

I have been using DNG converter from the beginning. But suddenly the bottom part of the interface has disappeared where the Convert button is. What's happened

Very strange. Why would it disappear after all this time

Very good question. In fact I have just replaced my monitor with a higher resolution screen. However it is all irrelevant now as I have cured it. I uninstalled the old versions of the Converter and installed the latest version 9. All works ok. The hardest part was finding where the DNG Converter had squirreled away on my computer. Eventually found it but I couldn't get access to it through the Control Panel.
Many thanks for your reply

I have Lightroom 3 and have downloaded the DNG CONVERTER 8 7 1 to be able to open my CR2 files from my new canon 7d, however It still will not open my images

I have Lightroom 3 and have downloaded the DNG CONVERTER 8 7 1 to be able to open my CR2 files from my new canon 7d, however It still will not open my images

Fab ! Thanks so much. Sorry if these questions are rudimentary but i have been out of the game for a while and getting back into it, i have aged and technology has expanded! Am trying to re learn and keep up ! I appreciate the help

Does DNG Converter 5.6 Alter WB Info of DMC-LX3 RW2s?

I have converted a Panasonic DMC-LX3 generated ".RW2" to DNG using DNG Converter 5.6 for the exclusive purpose of being able to open it in the current version (2.1040) of Rawnalyze. The conversion prodeeds OK, and I am able to view the resulting DNG in Rawnalyze. It is my (humble, and barely-informed) understanding that the DNG Converter 5.6 performs de-mosaicing upon the RW2. However, I am uncertain as to:
(1) Whether or not the DNG Converter 5.6 has altered any White Balance information contained in the original DMC-LX3 RW2 image-file; and
(2) Whether any such alterations as described above in (1) result in an alteration of the "Shot WB Coefficients" (that I am assuming represent the DMC-LXW "raw" mode White Balance Scales) displayed when Rawnalyze is in Histogram display mode.
My goal is to accomplish a "UniWB" scheme using the DMC-LX3 - by setting the "Custom White Balance" in the DMC-LX3 to a self-created color-target image displayed on my computer's LCD/TFT flat-screen display. See:
http://ricohforum.com/phpbb/viewtopic.php?f=22&t=1556&start=50#p17852
My original self-created color-target image was derived from the DxO Mark database for the DMC-LX3 Firmware Level 1.0 first published on or around November 17, 2008. See:
http://ricohforum.com/phpbb/viewtopic.php?f=22&t=1556&start=40#p17389
for my initial details (including a link to the DxO Mark database entry for the DMC-LX3).
The DxO Mark White Balance Coefficients are: Red = 2.55; Green = 1.00; and Blue = 1.52.
When I used the relative weightings listed directly above to create a color-target (using the DMC-LX3 at the latest Firmware Level 2.1, and using the "Standard Color" selection within the "Film Mode" settings: Contrast = 0; Saturation = 0; Sharpness = -2; and Noise Reduction = -2) ...
the resulting DNG (converted from a DMC-LX3 RW2) shows "Shot WB Coefficients" as: Red = 1.0760; Green = 1.0000, Green = 1.0000; and Blue =1.1597 when viewed in Rawnalyze Histogram display mode.
My first (humble, and barely-informed) assumption from the above result is that (perhaps) I need to re-scale the DxO Mark White Balance Coefficients used in my initial experiment by a factor equal to what Rawnalyze reports as the "Shot WB Coefficients". When I do such a re-scaling (shown here rounded to four digits following the decimal point - despite the fact that the original DxO Mark data is only precise to two digits following the decimal point), I get:
Red = 2.370
Green = 1.0000
Blue = 1.3107
I am thinking that I should make a new color-target for setting the DMC-LX3 Custom White Balance where the relative weighting of Red, Green, and Blue in the color-target reflects the above-listed modified RGB Coefficients. In fact, I did just that (as you will find if you read the first Ricoh Forum post that I cite above) ...
However, I am (just barely) wise enough to recognize how little I know about these things (details surrounding "raw" image-files in general, the Adobe DNG Converter 5.6, and the very interesting Rawnalyze 2.1040. I want my action sand information disseminated to be accurate (for the benefit of my own DMC-LX3 "UniWB" implementation scheme, as well for the benefit of any readers who might assume that I actually may know something about what I am posting!).
Gabor, I know that you are out there somewhere (it appears only a few hundred miles to the north of me in Seattle). I have been doing all the "Googling" and forum-reading that I can to try to understand the details of these matters (including reading your Rawnalyze on-line help information). If you have the time - would you be so kind to enlighten me as to what your understanding of these matters is (or, if possible, refer me to information sources where I might be able to be able to figure these specific questions out on my own). Many thanks!

function(){return A.apply(null,[this].concat($A(arguments)))}
It is my (humble, and barely-informed) understanding that the DNG Converter 5.6 performs de-mosaicing upon the RW2
You could convert it in demosaiced format (it is an option under Preferences, if you select the compatibility as "Custom"); however, if Rawnalyze can display the DNG, then it is certainly not demosaiced.
function(){return A.apply(null,[this].concat($A(arguments)))}
Whether or not the DNG Converter 5.6 has altered any White Balance information contained in the original DMC-LX3 RW2 image-file
The converter usually changes the temperature and tint; however, Rawnalyze displays the coefficients of the raw channels, which are stored in the raw file either by the camera or by the raw/DNG converter.
function(){return A.apply(null,[this].concat($A(arguments)))}
the resulting DNG (converted from a DMC-LX3 RW2) shows "Shot WB Coefficients" as: Red = 1.0760; Green = 1.0000, Green = 1.0000; and Blue =1.1597 when viewed in Rawnalyze Histogram display mode
This is not excellent, but not horrendeous either. Have you tried using a totally clipped raw image as white balance template? It works with some cameras, but not with all. Give it a try and post the results pls:
a. shoot a white sheet with +4 EV bias,
b. verify in Rawnalyze if everything was clipped,
c. load that raw image in the camera as WB template,
d. make a shot with "custom WB" or whatever the name of that option is with your camera, i.e. using the previous shot as WB template,
e. verify the WB coefficients; they should be very close to 1.
Gabor

File size difference between DNG Converter and Lightroom Beta 4

Hi,
I want to go the all-DNG route and am trying several things ATM. I want my files to be as small as possible, thus I disable previews and RAW embedding and enable compression in DNG Converter. In Lightroom, there are no options at all. What I do get, are pretty amazing file size differences:
Original .NEF as it came from my D70s: ~5MB
.DNG created by DNG Converter: ~1MB
.DNG created by Lightroom: ~4MB
The very small file size in DNG Converter is the one that bother's me most. I get these small files from time to time. I checked both the DNG and the NEF in Photoshop, and they seem to be identical. So my question is: What triggers these small file sizes? Do I loose anything? Or is the Lightroom DNG converter not as advanced as the stand alone version?
Maybe this helps: I get the ridicolous small files for very dull subjects that tell the computer scientist in me that it should be easily compressable by common compression algorithms.
Thanks for any pointers,
Markus

Thanks for the hint! It did make me revisit those files and now I see the reason for the small file sizes: The Apple Finder does note update the file size view once a file was added to a folder. Here's what I did:
Opened a folder full of .NEFs in detail view in Finder.
Converted them using DNG Converter
Looked at the sizes of the files as they were shown in the Finder window allready open.
Unfortunately, those file sizes are not correct. If I open a new Finder window of the same folder, file sizes are correctly reported as between 3.5 and 5 MB.

Confused - DNG Converter RC for RAW files from d810 - doesn't work...

hi everyone -
sorry for the stupid question, but i've never had to do this before. i read somewhere here that if you download camera raw 8_6 and dng converter 8_6 you can convert raw files from d810. i just tried that with the dng converter and it says that the files are not recognized.
what am i doing wrong? can someone help me figure this out?
many thanks in advance.

The first thing to point out is that the release candidate will not recognize the new small raw format. You'll have to shoot the full-sized raw images. The other thing to be aware of is that, in the DNG converter, when being prompted for the location of your raw images, it is asking for the FOLDER. Choose the folder, but don't open it. Then the DNG converter will convert the raw files contained within that folder.
If you want to shoot TIF, you would probably have better image data to work with than you would with JPEG images. But it still wouldn't be as flexible, and you wouldn't have as many options as you would shooting raw. Try the DNG converter with my suggestions and see if it works for you.

DNG converter for older versions of MAC OS?

Hi,
I'm helping a friend who is happily using PS CS3 on a Mac with Lion or Lepard. I'm a PC person so I'm not sure what those two names mean. Anyway, he has a couple of newer cameras (a Sony and a Nikon) for which CS3 can't interpret the RAW files. As I understand, Adobe is not providing support in CS3 for new RAW files and my friend does not want to upgrade to a later version of Photoshop CS or CC. So, I suggested the free Adobe DNG converter.
In looking at the Adobe specs on the DNG copnverter, it says that it requires Mac OS X 10.6 through 10.8. So, two questions:
1) Is OS X 10.6 tru 10.8 the same as Lion or Lepard (I suspect not)
2) Is there an "older" version of the Adobe DNG converted I can have him download that is compatible with his OS and has (or can get) the code for recent cameras?
Thanks -- Dan

To answer the other part of your question, you can download older versions of the DNG Converter from http://www.adobe.com/downloads/updates.html
The question is, though, what version of the DNG Converter is needed to handle the files. Since you didn’t specify the extract models of cameras, that is impossible to verify, yet.
You can look at this list of cameras and ACR version numbers to get an idea what the minimum DNG Converter download that would be needed to support them, and then check the system requirements of that particular DNGC version:
http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
Finally, Adobe is still offering the PS-CCLR subscription for $10/month (in the US). It was supposed to expire on Dec 3rd, and then Dec 8th, but it’s still there, now without a specific expiration, but that doesn’t mean the offer won’t expire. $120/year for the PS-CCLR subscription is about as much as it used to cost to upgrade PS-non-extended every 18 months, so if your friend can afford $10/month they can have the latest PS and run it on up to two computers.

I have a Canon EOS 70D and Photoshop CS5. I have already downloaded the DNG converter 8.2.

I still can't see my RAW files. Please help!!!

You've posted to the Photoshop Elements forum, which is a different product to Photoshop CS5 but, for this question, the same answer will apply.
As you probably know support for the 70D was added to ACR 8.2 which requires CS6 or CC. But the DNG Converter can convert the files to to the Adobe RAW DNG format that CS5 can then open. However installing the converter does NOT give CS5 the ability to open the 70D RAW files directly. After installation you have to run the converter and point it at your 70D files where it will convert them to new .dng files that will then open in CS5 Camera RAW. The .cr2 files will never open directly in CS5.
Cheers,
Neale
Insanity is hereditary, you get it from your children
If this post or another user's post resolves the original issue, please mark the posts as correct and/or helpful accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks.

Camera Raw and DNG Converter for PSE10 and PS CS5.5

I recently bought a Nikon D5200. I have Photoshop CS5.5 at home and PS Elements 10 at work. I had to download a DNG coverter in order to open my RAW files (NEF). I have 2 questions: 1) Which are the latest updates that will work with each of these programs (the listings on the Adobe Download pages are confusing) and 2) Do any of these updates allow a new NEF file to be opened directly without the extra step of DNG conversion? Bit of a pain.

Latest DNG converter can be downloaded from following link:
http://blogs.adobe.com/lightroomjournal/2013/09/camera-raw-8-2-and-dng -converter-8-2-now-available.html
Regards,
Ashutosh

Canon G15 raw files and DNG converter

DNG 7.2 does not include the G15 raw file format. When will the Canon G15 raw files (CR2) be converted by the DNG converter?
This a question to the Adobe staff. Thanks for your answer.

You can use the DNG Converter 7.3 Release Candidate currently available on Adobe Labs:
http://labs.adobe.com/downloads/cameraraw7-3.html

DNG Converter 5.2 and Camera Profiles

Hi!
I tried to search for an answer but did not find any.
Question - how and when DNG Converter will use Camera Profiles?
How do I specify which profile to use?
I assume it can use them - version 5.2 comes bundled with them...
Тhanks for the help!
P.S. Since new version has installer, I'd suggest to create uninstaller too.

>This somehow implies that DNG Converter reads settings from installed Lightroom. I'm not sure that this is the case - DNG Converter seems to be completely independent product.
Yes, it does...for the camera model, if you have modified the Camera Raw Default in either Lightroom or Camera Raw then DNG Converter will use the user specified default. If there is no user set default, then of course will use the regular Camera Raw Defaultwhich in the case of 5.2 is now Adobe Standard. (I can't remember what version of DNG Converter started reading the CR prefs).
>If I give DNG file to someone, who uses DNG-compatible program (other than Adobe's), do I have to give him all profiles as well?
If you are using a "custom" profile other than Adobe Standard, the behavior is to embed that profile in the DNG so it is self describing. The only complicating factor is what version of Camera Raw/Lightroom the recipient is using. If they are using a version prior to Lightroom 2 or Camera Raw 4.5, then those older versions ignore the embedded profiles and will use the earlier simple profiles that have been used since DNG/ACR was introduced.
As for checking on updating the DNG Profiles in the future, DNG Converter, as it's rev'ed, will include any new profiles that come out and will update them for any already installed and add any new profiles available for a given camera. The odds of updating existing DNG Profiles is not largethat's what the 2 beta rounds was for, to shake them out. But it's possible. It's more likely that profiles for new cameras will be added.

DNG converter question

Similar Messages

Maybe you are looking for