Support for DXO DNG format

I recently upgraded to Version 4.1 of the DxO package and it seems that images saved as DNG's by DxO are not supported by Aperture. Has anybody else had this experience and does anyone know if this is likely to change?

Hi Tony from London, Brit in exile here!
If the camera RAW is supported by Aperture, then the DNG should be ... provided it is saved in DxO as "non-linear."
My assumption (and assertion to a degree) is that Aperture's non-destructive RAW workflow means they idealize starting with RAW. Non-linear DNG is essentially RAW in a different (and standard) file format.
Linear DNG has been decoded by a 3rd party utility and therefore does not fit the Aperture "non-destructive" RAW dictat.
BTW, to test this, compare a linear DNG out of ACR with that from DXO. I am pretty darn sure you will see differences. All RAW converters are proprietary, whcih is their value prop. of course. But they are different and the output results are different.
Assertion time. Equally, consider running the same RAW image through DXO in the future. Assuming DXO has updated its sw, my assumption is the resulting DNG will look different (hopefully even better). Oh, the digital negative from DXO version x is not the same as that from version y? Can I therefore consider it my negative?
So my suspicion is that the Aperture team determined they would look after the RAW, and never ever touch it. This allows updated RAW conversion (v1 or v1.1 so far) to be run or re-run at a whim and for us to decide which to use.
G.

