DNG Profile Editor won't open DNG from Panasonic LX3

I need help. I've just added a new camera (Panasonic DMC LX3) and I want to create custom camera profiles for use in Lightroom. I have done this with all my cameras before with no problems. The raw files open fine in Lightroom (2.6) and CS-4 Camera Raw (5.6.0.148). First I exported to DNG from Lightroom then tried to open the file in DNG Profile Editor. I received the following error message:
"DNG Profile Editor could not open the selected image. Note that the selected image must be a valid DNG colr image". I tried the usual closing and re-launching the application, restarting the computer, etc. all to no avail. I then downloaded the latest stand alone DNG converter (5.6) and performed a fresh conversion with that. Still no luck. The DNG's all open fine in Lightroom and CS-4. Any suggestions? These profiles have become an important part of my workflow.
Mac Pro 2X 2.8 Quad Xenon, 10GB ram, 4TB HDD, OS-X 10.5.8
and MacBook Pro 2.4GHz 4GB ram, OS-X 10.5.8
Lightroom 2.6 (64 bit)
CS-4
DNG Profile Editor 1.0.0.39 Beta 2

Yes, I used the stand alone converter as well as lightroom. I did find a solution on another post. I changed the dng compatibility in the drop down menu to "Camera Raw 4.6 and later" (it was set to " Camera Raw 5.4 and later") and it worked fine. This worked with both the stand alone DNG converter and exporting as DNG from Lightroom. It seems that the DNG profile editor hasn't been updated since the 2008 beta so It doesn't recognize the newer spec DNG. Thank you for your assistance, I was starting to panic...

Similar Messages

What kind of DNG file for DNG profile editor ?

Can somebody help me??? I have a problem to use DNG profile:
I am user of Fujifilm S5Pro, which has RAF file (=raw). The ACR (start from version 3...) and DNG understand my RAF files very well. But DNG profile editor dose not want to open it, even if Adobe DNG Converter 4.5 converts it to DNG file. My workflow is:
Launch Adobe DNG Converter.exe, => convert RAF to DNG (tryed different settings);
Launch DNG profile editor, => trying to open DNG file => have error???
May be I'm doing in a wrong way? Please advise me.

