Colorchecker passport and the DNG profile editor

I finally got around to getting a Colorchecker passport to use with the DNG profile editor.
I was secretly hoping I could save time by shooting the chart on location and make an instant profile out of that - then the colors would be at least "close ballpark" so I would just have to apply white balance and then move on to more specific adjustments. But of course it wasn't that easy, it still takes a fair bit of color tweaking to get right in most circumstances.
So I'm wondering if my energy would be better spent trying to perfect one good dual illuminant general profile. For this I would use 3000 K tungsten at one end and 5500 K studio flash at the other. Or would it be better to use overcast daylight? In either case it's obviously important to ensure the chart is absolutely evenly lit.
And then I should probably have a separate profile for fluorescent tubes.
I'm curious what other people's experiences with the colorchecker/DNG profile editor are? How are you using it?

The color profile changes with the lighting, so a profile that was computed for daylight won’t be right for tungsten or fluorescent.  Keep in mind that a custom camera profile is the set of corrections on top of an existing Adobe profile that the DNG has assigned to it, perhaps Adobe Standard, and all Adobe profiles are dual-illuminant profiles, so it makes sense you’d want to also create a dual-illuminant profile for general purpose use that has the same two lighting scenarios as Adobe used:  2850K and 6500K.  The 6500K is the tricky one because full sun is warmer, closer to 5000K, and you need the right amount of haze to create 6500K sunlight, unless you are using standard D65 bulbs, indoors, which is likely what Adobe does.
I use a dual-illuminant profile for general purpose use, but since the WB-Tint values of both the tungsten and daylight ends are close to zero, lighting that has a tint not close to zero needs a separate profile.  The common example is the greenish light from fluorescents, and I have several single-illuminant profiles for various artificial lighting scenarios with WB-Tint values that are relatively non-zero.  I also have ones for very red sunsets and very blue twilight.  If I had studio lighting I’d make a profile for that.  Sometimes I make a custom profile for a church or other venue that has significant non-neutral walls or ceilings, or where sunlight through the stained-glass windows shining on the walls are giving a significant color-cast including a non-zero tint value to the lighting.  If you know you’ll be doing some shots near a large amount of tall, green vegetation then a custom color profile can correct for the green tinge to the ambient lighting coming down from above mixing in with the sunlight. 
Adding to the suggestion about wearing neutral clothing, I’d argue for dark neutral clothing because something lighter clothing will reflect environmental colors (sunlit vegetation or brick walls, etc, outdoors) and not be neutral. 
Besides non-neutral clothing, try to avoid areas that have green grass or tree leaves or brick buildings that also color the light and reflect off the colorchecker.   For the sunlit shots, I put my colorchecker face up on the sidewalk or parking lot, to avoid coloration from the grass and far away from trees or buildings especially in the direction I’m pointing the camera, so the only lighting is direct sun and ambient blue-sky, possibly diffused by hazy clouds.  I point the camera down at the colorchecker, at a 45-degree angle and at a compass direction and not directly toward the sun, nor directly away from the sun.  I try to shoot the target that is face up on the ground perhaps at a 90-degree angle from the sun to minimize any residual glare from the colorchecker’s slightly non-matte surface.  Obviously directly away from the sun, the color-checker will have my shadow on it or I will be blocking the light from the sky near the sun.
I use the same sort of process for the tungsten end, choosing a room with neutral walls and put the target relatively flat on the floor facing up, perhaps tipped up somewhat toward the light, but not so much as to have any glare from the lighting, either, in other words, not with the lighting directly behind the camera, but somewhat over to the side.

