DNG problem...

Many of our clients shoot with medium format digital backs - Imacon backs in particular. The native raw file format for Hasselblad/Imacon is the 'fff'. The raw processing software used is called FlexColor 4.5.
Using Flexcolor, one can export the native fff files as DNG files which are supported by Adobe Camera Raw. The images open, may be edited/adjusted, and saved out. No problems.
Aperture somehow only recognizes the thumbnail image and processes out a 1.6 MB +/- file - settings were checked several times by several testers to ensure that 'TIFF - Original Size (16bit)' was selected as the export setting.
It is our opinion that Aperture 1.0 is still very much a 'beta' application. Apple seems to be using the professional market as a means of 'beta-testing' their software - all for only $499.00 US. I wish we could all run our businesses like that.
C Jones

What you are experiencing is a fundamental flaw in OSX.
In OSX, all images are handled by Core Image, or to clarify, all of OSX, and apps made by apple, and maybe ones that are new and decided to use Core Image.
Now the problem you experience has to do with OSX having broken support of DNG. In principle what you tried to do should work perfect, and infact if works with any app that has working DNG support (in other words more any app not made by apple). The problem is that for some reason in OSX, DNG files are only supported if the camera that the RAW file the the DNG file was made from is also supported. Since your Digital back is not supported in it's native raw format, you are out of luck. Of course this makes zero sense, makes DNG worthless on OSX, and means Apple is lying about it's DNG support, but thats the way it currently is. Cross fingers for this to be supported in the future.
Its even more frustrating for those who own a camera thats raw format is supported, but the camera that made it is not on the "special" list of accepted cameras, for those cameras not on it, it doesn't work either.
How the current DNG support came to be as is? who knows, but something went seriously wrong, thats for sure.
Something to keep in mind is any problem with files in Aperture is actually a support from in OSX, aperture can only do what the core parts of OSX can do. Apps like PS don't use core image, so they work fine with DNG.