I tried to do the same on other PC with Vista (fully English). Also update DNG converter up to 4.6. And no success... :-(.
Every time I have the same error: "DNG Profile Editor could not open the selected image. Note that the selected image must be a valid DNG color image."
I could not understand... where is a bug.
Moreover, I took NEF from Nikon D80 and CR2 from Canon 20D and converted them to DNGs by converter 4.6. DNG Profile Editor did not want to open them on both Windows Vista and XP, and made the same error.
Do I really do wrong things? I'm completely lost
Thanks in advance,
Slava

Adobe DNG Profile Editor

Has there been any update to this beyond that in 2008 found on Adobe Labs? (I want to try using it to calibrate ACR for my camera with a shot of a MacBeth Color Chart.)
To be more precise about this, I currently use ACR Calibrator to calibrate ACR for my Canon 1Ds II. I now see there is beta 3 of Adobe DNG Profile Editor but note that it utilises a small subset of the GMB Digital Colorchecker SG target chart.
ACR Calibrator seems to produce quite different results from Adobe DNG Profile Editor. I have followed the steps below when using the latter.
Download DNG Profile Editor and drag to Applications
Launch Photoshop and open the raw file of your macbeth target.
In camera raw, place all settings to zero, curve to linear and turn off any sharpening etc. Click Save Image, choose dng as the file format and save it.
Launch DNG Profile Editor.
File / Open DNG File and choose the dng file you saved previously.
Select the chart tab in DNG Profile Editor.
Move the colored circles to the center of the matching colored corner square in your raw file
Click Create Color Table.
Choose File/Export <Camera> profile... Give it a name and save.
Exit DNG Profile Editor.
Re-launch photoshop and open a raw file. In Camera Raw, on the calibration tab, you should now see the profile you just saved.

ssprengel wrote:
I don't know of any other references or CC Passport numbers other than what Google can come up with. Babelcolor has some standard-deviation of spectrum numbers for a sampling of 20 charts done in 2006 and also some worst-color vs average-color visual comparisons to get an idea of how variable charts or at least their measurements can be. Somewhere it says the me4asurements were done of the standard and also the minichart, mixed together, I assume. I don't know if there is a list of the raw data or not.
To understand the source of the variation you really need to see multiple measurements with the same instrument, with different instruments, and of different charts from different manufacturing runs and different ages and measured in different temperatures and humidities, otherwise it's not easy to say whether the variations we're seeing between the CC standard and the CC passport in the article are within the normal variations or not or if they represent a significant difference not explained by normal variations.
Yes, I know the Babelcolor data and I have already included them in the study.
Obviously I do not have the opportunity to have the information to get an overview of the real things, but by analyzing various measurements I saw that Myers had to be the closest to official data of the CC Passport and instead is the more distant. Hence my doubts about the measurement.
Thanks anyway.
Marco

Adobe DNG profile editor bug w/ GH2 files where aspect ratio is not 4:3

Hi,
posting here as Adobe DNG subforum is essentially dead
Panasonic GH2, select aspect ratio 3:2, get .RW2 raw file, convert it to .DNG using Adobe DNG converter (6.4.0.121 beta), try to open w/ Adobe DNG profile editor (1.0.0.39 beta 2) -> error message "DNG Profile Editor could not open the selected image. Note that the selected image must be a valid DNG color image".
XRite software has no issues to process the same .DNG file (converted from the original .RW2 w/ 3:2 aspect ratio).

Eric - just make it easier for you to reproduce the bug - here is the original .RW2 file (certainly ignore the quality of colorchecker shot in terms of how the target is lit, etc - it was not to make a profile actually - it was to illustrate the bug in question) = http://www.box.net/shared/f419prmuo2 ... and I am uploading the converted .DNG file too just in case = http://www.box.net/shared/gy5o9zzi57

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.

Captivate 5.5 skin editor won't open

I'm working in Captivate 5.5, and the Skin Editor won't open, either from the Project menu or with Shift+F11. Any idea what's causing that? Is there another way to get at the Skin Editor, such as through the Publish dialog box? I couldn't find another way.
-Stuart

Hi Stuart
At any point have you had a second monitor attached? If so, it's quite possible that the dialog is indeed opening, but was last opened on the second monitor. In that case you need to either make your resolution large enough so that you see the dialog sitting in the odd location or re-connect the second monitor so you may then view the dialog and drag it back to the visible area of the screen.
Cheers... Rick

DNG Profile Editor: Can't create profile from JPG file

Guys, could you tell me why DNG Profile Editor fails to create color table using 4 colored circles ? It says "Unable to check white balance using gray patches. Please use the four color circles to identify the four corner patches of the chart and try again" even though I places four circles properly (it works with DNG files shot with my Nikon D700).
I created this DNG file from JPG file by opening it in Camera Raw plugin and saving as DNG file. Original JPG was shot on camera of Samsun Galaxy S phone. I know I'm crazy but I want to have color profile for it All patches are properly exposed after slight correction of Exposure slider in Camera Raw.
I'm using latest beta3 build
Here is link to DNG and JPG file I'm trying to use
http://www.box.net/shared/4v2rzlzjfp
Thanks!

If you convert your JPG to a DNG can you change the profile to the one you computed from the other JPG you converted to a DNG?
Profiles are not for JPGs. Profiles are for RAW files that ACR supports. You can't (easily/ever) get a RAW file from your Galaxy S and Adobe doesn’t' support that RAW format even if you could.
To see if your profiling is working, you can used the ColorCheck module from a trial version of Imatest that you download from www.imatest.com and look at the color-error.
You can also try the Read_Color_CC24.jsx script from Rags-Gardner:
http://www.rags-int-inc.com/PhotoTechStuff/ColorCalibration/

DNG Profile Editor not working with new Profiles from LR 3.6?

I'm noticing that DNG Profile Editor is not really able to work with profiles from newly supported cameras, like the X10. Apparently the profile spec has been updated. Has DNG Profile Editor been abandoned or will it be updated to work with the new spec? I really hope it is!

Thanks. I am looking forward to editing the v4 profiles for the D700 - I just want to change a few colors in the existing profiles. I think the existing v4 profiles do an excellent job of matching the Nikon colors, but I don't like a few of the Nikon colors. Some colors have too much Red, but Red is too Orange.
I have selected a number of images that have colors I want to change. I selected the Camera Neutral (v0) and Camera Portrait (v0) and using the latest DNG Profile Editor I select the 18 colors from the Color Checker Chart. I then use the images that have the colors I want to change and determine which of the 18 points I selected from the Color Checker are close. I then edit those points - only 6 points. I only need to change the Hue by 5 units or less. I don't change any of the other selected points of the Color Checker, but feel that by selecting them I locked in the exisiting colors. Hope this is a good aproach.
I wish Nikon would do something equivalent to the DNG Profile Editor for their Picture Control profiles so they could be edited and loaded into the camera.

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

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.

DNG profile editor

A couple of questions about DNG Profile Editor:
1-I know Lab values on my ColorChecker (measured with an EyeOne 2° D50). I shooted it with a Nikon D80 and I want to tweak one of the new Camera Raw profiles to match those values or to go closer. I see that changing the base profile (popup menu in Color Tables Pane) the image appearence changes a lot but the Lab numbers readout doesn't. I followed the tutorial on the Adobe site but I can't figure out how to make the camera calibration without having a numeric value, before and after, to look at. The tutorial tells that you may 'adjust the selected color via the Hue, Saturation and Lightness slider and you will see the preview in real-time'. That's true but does it means that is a sort of 'visual calibration'? Is there a way to tweak colors by the Lab numbers in order to have the best match from original Lab values in input (on the target) and Lab values in output (in a ProPhoto rendered image)?
2- When I create a Color Table from my ColorChecker it appears that in the Color Tables colors are already (and automatically) changed. Does it work like the ACR Calibration Scripts that way? And is it possible to change the reference Lab values (ColorCheckers are different in color values) as it was with a simple ACR script's editing?
Giuseppe Andretta

Eric,
Before starting, I want to say that I had cataract surgery last month. The vision improvement was almost instantaneous and dramatic. I can now state that color differences in individuals can be much greater than expected. It is hard to express how big the difference is in my own vision, let alone between two other individuals. Any color assessment tools must accommodate numeric as well as visual comparisons. That said, the healing process has also affected how much time I can spend comfortably in front of my screen. I hope my comments will be taken constructively.
As others have commented, I also feel that the CC24 Lab target values being used should be documented. Published values from Gretag, Lindbloom, Babbage, and others disagree. Without the target numbers it is difficult to determine accurately the calibration result.
My first attempt seemed to go smoothly, but when I verified the results with ReadColors.jsx (my script) the numbers degraded slightly. I was using the Gretag target values, so these may not be what Adobe is using. Also, I had already calibrated ACR for my D3. The doc seemed to imply that the ACR tabs would all default to zero and that was what displayed in the Color Matrices panel. But that was not what showed in the ACR panel. So I tried again, setting all ACR sliders to zero. This calibration attempt was a disaster, numerically and visually. Now I am confused. What is the relationship between these and what are the recommended user actions? In each case, I exported the DNG profile and selected it subsequently in ACR to re-open the image.
Next, I played with the Color Tables panel. I set a watchpoint on the blue patch. As long as I hold the eyedropper over the blue patch the Lab (and other numbers) track. But as soon as I move the mouse to the sliders, the numbers disappear. If I move the hue and saturation sliders the image and the patch sample both change. And, yes a little arrow shows in the color wheel. But after moving the eyedropper back, none of the numbers have changed. The lightness slider is even more bizarre. Obviously no arrow (z-axis) but the image brightens and darkens (OK), without any corresponding change in the patch sample (watchpoint) on the right (not OK). And again, no change in the numbers at all. It would be very helpful if the target values were shown here and if the currently selected watchpoint that would track the numeric changes. It would also be nice if the watchpoint could show the target color as well as the initial and changed image patch colors.
I dont understand the purpose of the Tone Curves. I understand gamma and Adobe linear, but these do not correlate to the ACR tone curves. And again the image changes but the numbers do not. Since we cannot set watchpoints in the neutral patches it is very difficult to assess any changes the user might make.
Next, I used the Chart panel to Create Color Table. When I return to the Color Tables panel, there are the 18 color (no neutral) watchpoints. I can see that blue has changed in the watch point and the arrow in the color wheel. But the numbers are still the same as before. Scrolling through the watch points I can also see that the hue and saturation sliders have changed. But the lightness slider did not change in any of the color patches. I anticipated that this would be the major improvement over the ACR sliders. Is this just not in the calibration algorithms yet?
This is a good start, but until I know what the target values are and what I should be doing about the existing ACR slider settings, I am at a stopping point.
Cheers, Rags :-)

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 step-by-step usage

