DNG SDK vs Lightroom - difference(s) in TIFF output?

Hi, I'm thinking about writing a batch program that uses the DNG SDK to create full-size JPEGs of images i've edited (by exporting to TIFF from the DNG SDK and then using imagemagick to convert to JPEG). I often forget to export the image after I've developed it in Lightroom, and it'd be handy to just batch process any DNG I've made changes to since import.
If I save the develop metadata into a DNG from lightroom, how much (if any) of those development changes will the DNG SDK use when rendering a TIFF? Examples:
- I typically make basic adjustments - exposure, recovery, highlights, contrast - will those be read automatically from the DNG?
- If I embed one of the new color profiles into the DNG, will that be used when rendering?
I'm guessing that the answer is a no, but I thought it was worth asking...
Thanks,
Joe

The DNG SDK is mostly sample code, and is not intended to be used "as is" for actual work. It does not contain the all the actual rendering algorithms used by Adobe (for example, the de-mosaic algorithm in the SDK is very basic). It does implement the full DNG 1.2.0.0 profile color model, however, as a guide to others trying to add DNG 1.2.0.0 support.
P.S. If you need to use the actual Adobe rendering algorithms, they are currently available in binary form (not source code like the DNG SDK), via the DNG WIC codec. This is Windows only, however.

Similar Messages

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

  • Why is Lightroom oversaturating blues in TIFFs

    Recently I have had a problem with Lightroom over saturating the blues in the skys of my photos.  I start with a RAW file from my Canon 1Ds Mark 3.  I start processing it in Lightroom and then send it to Photoshop CS5 as a TIFF to do more editing.  The file is saved as a TIFF and appears in the lightroom catalog.  In lightroom the skys are now highly saturated, much more than in CS5.  I can view the Tiff file in the Windows Preview window and it looks the same as in CS5.  If I use lightroom to export to a JPG, the JPG is saturated just like the TIFF appears in Lightroom.  Windows Preview shows the JPG highly saturated just like it looks in Lightroom.  This problem started in Lightroom 3.6 and has continuted in Lightroom 4.  I first noticed it in February 2012.  I am using the ProRGB color space when opening it if CS5 and as the workspace in Photoshop CS5.  It makes no difference if I save the files in 16 bit color or 8 bit color.  Color Management Policies in CS5 are set to Preserve Embeded Profiles.  I have tried uninstalling and reinstalling both LR4 and CS5, but that had no effect.
    These 2 screen captures show how the blues became more saturated in Lightroom after being edited in Photoshop.  Since I do not have Camera RAW 7, I tell Lightroom 4 to render in Lightroom and send a TIFF to CS5.  Can anyone tell me what is causing the shiff in the blues?
    System
    Lightroom version: 4.0 [814577]
    Adobe Photoshop Version: 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch]) x64
    Operating system: Windows 7 Business Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Physical processor count: 4
    Processor speed: 2.6 GHz
    Built-in memory: 8190.5 MB
    Real memory available to Lightroom: 8190.5 MB
    Real memory used by Lightroom: 784.5 MB (9.5%)
    Virtual memory used by Lightroom: 762.4 MB
    Memory cache size: 31.7 MB
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1200
    Graphics Card: Nvidia GeForce8800 GTX
    Video Memory : 731 MB

    I checked the HSL sliders in LR and you are right they were off.  But, why are the sliders changing like that?  I have discovered that it has nothing to do with CS5 at all.  I exported a RAW file from LR4 that I had done no editing at all to, to a TIFF file and got the same problem.  The HSL sliders are off and blues are over saturated.  This does not happen when I export the RAW file to PSD or JPG, so far only to TIFF.  Am I missing something.  Why is this happening?  I have been using Lightroom since version 1 and have use versions 2 and 3 as they came out, but I never had this problem until this year.  Is this a bug?  If so, it began in version 3.6.  I bought version 4 hoping it would fix it, but it didn't.

  • DNG SDK not working on Mac (Leopard)

    Hi, I am writing a program to create dng files via the latest adobe dng sdk. I follow the same basic recipe as outlined in the example dng_validate code. On a Windows PC, the created thumbnails and previews appear just fine. However, the same code on the Mac creates dng files that do not show the thumbnails or the previews. In addition, apple programs like Aperture do not recognize these dng files either, even though they validate correctly by the provided dng_validate program on the Mac. Is this a bug in the Mac version of the SDK? OR, are there additional steps that are needed for these dng files to work???

    Hi Eric,
    An example image is given below. The first one (test.dng) is the image we created with the Adobe DNG SDK on a Mac. The second image (test_dngv.dng) is the result of running it through the dng_validate program (which uses a compressed image by default with the -dng option), and therefore much smaller in size.
    Neither of these images produce visible thumbs or previews on the Mac (not in any of the Apple programs such as Finder, Preview, Aperture, iPhoto etc.). However, when placed onto a Windows machine, they appear just fine everywhere.
    As the previous poster has indicated, this may not be the fault of the Adobe DNG SDK, but for all practical purposes it is a hindrance to us. Whoever is at fault, the bottom line is that the DNG format is proving to be less portable than other image formats such as TIFF or JPG. We have no problem moving these other formats from any computer to any other computer, whether it be Mac or Windows. We are trying to support Adobe and its efforts with new standards, but this is costing us valuable engineering time in dealing with these matters, that just do not exist with other formats.
    And, I apologize if this is presented in the wrong forum. However, we would appreciate if you can help us in this matter. Obviously, it can be done, since the Adobe DNG Converter program is capable of generating dng files with proper thumbs and previews on a Mac. It is just not documented anywhere for developers trying to work with the DNG SDK.
    http://www.davidklepacki.com/test.dng
    http://www.davidklepacki.com/test_dngv.dng
    Thank you,
    David

  • DNG SDK thinks 0xFFFFFFFF is invalid white level for 32 bit integers

    As discussed in another message the DNG SDK does not seem to be able to write floating point DNGs. Since I need higher dynamic range than a 16 bit sample I instead went for 32 bit integers.
    This works, and I manage to create a file but when I run dng_validate on it it says the white level is invalid. The white level I have of course set to 0xFFFFFFFF to make use of the full 32 bit range. Looking into the code in dng_ifd.cpp where this test is made it seems like the default max white level is set to 65535.0 and the file's white level is compared against that, regardless if the sample type is 16 or 32 bit. This means that I can only make use of 16 bits of the 32 bit integer which seems kind of strange. Looking into the DNG spec I don't see anything there that forbids using the full 32 bit range of 32 bit samples. So this looks like a bug to me.
    This is with version 1.4
    the created file can be opened in Lightroom 4, so the only problem seems to be that dng_validate does not think its valid.
    Message was edited by: torger76, removed clipping issue, that was a fault in my code.

    Hello Charles,
    I would be concerned too if my MacBook Prowas running slowly.  I found a couple of articles I recommend to help isolate and troubleshoot this issue.
    I recommend reviewing this article first for possible causes of the slowness:
    OS X Mavericks: If your Mac runs slowly
    http://support.apple.com/kb/PH13895
    You can further isolate the issue by determining if it is only happening in your user account or if it is happening system-wide:
    Isolating an issue by using another user account
    http://support.apple.com/kb/TS4053
    Thank you for using Apple Support Communities.
    Best,
    Sheila M.

  • Dng sdk question

    hi!
    I was wondering, did anyone write a simple conversion program from dng to tiff format using this sdk?
    I was trying to do that, but for some reason i cannot get results that look like the pictures from the photoshop itself
    Thanks,
    Ray

    Ray, the DNG SDK contains a command-line tool called dng_validate which does exactly that, i.e., produces a TIFF from a DNG.
    It will not produce identical results to Camera Raw, because Camera Raw contains other editing adjustments and image processing algorithms which are not contained in the DNG SDK.

  • Using DNG SDK for 10bit DNG files

    Is there any simple way one can use DNG SDK to write 10bit DNG files?
    From what I have seen, DNG SDK can only validate/read/write 8 or 16bit files. I have quite a lot of 10bit raw data to be saved and performing a 16 bit conversion would be both time and space consuming.
    If there is no simple workaround to achieve this, is there any chance for future SDK versions to support nonpower of 2 pixel bit depth?
    Thank you for your time.

    > See these specifications for more information on TIFF and TIFF-EP
    I do know that specification. However, DNG deviates from the normal TIFF in enough points to warrant explicite specifications, particularly because several cameras' raw data is compressed in like but not identical ways.
    > I'm curious if CR will open 10bit DNG....
    The Pentax K10D creates 12bit, uncompressed DNG in this packed format and that will be processed by ACR correctly, so I guess you won't have any problem.
    On the other hand, it is interesting, that the DNG converter stores 12 and 14bit data in 16bit form, thereby avoiding the issue; a huge waste of space.

  • Get DNG Date Created from dng sdk

    I have successfully compiled the dng sdk and the validate app and I wondered what is a simple way to just get the date created out?

    Maybe your scanner software is doing something strange saving as a DNG that ACR does not like?  Try scanning as a TIF and open in ACR if that works for you.
    Scanning large format negatives as a 16 bit RGB tiff is and then opening in Camera RAW is my preferred workflow and I get to use all of the ACR tools and adjustments, much easier to do some of these than in Photoshop.
    Maybe the TIFF route might work for you - and once in ACR you can always save the output as DNG
    Mike

  • Lightroom won't open TIFF or JPEG files to CS5

    Recently upgraded to a new iMac. This morning when I tried to open a TIFF file from Lightroom 3.4.1 into Photoshop CS5 I got a message saying: Lightroom was unable to prepare the selected file at /Volumes/Drobo1/Photos/2011/02-14-2011 Yellowstone/Yellowstone-0641-Edit.tif for editing.
    It will not be opened.
    The only way Lightroom will open a TIFF or JPEG image to CS5 is if I tell it to open a copy of the image with Lightroom Adjustments. If I say I want to edit the original or a copy, it won't do it.
    If I go into CS5 and open the TIFF there, it works fine, so the problem doesn't seem to be with CS5.
    Lightroom WILL open RAW files into CS5 without any error message.
    I'm using Snow Leopard 10.6.8, which was upgraded yesterday and am wondering if that's the problem since I could open TIFFs on the new computer before.
    Phil

    Do you have full permissions to the DROBO folder the files are in?  I'm a Windows person so I can't tell you how to check this, but upgrading a OS and then things not working might be related to permissions where the files were created with a profile on the previous OS.

  • How to compile DNG SDK with GCC?

    I tried to compile DNG SDK with GCC, but I got stuck to the following error message:
    ... dng_flags.h:33:28: error: RawEnvironment.h: No such file or directory ...
    In other words, it seems that file 'RawEnvironment.h' is missing. I cannot find this file from DNG SDK or XMP SDK. Do you know where I could find this file or do you know how to compile DNG SDK with GCC?
    Regards Sami

    Please define either qMacOS or qWinOS (i.e., in your list of preprocessor defines). As you can see in line 32 of dng_flags.h this is required.

  • DNG SDK build project cannot find the xml sdk

    On win7/x64.  Installed dng sdk and all dependencies per the readme files.  xml sdk built OK with vc10 express, as 64 bit static and dll.
    But the vc solution for dng_validate has incorrect names for the xml sdk build projects, so it cannot find those components.  Specifically it looks for "..\..\..\xmp_sdk\build\vc\XMPCore.vcxproj".  the actual paths in the xmp sdk are different and longer, like "..\..\..\xmp_sdk\build\vc10\dynamic\windows_x64".  Moreover there is no XMPCore.vcxproj there.
    I suppose the real problem may be that the dng sdk project is trying to build it as .net managed code, while the xml sdk was built as open code.  So I guess what I am looking for is a way to build the dng sdk open.

    I would confirm your post, but I have not found a solution. I wish someone at Adobe would look into this.

  • No thumbnails in finder/preview after exporting files as dng out of lightroom?

    Does anyone have experience sorting out the issue of no thumbnails in finder/preview after exporting files as dng out of lightroom?
    There are several conversations in the forum about this problem, but cant seem to find a solution.
    Anyone know how to sort this out?

    Thanks for your reply.
    Mac does support previewing dngs in finder and preview. This has not been a problem before (besides when using my fujufilm compact camera, which mac now has updated the Apple camera for).
    To answer your Q about dng files. Thats exactly what i do. I have work which involves communicating/transfering multiple lr -edited files to someone else whom further edits in ps. Not only that, I personally use dng as a way of storing my files. I suppose like to keep my files tidy and uniform.
    Any mac users out there who has a a solution to my issue with previewing dngs?

  • Build DNG SDK on Mac with XCode 6.2

    Hello everyone,
    I am trying to build the DNG_SDK Version 1.4 with XCode 6.2. I have downloaded all the third party libraries for xmp and dng sdk. After linking errors with the current xmp sdk 201412, I tried to compile DNG_SDK with XMP SDK Version CS6. The XMP Subproject is found in my DNG_SDK and is build successfully.
    For the DNG SDK I still get linker errors and I have no clue why (regardless which architecture I select i386 or x64):
    Ld /Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release/dng_validate normal i386
        cd /Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/projects/mac
        export MACOSX_DEPLOYMENT_TARGET=10.9
        /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cl ang++ -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOS X10.9.sdk -L/Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release -F/Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release -filelist /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Intermediates/dng_validate.build/Default/dng_validate\ release.build/Objects-normal/i386/dng_validate.LinkFileList -mmacosx-version-min=10.9 /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Products/libXMPFilesStatic.a /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Products/libXMPCoreStatic.a -framework Carbon -Xlinker -dependency_info -Xlinker /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Intermediates/dng_validate.build/Default/dng_validate\ release.build/Objects-normal/i386/dng_validate_dependency_info.dat -o /Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release/dng_validate
    Undefined symbols for architecture i386:
      "TXMPMeta<std::string>::Initialize()", referenced from:
          XMPFiles::Initialize(unsigned int, char const*, char const*) in libXMPFilesStatic.a(XMPFiles.o)
      "TXMPMeta<std::string>::SetProperty(char const*, char const*, std::string const&, unsigned int)", referenced from:
          P2_MetaHandler::SetAudioInfoFromLegacyXML(bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetVideoFrameInfoFromLegacyXML(XML_Node*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          MP3_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MP3_Handler.o)
          ReadIDXFile(std::string const&, std::string const&, TXMPMeta<std::string>*, bool&, MD5_CTX*, bool) in libXMPFilesStatic.a(SonyHDV_Handler.o)
          XDCAMEX_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(XDCAMEX_Handler.o)
          XDCAM_Support::GetLegacyMetadata(TXMPMeta<std::string>*, XML_Node*, char const*, bool, std::string&) in libXMPFilesStatic.a(XDCAM_Support.o)
          RIFF::importProperties(RIFF_MetaHandler*) in libXMPFilesStatic.a(RIFF_Support.o)
      "TXMPMeta<std::string>::SetProperty(char const*, char const*, char const*, unsigned int)", referenced from:
          ID3_Support::ID3v1Tag::read(XMP_IO*, TXMPMeta<std::string>*) in libXMPFilesStatic.a(ID3_Support.o)
          P2_MetaHandler::SetXMPPropertyFromLegacyXML(bool, XML_Node*, char const*, char const*, char const*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetGPSPropertyFromLegacyXML(XML_Node*, bool, char const*, char const*) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetAltitudeFromLegacyXML(XML_Node*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          MP3_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MP3_Handler.o)
          MPEG4_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MPEG4_Handler.o)
          ReadIDXFile(std::string const&, std::string const&, TXMPMeta<std::string>*, bool&, MD5_CTX*, bool) in libXMPFilesStatic.a(SonyHDV_Handler.o)
      "TXMPMeta<std::string>::DeleteProperty(char const*, char const*)", referenced from:
          P2_MetaHandler::SetRelationsFromLegacyXML(bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetDurationFromLegacyXML(bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetGPSPropertyFromLegacyXML(XML_Node*, bool, char const*, char const*) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetAltitudeFromLegacyXML(XML_Node*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(P2_Handler.o)
          JPEG_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(JPEG_Handler.o)
          MPEG4_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MPEG4_Handler.o)
    Any hint is appreciated. Thanks
    I found a hint here (Xcode Compile Error Undefined symbols for architecture x86_64:   "TXMPMeta<std::string>::Initialize() that a include statement would be missing, but that is defined in the dng sdk (dng_xmp_sdk.cpp):
    #if qMacOS
    #ifndef MAC_ENV
    #define MAC_ENV 1
    #endif
    #endif
    #if qWinOS
    #ifndef WIN_ENV
    #define WIN_ENV 1
    #endif
    #endif
    #include <new>
    #include <string>
    #define TXMP_STRING_TYPE std::string
    #define XMP_INCLUDE_XMPFILES qDNGXMPFiles
    #define XMP_StaticBuild 1
    #include "XMP.incl_cpp"
    This cannot be the reason..

    Thank you so much! That has worked!
    I have downloaded XCode 5.1.1 and the build ran without errors. But still I is unclear to me what has changed. The Xcode-project file included in the dng sdk was configured compiling on Mac OS SDK 1.6. Anyway, I can go on with that. Thanks again

  • Compile DNG-SDK with VC6

    Hi all,
    I downloaded the DNG-SDK, and now am trying to compile it with VC6.
    There are two main problems:
    1) The data type 'unsigned long long' doesnt exist. What could I use instead?
    2) Is '__int64' ok to use instad of 'signed long long'?
    3) The constructor of class range_tag_set in Dng_Image_Writer.cpp does not compile. Does someone know the problem? What should I change?

    Please define either qMacOS or qWinOS (i.e., in your list of preprocessor defines). As you can see in line 32 of dng_flags.h this is required.

  • DNG SDK - What a Complete MESS !!!!!

    Hi - and sorry for this to be HIGHLY infriendly message
    I have downloaded and installed ALL latest greatest of anything pertaining to the DNG SDK -
    Followed ANY read me, configure, make, make install files available there.
    Installed CMAKE and everything else....
    I am on OS X 10.9 and USE the xCODE version of Mavericks
    I am developing MANY different things and NEVER have problems.
    I have in my life NEVER exprienced something as cumbersome and clumsy as this. NEVER!!!!
    I am trying to compile/build the inlcuded and generic dng_validate project. And this proves to be IMPOSSILBE.
    Simply put. I cannot figure it out. And I cannot do more that to follow the instructions provided in the SDK.
    This is incredible and I am missing the words to describe anger I am feeling.
    I realize this sdk is something that adobe cares nothing about - hence all the problems adobe are having with their own apps, which arent even capable of reading DNGs correctly...
    To whomever, maintaining this SDK ---- You are doing a really bad job at it !!!!
    Regards
    Morten

    The SDK is from 2 years ago. XCode has changed quite a bit since then, and the build settings are therefore a bit out of date.
    It's not any different with other projects in XCode that haven't kept up with the changes to the tool chain.
    It's not easy/trivial, but it is far from impossible to get this to build if you have experience writing your own code and not just building other people's code.
    You also have to make sure you are using the correct versions of the XMP SDK and the third party code.
    David Blake

Maybe you are looking for