Does DNG Converter 5.6 Alter WB Info of DMC-LX3 RW2s?

I have converted a Panasonic DMC-LX3 generated ".RW2" to DNG using DNG Converter 5.6 for the exclusive purpose of being able to open it in the current version (2.1040) of Rawnalyze. The conversion prodeeds OK, and I am able to view the resulting DNG in Rawnalyze. It is my (humble, and barely-informed) understanding that the DNG Converter 5.6 performs de-mosaicing upon the RW2. However, I am uncertain as to:
(1) Whether or not the DNG Converter 5.6 has altered any White Balance information contained in the original DMC-LX3 RW2 image-file; and
(2) Whether any such alterations as described above in (1) result in an alteration of the "Shot WB Coefficients" (that I am assuming represent the DMC-LXW "raw" mode White Balance Scales) displayed when Rawnalyze is in Histogram display mode.
My goal is to accomplish a "UniWB" scheme using the DMC-LX3 - by setting the "Custom White Balance" in the DMC-LX3 to a self-created color-target image displayed on my computer's LCD/TFT flat-screen display. See:
http://ricohforum.com/phpbb/viewtopic.php?f=22&t=1556&start=50#p17852
My original self-created color-target image was derived from the DxO Mark database for the DMC-LX3 Firmware Level 1.0 first published on or around November 17, 2008. See:
http://ricohforum.com/phpbb/viewtopic.php?f=22&t=1556&start=40#p17389
for my initial details (including a link to the DxO Mark database entry for the DMC-LX3).
The DxO Mark White Balance Coefficients are: Red = 2.55; Green = 1.00; and Blue = 1.52.
When I used the relative weightings listed directly above to create a color-target (using the DMC-LX3 at the latest Firmware Level 2.1, and using the "Standard Color" selection within the "Film Mode" settings: Contrast = 0; Saturation = 0; Sharpness = -2; and Noise Reduction = -2) ...
the resulting DNG (converted from a DMC-LX3 RW2) shows "Shot WB Coefficients" as: Red = 1.0760; Green = 1.0000, Green = 1.0000; and Blue =1.1597 when viewed in Rawnalyze Histogram display mode.
My first (humble, and barely-informed) assumption from the above result is that (perhaps) I need to re-scale the DxO Mark White Balance Coefficients used in my initial experiment by a factor equal to what Rawnalyze reports as the "Shot WB Coefficients". When I do such a re-scaling (shown here rounded to four digits following the decimal point - despite the fact that the original DxO Mark data is only precise to two digits following the decimal point), I get:
Red = 2.370
Green = 1.0000
Blue = 1.3107
I am thinking that I should make a new color-target for setting the DMC-LX3 Custom White Balance where the relative weighting of Red, Green, and Blue in the color-target reflects the above-listed modified RGB Coefficients. In fact, I did just that (as you will find if you read the first Ricoh Forum post that I cite above) ...
However, I am (just barely) wise enough to recognize how little I know about these things (details surrounding "raw" image-files in general, the Adobe DNG Converter 5.6, and the very interesting Rawnalyze 2.1040. I want my action sand information disseminated to be accurate (for the benefit of my own DMC-LX3 "UniWB" implementation scheme, as well for the benefit of any readers who might assume that I actually may know something about what I am posting!).
Gabor, I know that you are out there somewhere (it appears only a few hundred miles to the north of me in Seattle). I have been doing all the "Googling" and forum-reading that I can to try to understand the details of these matters (including reading your Rawnalyze on-line help information). If you have the time - would you be so kind to enlighten me as to what your understanding of these matters is (or, if possible, refer me to information sources where I might be able to be able to figure these specific questions out on my own). Many thanks!

function(){return A.apply(null,[this].concat($A(arguments)))}
It is my (humble, and barely-informed) understanding that the DNG Converter 5.6 performs de-mosaicing upon the RW2
You could convert it in demosaiced format (it is an option under Preferences, if you select the compatibility as "Custom"); however, if Rawnalyze can display the DNG, then it is certainly not demosaiced.
function(){return A.apply(null,[this].concat($A(arguments)))}
Whether or not the DNG Converter 5.6 has altered any White Balance information contained in the original DMC-LX3 RW2 image-file
The converter usually changes the temperature and tint; however, Rawnalyze displays the coefficients of the raw channels, which are stored in the raw file either by the camera or by the raw/DNG converter.
function(){return A.apply(null,[this].concat($A(arguments)))}
the resulting DNG (converted from a DMC-LX3 RW2) shows "Shot WB Coefficients" as: Red = 1.0760; Green = 1.0000, Green = 1.0000; and Blue =1.1597 when viewed in Rawnalyze Histogram display mode
This is not excellent, but not horrendeous either. Have you tried using a totally clipped raw image as white balance template? It works with some cameras, but not with all. Give it a try and post the results pls:
a. shoot a white sheet with +4 EV bias,
b. verify in Rawnalyze if everything was clipped,
c. load that raw image in the camera as WB template,
d. make a shot with "custom WB" or whatever the name of that option is with your camera, i.e. using the previous shot as WB template,
e. verify the WB coefficients; they should be very close to 1.
Gabor

Similar Messages

  • Does DNG Converter support CFA DNG for X-Trans files?

    Does Adobe DNG Converter support the X-Trans sensor layout from ie. the X100S? Can converting an X-Trans sensor RAF file to to DNG result in a file that is _not_ in any way demosaiced and/or linearized?
    If DNG Converter truly does support conversion of X-Trans to CFA DNG files, how can the resulting files be so much smaller (when not linearizing or ticking lossy compression of the DNGs)? The RAF files are all around 32 MB, while the DNGs are around ~23 MB. Is it only a matter lossless compression, or is the mosaiced data in some way altered?
    If DNG Converter does support CFA DNG for X-Trans, at what DNG Converter version did you first implement support for the X-Trans sensor layout and conversion of X-Trans data to CFA DNG files?
    These are important questions that I'm having a hard time finding answers for. I'd appreciate answer to any (but preferably all) of the questions.

    Here's the link to the Adobe DNG Converter forum:
    Digital Negative (DNG)

  • Why does DNG converter turn 11 MB files to 40 MB files?

    My DNG converter 6.3 makes DNG files of about 40-41 MB out of the 11-12 MB RW2 raw files from my Panasonic Lumix GF1. Why? It does not increase the size of the raw files from my Canon G11, rather the opposite. How can I cure this problem? Please help!

    I am having the identical problem while setting my DNG converter to "4.1 or Later."
    Basically, can someone describe in lay terms what the "lens correction" and "op codes" issues mean. Also, I assume I cannot choose "5.4 or later" in the DNG Converter when using version CS3 of Photoshop because that is where the compatibility becomes a problem. Is that correct?
    Can one simply upgrade the version of Camera Raw without upgrading Photoshop? Also, if I did upgrade Photoshop, would I be able to go back to those DNGs that are in the 40mb range, convert them to DNG again, and get a new DNG file that is more in the range of 10-12mb? Or am I now stuck with those 40mb DNGs? (I did not choose the "embed original RAW file" option.)
    Thanks
    Patrick

  • Why does DNG Converter insist on lossy conversion?

    I use DNG Converter to convert RW2 files to DNG so I can work on them in various PP programs.
    No matter whether or not I have the "lossy" box checked, DNG Converter insists on doing a lossy conversion.
    How can I stop this?
    Sample images:
    Original RW2 image, with histogram:
    DNG image - note loss shown on histogram.  There is also posterized banding, although in the small image allowed on this site it is very hard to see.

    Thank you for pointing out the problem.  Preview from DNG Converter is JPEG.
    ==================================
    UPDATE:
    My previous comment, above, is irrelevant.
    The preview is JPEG, but I am working with the DNG file.  So my original question remains unanswered.
    I have found the same issue with RW2 files.  I will investigate settings for FastStone Image Viewer (the program I am using for editing).  So far I find no options to change treatment of DNG or RW2.

  • DNG Converter-does it automatically recognize camera files?

    If I have multiple Sony cameras, all with .ARW extension, does DNG converter automatically recognize the different cameras, or do i have to manually segregate from the different cameras and convert only one camera's files at a time?
    One more question:  why doesn't DNG converter have its own community?

    The exact camera model is stored in the Raw file headers and will be automatically detected. DNG converter is the same as Camera Raw, so any questions can be directed there.
    Mylenium

  • DNG Converter does not recognize my Canon Raw files

    I have the Canon EOS Rebel 450D. I downloaded the Mac version of the DNG converter, ver. 5.6. However it does not recognize the Raw or CR2 file. According to what I read on the Adobe website, my camera is supported. Why is it not recognizing the file?

    Seem to be a few threads recently where people are having printer connectivity problems - often Canon. If you haven't already, you could try resetting the printing system, it sometimes helps re-establish a connection:
    http://support.apple.com/kb/HT1341

  • DNG converter 8.3 download. does not contain camera raw 8.3 update. Where can I find it? (Mac)

    DNG converter 8.3 download. does not contain camera raw 8.3 update. Where can I find it? (Mac)

    Finally found it here
    http://helpx.adobe.com/x-productkb/multi/camera-raw-84-support-policy.html#Revert%20to%208 .3%20on%20Mac%20OS
    No installer, just the plug-in.

  • DNG Converter 6.4 does not recognize any RAW files

    Hi,
    I have updated DNG Converter from 6.2 RC to 6.3 and 6.4. DNG Converter 6.2 RC from Adobe Labs recognizes all my RAW files (Canon PowerShot S50, PowerShot SX1IS, EOS 400D). The official releases of 6.3 and 6.4 do not recognize any RAW files of these cameras.
    I select a directory, where the raw files are located, but DNG Converter tells me that no files where selected. With 6.2 RC, I select the directory and everything just works fine.
    What's wrong with this picture?
    atb,
    MOS-6502

    Ahh, I forgot:
    System is Windows Vista Ultimate 32bit, patched up to date.
    atb,
    MOS-6502

  • DNG Converter ver. 6.4 does not recognize NX100 .SRW files

    I downloaded/installed DNG converter ver. 6.4 on my iMac with updated OS-X 10.6+. It installed okay, but it will not recognize my NX100 .SRW RAW files. They are grayed out, so unselectable.  The ReadMe file says the NX100 is covered with this version, so what am I missing?
    As a side note, I also have a copy of Lightroom 3, and it has the latest ACR, so it can read the .SRW files, but I would like to try using the DNG converter so other software I have could be used for editing.  The DNG converter should let me quickly convert my .SRW files for this purpose, without having to first process them through LR 3.  Could this be the roadblock, having ACR also installed?
    thanks,
    Dennis

    In addition, you can also use Lightroom to do the conversion.
    You just select the files you want to convert and then click Library > Convert Photo(s) To DNG
    In fact, you can select your entire library and convert them all to DNG.  You don't need to make sure to only select RAW files, because there is an option to "Only Convert RAW Files".  So, why not just select everything?
    Using Lightroom to do the conversion also gives you the ability to convert specific individual files, instead of needing to select an entire directory, if that's what you'd like to do.

  • How do you stop DNG Converter from embedding Adobe's ACR default settings instead of custom settings?

    I notice that the new version of Adobe DNG Converter (8.6, and maybe earlier) appears to place Adobe's ACR defaults in the converted file.  Thus, the converted files open up in Bridge with an indication that they already have settings made, and, hence, ACR does not apply the custom camera settings.  One has to Clear Settings first in Bridge, then open in ACR.
    This behavior is new, perhaps to 8.6.  But it's presence defeats the purpose of having custom Camera Defaults.
    Is there any way to prevent DNG Converter from installing settings?

    ssprengel wrote:
    What do you mean by “custom camera settings”?  Do you mean you’ve changed the Camera Raw defaults for a particular camera and those aren’t being seen until you do a Reset?  Or do you mean some sort of Nikon-settings that Adobe never looks at?
    Also at what point in the workflow are you converting these files, just after copying them to your hard-disk and before touching them with any other Adobe software, or after they’ve been adjusted in Nikon software, or after they’ve been adjusted in Bridge/ACR, initially as NEFs?
    I mean my custom camera defaults that are set by the Save New Camera Defaults for a given camera.
    My workflow is to take my original raw files first into Adobe DNG Converter.  I then open the folder in Bridge.  At this point I notice that my original raw files remain unaltered (there is no "settings" icon in the top right corner – circle with two lines and up-arrows – in the image's thumbnail), but the converted dng's (otherwise untouched and unopened in ACR) have a "settings" icon.  When I open the original raw file in ACR, it opens using my custom camera defaults.  When I open the otherwise virgin dng in ACR, it opens using the Adobe defaults (the same defaults that would be employed if no custom camera default had been set).
    This behavior is new.  DNGs formed by earlier versions of the DNG Converter did not apply any settings to the converted file, and when they opened in Bridge, they were given the custom camera settings.
    In order to retain the old (and proper) behavior, I now have to take the just-converted documents into Bridge, select them, and immediately apply Develop Settings/Clear Settings.  That gets rid of the settings that have been installed by the DNG Converter (as well as the "settings" icon on the thumbnail).
    I notice there is a new feature in Adobe DNG Converter 8.6, namely, a panel-specific toggle between the settings and the default settings. This indicates to me the likelihood that Adobe has been making some alterations with the settings that is having unintended consequences.  It clearly is not proper for DNG Converter to be adding (installing) settings, because that prevents the custom camera default settings from being applied, and hence defeats the purpose of the custom camera default settings.

  • Even with the dng converter I can´t open my nef´s from new nikon D610 to use in LR4...any suggestions?

    I found out that LR4 does not support the Nikon D610 files. Downloaded the DNG Converter, but still i can not choose the nef´s (grey shaded and no chance to click/select them...please help.Thank you in advance, Christoph

    Please supply additional info about the procedures you are following.
    Be aware that the DNG Converter is a standalone program that does not work through Lightroom. Its primary function is the conversion of raw files from supported camera models. Use the latest version which is version 8.7.
    You will need to open the program and first select a folder / sub-folder that contains the files you wish to convert and proceed from there. see the screen capture.

  • Adobe DNG Converter failure

    I have used Adobe DNG Converter 8.6 for a few weeks (on Windows 7 Ultimate 64) without incident to batch convert my Canon RAW files to DNG.  However, now when I try to open the program it does not work. 
    The problem seems to be that the GUI interface does not allow any of the boxes to be clicked or filled; the 'ert to DNG even th' text in the first box of Item 2 is a trace from a website on a previous application.  See below for what happens when I run the application.
    I do not believe I have installed any new / disagreeable software; I have tried unistalling and reinstalling to no luck.  Any input is much appreciated.

    I have a similar problem, yet different, with the latest DNG Converter (rel. 8_7). The design interface is flawed. It chops off the bottom of the box where all the action buttons are. I was previously using rel. 8_3 and it worked fine. Just got a Canon 7D Mk II so need the Oct. '14 release of DNG Converter (e.g., 8_7). It's a serious problem. Who at Adobe can fix this? Also, the program doesn't install into the Win 7 Control Panel, so there's no way to find it to run an uninstall. Tried contacting Sharad Mangalick re: this issue over a week ago - got no response - asked him to forward info to PM who's responsible for this product. Sent him description of issue and screen grab ....

  • How to make windows 8.1 compatible with dng converter 8.1?

    I have installed the DNG Converter 8.1 so that I can view/edit RAW files on Photoshop Elements 12, but Windows 8.1 states "the source folder does not contain any supported camera raw files".  I have an Sony Alpha 6000 (version 8.4), and have moved the RAW files into a folder on my C drive.  DNG Converter won't work even if I run it on Windows 8, is there no way to make Windows 8.1 compatible with DNG Converter 8.1? 

    From that faq:
    http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    I see that you need the DNG converter 8.4 to convert Sony Alpha 6000 raw files.
    Download that version of the DNG converter to replace your version 8.1.
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh for Mac
    Adobe - Adobe Camera Raw and DNG Converter : For Windows for Windows

  • What's the Difference in Conversions done with ACR vs. DNG Converter?

    As an experiment, on my PC workstation I just converted a set of 40 Canon CR2 files with both the free DNG Converter 6.5 and Camera Raw 6.5 (both 32 bit and 64 bit).  With Camera Raw, I dragged the files to Photoshop, then used the [Save Files] button and chose .dng format.  I chose "Medium" thumbnails in both cases.
    The DNG Converter and Camera Raw 32 bit took almost twice as long as Camera Raw 64 bit (56 seconds vs. 33 seconds).
    The .dng files produced by Camera Raw ended up larger than those by the DNG Converter, about 9% larger on average.
    A file comparison shows that the differences are all near the start of the file, and that the latter 80% of the data is identical in all three cases.
    The DNG converter files are more different from the Camera Raw files than the two different sets of Camera Raw files are from eachother.
    This leads me to ask these questions:
    1.  Why are the 32 bit DNG converter app and Camera Raw 32 bit plug-in so much slower than the Camera Raw 64 bit plug-in?  I have an 8 core machine, and in general don't see a 2:1 difference between equivalent 32 and 64 bit code.  It appeared by watching Task Manager that all of them were using more than one thread to do the work.
    2.  Are there any plans to release a (much faster) 64 bit DNG Converter for Windows x64 users?
    3.  Is there a practical / usability difference between the .dng files generated by Camera Raw vs. those generated by the DNG converter?
    -Noel

    ssprengel wrote:
    You can see how many CPU cores are being used by watching the performance tab with core performance separated, as long as nothing else much is going on.
    Not really.  Particular threads do not normally maintain a long-term affinity for particular cores, so the usage gets spread around as Windows does its multitasking stuff and what you normally see is just activity across the board, as seen in the screen grab below (that was DNG Converter running).  Only inasmuch as the overall percentage is higher than 1/n (where n is the number of cores) can we infer a certain amount of multithreading.
    And yes to both of you - every setting that I could find is perfectly consistent across the board, including compression.  And as I mentioned before, the embedded previews are coming out exactly identical, both in size and color.
    -Noel

  • Loupe in Bridge doesn't display DNG images created using DNG Converter correctly. Why?

    I have noticed recently an anomaly in Bridge when viewing DNG files that are created by converting my Nikon NEF files to DNG using the DNG converter. Specifically, when clicking on the preview image of a DNG file, in order to open the loupe, the 100% image seen in the loupe remain fuzzy, whereas when clicking on a preview of the original NEF file the 100% view in the loupe is sharp and clear.
    I am using DNG Converter version 4.6.0.3, and it also occurs when using version 4.4.1. I am using Bridge version 2.1.1.9.
    I have no reason to believe that Bridge is at fault, since the loupe function does work properly when viewing the NEF file. It would seem that there's a problem in the DNG conversion.
    However, despite this anomaly seen in Bridge, when I open the DNG file in Camera Raw, it is perfectly normal at 100% or any magnification.
    I have tried re-setting the JPEG review size in the DNG converter, but that makes no difference.
    What's going on here? I don't want to keep both the NEF and DNG versions, for reasons of space, but I'd like the loupe to work correctly. Help, please?

    Try to recreate the thumbnails for that folder.
    Use the latest version of the converter (5.4)

Maybe you are looking for

  • No Audio Output after Upgrading to windows 7; Soundblaster Card is installed

    After upgrading to Windows 7 Ultimate (64-bit), I found that my speakers (which are built into my HP w2207 monitor) are not recognized.  In the notification area I have the speaker with a red x in it, and it says "No Audio Output Device is installed"

  • Wrong Operation number(Activity  Number) showing in Production Order

    Friends I have created a production order. Wrong Operation number(Activity  Number - RESBD-VORNR) is  showing for some of the Production Order components(all are phantom components only)   where as the activity number in its  Routing components (RCM0

  • Communicat​ion données

    Bonjour,  Je souhaite faire remonté des données de mes VIs bas niveau vers mon VI principal.  Ces données sont surtout des messages d'infos à l'utilisateur. (exemple : Test OK ou Programme OK en 14 s ) etc  Le problème, c'est que j'ai pas mal de nive

  • Importing DV is IMPOSSIBLE!!!!

    I have Final Cut Pro 5. I have a HDV Sony Camera. I have a standard DV tape instead, with DV footage recorded (not HDV). I recorded a DV tape in a HDV camera (the camera can record in both formats). So last week I uploaded DV footage easily. I had th

  • How to post blog

    As an Independent SAP Consultant, how could one post blogs in SDN? nikhil