I hope all will forgive the long post, trying to both verify my understanding and perhaps help others by providing more detail.
1. Shot the CC with a D300 and D200 outside with cloud cover, exposures within seconds of each other, different lenses but both Nikkor.
2. Brought both nefs into ACR, white balanced (approx. 5500K) and equalized exposure using second neutral patch, applied new Adobe standard beta profiles to each. Very good match, first time I've ever seen truly equal images from the two cameras thru ACR.
3. Created DNG's of each cc image nef with DNG Converter.
4. Used DNG Profile Editor on the D300 image (white balanced), set base profile to Adobe standard beta, selected only the Red, Green, and Blue patches on second row. No changes to three colors, created recipe with "Edit both color tables smimultaneously" checked.
5. Opened recipe file with Wordpad, very interesting to examine, easy to see what's going on since in XML format. Six color adjustment sections, three for 2850 and three for 6500. Also the entire base profile in binary form is encapsulated in the XML file.
6. Opened D200 DNG file in PE, white balanced, used old 4.4 profile as base (deliberately trying to create different colors than D300). Loaded the D300 based recipe, exported new D200 profile.
7. Now back to ACR, loaded D300 cc image with Adobe standard beta profile selected and white balanced, and D200 cc image with old 4.4 profile selected and white balanced and exposure adjusted to match D300 image. Opened both in Photoshop CS3 in ProPhoto space. As expected, there was considerable difference in the color patches, both visually and by the numbers.
8. Back again to ACR, loaded D200 cc image with recipe modified profile from step 6 and white balanced and exposure adjusted to match D300. Brought into PS and compared to D300 image. Now the Red,Green,Blue patches matched well with the D300 image, only slight differences. Actually just selecting those three patches brought all 18 cc patches into a fairly close match.
In conclusion it appears to me that a recipe has enough information, with the color table entries and the embedded base profile, to "move" the same colors in another profile to achieve a good match. And it's apparently moving "both ends" (2850K and 6500K separate sections) of the profile appropriately, although I'm less sure of this. Quite an interesting and useful development by Adobe.
Richard Southworth