Similar Messages

  • Creative use of CC calibraton in the DNG Profile Editor

    The DNG Profile Editor can be used to create profiles that mimic film looks.
    I think right now it is manual trial & error process involving changes in hue, saturation and lightness, but it could be theoretically achieved with Color Checker calibration working in reversed order.
    - Photograph the CC using your favorite film
    - If B&W, develop in your favorite developer
    - Scan the film
    - Use the scan in the DNG Profile Editor as target values
    The current DNG Profile Editor obviously does not allow that, it would require adding a new tab and clone the CC calibration feature and alter it to use the photographed values as target values as opposed to internal values.
    I don't know if it would be worth the effort, but I thing the idea is worth of sharing.
    By the way, unless I'm doing something wrong, the saturation slides don't seem to go 0%, so creation of B&W profiles is not possible.

    Good idea. Yes, I've posted an example on my Flickr.
    I chose a picture with good reds and yellows. There are four images in the set:
    1. The original, untouched image. This is using the new Adobe Standard beta profile, brought into Lightroom with all default settings, including linear tone curve, no exposure or color adjustments, white balance "as shot", etc. For reference.
    2. The image with my test profile applied, but no further adjustment.
    3. My original attempt at the image, using the "old fashioned" pre-DNG-profiles raw processing method, for reference. The yellows are orangeish, which isn't that objectionable but also isn't accurate. The reds are weaker than I would like.
    4. The "final" image, with my test profile plus additional tweaks -- white balance, tone curve for contrast, crushing out the blacks a bit more, etc. Two or three minutes of total processing, versus quite a bit more for the previous attempt with no "special" profile. The reds and yellows are perfect.
    The Flickr set:
    http://flickr.com/photos/100mph/sets/72157606547890574/
    This was just a first, pretty quick attempt at playing with the DNG Profile Editor. I'm sure it can be tweaked more and even more can be accomplished.
    [Edit: note: I changed the "upload date" on the test images so they wouldn't stay at the top of my Flickr page. Ignore the 2007 date, it doesn't mean anything.]

  • Converting LUTs to Camera Profiles in the DNG Profile Editor

    Hi,
    I've just started using the DNG Profile Editor, and can't seem to get the process right.
    I have some film LUTs that I'd like to convert to camera profiles for my 5D Mk II.
    Here's how I'm trying to do it, maybe someone can help me figure out what I'm doing wrong.
    This is what I tried first:
    1. Take a Color Chart into Photoshop, apply the LUT via Color Lookup adjustment layer.
    2. Save out as 16bit TIFF
    3. Open as Camera Raw, then save out as DNG
    4. Open the adjusted color chart into DNG Profile Editor, run it through the color chart section to create a recipe of color adjustments.
    5. Export out as Camera Profile
    But when I open up a 5D image in Lightroom, the profile doesn't show up in the list, so I realised maybe it needs to be saved specifically as a 5D profile, but I can't figure out how.
    If I:
    1. Do steps 1-4 as above
    2. Open a 5D DNG file so that I can set a 5D profile as the base profile
    3. Load the recipe
    The color adjustments appear on the color wheel, but nothing happens to the 5D image, no colour change at all.
    Exporting it (which does say 'Export as 5D profile') does then give me a profile that shows up in Lightroom, but it doesn't do anything to the image...
    What's the correct way of doing this?
    Thanks!
    S

    I don’t know claim to know anything about the internals of DNG Camera Profiles, but I’m pretty sure you cannot take a RGB-file (TIF/JPG) DNG and make a raw-file DNG Profile for use with your camera raws, which sounds like what you’re trying to do.
    Despite looking like it might work in DNGPE, starting with an RGB-file recipe (rather than a RAW-file recipe) will only lock the specific colors on the color wheel, rather than create a raw-capable camera profile.

  • How do I remove the DNG Profile Editor 2 from a Mac

    It sits in my dock.  It can't be closed.  It can't be dragged to the trash from the dock or from the Finder.
    My computer can't be restarted because this application is open.  I want to get rid of it but can't
    figure out how to do it.  I run Mac OS X 10.5.6. Thanks

    When you completely erase the former owner account information and install a new OS X
    using your Apple ID to get the system download from Apple servers, (so you can use App
    Store) any older sync'd items in the bluetooth list should be gone. They are not there by
    default, so they would not be there after a new fully clean installation of OS X.
    What vintage is this second-hand Mac computer product? Does it have an optical drive
    and system DVDs or it it newer and relies on download upgrade via App Store?
    If you have system discs, (10.6.3) you could install Snow Leopard then update it, to 10.6.8
    then visit the App Store online from the updated Snow Leopard, to see about upgrade to
    the latest OS X the computer can use. Then with your Apple ID account, set up the Mac to
    with a new installation of the most recent OS X it can use.
    There should be nothing old in a computer correctly set-up for resale by the original owner
    or by a reseller who does business in an official capacity, using proper methods.
    In any event...
    Good luck & happy computing!

  • Where should DNG profile editor install the .dcp file?

    Just made my first attempt to create a custom camera profile using the X-Rite color checker passport and the DNG Profile Editor.
    Thanks to the excellent tutorial, the process went smoothly.  Next I took the final step of exporting the profile (.dcp) file, expecting to find the new profile when I opened an image in ACR.  Unfortunately the new profile was not listed in the Camera Profile dropdown menu.
    After much searching I discovered that the profile was written to the folder containing the .dng images used to construct the profile.  Obviously not where it belongs in order for ACR to find it.   I assumed that "Export Profile" would automatically write the .dcp file to the proper location.
    Where should the .dcp files be installed for Win7x64 running ACR 8.2.?
    Is there a way to establish the proper location as the default in the Profile Editor?
    Thanks for your help.

    Custom-created .DCP profile files go into the following location under your Windows Users folder:
    C:\Users\YourUserName\AppData\Roaming\Adobe\CameraRaw\CameraProfiles
    The AppData folder is a hidden-system folder so you may need to turn on the viewing of those type of folders in your Explorer folder view options or just type \AppData into the folder address area and hit Enter once you get to your username folder.

  • **-Camera Profiles and DNG Profile Editor FAQ-**

    A page containing answers to Frequently Asked Questions about Camera Profiles and the DNG Profile Editor can be found
    here

    New FAQ entries:
    What changed between beta 1 and beta 2?
    Is it safe to delete beta 1 profiles? What will happen if I do?
    I now have the beta 2 profiles and want to delete the older beta 1 profiles. How do I do this?
    Please read carefully.

  • Camera Profiles and DNG Profile Editor

    I saw the lightroom 2.0 eseminar and the presenter mentioned Camera Profiles and the DNG Profile Editor. All I see is ACR4.4 and 4.3. The the FAQ page says I need ACR4.5 and I can't find it and haven't gotten any update notice. Should I just wait for an update or forget it?
    Don

    >I have CS4. Will this overwrite ACR 5.1 in CS4?
    If you have CS4, you should update to ACR 5.2. If you install 4.6, you will break your CS4 install. Either just run the Adobe updater app, or go to http://www.adobe.com/support/downloads/new.jsp to download it. DNG converter is a separate download. Both camera RAW and NDG converter contain the final release version of the new profiles. DNG profile editor can still be downloaded from Adobe Labs: http://labs.adobe.com/wiki/index.php/DNG_Profiles. There is also a profiles download there that you don't need if you install DNG converter 5.2.

  • DNG Profile Editor can't read ColorChecker shot on slide film

    I use my DSLR (Olympus E-5, 50mm macro) to digitize old Kodachrome and Ektachrome slides.  As it happens, I have reference shots of a Macbeth Color Checker I shot back then.  I thought I would be able to create custom DNG profiles to get accurate digital conversions of the slides.  But when I shoot the slide of the color checker, convert to DNG and try to build a profile in the DNG Profile Editor, I get an error when I hit the Create Color Table button, specifically, "Non-neutral grey patches.  The gray patch in row 4, column3, has a significant color cast.  Please reshoot the chart carefully to avoid color casts and try again."  I've had the same problem with Kodachrome 64, and Ektachrome 200.
    If I shoot a ColorChecker directly using the same illumination (I've tried both strobe and incandescent for the slides, neither works) the profile is generated OK.
    BTW, the RGB values for neutral color checker patches on the short of  the slide (strobe illumination) when I open it in the profile editor are
    White  123, 127, 92
    LLG  91, 94, 78
    LG  61,60,60
    DG  27,26,31
    DDG  7, 6, 9
    Black 0, 0 ,0
    I tried reshooting the slide gelling the strobe with 30Y, so I got 89,89,88 for what I think is row 4 column 3, but I got the same error message.
    So you can see that there is not a consistent color shift across the brightness range (skews from -B at the light end to +B at the dark end, while R and B are relatively constant)
    OTOH, the values for the Color Checker shot straight with the camera are consistent in the color shift across the brightness range:
    White 104, 104, 107
    LLG  71, 70, 75
    LG  46, 45, 48
    DG  24, 23, 26
    DDG  10, 10, 11
    Black 2, 2, 2
    Any way to get around this or am I just screwed. 
    Thanks

    Hi!
    I tried YouSendIt. The Express app did not install, and Safari reported an error, bad server response or something. I have earlier uploaded files using SendThisFile, but that required a URL, not an e-mail address. so if you are still interested in the files, you might mail me an upload URL. - Fine anyway that you already fixed the bug.
    -BTW, the "Subscribe to this discussion by email"-button does not work for me, it keeps deselecting itself.
    Kind regards - Hening.

  • DNG Profile editor and white balance

    I am very happy to see the practical realization of the extentions announced in the DNG 1.2 specification. This is a great step forward to achieve wide acceptance of DNG.
    While reading the User's Guide, I found following statement (in the Tutorial 1):
    >3. (Optional) If the image is not already white-balanced, you can perform a click-WB using a context click
    Why would one white balance here? What effect does that have on the result? The profile describes, which HSV will be converted in which HSV; this has nothing to do with the WB of a particular image.

    The WB feature in the DNG Profile Editor (PE) is there because it is possible that you might open a DNG file in PE that has not already been white balanced. Imagine you photographed an image under tungsten lighting but had the in-camera WB manually set to daylight. If you didn't set the WB before converting the image to a DNG, it will appear very warm when you open it up in PE. So PE's WB feature is designed to save you time by letting you do a click-WB instead of having to go back to CR or LR to adjust the image's WB.
    PE is named "profile editor" because it only edits profiles. It is not an image editor. So you are correct, you do not really need an image to edit profiles, technically. However, unless you have an image open you have no way to evaluate how good your adjustments are.
    Typically the only reason to make a profile or edit a profile is if there's something about an existing profile that you're unhappy with. And you'd be unhappy because you'd have an example of a "problem" image, where the existing profile doesn't produce the result you want. That's the image you want to bring into the PE, so you can pick out the colors that are "wrong" and fix them.
    Then ideally you would open many more images in PE just to verify that your adjustments generalize well.

  • The current DNG Profile Editor cannot interpret 7.1 raw settings

    Hi,
    I am frustrated that the DNG Profile Editor is not able to apply Lightroom's or Camera Raw's settings since the new Process 2012 has been in effect.
    This SEVERLY limits the usefulness of the Profile Editor. And yes I know it is a beta.
    However, are there no plans to release a compatible version?
    Thanks,
    Juan

    Ah, that's the problem, I have v1.3. Thanks! I've tested it and it validates all DNG files fine.
    The reason I have the wrong version is the Adobe DNG SDK web page (here) links to the 1.3 version of the SDK. The only way to know there's a newer version is if you search for it or someone tells you - like you have.

  • How to make dual illuminant profile in DNG profile editor?

    I have just started working with the DNG Profile Editor.  In another discussion I commented on the clarity of the instructions provided by the tutorial.  I had no difficulty creating a single illuminant profile using the X-Rite color checker passport.  But when it came to producing a dual illuminant profile, following the instructions exactly, I was stymied. 
    1.  Open dng image of Color Checker photographed in 6500K illumination.
    2.  Open dng image of Color Checker photographed in 2850K illumination.
    3.  Select Chart tab in editor.
    At this point one is instructed to "Click the 6500 K-lit ColorChecker image window to select it."
    But the 2850K lit image (last loaded) has replaced the 6500K image window (at step 2) and I can find no way to reopen the 6500 K lit image window in order to proceed to the next step.
    As a matter of interest, why do these instructions suggest setting the pop-up window in the Chart Pane to "6500K only" and then create color table with first image.  Thereafter select second image, set pop-up window to "2850K only" and create color table.  I seems to me that, having loaded two images (even if I can only see the second image loaded) one should choose "both color tables" and then create color table.  In fact I have tried this and it does produce a profile, but I have no way of determining if it is a correct dual illuminant profile.
    Please help.

    2. HYPERLINK "/people/MadManChan2000"MadManChan2000,
    Oct 21, 2013 9:09 AM in reply to blumesan
    Note that the "Both color tables" option always creates a single-illuminant profile. The "Both color tables" option means that the computed color corrections will be applied to both color tables (i.e., the color table for the first calibration illuminant, which is usually Standard Light A, and also the color table for the second calibration illuminant, which is usually D65).
    After playing around with the Profile Editor for a while, and examining the results with dcpTool, I now understand (I hope) what Eric is saying. In his language a single-illuminant profile is one created from a single dng image using the "both color tables" option (without regard to the illuminant used to capture that image.) When one does this (using Adobe Standard as the base profile) an examination of the resulting profile with dcpTool shows the following:
    Two illluminants are identified: 17 (Std A) and 21 (D65).
    Color Matrix 1 & 2; Forward Matrix 1 & 2; Hue Sat Delta Tables 1 & 2.
    Which certainly gives the impression of a dual illuminant profile to novices like myself.  My guess is that the PE software itself applies a default assumption of these two illuminants, corrects the image for each illuminant and constructs two color tables, one for each illluminant. When used, the profile will interpolate between the two tables based on the white balance of the image being edited.
    If this is indeed correct it makes me wonder in what way does such a profile differ from a dual illuminant profile created from two dng images, each captured under a different illuminant (2800K & 6500K) as described in Tutorial #6 of the PE instructions. These instructions contain the following description of such a dual illuminant profile: "The result is a single profile that performs well under a wide range of illuminants instead of a single fixed illuminant."   Which really make me scratch my head. Should one conclude from this that a single illuminant profile (created using the "both color tables" option) will perform less well under a range of illuminants?  Will it perform well only under a narrow range of illuminants centered around the illuminant used to capture the single image? 
    As a footnote, it is worth remarking that I (and perhaps others) have been confused by examining profiles created by the XRite software when using only a single dng image. Examining such a profile with dcpTool one sees the following structure:
    One illuminant only #23 (D50)
    A single Color Matrix table.
    A single Hue Sat Delta Table.
    Thus one comes to expect this structure in a single illuminant profile.
    I would be very happy to see Eric's comments..

  • Creating profiles for special illuminants in DNG Profile Editor

    I have successfully used the DNG Profile Editor with images of the ColorChecker Passport to create simple dcp profiles for daylight and tungsten illumination.  I have obtained very satisfactory profiles using both a single image and the "both color tables" option, as well as two images (one tungsten and one daylight) and the "dual illuminant" method.
    Now I wish to construct separate profiles for use with unusual light sources: fluorescent lights and white LED lights.  Can some one tell me how this is best done using the DNG Profile Editor.
    Appreciate any suggestions.
    Mike.

    When there are two illuminants in a profile ACR will interpolate an effective profile based on how far the actual image WB is from one of the illuminants in the dual profile.  For example if the profile is using the 2650K (Tungsten) and 6500K (hazy sunight) as the two illuminants and your images is taken in direct sunlight with a WB of 5000K then the profile will be more the D65 profile but a little bit of the redder A profile mixed in.  This allows the dual profile to be used for any lighting with a Temperature between A and D65 that also has a Tint number close to or a little above zero.  An A/D65 dual profile fails for fluorescent lighting because the Tint number is quite a bit different than either the A or D65 Tint numbers.
    To your question, for a single illuminant profile, you should use the Both Color Tables option so that no matter what WB your photo has, the profile used will be the same.  This makes the illuminant A and D65 irrelevant because any interpolation between the two illuminants would result in the same profile numbers.
    However, I also think that the dual illuminant numbers are not necessarily hard-coded to A and D65, at least not when you use the CCPP plug-in for LR to create the profile, but are actually whatever your photos WB numbers are, so you can make dual-illuminant profiles for other pairs of lighting, such as fluorescent and daylight or fluorescent and incandescent, or even sunlight and shade, depending on what mixed lighting you have at your location and time of day.
    An easy way to test this would be to make a dual profile, one DNG being fluorescent and one being your blue LEDs (two sources far away from A or D65), then also create two single profiles, one for each of those same two lighting sources.  Test the dual-illuminant profile with the fluorescent CCPP image, and then switch the profile to the single illuminant fluorescent one and see if anything looks different.  Do the same test with the blue-LED CCPP image with dual and single blue-LED profiles. 
    If the look of the image is the same when using a dual profile where one end is the same as the single profile both tested with the actual CCPP image that was used to make the profile or one end of the profile, then the illuminant numbers in the dual profile change to whatever the DNGs illuminants were.  However, if the look changes between the dual profile and the single profile when applied to one of the dual-profiles image's WB then the illuminant numbers must be fixed to A and D65, and so any dual profiles are useless if the two illuminants do not match A and D65.
    If your experiment fails using the DNGPE, then try it using the CCPP software and the LR plug-in. 

  • About to use DNG Profile editor

    I've had my Colorchecker for a few weeks, and I finally have time to set up my profiles for LR 3.4. In reading the DNG Profile editor tutorial page (http://labs.adobe.com/wiki/index.php/DNG_Profiles:Editor), I have a few questions:
    1) If I use Tutorial 5, I am guessing I will have to create a profile for each lighting/WB condition, i.e., one for Tungsten, one for Fluorescent, one for sunny, one for overcast, one for flash, etc... Is that correct? Is there an advantage to doing this vs. going for the dual-illuminant approach explained in Tutorial 6?
    2) In Tutorial 6, for the dual illuminant profiles, it states that one of the reference shots should be taken at 6500K. I'm not quite sure how to achieve this, since daylight and flash, to semi-constant WB sources I can easily achieve, are around 5000-5600K.
    3) Should I (in LR) White-balance the Colorchecker reference shots, then convert to DNG, prior to bringing the DNG file into DNG Profile editor? Or is it preferable to WB as explained in Tutorial 1, step 3?
    4) Finally, it's somewhat unclear how I bring the profiles into LR for use during the Import or Develop phases. Tutorial 1, step 9 mentions a "CameraProfiles directory" for ACR and LR, so I'm guessing I need to go digging through the Adobe folders to locate this directory and place/save my profiles there?

    eswrite wrote:
    1) If I use Tutorial 5, I am guessing I will have to create a profile for each lighting/WB condition, i.e., one for Tungsten, one for Fluorescent, one for sunny, one for overcast, one for flash, etc... Is that correct?
    If you want a broad purpose DNG profile then yes, doing a dual illuminate profile is useful. Shoot a target under tungsten and under daylight and make the dual illuminate profile. There's no real reason you need to spawn off a bunch of other profiles for only slightly different light. The dual illuminate will handle cloudy or overcast just fine. If you also shoot with special lighting sources like fluorescent (which doesn't have a complete spectrum) or other non-standard lighting sources then do a profile for those special conditions. If you are creating a profile specifically for studio flash, you can get by doing only a single illuminate profile for the strobes...but in that case, the profile won't be as accurate if you also try to use it under tungsten–which would be the reason to do a dual illuminate profile.
    As far as the D65 color temp, the closer you can get to it the better, but D55 should work fine. The key is to make sure it's evenly lit. The big difference between D65/D50/D55 is the relative amount of the blue light components-all three will be fairly close. Tungsten however has vastly less blue which can impact the sensor's spectral response–which is why the dual illuminate is suggested.
    Once you do the CC shot, don't bother with tone/color corrections in ACR before converting to DNG. They won't have a material impact on the profile creation. The CC shot MUST be evenly lit and of an optimal exposure...
    As far as where the profile goes, it depends on the system. Once you've created the profile, PE should default to the correct location, otherwise state your system and we can tell you where to put them.

  • DNG Profile Editor "base profile" question.

    I'm profiling a Canon 5D3 with both the Adobe DNG Profile Editor and the Xrite ColorChecker software. It's been about 3 years since I last profiled a camera, so I'm re-doing the learning curve. My question now is how and why the DNG Profile editor depends on a "base profile?" Specifically, why does the DNG PE Chart Wizard generate different results depending on what base profile is used.
    I see in the documentation that "all color adjustments made in the DNG Profile Editor are defined relative to a base profile." I understand that logic when making a custom profile via manual tweaks. You have to have a starting point. But I don't understand that logic when using the Chart Wizard. I expected the Chart Wizard to arrive at the same pre-defined target point regardless of the starting point. It does not seem to do that.
    I discovered the difference by using an apparently bad workflow. I shot my colorchecker chart, converted the CR2 to DNG and brought it into Photoshop via ACR to inspect. That stored "Adobe Standard" as the base profile in the DNG.
    Then I fed this DNG to the DNG PE Chart Wizard and generated a profile. I opened the image in ACR and applied "My Profile", which became the base profile in the DNG file. I thought I did something wrong, so I ran the same DNG through the Chart Wizard again and generated "My Second Profile." That version looked very strange, so I did it again and made "My Third Profile."
    Now I have three profiles. My First Profile was made from Adobe Standard base. My Second Profile was made from My First Profile base. My Third Profile was made from My Second Profile base. Each iteration becomes more strange (bad), so this is clearly not the proper workflow. But what is? What base profile should be selected for Chart Wizard and why does it matter?
    Being curious, I did the same exercise using the Xrite ColorChecker software. That software generates the same result, regardless of what base profile is stored in the DNG files. I'm not sure I like the results, but at least they are consistent.

    DNG Profile Editor lets you define color edits (in the first tab) using a set of color control points.  These control points in turn define a color lookup table used to perform the color correction when processing a (raw) image.
    When you use a Base Profile, the resulting color table in the final profile is a combination of the base profile's color table, plus the color table defined by any edits that you've added in the first tab (using the Chart Wizard counts as adding edits to that first tab).
    The reason you can get different and less smooth results if you apply the Chart Wizard iteratively is because you are applying lookup table after lookup table.  The current color table-building method used by DNG PE has some limitations regarding smoothness of color profiles if two color control points are placed too closely (this can happen with the Chart Wizard, or if you specify two points manually that are close to each other).  These problems can become more noticeable if you apply the DNG PE iteratively.

  • Questions about DNG Profile Editor recipe code

    I have been playing around with DNG Profile Editor. With a text editor I made the following recipe:
    I have some questions:
    1. Right now I have my control points at 60 saturation. Will using two points for each color (say 70 and 40) make my changes more consistent across darker and lighter shades of the specific color?
    2. Does DNG Profile editor respect HueLow and HueHigh, are they just placeholder numbers, or are they ignored if two points are close to each other?
    3. What does FeatherAdjust do? I'm guessing it controls the rate of drop off of the corrections. Is the value respected by DNG Profile editor when it creates a profile?
    Thanks for your time and attention,     -Bruce.

    1. For now DNG-only. Here's why:
    http://labs.adobe.com/wiki/index.php/DNG_Profiles_FAQ#PEOnlyDNG
    http://labs.adobe.com/wiki/index.php/DNG_Profiles_FAQ#WhyNameDNGPE
    http://labs.adobe.com/wiki/index.php/DNG_Profiles_FAQ#WhyPESeparate
    2. Standalone for now. See above links for why.
    3. Use the 'Preview Color Changes' option in the Options menu.
    4. You can use 'Apply Raw Adjustments' in the Options menu to see your raw adjustments. This is __not__ recommended for building a general-purpose profile because you are then optimizing a profile with specific image adjustments in mind, rather than building a profile based more on the inherent camera characteristics.
    5. True, that is a limitation of this implementation.
    6. I am not sure what you mean. The Chart Wizard automatically optimizes the color patches in a test shot based on reference values for many physical charts, which is more practically useful than the numbers printed on the reference card that comes with the chart.
    7. Make sure you avoid color casts in the bottom row. The PE is picky about making sure your gray patches are relatively neutral. It is an attempt to help you get a better profile.
    8. Use 'Show Affected Colors' from the Options menu.
    You may wish to read this page carefully and thoroughly:
    documentation
    It is the reference online documentation for the DNG Profile Editor and a few of the things you wish to do, such as preview all color changes, apply raw adjustments, and visualize the extent of each color adjustment, are all documented there.

Maybe you are looking for