DNG Converter: limited path

DNG converter worked for some time on my PC with Windows 7 but since a few days the onlyu path it can see is c:/users/myname
Any idea where DNG converter gets this crippled path? All my other software runs fine BTW.
I tried reinstalling DNG Converter and Camera RAW but I am afraid it uses some kind of registry setting that is not removed when reinstalling..
Can anyone help?
Bas

Installed 6.1 and have the same problem. I can neither navigate to a folder to choose files or navigate to a folder to save files.
On the computer with this problem, I installed Windows 7 (Professional) from scratch. On my laptop, which doesn't have this problem,
I updated to Windows 7 (Home Premium) from Windows XP Home.
This problem also comes up in Lightroom (2.7) and Bridge CS5. It isn't present in Bridge CS3.
It appears that the lastest Adobe programs need to run under the default Administrator account to be able to choose folders elsewhere on the computer/drives. I'm running them under the account I created when installing Windows 7 (named it "Rod") and that account is an Administrator account. But I have to log in to the default Admin. account to be able to browse to folders using the "choose folder" button (in DNG converter, Bridge CS5, and Lightroom 2.7)
I don't have this same problem on my Windows 7 32-bit laptop and I recall reading somewhere that the 64-bit OS handles security stuff differently?? Not sure.
rod

Similar Messages

Problem With DNG Converter

I just installed the DNG converter and can't get it to work.
When I first installed it, it let me go to the correct folder one time, but after that one time, when I click the Select Folder button I get this error message:
"There is no disk in the drive. Insert a disk into drive
/Device/HardDrive5/DR15"
It makes no sense to me.
I'm running Win 7 64bit

I get a message like this, sometimes, not with the DNG Converter, but just in general, if I leave my card-reader plugged into my computer after I have removed my card, so the computer sortof sees it but not entirely.
From your description I would guess that the DNG Converter is remembering the location of your previous conversion and that was on a removable drive or other device, that needs to be plugged in, again. What was the path for your successful conversion, initially?
Can you do another conversion from another location or does the error prevent selecting a new location?

Latest DNG converter not working in command-line mode

Today I downloaded Adobe's latest DNG converter. It is failing with both .NEF and .CR2 files when run in command-line mode. It does appear to work in GUI mode. The switches+arguments I've used for my tests are:
-u -e -p1 filename.CR2
(or filename.NEF)
With an older (CS2) version of the converter, the above arguments produce a .DNG output file as expected (with .CR2 files; I didn't try it with D3 .NEF files; surely that older version doesn't support the D3's format).
With the very latest version, running the program with the above command produces no output. There's no error message.
The 'readme' file that comes with the converter doesn't include any information about command-line usage, but I did find a PDF file covering this (adobe.com/products/dng/pdfs/dng_commandline.pdf). The switches+arguments shown in the PDF file appear to be exactly the ones I used in the past.
I'm sure I'll need to use the most recent version to convert D3 RAW files. Is there something wrong with how I'm specifying its command-line switches/arguments?

It struck me silly that I've been running tests with v.3.3 when 5.2 is the latest, so I downloaded it. The setup "wizard"...hmm, why is it a "wizard"? It provides no choice of installation path. I didn't realize this because immediately after I'd launched it, I knocked something onto the floor, reached down to pick it up ... and looked back up just in time to see the "wizard" complete the installation...but where, I didn't know. It didn't display any information about where it had installed the app. Adventures In Discoverability. :) I hunted around on the hard drive until I found it (C:\Program Files\Adobe -- well, at least you can launch it if you think to look for it in the 'Start' menu). So ... that needs a bit of work. Anyway, I copied the app into a directory of my choice -- one that's in my system's %PATH%, replacing spaces in the name with underscores. It works fine in that directory -- no problem with the name-change as far as I can tell. Now back to the fun stuff...
This version doesn't seem to require a fully qualified path to the input file or to the output directory when "-d" is used. That's an improvement. IOW, this worked:
converter -p1 -d DNG filename
where "converter" is the program's name, "DNG" is the name of a subdirectory of the directory where I'm running the test, and "filename" is the name of a RAW file in that directory.
The program still doesn't know how to create a directory (or ask about creating one if it doesn't exist). Fails silently if "-d" is used and the specified directory doesn't exist. But at least this version returns an exit code of 1 due to the failure -- better than returning 0.
Still doesn't understand wildcards. Hope done sprang eternal there for a moment, but oh well. Back to "for" loops...
Still fails silently, returning exit code 0 (oops), if a nonsensical command-line is used (e.g., using "-c" as the only argument).
Hey, how about a truly silly command-line error -- a command line including both "-c" and "-u". What happens? It "consumes" the first of the two mutually exclusive switches, ignoring the second -- you get a compressed DNG file. Swap the order of the switches, and you get an uncompressed file. (I'd vote for a syntax-error message in that case, m'self.)
Interestingly strange little program...If I run it from the command line, it drops back to the command line immediately after I press ENTER. That makes it appear to have failed. But it hasn't -- it's running in the background, and a few seconds later the DNG file is created. But, if I run it from within a batch file, it does NOT return control to me until it has completed writing the output file. Wonder what's up with that.
Fun stuff. :)