I hope all will forgive the long post, trying to both verify my understanding and perhaps help others by providing more detail.
1. Shot the CC with a D300 and D200 outside with cloud cover, exposures within seconds of each other, different lenses but both Nikkor.
2. Brought both nefs into ACR, white balanced (approx. 5500K) and equalized exposure using second neutral patch, applied new Adobe standard beta profiles to each. Very good match, first time I've ever seen truly equal images from the two cameras thru ACR.
3. Created DNG's of each cc image nef with DNG Converter.
4. Used DNG Profile Editor on the D300 image (white balanced), set base profile to Adobe standard beta, selected only the Red, Green, and Blue patches on second row. No changes to three colors, created recipe with "Edit both color tables smimultaneously" checked.
5. Opened recipe file with Wordpad, very interesting to examine, easy to see what's going on since in XML format. Six color adjustment sections, three for 2850 and three for 6500. Also the entire base profile in binary form is encapsulated in the XML file.
6. Opened D200 DNG file in PE, white balanced, used old 4.4 profile as base (deliberately trying to create different colors than D300). Loaded the D300 based recipe, exported new D200 profile.
7. Now back to ACR, loaded D300 cc image with Adobe standard beta profile selected and white balanced, and D200 cc image with old 4.4 profile selected and white balanced and exposure adjusted to match D300 image. Opened both in Photoshop CS3 in ProPhoto space. As expected, there was considerable difference in the color patches, both visually and by the numbers.
8. Back again to ACR, loaded D200 cc image with recipe modified profile from step 6 and white balanced and exposure adjusted to match D300. Brought into PS and compared to D300 image. Now the Red,Green,Blue patches matched well with the D300 image, only slight differences. Actually just selecting those three patches brought all 18 cc patches into a fairly close match.
In conclusion it appears to me that a recipe has enough information, with the color table entries and the embedded base profile, to "move" the same colors in another profile to achieve a good match. And it's apparently moving "both ends" (2850K and 6500K separate sections) of the profile appropriately, although I'm less sure of this. Quite an interesting and useful development by Adobe.
Richard Southworth

