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.

Similar Messages

  • Looking for DNG Converter 8.7 Beta

    I've been able to find ACR 8.7 beta, but although the Adobe Labs mentions the new DNG Converter, I haven't been able to find it. Clues? (for OS X). ...doug

    The phrase DNG Converter is in a link on the Labs home page:  http://labs.adobe.com/

  • 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...

  • 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.

  • DNG Converter no longer converts focusing points from Canon CR2 files

    Hi all,
    Up until some time between July 2010 and September 2010, the focusing points embedded in the original Canon CR2 files were also converted and containded in the DNG-file. Hence up until this point in time the focusing points were shown in Apple's Aperture. Since September 2010 this is no longer the case.
    I had hoped for the DNG Converter 6.7 Beta to have corrected this truncation of the files.
    I am using af Canon EOS 1D Mark III. I am running OS X Lion 10.7.3
    1. Has anybody else experienced the same change in behavor of the DNG Converter?
    2. Can anybody still see the focus points in Aperture or equal Imaging program?
    3. Does anybody have an idea, how to contact Adobe for such a feature request?
    Thank you in advance for your help.
    Kind regards,
    Allan

    Hi MadManChan2000,
    Thank you for your answer. So what you are saying is that for some reason Apple's Aperture is no longer reading these MarkerNote metadata correctly?
    Kind regards,
    Allan

  • DNG converter fails to extract embedded .cr2 raw files

    I just tried to extract embedded raw files from 889 raw files from a Canon 5D3 having been converted by the DNG converter 6.7 beta - the DNG converter only succeeded with extracting three of them. I also tried with the 6.6 stable version with the same result.
    If DNG converter can't easily retrieve the embedded raw files then I think this "feature" should be left out - it's misleading people into taking unwanted risks when you're better off just keeping the originals (it's a bit more messy to organise and archive two sets of files, but I'd rather do that than having to mess around with this)
    So stay away from this "feature" unless you want to paint yourself into a corner.

    Download and test the most recent version (final GM) of DNG Converter 6.7 and retest...might also be useful to provide a bit more info such as OS & CPU...and also whether or not the DNGs behave normally in ACR or LR. Basic troubleshooting info to test or duplicate your findings would be useful (required) before you can honestly be making such "blanket" statements about DNG Converter...

  • Profiles are gone with Camera Raw 6.7 beta and DNG-Converter

    Hello,
    when i open a picture taken with the new Nikon D800 neither LR nor PS show the profiles i can see with the pictures taken from the D700. This also doesn't work when i convert them to dng with the beta version 6.7 of the dng-converter.
    My workflow uses the x-rite colorchecker to generate profiles. It wouldn't be nice if this will not work any more.
    Andreas
    new picture                                                      old picture (no changes in program configuration)

    Thanks to all answerers,
    i think in my first try i did something wrong (didn't check wheter the file was actually created in ..\roaming\adobe\cameraraw\profiles).
    The rest was confusing about the camera dependency of the profiles.
    Everything works fine now.
    Thanks again
    Andreas

  • Preferences Change in DNG Converter 4.6 Doesn't Persist

    I am using DNG Converter v4.6.0.30 on a Mac running OS X 10.6.2 and I'm noticing that preference changes do not persist in the next session.  I'm trying to change "embed original RAW file" and the next time I run the program, the setting is unchecked.  I've uninstalled and reinstalled the program (moving the preference file to a difference location).  After reinstalling the application, there is no preference file in the ~/library/preferences folder.
    I checked the contents of the com.adobe.DNGConverter.plist file and it only contained items pertaining to Default Folder X (for example, one of the items was DefaultFolderX:NSNavOpenPanel:column.width).  I relaunched DNG Converter and the preference file was created, but it only contained one item - bplist00—_&NSNavBrowserPreferedColumnContentWidth#@g@.  I reopened DNG Converter and selected "embed original RAW file" and then closed the application.  I checked the preference file and it still did not have anything pertaining to "embed original RAW file."
    How can I get DNG Converter to "remember" the preferences I selected?
    Thanks,
    Rocky

    You do need ACR 8.4 for the A5000.   I would buy Elements from Adobe not the Mac app store so upgrades work better.
    The DNG Converter should work, though.  You need to single-click on the folder with the raw files in it, rather than open it to reveal the raw files.  They are grayed out because the DNGC needs to work with a FOLDER not a file, so if you can see the files, then you’ve clicked down into the folder and go back up one, and just select the folder name.

  • 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. :)

  • DNG Converter vs. Using ACR

    If I am going to use the chart feature in DNG PE to make my own profile, is it better to convert my Raw Canon file to the DNG format through the DNG converter or through adobe camera raw using the save feature. What changes made in ACR will be "stored" in the DNG file? Which way to go?

    Doesn't matter. Both will work equally well.
    All of your edits made in ACR will be stored in the DNG (as metadata; the original image data is not touched).
    It doesn't matter what edits you made, however, since those edits aren't taken into account when the PE builds a profile from the Chart Wizard.
    See here for more info, under "Apply Camera Raw Adjustments"
    http://labs.adobe.com/wiki/index.php/DNG_Profiles:Editor#options_menu

  • New adobe DNG converter and CS4 quality problems - EOS 7D

    Hi,
    A friend of mine uses Adobe Photoshop CS2.
    He plans to buy Canon EOS 7D or EOS 5D Mark II in the future but first we did some tests and conversions.
    We found many problems and quality issues.
    First Problem is that CS2 doesn't support Canon EOS 7D directly so user has to use DNG Converter to convert the EOS 7D file from .cr2 to a .dng.
    When i use and test this, CS2 recognizes and opens .dng file correctly then i optimize sharpness, color etc etc in the photoshop and save the file from the file menu (Save AS) as .jpg file.
    Adobe Photoshop CS2 fails to save exif data.
    It just saves the camera model nothing else.
    On the other hand if i use CS4 it saves all exif data (without dng):
    The next problem is quality.
    If i use indentical settings in RAW converted between CS2 (dng) and CS4 (cr2) CS2 images look sharper and have more "per pixel sharpness" than CS4 raw images.
    Here's a sample (raw file taken from dpreview.com) that i tested it using both raw converters:
    So these are two problems that i don't like nor does my friend and i am asking you if you would fix that and why such hudge difference ?
    As the CS4 is being the newest the best of all photoshop it should had better picture but in this case the older version has better picture and i don't see any logic in that.
    So if user wants to go for better quality he/she will pick CS2 but have a disadvantage - Exif is not saved in the .jpg file.
    I also think that if dpreview would have used CS2 instead of CS4 they would get much higher "per pixel sharpness" from Canon EOS 7D as they did now.
    Thanks.

    Spc.. wrote:
    If i use indentical settings in RAW converted between CS2 (dng) and CS4 (cr2) CS2 images look sharper and have more "per pixel sharpness" than CS4 raw images.
    You can't use the exact same settings since the settings in ACR 3.x (Photoshop CS2) don't match up to ACR 5.x (Photoshop CS4).
    Seriously, there was a major change in ACR 4 and then 5 that make comparing ACR 3.x and 5.x pretty pointless...
    Fact is if you aren't getting optimal results from Camera Raw 5.x then you don't know how to use it...simple as that.
    ACR 3.x had a very crude image sharpening process compared to either ACR 4.1 and above of any 5.x version.
    Seriously, Photoshop CS2 and Camera Raw 3.x is way old tech...if you can't get better IQ from 5.x you are doing something wrong.

  • Camera Raw 5.2 and DNG Converter Available - Note from Adobe

    Camera Raw 5.2 and the DNG Converter is now available:
    http://blogs.adobe.com/lightroomjournal/2008/11/camera_raw_52_and_dng_converte.html
    Lightroom will be updated to version 2.2 with equivalent camera support in December.
    Regards,
    Tom Hogarty
    Lightroom, Camera Raw and DNG Product Manager

    Well, I managed to locate and download both the ACR 5.2 and the DNG 5.2, but it was a bit of a challenge. I have a couple of comments regarding the DNG installation.
    As a sometime OS beta tester, I have developed a habit of keeping C:\ for the operating system only. When a new OS or beta is issued, I just format C: and install the new OS. I try to keep applications off C:. It is hard, though, with all the default installations. It would be nice to have the option to install DNG.exe in my applications partition.
    My workflow involves importing NEF's from the memory card to a folder, and at the same time converting those NEF's to DNG's and putting them in a different folder in a different partition. Both these NEF's and DNG's are archived. A copy of the DNG's are used as working images. The virtue of DNG's is that there are no sidecar files to keep track of when exporting images. Unless I really mess up, I never go back to the NEF's again. I guess that I am an "outlier" too. I guess that this is essentially the 5 - A "double DNG-only" workflow, using type 2, the native-DNG-DNG system. This is discussed in detail by Barry Pearson at http://www.barrypearson.co.uk/articles/dng/safety.htm#personal
    I do like the camera profiles. I previously have used the Fors script. My Nikon D200 lacked red and the Fors script fixed that. Not surprisingly, different profiles are appropriate for different image types. Is there any way of determining the methodology and reasoning between the different profiles, and what specific problems each one is designed to correct. This might permit better matching profiles to image types, with less trial and error.

  • DNG converter don't work for some RW2-files

    Hi,
    i found out, that there ist now direct support from CS4 to my new Lumix LX5. :-(
    In  some forums i got the hint to use the free DNG converter. that works  for most of the files, but some rw2's it can't convert. yesterday i made  10 pictures and the converter only identificate 7 of them. The only  thing i noticeed ist, that this files are "only" 7MB. The others are  10MB. When i use irfanview to look the rw2's are no problems. the  pictures are all very good. somebody an idea whats wrong with the 3?
    Thanks
    pittip
    sorry for my english, but i hope you understand me!??

    I don't know anything at all about your file format, but it sounds as if there is an option to create compressed raw files.  I know Canon has this option.  It may be that somehow you used this compressed option, assuming that there is one, and it may be that the DNG converter does not support the compressed raw format.  If not, maybe someone else will have a better answer.

  • 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 6.4 and DNG codec 1.1 for Win7 32 & 64bits released!

    The DNG converter 6.4 has been released, http://www.adobe.com/products/dng/  with support for many new cameras, including:
    Canon EOS 600D (Rebel T3i / Kiss X5 Digital)
    Canon EOS 1100D (Rebel T3 / Kiss X50 Digital)
    Fuji FinePix S200 EXR
    Fuji FinePix F550 EXR
    Fuji FinePix HS20 EXR
    Fuji FinePix X100
    Hasselblad H4D-40
    Kodak EasyShare Z990
    Nikon D5100
    Olympus E-PL1s
    Olympus E-PL2
    Olympus XZ-1
    Samsung NX11
    Note that it is the last version to run on Power PC Macs: http://blogs.adobe.com/lightroomjournal/2011/03/dng-converter-6-4-last-to-support-powerpc- mac-systems.html
    Also released today: The DNG codec 1.1 that now supports the 64bits version of Windows 7, but does not support Vista anymore.
    http://labs.adobe.com/wiki/index.php/DNG_Codec
    Finally, the DNG Profile Editor beta 3 is out too, and has also been updated to address bug fixes and support DNG files utilizing the updated DNG 1.3 Specification.

    I just downloaded and installed this version on Windows 7 Home Premium 64bits.
    I can report it works great with my Raw DNG files, from camera:  Pentax K-m/ K2000.
    Probably also with all other Pentax camera's.
    Jan (Netherlands)

Maybe you are looking for