Print resolution with DNG converter 5.7 beta

I am using Lightroom 1.4.1, Vista 32bit sp2, Canon 350D and 550D cameras and Canon i9950 printer. In order to open Canon RAW files from the 550D I am converting to DNG with the latest Adobe DNG converter (5.7.0212 beta). I use ACR 4.1 compatibility in accordance with the guidance given on the DNG Converter preference page. I have today noticed some abnormal behaviour that the beta release page asks me to report here.
Converting 550D file to dng using the ACR 4.1 compatibility, opening the dng in Lightroom and printing the full (18M) frame at 6x4 inch, with the print options set to 480dpi and medium sharpening, I obtain a print which has a resolution of 100dpi or less.
Crop the image to quarter size and print as 1 above - print resolution normal (480).
Convert a 350D image (8M) and print as 1 above - print resolution normal
Print 550D RAW using Canon DPP - print resolution normal
Convert 550D file to dng using ACR 5.4 compatibility. Opens OK in LR1.4.1 (fortunately), print as 1 above and print resolution is normal.
The only apparent difference between converting at ACR 4.1 and 5.4 compatibility is the print resolution - the 5.4 version seems to open and be stable with LR 1.4.1. To use 5.4 compatibility is an obvious workaround - are there any pitfalls when using this version?

samuelphoto wrote:
How do I get it to work within Bridge when I use the command "Get Photos from Camera..."?
You can't...DNG Converter is a stand alone app and can't be used with Bridge...since you are working with Bridge CS4. if there is no built in support for your camera, you'll have to do a finder copy and then convert. Also note that you are not limited to using DNG Converter 5.7. You can use the most recent DNG Converter which is 6.2 (the 6.3 version is an RC and not yet released). But, that won't help Bridge CS4 either...
You can use the Canon software to do the import from camera or card...

DNG Converter 5.4 beta

Hi
(sorry about my english!)
I can see that Abobe has fixed some serious problems regarding the conversion of RAW files from the Canon EOS 5d MarkII.
I have planned to write an illustrated comparison to some forums about converted RAW by Canon software compared to the Adobe converter.
I'm glad I didn't wrote it yet - The result of version 5.4 beta as least not completely ridiculous, as it was with the DNG converter version 5.3 public.
Thanks Adobe for repairing thoose bugs
Benny Pedersen,
http://www.elementsvillage.com/gallery/showimage.php?i=246&noignore=0&postid=18902#post189 02

I don't think you will get an answer to how much the various upgrade paths costs until the product is announced in a month or two or three.
The fact that LR 3 beta 2 expires the end of June is a hint. You can look at the current upgrade pricing from various versions of Photoshop to CS4 if you want to see if there are tiers but that doesn't mean LR upgrades will use the same structure, either.