Similar Messages

  • Digital Camera Raw Support 1.0.1 seems to fix some DNG Problems

    The actual Update seems to fix some DNG Problems , after the first Update i converted some d2xs files into dng an the look very strange ,now after this
    update , the dng files from d2xs are working ...
    does anyone has some raw files from cameras with are not support in native raw , who could try this out ...
    bye
    herbert

    I was hoping that it would cover the Leica M8 DNG files - the update means that you can see (and even modify) the thumbnails, but the full file still doesn't come up.
    kind regards
    jono slack

  • DNG problems in Windows XP Explorer

    I have been shooting with the Olympus EP1 and since LR does not recognize the files yet I decided to try the new version of the DNG Converter.
    It (the DNG converter) recognized the EP1 RAW files fine, converted them and I was then able to import into LR without any problems.
    However - if I attempt to open the folder where the DNG files are in using Windows Explorer (or My Computer) - using XP Pro SP3 - Explorer will not show the files in the folder (neither a listing of them or the thumbnails) and trying to change folders will result in a "Not Responding" dialog box. I have never had this problem using any of the Olympus RAW files (multiple different Oly cameras).
    Any suggestions (because it is pretty annoying) aside from giving up on DNG and waiting for the LR update?
    Thanks,
    Steve Wandy

    Hi Steve,
    I'm unable to reproduce the problem. Can you let us know what DNG Conversion options you used and what Lr import options you used? Also, does this happen when you put the DNGs in a different location in your filesystem--for example if you use a folder on your desktop instead of a external drive, etc.
    Thanks,
    David

  • Vuescan DNG problem

    Hi all,
    I am having a problem with DNG's generated in Vuescan. I have a substantial amount of scans saved out as Vuescan DNG.
    I now know this is not very wise if you want to postprocess in ACR and LR, because vuescan DNG's are not real raws. They are rendered untagged files, this is why you don't want to process them in ACR and LR.
    Not wanting to rescan many strips of film I decided to open them in Vuescan and save them out as tagged (prophoto and gray(for B&W)) TIFFs for postprocessing in ACR/LR.
    However here comes the problem, the DNG's show up in Vuescan as only 300dpi (originally scanned at 4000dpi) and the resulting TIFF is very tiny and unusable (pixilated). These DNGs have been opened before in ACR and/or LR.
    According to Ed Hamrick, the author and maintainer of Vuescan, once opened in ACR/LR a tag is written into the DNG, c716 for ACR and c717 for LR alongside a low res preview (despite rendering a 1:1 preview). This is causing Vuescan to only see a low res preview at 300dpi (my ACR workflow setting). Ed is not able to give a solution and regards these DNG's as being manipulated. Maybe Vuescans implementation of DNG is defying the purpose of DNG being an archival file format, but that is not solving my problem right now.
    Is there a way to strip off all the tags and preview(s) written into the DNG to return the Vuescan DNG into its pristine state before opening into ACR/LR, because these untouched DNG properly show up as 4000dpi files in Vuescan.
    Any help is greatly appreciated
    Regards,
    Jaap

    Hi Sandy,
    Thank you for your answer. I ll give it a try.
    The reason you don't want to process vuescan dng's in ARC/LR is that these dng's are rendered files as opposed to real raw files which have te be demosaiced in the raw converter.
    Vuescan dng's behave much like a tiff, but they are untagged and ACR/LR assumes sRGB when the file is opened and with all under the hood conversions the result is not what you would get if you open proper tagged TIFFs.
    I remember Andrew Rodney explaining this very clearly but unfortunately i m not able to recall where i once read it.
    Jaap

  • Why is there Intermittent Aperture DNG Problems?

    I am having intermittent problems downloading DNG files from my Leica M8. Most of the files are brought in fine but there are always a couple of files that give an error message. These files however can be downloaded using Capture with no problems, and then they can be imported into Aperture without any problems.
    Anyone else come across this? Anyone know what's going on?

    I'm shooting with an M8 as well, no problems to report bringing in DNG's directly from the card. I did have issues with extreme III cards with Tiger and a card reader but I switched to the Ultra II which plug directly into the USB port.
    It is good practice to format the cards after each download in the camera, also the M8 is a bit fussy about which cards you use and there have been reports of issues with some cards not on the recommended list here
    http://www.leica-camera.co.uk/assets/file/download.php?filename=file_2547.pdf
    Also I don't use the supplied USB cable for transfer but rather directly download from the card.

  • DNG Problem in Aperture 3.0.1

    Just upgraded to Aperture 3.0.1 right after installing the 3.0 upgrade (I have been using 2.1.4 for some time). Am trying to convert RW2 RAW files to DNG. I use the latest Adobe RAW converter (5.6), but although Aperture can read the RW2 files, it can't read the resulting DNG files. It DID read DNGs when I first tried it last week. Today, it no longer works. Aperture DOES read DNGs created from PEF files though. Both file formats are supported and Aperture 3 DID read DNGs from RW2s last week.
    Any idea what's going on?
    Steve

    I've seen the notes about not using linear conversion, and I don't think I am. I say I don't think because I only see one place in Adobe Converter to check linear conversion. That's in the 'compatibility' box and then only if I do a Custom setting. The default in the Custom setting comes up without linear checked. I am assuming that if I leave compatibility set to the default of "Adobe 5.4" that linear is not checked. However, I also went ahead and used "Custom" with linear unchecked and it still doesn't work.
    The weird part is it worked about 4 days ago with the last set of RW2-DNGs I imported. Today, it doesn't work with new RW2-DNGs OR the ones that did work 4 days ago. Have tried reloading Adobe Converter and restarting Converter and Aperture, to no avail.

  • Help!  Serious DNG problem!

    I shoot and edit professionally--use Bridge, PS, LightRoom (experimentally), etc, etc, and I do not normally convert to DNG or use it.
    A client sent 120 DNGs made from scanned images (so called "RAW" scans). I opened them with Bridge and much to my surprise all the images were in need of horizontal flipping--many had signs and wording in them, all backward--X&^$!!!!. This client is now in the far reaches of Indonesia! Can't contact him for originals. Deadline looming!
    If there is a way to horizonatally flip a DNG without having first to save it as a Tiff? If there is a way to do that in LR or Bridge of PSCS2 or 3, I cannot find it!
    Can anyone offer a quicker way to do this--these files average 150 megs each. They can Not be be bulk loaded. When I open one in PS, it opens in ACR, then has to be Opened in PS, then saved as Tiff, then reconverted to DNG.
    I knew there were good reasons not to deal with DNGs personally, but this one was not on the list. Someone, please call me a moron and indicate how that can be done, what I have missed. Any app or utility that will do that?

    Don,
    Duhhhhh!
    How could I have missed that! I am a blind moron! Panic striken eyes never see what is right in front of them!!! :) :) :)
    Thanks, you and LR saved my bacon! I can write the flip back to DNG with the Export Metadata command and send them on to the guy's publisher image edited and ready for the next step. He insists they come in as DNGs and go out as DNGs--and this is the first time he sent them needing flipping. A BIG lesson learned! Thanks again.

  • Referenced DNG problem

    With the new updates, my Fuji S2 pro is finally supported. Everything works fine when I import DNGs to the library, but when I import them as referenced files, I get an unsupported image format error. Same files, only difference is whether they're referenced or in the library. Am I doing something wrong?

    On a closer look, it looks like the camera is actually capturing more photosite readings than the Adobe converter is producing.  However, Canon specifies the camera to produce 3648 x 2736 pixels, which is what you're getting from the Adobe converter.
    You should understand that Adobe is all about adhering to specifications.
    In your other thread you made the comment "more adobe junk!" I'm not sure to what you were referring, but I'd say it sounded out of line.
    Notably this is a 4:3 ratio, which consumer grade cameras often produce.  Who knows, maybe it was a marketing decision at Canon to use a 3:2 imager and supporting chips, and just not process all the pixels to make the final images.  They probably thought no one would notice.
    I don't speak for Adobe, but I don't anticipate them ever making those extra pixels available to you.  They don't break away from specifications lightly.
    -Noel

  • Problem with Adobe DNG in Aperture 2.1.4

    I've never had a problem with DNGs until now. I have Pentax DSLRs and can import their RAW format (PEFs), but my workflow involves converting PEFs to DNGs using Adobe RAW Converter, then importing the DNGs to my managed Library.
    Just got a Panasonic Lumix DMC-LX3 which has RAW format of RW2 which I understand is not supported by Aperture 2.1.4. However, given my workflow, I simply converted the RW2s to DNGs using ARC v.5.6. The problem is Aperture doesn't recognize the DNGs. This doesn't make sense as I would think the DNG coming out of ARC should be readable irrespective of what the original RAW file format was.
    Any ideas on what the problem is (short of upgrading to Aperture 3)? This seems like an Adobe DNG problem, not an LX3 file format issue.
    Thanks for any help anyone can provide.
    Steve

    The buttons are on the same line. I would like to upgrade to 2.2 and I'm sure that we will at some point, but it won't happen without some time dedicated to testing. I'd like to get this figured out with version 2.1. The strange part is that it just showed up after the portlet was enhanced. I looked at everthing changed and I can't figure out what could have caused it. Anyone have any idea what would cause 2 buttons in one TD tag not to both receive the onclick event?

  • Aperture 3 and DNGs from LX5 raw files: unsupported image format

    My LX5 arrived, and I tried converting a raw file to DNG with Adobe DNG Converter 6.2.0.21 beta and importing it into Aperture. No luck: Aperture says it's an unsupported image format. I tried setting the compatibility as far back as possible in the preferences, and still no luck. Any idea why this doesn't work? I used Adobe DNG Converter multiple times to work with raw files from unsupported cameras, so it's a real surprise to get the unsupported image file message.
    —Andreas

    Unfortunately, this is more about Apple dragging its feet than a cutting edge issue. I got an LX3 and upgraded to Aperture 3 in February of this year. RW2s straight out of the camera always imported just fine. However, I've never been able to get a DNG generated from an RW2 with Adobe DNG converter to work. Interestingly, DNGs from another file format I use (PEF) work fine in Aperture.
    I submitted a issue report to Apple about the RW2 to DNG problem back in March, and like so many other suggestions to them, it seems to have vanished into the ether.

  • Open With default Application in Bridge

    When I double click a "RW2" file in Bridge my Photomatix application opens the file. Nowhere in the file associations do I see Photomatix or the "RW2" file format for that matter. I reset to default associations - still no joy. The only app showing in the "Open With" pull down in Bridge is "Photomatix (default)". How so I change this default to PS4?

    To my knowledge RW2 is the Raw format for Panasonic ?
    The file type association in Bridge prefs should be found under Panasonic.
    In your situation it might show Photomatix. (mind you that Photomatix claims
    to rather not convert Raw files in their own app because they have no good
    converter for that and they are better in working with tiff). See if you
    have the option to change this to CS4.
    If not you will have to look in the supported Raw formats for your ACR
    converter to see if your camera model is supported in the list for the ACR
    plug in for CS4:
    Try this link (otherwise find it with a search on the Adobe.com site):
    http://www.adobe.com/products/photoshop/cameraraw.html
    Mind that this is already the ACR 6 version that will only work with CS5.
    Scroll down for the latest version for CS4 which should be ACR 5.7
    Check your version in PSCS4: go to the menu Photoshop / about plug ins /
    Camera Raw, This should show only one plug in with version 5.7
    Also try to convert the files to DNG using Adobe's free DNG converter. DNG
    files have much benefit and work also with older ACR and PS versions:
    http://www.adobe.com/products/dng/
    Problem is BTW longstanding, every vendor uses his own Camera Raw format and
    to makes things worse, they also make a slightly different format for almost
    every new type of camera they put on the market.
    Adobe kindly delivers about 3 to 4 times a year a free new update for ACR
    and DNG with support for most of those cameras.
    It is best to first check compatibility with new cameras and third party
    software. If you want to work with Raw files you better wait until support
    is there or you have to use the vendor software (not always that nice to
    work with)
    The only app showing in the "Open With" pull down in Bridge is "Photomatix
    (default)". How so I change this default to PS4?

  • 10.4.9 problem on DNG files and cd open/close tray

    After the new OS release, the file preview of my Leica M8 DNG files are no more visible. I need to open them but even setting "show icon preview" in the folder prefernces i get no result. Apple Preview also doesn't open the file anymore.
    In addition, to open the CD tray, now it requires to push the botton for at least double the time.
    Waiting for the fixies to this annoying problems.....
    .oesse.

    I updated to Tiger 10.4.9 the other day on my MacPro and today found that the Eject key wouldn't open the CD tray. When I realized that I had just experienced the same problem on a G5 at work a light went off in my head. Now reading this posting, I see that it is not "broken" but that the behavior of the key has changed.
    Since the behavior of the key has always been to just hit it, not hold it down, to open and close the tray, I don't see any good reason to change it. No other key on the keyboard requires one hold it down. It's counter-intuitive. I had already filed a ticket with my company's Mac tech support service to say my CD drive was malfunctioning and may need replacement. I had been able to open the door with a paper clip in the tiny hole and then insert and play a disk, but had not been able to make the tray operate normally. All of this because the behavior of the key has changed. I'd be willing to bet that people will be buying and replacing drives because they aren't aware. Certainly there will be a lot of money and time spent registering and responding to tech support calls on this silly issue. What a waste.
    I hadn't realized that the work computer had been updated to 10.4.9, and will still need to check this out, but I assume that is the case. I have to admit I didn't read the ReadMe file for the update I did at home because I was rushed and decided to forego that. Perhaps it speaks of this change. Does anyone know? Certainly if it does not, it should. I for one think Apple was a little knee-jerk on this one. Those who whine about a tray opening when they slip up and hit the wrong key should just be told to grow up.

  • Can't open a dng or raw file in cs5, just stops working. So many problems in cs5!

    I totally feel for you. Just upgraded from cs4 to cs5 and it was the  biggest mistake i ever made. It will probably end my livelihood as a  photographer since EVERY time i open a raw file it crashes photoshop,  makes it freeze up after i have adjuted the file in camera raw then I  hit open; i get a few bars then it just stops working.
    Even got  tech help, which helped when i was on the phone with them. The next day  the problem came back even when I danced the same jig that I did when I  had the guy on the phone - he had me move a raw file on to the desktop  rather than take open from my hard drive, then I was able to open it, so  we came to the conclusion that my drive was corrupt. I had the same  information backed up on a brand new hard drive so we compared files  from the each drive against the other. The files from the new drive  opened successfully. Yesterday. Now Photoshop cs5 doesn't open any raw  or dng files at all from anywhere so it can only be a problem with  photoshop. We thought we had the problem solved but we did not. This  never happened on CS4 unless i was trying to open 30 or more raw files,  and even then it gave me a warning that it had no more ram, it didn't  just lock up and do nothing. I'm at my wit's end. Even though there are a  lot of great new things in cs5, they aren't very useful if you can't  use the product to do the simplest thing.

    1) Install the Photoshop 12.0.1 update
    2) Install the latest ACR update.
    If problems continue after that, then there probably is something wrong with your system.

  • Problem with DNG Color Profiles in Lightroom 5.4

    Hello folks,
    I recently updated from LR 5.3 to Lightroom 5.4 and since then I am having problem when using dng color profiles which were created with Colorchecker Passport. Every time I use such a profile which was created for my Nikon D 800 I get very greenish tones in the pictures.
    I use Windows 7 Pro on a HP Z 210 Workstation. The monitor is a hardware-calibrated Quato which was recently calibrated.
    Does anyone have this problem too and - if yes - know how to fix it?
    Thanks!
    Yours, Albert
    PS: As English isn't my mother tongue I apologize for any mistakes in the text above.

    Hello Andrew,
    I do have a Nikon D 800 and a Fuji X-E1. I haven's noticed a problem with the Fuji so far. I think I will recalibrate my monitor tomorrow and see if the problem still exists.
    I can supply raws and DNG profiles but I don't know where I should upload them - I suggest I could do it on my own webspace. Would that be ok?

  • When opening a 6x4 landscape orientation raw (.dng) file in Photoshop CS5, it will automatically crop to a 4x6 orientation.  How can I change this?  I did not have this problem before now.

    I need to know how to correct this so it doesn't automatically change the orientation.

    That's new to me. I usually use the standalone dng converter to convert any raws to dng. Then I can open in Photoshop. Since I have never had this problem, the best I can do is to get you close to a fix if I don't have an exact answer. There is also a Camera Raw forum that can better advise you.
    Adobe Camera Raw  Also since you mention Lightroom, see if they know anything. Photoshop Lightroom
    Since I'm most experienced in Photoshop, I can only hand out stock troubleshooting that would just miss the problem. Photoshop CS5 does host ACR. Is this happening when you open the dng in ACR from Lightroom, and not after you open the dng from ACR into Photoshop?
    Finally when a dialog box isn't working correctly. It's the Alt key on your keyboard that would change the Cancel button into Reset in ACR. It might not work if you are using a Bluetooth keyboard. (My screen capture keys won't let me show the Reset button)
    So try that and if it fails, check out the other forums. If no one else joins this thread, I should tell you I"m out of ideas, can't seem to locate an answer, and I don't want to hold you up.
    Gene

Maybe you are looking for

  • HR-ABAP-Infoset-creation-getting default value-standard-ss

    Hi All, Here I am having the requirement that I need to create a new infoset with specified infotypes in the HR-ABAP .For this I have used SQ01,SQ02,SQ03 T.C's and I have selected tables-fields whatever I required. But I am not able to get a default

  • SCSM Migration and Upgrade

    We are currently planning to upgrade to SCSM 2012 R2, from SCSM 2010.  We would like to use all new servers and accounts in the new environment but still want to retain the old data.  I have not found good documentation on how to accomplish this.  Th

  • Runtime expection

    HI, When i am  testing in SXMB_MONI in PI it gives  the follwoing  error Information. com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_JobRecordRequest_to_KPMG_SAP_APPL_: RuntimeException in Message-Ma

  • How to Keep Checking Mail Without Screen Lighted?

    I apologize for asking so many questions but I just got an iPod yesterday and it is my first iGadget of any kind.  I would like for it to keep checking mail and signal me when new mail arrives.  I understood iPods would do this -- it's one of the mai

  • I seem to have no free harddrive space but Finder says 11 GB free.

    Hi all, I've been running into a strange problem lately: At some point, all my programs report that I have no more free space, even Photo Booth doesn't save video beyond 5 seconds or so or at all, but in Finder it says 11 GB free on any folder in my