DNG Profile Editor - questions about

0) Thank to Eric Chan for your work on this. Until now I used the Camera Calibration process through Photoshop and Camera Calibration table. But I see this as a big progress.
1) Will it stay only DNG editor or it will be also for raw pictures without a necessity to convert them to dng?
2) Will it be only stand alone aplication or as well a part of the LR?
3) Now I can switched off and on one color change (by the left mark in the Color List Box). Could it be possible to switch off and on the whole Color List Box to see all done changes?
4) I have red your comment that this tool doesn't work with lightness, only hue and saturation. But if I want to work on a specific picture (i.e. a man wearing a red sweater), it will be fine to have it in the brightness close to an end picture. Will it be possible to open a picture not only with WB, but also with exposure, blacks and other basic development setting?
5) Under the eye drop tool, I can see numbers of "initial" or "starting" color. But I can't see the numbers of changed color. It would be fine if I know the new numbers to see how close I am to them. It would be fine if the number over the color List Box will be also for starting color and also for end colors.
And one little proposal: if the color will not change, show in Color List Box only the starting (left) half of a color. Than I can simply see that I didn't set a new color or the color stay exactly the same (it is only a question if exactly the same or very close to the same).
6) It could be, that I will not use the exact color checker table for what you did process on the tab Chart. But many of color checker are delivered with exact numbers and picture on a cd, so it will be fine if I could open this "master" picture of a checker producer in a right panel under the Color List Box and simply take from it the end colors. First go to the main picture on left, choose the "initial color" and then simply go to this "master" picture in right and take the "end color". What do you think about this?
7) If I work on the tab Chart, I get the error window "not neutral gray patches, row 4 culumn 1". But if I move the circle to row 4 culumn 2 it works fine. Is there any difference or problem?
8) And last: how far is acting the shift of color. It will not work only for the one color but close surroundings will be also efeccted. How smal or large is the surroundings? E.g. if we take 360 degres for hue.
Tom

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.

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.

DNG Profile Editor won't open DNG from Panasonic LX3

Similar Messages

Maybe you are looking for