Skip navigation
This discussion is archived

Bottom line - DNG working or not

4697 Views 22 Replies Latest reply: Dec 6, 2005 7:32 AM by tjr3000 RSS
1 2 Previous Next
tjr3000 Calculating status...
Currently Being Moderated
Dec 2, 2005 1:58 PM
Here is my dilemma:

I am sitting on four years of DNG files that have been converted from various Canon RAW files types (D30, 1D, 1D2, 1Ds). All of those DNG files have the original RAW file embedded into the file. All of those files import into Aperture, but not correctly. They are all reporting only the resolution of the embedded JPEG preview, which is around 256x171.

Flat out - this is not acceptable.

This app is too new for me to think that it's not me that is doing something wrong, but based on the other posts here, I'm beginning to think that it is NOT me but the program that has issues.

So, to the folks out there that have the answers, or who are confident enough in their claims: Does Aperture truly support DNG or not?

I really am hoping that I did something wrong. If this app does not support RAW files that have been converted into the DNG format, Apple is going to have a very difficult time convincing any Professional photographer that this is truly a professional tool (despite what the video advertisments might have you believe).

Thanks for the help.

We've got em all!   Mac OS X (10.4.3)  
  • buttel Calculating status...
    Currently Being Moderated
    Dec 2, 2005 2:14 PM (in response to tjr3000)
    I have had success importing DNGs, for my 1DS mkII and Digital Rebel XT. All metadata is stripped, but the image is fine and not restricted to a JPEG thumbnail as you described.
    I did not have success importing DNGs from my pocket camera, a Powershot S50. Those acted as you described.
    I started another discussion about importing images:

    dual g5 2ghz Mac OS X (10.4.3)

    dual g5 2ghz   Mac OS X (10.4.3)  
  • ImageMac Calculating status...
    Currently Being Moderated
    Dec 2, 2005 2:17 PM (in response to tjr3000)
    Well, speaking for myself, I can't get any DNG image to import to Aperture successfully. After import the image thumbnails are grayed out and when selected I receive a message saying "Image format not supported".

    In going through the Getting Started book that came with Aperture, I am realizing that DNG is not listed among the supported file formats.

    Is anyone having luck with DNG imports?
    2.0 DC PowerMac, Mac OS X (10.4.3)
  • ImageMac Level 1 Level 1 (10 points)
    Currently Being Moderated
    Dec 2, 2005 2:36 PM (in response to tjr3000)
    I've just found the same issue. DNG files created from a LEICA Digilux 2 are not supported in Aperture but DNG files from a Nikon D2H are supported.

    I truly hope this is a bug!
    2.0 DC PowerMac, Mac OS X (10.4.3)
  • buttel Level 1 Level 1 (10 points)
    Currently Being Moderated
    Dec 2, 2005 3:49 PM (in response to tjr3000)
    Apparently Apple, (and several other vendors) have not completely implemented their DNG readers. Here is a discussion on the Adobe web site you might find interesting:

    dual g5 2ghz   Mac OS X (10.4.3)  
  • photohag Calculating status...
    Currently Being Moderated
    Dec 2, 2005 4:04 PM (in response to tjr3000)
    DNG files coming directly from a camera are "supported", converted files are not. I was told that this is being addressed and that the Aperture specs on the Apple site will be updated.
    I like the program and I want to love it but they have some work to do make it function as it should. It is a lot to ask to change your workflow completely and run everything through Aperture.
    I don't know how many professional photographers they collaborated with when creating this but they obviously should have spoken with a few more...
    G5 dual, Mac OS X (10.4.3)
  • Jack Burden Calculating status...
    Currently Being Moderated
    Dec 2, 2005 4:05 PM (in response to buttel)
    That thread on the Adobe forum does not seem conclusive to me, though it's been posted to several here. If you read more of Adobe's documentation on DNG, it seems that unless you use the linear conversion feature, then you are relying on any other app's ability to specifically support the camera. Frankly I'm still confused, but I'm starting to think that this DNG compatibility has limits based on the preferences that you choose in DNG Converter. To copy what I said on another thread:

    look at the Prefernces inside DNG Converter and read what they say. If you select "Convert to Linear Image," it says:

    "The image data is stored in an interpolated ("demosaiced") format. This can be useful if a camera's particular mosaic pattern is not supported by your DNG reader." (emphasis added)

    I haven't really messed with this, but it seems like the only really valid and useful way to deal with DNG would be to "convert to linear image" AND "Embed Original Raw File." ... otherwise, it would seem that you are not gaining any compatibility advantage, because you're still relying on camera specific support. I don't think the DNG documentation is nearly explicit enough on this. I've just read the PDF titled "Introducing the Digital Negative Specification," and it does not elucidate this... Of course doing it the way I suggest has two disadvantages: double the file size (but let's ignore that, since the priority is being arcvhival) and also a potential decrease in quality by going to linear prematurely.... the truly best way would be something that DNG Converter does not offer: If you really wanted the utmost in archival, it seems you would take triple the file size hit and do the file three ways: "Preserve Raw Image," "Convert to Linear Image," and "Embed Original Raw File" all at the same time... then you would make it part of the standard for DNG-supporting readers to prefer them in that same order automatically. Am I thinking clearly?

    of course I'm totally new to DNG, and I want my position to be attacked with more useful details from others who are digging into this...

    G5 dual 2.0    
  • Alastair Brown Level 1 Level 1 (65 points)
    Currently Being Moderated
    Dec 2, 2005 4:51 PM (in response to photohag)
    If a camera is supported, then DNG buys you nothing? A converted DNG file from an unsupported camera would be hugely useful, but doesn't seem to be even a remote possibility.

    The Aperture marketing material definately gave the impression that supporting DNG extended the usefulness of the product. As far as I can see, it is a complete irrelevance.
    PowerBook G4 15" 1.67 DL, Mac OS X (10.4.3), 2gb RAM
  • isometry Calculating status...
    Currently Being Moderated
    Dec 2, 2005 5:20 PM (in response to tjr3000)
    Just a me too post: .DNGs converted from .CR2 sourced from a Canon 20D also come out at 256x171... very frustrating. also renders them like this.

    I've seen rumors that the upcoming 10.4.4 update may bring with it improved RAW support: my fingers are crossed.
    Powermac G5 Quad, Mac OS X (10.4.3)
  • isometry Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 2, 2005 5:22 PM (in response to Alastair Brown)
    .DNG from some supported cameras doesn't work either - see my reply regarding the Canon 20D.
    Powermac G5 Quad, Mac OS X (10.4.3)
  • buttel Level 1 Level 1 (10 points)
    Currently Being Moderated
    Dec 2, 2005 5:55 PM (in response to Jack Burden)
    The point of the Adobe post is that a DNG file reader, such as ACR 2.4, if properly implemented, can READ DNG files from a camera that was not anticipated when the software was written - thus Adobe's claim to a more robust archival format.
    There are three sources of confusion:
    1. ACR 2.4 can't READ RAW files from an unanticipated camera, but it can READ DNG from the same camera.
    2. I have observed the linear option on RAW conversion, but this is a red herring. ACR 2.4 is reading uninterpolated DNG files from unanticipated cameras.
    3. Apple's implementation of DNG DOES NOT allow it to READ DNG files of cameras whose RAW files it doesn't support. My guess is that they rushed to add it and therefore hamstrung their implementation. If Apple would address this issue we could all happily convert our unsupported RAW files to DNG. Then of course if they would import embedded IPTC metadata from the DNG files we'd really be cooking.


    PS. I tried the linear option on some RAW Powershot S50 files I have, and Aperture still couldn't manage the resulting DNGs.

    dual g5 2ghz   Mac OS X (10.4.3)  
  • Jack Burden Level 1 Level 1 (25 points)
    Currently Being Moderated
    Dec 2, 2005 6:47 PM (in response to buttel)
    Buttel -

    Thanks for the extra info. This DNG really is confusing. This point really gets me:

    There are three sources of confusion:
    1. ACR 2.4 can't READ RAW files from an unanticipated
    camera, but it can READ DNG from the same camera.

    ... Adobe's website says that DNG Converter and ACR support the same cameras, so how would DNG Converter convert it in the first place if ACR could not read it? It's possible that Adobe has added cameras to DNG Converter that are not in ACR without updating that statement, but as it reads, that statement is not helping me

    - Jack

    G5 dual 2.0    
  • buttel Level 1 Level 1 (10 points)
    Currently Being Moderated
    Dec 3, 2005 12:40 AM (in response to Jack Burden)
    DNG files treat raw data from image sensors in a consistent fashion. Camera manufacturers have not felt any need to treat raw data consistently. Therefore each manufacturer is free to (and does) create a new format each camera's RAW file, even though the information needed to convert the raw image data into TIFF, PSD, or JPEG is not all that different.

    So what happens now when a new camera is introduced is that all the software houses that handle RAW files race to create converters specifically for that format. And photographers wait for Adobe (not too patiently) to update ACR to handle their hot new cameras. And those with older versions of Photoshop wait for the new DNG converter, which can translate the new RAW format to DNG, so that their older (ACR 2.4 for example) can read it.

    Of course if the camera manufacturer introduces a new camera with DNG formatted raw files, the software houses don't have to translate, the photographers don't have to wait for Adobe to update ACR and the DNG converter.

    The advantage of DNG should be that if a software house fully implements the DNG spec when reading files, it should have no trouble converting those files to a non raw format.

    It also means that if you have converted your RAW files to DNG, you can feel more confident that those files will be readable on future computer systems. This is because it is much more likely that companies will invest the effort to code a single DNG converter rather than a plethora of RAW converters for any new computer systems.

    I am speculating that Apple, in a rush to get Aperture to market, crippled their DNG implementation by coding to handle the specific parameters of the cameras they support, rather than coding to the general parameters in the DNG spec. If they had the time, any RAW format that the DNG converter handles currently would be supported by Aperture in DNG files. (but not necessarily the RAW files those DNG files were derived from). Too bad.

    Going forward there is no guarantee that DNG will handle new imaging technologies. I don't for example know how it handles Fovean files, and there are likely to be other imaging technologies that the DNG spec doesn't anticipate. Oh well.

    Anyway, I hope this is helpful. I hope I can pull my Powershot S50 RAW files into Aperture one day. I hope all the IPTC metadata embedded in all my RAW files will be read by Aperture one day. I hope I can export RAW files from Aperture intact with embedded metadata so I can perform raw operations outside of Aperture.

    Good night,

    dual g5 2ghz   Mac OS X (10.4.3)  
1 2 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.