Similar Messages

  • Captivate 3 support for Open Document format?

    Hi,
    Does anyone know about support for Open Document Format in Captivate 3? (OpenOffice presentations)
    Is it possible to save OpenOffice presentation in open document format or does it have to be saved as microsoft power point file?
    What about Captivate 4? Any improvement?

    On the OpenOffice.org site, look under projects, and there's an Open Document Toolkit for Java. I've no idea of its status though.

  • Aperture support for unsupported raw formats

    I was doing some tests with Aperture to see if it could fit my workflow. My concern was support of old files from a Nikon Coolpix 5400, raw (thanks to firmware update at the time) as well as a recent Nikon DSLR. No problem with the DSLR. 5400 was not supported. After some internet research I found out there is a pref file (Raw.plist in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources) that has info about all supported cameras. This add raw support for the cameras listed in the file for Preview, iPhoto, Aperture (system-wide). Same list that Apple provides as camera compatibility list.
    In that list I chose to duplicate the NIKON-E8400 array and renamed it NIKON-E5400. Didn't change any value in the array. To my surprise, even without rebooting, this added support for the Nikon Coolpix 5400 images. The image looks pretty much the same with these default settings (when opened in Preview for example) than it does in ACR in CS2. The only odd difference is the image size loosing 10 vertical pixels (from 2592x1944 opened in ACR CS2 to 2592x1934). I have no idea why it does this but it is no big deal really as it is no scaling, just loss of pixels.
    I am a bit concerned of course about the possibility to carry on this tweak in the next OS updates.
    I guess any raw from any camera could have support this way.
    Just need to name the array in Raw.plist properly. For mine I just opened a raw in text edit and saw first line the name of camera, was "NIKONE5400". I compared the format of this name to other names in the array and decided to add the "-" to look like others so "NIKON-E5400", and that was it. Now I was lucky the default setting for the 8400 I used as a base worked for the 5400, apparently. It could have not been the case and then I would have had to play with the values in the array. Quite a few so a long process I am afraid, but possible.
    The deal would be to release a little utility software that would let us play with these values easily and see a result live on a sample image, and once satisfied it would modify this Raw.plist file. This way people could add support to their own raws.
    If anyone in the know sees a big issue in doing what I did please tell.
    Of course playing with this Raw.plist file is at your own risks so keep backup and bee careful.
    The tweaking of this raw.plist file had been talked about in different forum in the past concerning the support of Canon 3xxD that had a different US name Rebel something. The change of name of the corresponding array added support before an OS update did it for everyone.

    I also modified my Raw.plist file to import RAW files from my Olympus C-5050Z. But that doesn't make Aperture import a type of RAW file it didn't support before. It just turns out that your Nikon 5400 RAW files are the same format as the Nikon 8400 files except for size, just as my Olympus C-5050 files are substantially similar to the Olympus C-7070 files. I think the Raw.plist file used by ImageIO contains hints on how to treat the data and color in the images and as long as the cameras don't behave too differently, substituting one model with another will work.
    The RAW.plist file is a standard plist file that can be examined and modified with the Property List Editor. What I would like to see is documentation of the parameters so that we can more easily add support for cameras that aren't supported out of the box.
    MacBook Pro   Mac OS X (10.4.7)   2.16GHz 2GB RAM 256VRAM

  • ICloud support for .pdf file format

    Help mentions iCloud supports .pdf file formats, but then does not show anything about how to get one of these files onto iCloud.  Since the pdf files I have were never created by one of the supported Application how does one place or retrieve a pdf file to/from iCloud?
    Thanks

    PSE 4 does do 16 bit - although there are a limited number of things you can do at that depth.
    It has essentially no support for actions.

  • Support for FITS file format

    Hi,
    I'm thinking about upgrading to 4.0 (from 2.0) but was wondering if anyone could tell me if 4.0 has support for 16 bit color depth? I generally use elements to do post-processing of astro images. These images are in fits format and there is a free plug in available for them but they require 16 bit depth. The maker of the plug-in makes no mention of 4.0 but says it works in 3.0. Here is a link to the plug-in:
    http://www.spacetelescope.org/projects/fits_liberator/index.html
    Here is partial requirements they list on their site:
    # Photoshop CS2 (best), or
    # Photoshop CS (16 bit colour)
    # Photoshop Elements 3.0 (partly 16 bit colour), or
    # Photoshop 7.0 (only 15 bit colour, and only partial functionality for more than 8 bit colour)
    # Photoshop Elements 2 (only 8 bit colour) (Elements 1.0 NOT supported)
    Also does 4.0 have support for actions like Photoshop cs? I'm on limited budget so I prefer not to upgrade to PS CS2 if I don't have to.
    TIA,
    Fred

    PSE 4 does do 16 bit - although there are a limited number of things you can do at that depth.
    It has essentially no support for actions.

  • How to extend interMedia to support for new Image Format

    Does anyone here has experience to extend interMedia to provide support for a new image format.
    I have read the related chapter in Oracle Intermedia User Guide, I'm not very clear about it. Hope a step-by-step tutorial for this topic is available.
    Thanks in advance for any idea

    Can you send the details of your application to [email protected] and explain the reasons extensibility is needed by your application?
    At this time, the only way to extend formats is to write your own procedures (ususally java stored procedures) to populate the image object... This does not extend the image processesing functionality to the new image format. Internally, this requires a translation to and from an intermediate format.
    Larry

  • Support for 3g2 video format?

    I'm using Premiere Pro CS3, and I don't see how to export to 3g2 format for my Samsung phone. Does PP CS3 support 3g2? If so, how do I get to that format? If not, is there some other way to output to 1 format and convert to 3g2? Thanks in advance to all replies!
    I'm a newbie to PP, so please be gentle! ha!
    Chris

    See the section
    File formats supported for export in the PPro Help.
    Frequently answered question
    Cheers
    Eddie
    Forum FAQ
    Premiere Pro Wiki
    - Over 250 frequently answered questions
    - Over 100 free tutorials
    - Maintained by editors like
    you

  • A video codec or support for a compressed format (ZEN

    i was wondering if creative could include support for some form of compressed video format in the next firmware release for the Creative Zen V Plus. i ask this as the supplied video converter uses incredibly large amounts of space even for a small video file since the avi is uncompressed (afaik)
    could support possibly be added for wmv or something as that is relati'vely small and it would be great if the player could support it.
    please reply as this is a very common 'issue' for most owners of this mp3 player.

    PSE 4 does do 16 bit - although there are a limited number of things you can do at that depth.
    It has essentially no support for actions.

  • Why is there no eprint support for open document formats, such as those produced by openoffice

    Why doesn't the eprint service support open document formats? This should be a minimal requirement!

    Sorry, as important as this issue is to all of us who use Firefox, this is a Firefox support forum - not an appropriate place to start a discussion like this.
    I'm locking this thread for two other reasons though. <br />
    # An appropriate hyperlink to the original article wasn't provided.
    # Copy and paste from the original article without quotation marks or proper attribution.

  • Outside In support for 7z archive format?

    7-zip, 7zip
    Will search export in Outside In support extracting the contents of files compressed with the 7z archive format?

    Hi Arti,
    The scenario is as follows: we have a common data model in use, and all new-defined services should adhere to this model. Besides the data model we also have Naming rules for our services, operations etc.
    So for all (rule)-services we've identified in our project we want to apply the contract-first approach by designing them in the ESR first (using all naming conventions and data types of the common model), and only then implementing them. For a service that is implemented in an ABAP-system this is easy, because you can generate a proxy in trx SPROXY etc. In this proces you're able to keep the names of the operations/messages that you defined in the ESR.
    For rules, I'm looking for the same thing. So I want my rules to use the data definitions of our ESR-WSDL (and you explained that this is possible and how to do it, thank you), and I want my rule-webservice to keep the name I've defined in the ESR-WSDL for it. What's not clear to me is if this possible in BRM. Could you explain to me this merging process in the service composer? Is it possible to use our naming-conv-compliant SI/operations-names, and 'bind' the defined rules(ets) (which implement the service) to this definition?
    Thanks again...
    Best regards, Fred

  • SAP support for ARTS POSlog format

    Dear all,
    We are trying to integrate SAP with a 3rd party POS solution. The 3rd party POS generates ARTS IXRetail POSLog V2.2 format.
    However in the ARTS webpage, we find that SAP conforms to POSLog V2.1.
    We believ that this might be a little old, and want to just confirm if SAP indeed confirms to the latest POSLog v2.2 format?
    Regards
    Gaurav

    Hi Masa,
    As i debugged the Travels entityset, while moving the last row on the internal table to the et_entityset there is a error in assigning timestamp value to 'LastChangeDate'.
    Also every time i see it is giving the error only while assinging last row of the internal table to the et_entityset.
    PS: I have seen a SAP note - 1803227 for this kind of type conversion error.
    http://scn.sap.com/thread/3375127
    I see this note is for IW_BEP - SAPK-20007INIWBEP, but we have IW_BEP - SAPK-20008INIWBEP in backend.
    Let me know if any other notes i have to implement.
    Thanks for your responses.

  • Apple's support of DNG format is fallacious

    on the Aperture brag page http://www.apple.com/aperture/ it purports "It also supports the Adobe DNG format."
    I went to Bridge/ACR, grabbed five tweaked nikon NEFS and saved them as DNG files.
    I imported this new folder of these five tweaked DNG files into Aperture. It did open the DNG files, but none of the adjustments to the image where evident and the display was the unaltered RAW file.
    Sorry Appleture, that does not constitute SUPPORT of the DNG format. DNG is not just another RAW format, it is a RAW format with the adjustments included.
    This is the last straw for me. Time to cut my losses.
    I am going to eBay my Academic copy of Aperture for $200. I am a huge fan of Apple products, but not Aperture. IF this was an intro price of $49 then I would not complain.
    This is nothing more than a improvement to iPhoto, but not enough to be called "iPhoto Pro".

    I absolutely agree, never did argue the point that Aperture did not pick up the DNG info. Just said that Bridge embeds info into the DNG. I also agree that this is a very large sticking point I have with Aperture. I just hope they offer the option of embedding informaition into the exported files as well as the ability to change the name of the file after importing. I understand their desire not to touch the files, but given that I would bet 99.9% of photographers would want to edit down first and then change the names on the keepers I think the developers need to change their paradigm on not touching the original files, after all, that was the idea behind DNG.
    Imagine 2 workflows.
    The current Aperture:
    Open Aperture
    Import 500 files
    Cull out 200 files.
    Keep 300 files
    Don't bother correcting because of the need to export and all the metadata will be lost.
    Export the keepers.
    Delete the remaining 300 files in Aperture
    Open Bridge
    Open the just exported files.
    Wait for them to load.
    Rename the files to what you want because Aperture forces a space in the name and you do not want that space.
    Enter all the file shoot info so if you export from Aperture, the metadata info that was imported within Aperture stays with the file and only that info.
    Close Bridge
    Reimport 300 renamed files back into Aperture
    Done, I think.....
    A new Aperture (Hopefully)
    Open Aperture
    Import 500 Files color correcting on the fly to see if they are keepers.
    Cull 200 Files
    Rename the remaining 300 files.
    Enter all file shoot info.
    Done
    The new Aperture now writes all the info back to the original file including filename, metadata etc. Everytime you export or open in Photoshop, Aperture passes the filename and metadata info along. Life is good.
    Granted they currently do not want to write into the file, but most of us would prefer it so when we send something to a client we do not have to keep reentering it. Furthermore, all of us would be doing it anyway, just in a different app., so whats the difference? I am very very hopeful they will correct this quickly in a future version, if not, it is a deal breaker for me, not to mention the other deal breakers it currently has.

  • Support for .chm format?

    is there support for .chm format in oracle text or are there any plans to extend support for other document formats?

    CHM isn't supported out of the box:
    http://www.stanford.edu/dept/itss/docs/oracle/10g/text.101/b10730/afilsupt.htm
    Depending on how much you need it, you can implement a custom external filter to manually parse your CHM, as discussed here:
    http://www.stanford.edu/dept/itss/docs/oracle/10g/text.101/b10729/ind.htm
    Hope that helps
    Ben

  • When will Adobe support Nikon NRW file format?

    Adobe guys and ladies,
    Is there any information that you can add to the dialog shown below that will help me decide if the NRW format used by the Nikon P7000 P&S will be compatible with my >> 10,000 image Lightroom collection?
    thanks,
    WK
    Customer 09/15/2010 11:13 AM
    I now shoot topside and underwater (using an Ikelite housing) with a D300S. My work flow is to copy the nef files to Lightroom 3 (for Mac) as dng files for tweaking either in LR3 or occasionally in Photoshop. I'm presently considering a P&S such as the P7000 but I'm concerned that the proprietary nrw format will be a "deal killer". How do I convert nrw files to either raw, nef or dng but not tif? WK
    Response 09/15/2010 10:25 PM
    HI Thanks for the question. As with any new model software to convert RAW images will have to be updated for newer models. The Microsoft WIC compatible NRW should easily be read and converted by your software once they update for the newer model. Of course for the best conversion we'd recommend using Nikon Capture NX2. Thanks -David
    Customer 09/16/2010 08:35 AM
    Hi, The issue of file incompatibility is of great concern for many potential P7000 buyers. Let me ask the question a bit differently: Can the NRW format used by the P7000 camera be read directly (or converted to NEF or DNG formats) by available Mac software such as Aperture, iPhoto, Adobe Lightroom 3 or Adobe Photoshop 5? thanks, WK
    Response 09/16/2010 08:35 AM
    HI Thanks for the update. I'm sorry but you'd have to ask Adobe and Apple about their plans to support the P7000 images. I'd guess based on their support for other RAW format we've produced that they would but since it is their software they would be the ones who could answer. Sorry we can't help more. -David

    clvrmnky wrote:
    Of course, Nikon does its best to obfuscate their file formats...
    That's a load of CR@P - please cease this continued misinformation.
    Even in the earliest days when Nikon encrypted their white balance, it was decryptable via the Nikon SDK (without having to use the rendering feature as well...). Its just that Adobe wasn't using the SDK because the Nikon formats are all based on tif and as such are easy enough for Adobe to deal with without resorting to the SDK that they hadn't bothered. At that time, Thomas Knoll made some off-hand remarks that started a huge wave of misinformation that has been propagated on the internet ever since. In my opinion, he owes Nikon and the photography community an official public apology.
    Nikon's purpose in controlling access to the information in NEFs was aimed at quality control, so idiots like me didn't start futzing with their camera data via plugins and fly-by-night applications and smearing Nikon's good name to people who didn't know enough not to blame things on Nikon. In the beginning, Nikon required approval before releasing their SDK to third party vendors. Now, it is available immediately to anyone willing to fill out a form on their website (and it includes complete documentation). Until you, or anybody else claiming this that or the other thing about the accessibility of information in Nikon's camera files, downloads the SDK and plays with it, to see for yourself, you don't know what you are talking about.
    The fact that there was a delay between the release of the P6000 and its support in CaptureNX does not prove anything except Nikon was eager to release the camera, and followed up with changes to the SDK and/or CaptureNX after the fact.
    I apologize if the tone of this post seems stern, but in my opinion, its time for the misinformation to stop, and the huge body of erroneous information on the internet to begin to be dismantled.
    Note: I am not a Nikon defender. I just don't like to see people being unfair to them.
    Rob

  • HT201071 Please add support for Hasselblad CFV-50

    I just replaced my Hasselblad CFV-16 with the CFV-50, and now I have bad redish view only of my files both in Preview and Aperture.
    Please add support for the file format from CFV-50, it's not a all new Digital Back (it's out since severals years now).
    We can still convert files into DNG using Hasseblad tools and made the DNG file reconized by Preview and Aperture, but would like to be able to manage my original RAW files from Hasselblad in Aperture like I was used to do

    This is a user-to-user forum and is not monitored by Apple for feedback purposes. You can give feedback to Apple here: Apple - Mac OS X - Feedback

Maybe you are looking for