DNG converter fails on some Hasselblad H2D-39 files

Hi,
I run CS3 so I tried the new 5.4 beta. When converting a batch of .3FR files, some files convert while others do not. Those that convert work well when opened in CS3, those that do not result in an error message in the converter. I cannot really se any pattern in which files work and which files fail.
Here is the sys info from CS3:
Adobe Photoshop Version: 10.0.1 (10.0.1x20071012 [20071012.r.1644 09:30:00 cutoff; r branch])
Operating System: Windows NT
Version: 6.0 Service Pack 1
System architecture: Intel CPU Family:6, Model:15, Stepping:11 with MMX, SSE Integer, SSE FP, SSE2
Physical processor count: 4
Processor speed: 2400 MHz
Built-in memory: 3070 MB
Free memory: 1106 MB
Memory available to Photoshop: 1677 MB
Memory used by Photoshop: 95 %
Image cache levels: 2
Serial number: xxxxxxxxxxxxxxx
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS3\
Temporary file path: C:\Users\xxxx\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
E:\, 69,2G, 55,6G free
br, Håkan

Hi,
Thanks for responding. I thought this was the forum pointed to from the download site, was not aware of the dng forum. Though there is another post on probs with convering Hasselblad files ( http://forums.adobe.com/thread/436615?tstart=0 ), my symptoms are quite similar ("Unknown error") so I would suspect this could be related to the same prob? As I am quite keen to get rid of the Phocus software, if there is anything I can do to help you fix the bug, just send me a note.
Thanks, Håkan
Ian Lyons kirjoitti 31.05.2009 kello 11:30:
If you're using the DNG converter then raising the issue on the
appropriate
forum might get a bit more attention
http://forums.adobe.com/community/dng
>

Problem running DNG Converter from command line in Windows XP

I'm a frustrated user trying to run Adobe DNG converter from the Windows command line - more specifically from a batch file.
- Am reasonably conversant with writing batch files
- Have read the PDF file provided by Adobe
I just can't figure the correct syntax for adding the command line parameters and, unfortunately, the Adobe PDF file doesn't have verbose examples for idiots like me. Nor can I find any such examples on the Net, or any discussion of this problem in the forums.
The Adobe PDF instructions state...
"The parameter list includes the conversion options you want to use, followed by the names of the files to convert."
As there is no switch to prefix 'the names of the files to convert' I assume I just leave a space and include the path to the source files at the end of the parameter list?
Here is the batch file line I am trying to use...
"C:\Program Files\Adobe\Adobe DNG Converter.exe [parameter list]"
Where I want to specify in the [parameter list] that...
(a) The destination directory (-d <directory> parameter) is c:\DNG_files
(b) And the source files are in directory c:\RAW_files
Here is the batch line with the parameters entered...
"C:\Program Files\Adobe\Adobe DNG Converter.exe -dC:\RAW_files c:\DNG_files"
I've tried variations of this with space between -d and C:\RAW_files and C:\DNG_files\*.* for the source files parameter.
I just keep getting DOS erros like "The filename, directory name or volume label syntax is incorrect"
Can anybody help me. I'm clueless how to solve the problem. :-(
I'm running DNG COnverter version 4.2
Thanks in anticipation.
Rob

Thanks for responding G Sch.
LOL. Well this lemming doesn't habitually rename .exe files (e.g. Adobe DNG Converter.exe) to a non-spaced alternative either! (Adobe_DNG_Converter.exe)
Still no luck...
*** Here is my batch file...
REM Copy and DNG-convert files from CF
CD c:\RAW_files
dir c:\RAW_files
"C:\Program Files\Adobe\Adobe DNG Converter.exe" -d C:\DNG_files
dir c:\DNG_files
pause
***Here's the DOS shell output...
<<BEGINS>>
C:\RAW_files>dir c:\RAW_files
Volume in drive C is Local Disk
Volume Serial Number is D084-58ED
Directory of c:\RAW_files
12/03/2008 10:29 AM <DIR> .
12/03/2008 10:29 AM <DIR> ..
11/03/2008 07:00 AM 10,661,632 _3110455.ORF
11/03/2008 07:01 AM 10,661,632 _3110457.ORF
11/03/2008 07:01 AM 10,661,632 _3110458.ORF
11/03/2008 07:02 AM 10,661,632 _3110460.ORF
11/03/2008 07:02 AM 10,661,632 _3110461.ORF
11/03/2008 07:03 AM 10,661,632 _3110462.ORF
11/03/2008 07:03 AM 10,661,632 _3110463.ORF
11/03/2008 07:04 AM 10,661,632 _3110464.ORF
11/03/2008 07:04 AM 10,661,632 _3110465.ORF
9 File(s) 95,954,688 bytes
2 Dir(s) 2,619,731,968 bytes free
C:\RAW_files>"C:\Program Files\Adobe\Adobe DNG Converter.exe" -d C:\DNG_files
C:\RAW_files>dir c:\DNG_files
Volume in drive C is Local Disk
Volume Serial Number is D084-58ED
Directory of c:\DNG_files
12/03/2008 02:46 PM <DIR> .
12/03/2008 02:46 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 2,619,731,968 bytes free
C:\RAW_files>pause
Press any key to continue . . .
<<ENDS>>
As you can see (a) Source files exist(b) DNG command line runs without generating an error (c) no output files in destination.
DNG Converter did not run.
If I remove everything after the command (i.e. the parameter list stuff) it fires up DNG Converter in interactive mode. Not what I'm after.
Any other thoughts on what the problem is?
Thank you.
Rob

RESIZE option in LR4's Convert to DNG and DNG Converter 7

Besides the option for lossy compression I would love to see the Resize option from LR4 Beta's Export dialog in DNG Converter 7 as well as in LR4's "Library>Convert to DNG" function.
In the wake of cameras like the Nikon D800 and others with huge image files and easy option to convert to smaller sized DNGs would be very helpful.

Mark Alan Thomas wrote:
Right. I'm not into the whole lossy compression thing. I like the idea of making smaller raw files, but I want the megapixels which remain to be good megapixels.
Now I get what you mean. Apologies.
That would be interesting and of course I absolutely second it: DNG with variable resolution but lossless compressed!
That would be a great option. So why not just offer both independently - resolution and compression?
Just don't disable the "Resize to fit" switch when "Use Lossy Compression" is off.
I understand the perils with this and I also understand that it's kind of counterproductive to the thought of a RAW/DNG file. But in the end, isn't it about flexibility and not purity of a system? Bring on some big fat warnings that make it clear to the user: "you are now leaving the path of a non-destructive file format!" But let the user decide.
For more safety you could even add the need to unlock this functionality in the Preferences.
Side note:
There have been plenty of high-res DSLRs so far, Nikon D3X, Canon 5D MkII, 1Ds MkIII, Sony SLT-A77, SLT-A55, NEX-7, Alpha A-850 Alpha A-900 - but none of them seems to have stirred up the discussion about need and sanity of high megapixel DSLRs like the D800 now does.
It's probably because it's the highest so far and Nikon offers no lower resolution RAW as Canon does. What most seem to agree on however is that the high megapixel count can be nice for many and provides flexibility, but it can also be a burden at the same time.
No idea why Nikon don't offer sRAW like Canon do. But considering all this, a flexible option for smaller DNGs with individually settable compression and/or Resize would be a tremendous accomplishment!

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

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

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

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

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

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

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

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

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

CS5 DNG Converter for Nikon D750?

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

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

How to make windows 8.1 compatible with dng converter 8.1?

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

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

DNG Converter 6.4 does not recognize any RAW files

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

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

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

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

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

DNG Converter: limited path

Similar Messages

Maybe you are looking for