DNG Profile problems..

I am using the profiles for my D3 in lightroom 2.2 but as it shares the same processing code I thought I'd ask here too..
I am getting odd (usually purple) colour blobs in some of the raw files which do not appear in NX2 rendering using the "vivid profile. The blobs do not appear in "adobe standard"
http://img135.imageshack.us/img135/6619/lrnxcomparison001ahn9.jpg
If anyone else is having this problem or can help it would be much appreciated.
Thanks.

Hi guys, thanks for the replies.
I fixed the problem by switching to "Adobe Standard" profile (and note no matter how far I push the saturation in LR then the blob is simply not there). This seems to match camera vidid much closer than "ACR 4.3 etc when I bump the saturation and contrast.
Also, the problem was visible (albeit to a lesser extent) in the Camera vivid profile with no additional saturation applied.
I took nose reduction off in all programs and the colour noise suppression in LR did not effect the purpleness.
I have an additional image which shows the problem much clearer which I may post if anyone is interested if I get some spare time this evening.
Thanks all.

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

Question about dng profiles

Question for Eric or his coworkers ...
Is there some limitation regarding size of LUT in the a dng profile? Biggest profiles produced by Adobe have 90x16x16. For profiles made with my program I'm using bigger LUT (120x16x61), in order to reduce slight banding issues and improve precision in shadows. I posted some of those profiles on CHDK forum when people were asking about them, and lately, I posted a profile for Canon 40D because Noel wasn't satisfied with sky saturation using Camera Standard
I'm asking this because ACR 6.5rc1 crashed 3 or 4 times so far, reporting an error, so I returned version 6.4. Also, ACR 6.5 published a day or two ago had some problems with screen refreshing after zooming a cropped image (so I reverted to 6.4 again). All previous versions were working flawlessly
I'm using Windows XP 32 bit, computer has 4 GB RAM

I suppose it's not because of profile, as I didn't have any problems until ACR 65rc1, but just want to make sure
If it is, I can make smaller one for you (just it would be slightly less accurate)
About refreshing problem (6.5 release), I opened a group of raws from 400D. First one had a crop made previously. When I zoomed it, nothing happened (I think I was using Ctrl, as I wasn't in a zoom pane, but I'm not sure). Then selected the second photo and returned to the first one. It appeared zoomed now. Strange.
Edit: tried editing some older Canon SX110 raws (dng) with ACR 6.5 again. Selected a group of about 100 photos, selected all of them, zoomed all of them at the same location to correct a bad pixel on some photos with spot removal tool. After correcting 10-15 photos, I got an error "The operation could not be completed". If I close error message, the same error window reopens again ...

Camera Profiles and DNG Profile Editor beta 2 now available

Hi everyone,
Beta 2 of the camera profiles and DNG Profile Editor are now available. Please visit here and enjoy:
http://labs.adobe.com/wiki/index.php/DNG_Profiles
I hope to have more detailed release notes/changes for you soon. You are welcome to ask questions, but please note that it may take a while for me to respond.
Eric

Eric,
I followed very carefully your instructions for installing the new beta2 profiles and deleting the beta1 profiles, but have the same problems as many others. I'd like to provide a bit more information. I'm running Windows Vista Home Premium and have installed Photoshop CS4, updated with ACR5.1 and Lightroom 2.1 final release. As others have described, the default for all of my images was set to one of the Camera profiles (Canon faithful beta1), but now the profile name in Lightroom is blank. I tried looking at the other profiles and it does indeed appear that the beta2 profile is being used, but if I then reset the image it now shows ACR4.4, whereas the image had been imported with the camera profile as default. Also, if I open an image in ACR5.1 that was specified to use the same camera profile, it now shows ACR4.4 and it is not using the beta2 profile of what I had been using, I can see this by selecting the other profiles. Going back to Lightoom, I guess I could select all my images and select the Canon faithful beta2 profile, but then the mark shows up bottom right of the image showing that they have all been edited/modified, is there anyway to get all my images using the profile I was using but the beta2 version, without this happening and how about new imports?
Thanks, David.

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 management

Is it possible to create and use a shoot-specific custom DNG profile to process a set of images for a given shoot, and then archive that DNG profile for safekeeping but removed from view of Lightroom's Camera Calibration panel, without compromising Lightroom's ability to still work with that shoot's images - say, to make further develop refinements, virtual copy variations, prints, etc.?
Asked slightly differently, when in Lightroom's Camera Calibration panel you select a specific DNG profile to apply to a given raw image, does the profile data from within that DNG profile become image-specific metadata of the target image and get stored along with the rest of the image-specific metadata in the Lightroom catalog itself (and subsequently in the DNG raw image file when I save the Lightroom data to that image file)? Or, instead, is only the IDENTITY of the selected DNG profile saved as image-specific metadata, with the DNG profile itself needing to remain "installed" in order to carry out any future Lightroom work on that raw image?
Using the X-Rite ColorChecker Passport in conjunction with Lightroom, it is quite easy to imagine creating custom DNG profiles specific to a given shoot's unique lighting conditions. Creating DNG profiles specific to a given shoot, the collection of shoot-specific DNG profiles for a given camera body could grow to be quite large over time, making it tedious to wade through that collection in Lightroom's Camera Calibration panel to select the particular profile for the shoot being processed. X-Rite makes the "DNG Profile Manager" available to registered users of the ColorChecker Passport to assist with this very problem. It's great that this utility allows us to "Disable" DNG profiles, allowing us to keep our Lightroom Camera Calibration "Profile" menu manageable. But, if you use the X-Rite DNG Profile Manager to do this, does "disabling" a given DNG profile interfere with any further work in Lightroom on images for which that given DNG profile has ALREADY been applied?
PLEASE do not speculate on this response. If you do not know for certain, please allow someone who does (an Adobe engineer, perhaps?) to enlighten us.
Thanks in advance,
/eddie

Thank you to those who have offered responses.
Please do not get confused. As the most recent response clarifies, this is not about storing profiles within original raw files, or the differences between DNG files and original raw files. In fact, at it essence, my real concern is not even about DNG files at all, really, although it includes them by association.
My original question can really be answered in consideration of Lightroom alone: When a custom DNG profile is selected for an image by using the Camera Calibration panel of Lightroom's Develop module, does Lightroom itself internalize that DNG profile selection by recording into the Lightroom metadata database only the IDENTITY of that DNG profile assignment, or the actual DNG profile data contained within that DNG profile? If Lightroom records into the Lightroom database only the identity of the assigned DNG profile, then Lightroom would of course need to go back into that DNG profile later for the actual DNG profile data in order to do any subsequent development processing of the image for which that DNG profile was assigned. If, however, selection of a DNG profile using the Camera Calibration panel of Lightroom's Develop module causes Lightroom to record into the Lightroom database the actual DNG profile data contained within the selected DNG profile, then Lightroom would have no need to go back into that DNG profile later for the profile data, and the DNG profile itself could be safely "un-installed" ("Disabled" by the X-Rite DNG Profile Manager) without adversely affecting Lightroom's ability to properly process that image using the selected DNG profile's information. DNG image files themselves are not even really involved in determining the answer at this level.
The interplay with the associated raw image's DNG image file occurs when Lightroom-maintained metadata for the image is saved out into the DNG image file itself, either automatically or manually, and, yes, I was being very specific to discuss DNG raw image files in that context. I understand from the response provided by "ssprengel" that saving the actual DNG profile data out into the associated DNG image file only happens when using "Update DNG Metadata & Preview" and does not happen through the more common routes of automatically or manually saving image metadata back to the DNG image file. Why this more robust ("complete"?) level of image metadata preservation out to the DNG image file only occurs through a more obscure mechanism is a mystery to me, but that is not the topic of this discussion.
So, my real question really still remains. Combining the ideas from both of the paragraphs above, if Lightroom only saves DNG profile data out to the associated DNG image file using this more obscure mechanism, then does that mean that Lightroom does not normally retain the DNG profile data within the Lightroom database at all -- that it really only retains the identity of the selected DNG profile, and that only when this obscure mechanism is explicitly invoked does Lightroom deem it appropriate to actually read the profile data out of the selected DNG profile and pass that profile data along to the associated DNG image file, and that even then Lightroom itself does not retain that profile data internally? If this is the case, then the DNG profile cannot be "Disabled" without adversely affecting normal Lightroom processing of the associated image [by "adversely", I mean without having Lightroom revert to the Adobe Standard profile or any other unintended side effects]. However, if Lightroom actually does retain this profile data internally upon original DNG profile selection, even if it doesn't bother to save it to the associated DNG image file except through the use of the obscure function, then it would be safe to "Disable" the DNG profile after initial profile selection and not interfere with Lightroom's normal ability to process the associated image using that profile.
Taking the obscure function awareness into account, I guess this now has the possibility of making this subject much more complex. If Lightroom does not store DNG profile data within the Lightroom database (which would require continued availability of the DNG profile for processing associated images), BUT Lightroom provides this obscure mechanism for "forcing" save of assigned DNG profile data out to the associated DNG image file, then what happens when the DNG profile is "Disabled" and Lightroom goes to process that image? Does it look into the associated DNG image file to determine if actual DNG profile data has been saved there and go ahead and use it if it exists? Or does Lightroom ignore DNG profile data saved to a DNG image file in all contexts, and unconditionally always require the assigned DNG profile to remain available in order to carry out normal Lightroom development or rendering processing of the associated image?
This is admittedly a lot of words to discuss a simple desire: I want to shoot with shoot-specific DNG profiles, assign them to the shoot's images and develop them, and then archive off ("Disable") the DNG profiles from that shoot so that my Camera Calibration "Profile" listbox does not become unmanageable. Period. If I absolutely must go back and re-Enable a specific DNG profile later to make a print of one of those images a year from now, then I guess that's what I have to do, but that seems a real shame when all other image-assigned "edits" store those "edits" as image-specific metadata, and profile assignment is just another "edit" (although saving the profile data, rather than just the profile identity, may not be included in this "edit"). Whatever works out to be the simplest, most straightforward course to accomplish my objective is what I need to do. Ideally, that would be painless if Lightroom records into the Lightroom database the actual DNG profile data when the profile is assigned to an image using the Camera Calibration panel's Profile selector.

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

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 Profil editor is always crashing on exit

as the topic says. im using latest beta version.
i7 2600k @4.2 Ghz
240 GB Vertex 3 for catalog and preview
16 GB ram
win7 64 bit
460 GTX 1GB
ps: i hope the question fits in this forum...
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: DNG Profile Editor.exe
Anwendungsversion: 1.0.0.45
Anwendungszeitstempel: 4cb71daa
Fehlermodulname: DNG Profile Editor.exe
Fehlermodulversion: 1.0.0.45
Fehlermodulzeitstempel: 4cb71daa
Ausnahmecode: c0000005
Ausnahmeoffset: 00019b4b
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789

Take your computer to an Apple store or service technician. You may have a hardware problem. This is not normal behavior.

DNG profile editor : where can we find a link for downloading an updated version (for Mac OS 10.9)

The links I found here (http://www.adobe.com/downloads/updates.html) are both for Windows, althought one is named "MacIntosh".
The beta version seems to have problems on Mac OS 10.9 (it is impossible to quit the application).

Adobe - DNG Profile Editor : For Macintosh : DNG Profile Editor 1.0.4

Jpg and DNG brightness problem - CS2!

I am using CS2 with camera raw plug-in 3.7
I am running Windows XP SP3.
I open a DNG file. I do NOT do any processing whatsoever!
I just immediately save it as a JPG file at maximum quality.
However, when I view the two files with the Irfanview picture browser, the JPG seems to be washed out compared to the DNG!
Can anyone explain this?

[email protected] wrote:
> It does not pertain to camera raw, rather with Photoshop or color Management.
The underlying problem that many people have trouble coming to grips with is
variants of:
'Why does my RAW image look different from the
1) JPEG
2) in camera Preview
3) manufacturer's version
4) etc...?'.
The question is simple but the answer is not. The answer touches on color space,
white balance, default Camera RAW settings and processing, camera profiles,
etc... Many of the threads here go into really good depth in examining each of
these topics but I don't recall seeing anything that approaches a comprehensive
answer, especially since we now have the DNG Profile Editor.
-X

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.

DNG profile with Fuji X100s raw files...

Hi,
I'm trying to make a dng profile for my Fuji X100s (I did the same recently for my Canon 5dII).
Because I shoot architecture and interiors, I profiled for daylight, tungsten, and flourescent light (I also did this for the Canon with success, much improved color, sepecially in fllourescent light).
With the Fuji x100s, the daylight profile was good, the tungsten seemed very desaturated, and the profiler kept giving me an error message for the flourescent light saying there was an extreme color cast on the grey patch and it couldn't create a profile (I tried 2850, 6500, and "both tables"). The grey patch on the flourescent card was reading (aprox) 3200K and +50 Magenta, so not off the charts, so to speak....
Why is this? Is it to do with the type of sensor in the camera (Xtrans CMOS)?
Thanks,
Alan.

JPGs are relatively small, and raw files relatively big, so if there is an issue writing data to the card where it corrupts after a certain amount is written, then the raw file could be the only file with enough data written to it thing that is corrupt. If every single raw file is corrupted the same way and none of the JPGs seem to be then it may be something else related to raw files on the computer, like the computer memory, or the drive that the camera-raw cache is on, or even a virus-scanner locking a file at the wrong time when it is written or read. The other thing to watch is that the raw files have an embedded JPG preview in them that may be ok, as well, and only when LR interprets the raw data will the corruption be visible. The embedded JPG preview is what you see in the Import panel grid and is also what you see momentarily just after you’ve imported, before LR has a chance to recompute a preview from the raw data.
To see both raw and jpgs in LR then you need enable the LR preference to treat raw and jpg files separately, for future imports so what you’ve already imported will stay the same, until you do a Synchronize on the folder Once you enable that preference then you can synchronize the folder to have LR reimport just the new (newly visible) JPGs.
The most important initial test to do is transfer the same set of files from the card to the computer more than once—you’ll have to disable the duplicate checking temporarily—and check if they have precisely the same corruption in each copy of the image or if it looks different. If it is the same then the data is likely bad on the card. If it is different, then the photos may be ok on the card and something in the transfer process or the computer, itself, may be bad, and there is hope you can mitigate the problem and get the uncorrupted raw data, somehow.

Documentation for DNG Profile Editor??

Hi. I am looking for the tutorial and documentation on Adobe DNG Profile Editor (v 1.0.0.39 beta 2). I assume this is the latest release, but if not, I would appreciate a link to the latest. I tried downloading documentation and tutorial from the following link, but the site never comes up.
http://labs.adobe.com/wiki/index.php/DNG_Profiles
I'd like to build some profiles for my 5DmkII and studio lighting situations, specifically for portrait / skin tone type work. Suggestions welcome.
Thanks,
Lou Dina

In the past I did some research in these fields and I want to share the fruit of that work (but English language is a problem).
> There can be Variations Among cameras.
I have analyzed two sets of cameras, two Canon 40D and two 400D illuminated by Solux Daylight 4700K bulbs.
The first test was done with a 400mm. Unfortunately, very little movement of the lens at f/5.6 (a mistake) has darkened the upper rows of ColorChecker and I had to correct them with the brush of ACR Exposure (the worst intervention reaches 0.17). After this intervention the cameras differ by an average error of delta E 2000 0.30 and a maximum of 0.75.
Link: http://www.boscarol.com/forum/viewtopic.php?f=58&t=321
The second test was done with a Canon 400D and a Canon Rebel XTi. In theory, the same model but for different markets.
Here the things were particularly interesting because:
- the cameras could be build from different processes due to different market areas
- the cameras were put on the market in 2006, and were produced with the technology of almost five years ago
- the cameras belonged to the entry level market segment, the techniques of production could be consistent with this low target
All these factors could lead really to differences in behavior. The results were an average error of 0.65 and a maximum of 1.26.
Link: http://www.gialandra.it/blog/files/343e438a6021337b5fdffb2cfbe0f08b-0.html
And probably if these tests had been made in laboratory the differences were even smaller.
I concluded that the differences in the behavior are all to prove.
On the Internet I found nothing of scientific.
> There are subtle Also Variations Among Conditions lighting, as well as chart shooting conditions (Exactly how the light is falling on the chart, the angle at Which you photograph the chart, etc.)..
These are the most important points. If the chart shooting conditions are a bit easier to control with geometry, get a light with a spectral power distribution right it is very difficult (and I suspect that even Adobe has not a decent D65 simulator). To obtain a light close to illuminant D50 I use 4700K Daylight Solux bulbs without glass diffuser. In front to the lamps I mounted a shape ring protection with a hole less than two centimeter (to avoid protection I have tried the black back version of the Solux bulbs but they do not have the correct spectral power distribution). Bulbs are powered by an adjustable power supply. Using the spectrometer as a feedback I can reach a CRI of 97.
It seems to me that even the not winter sunlight when the atmosphere is really clear is close to the D50, but I've never had a chance to measure it. In this condition the problems of non-uniform illumination do not exist, but be careful with the camera and target angles because the light is even more violent, the target should be perfectly at 45 degrees and the sensor should be parallel to the target.
Finally to have a more homogeneous illumination and all other problems I use only the mini format of the ColorChecker.
> There Are Also Among Variations lenses (eg, spectral transmission of Canon 50 f/1.4 is Not the same as Canon 180 f/3.5 macro, But They Are close).
I have studied the effect of five very different lenses in type, brand, cost, etc.. The spectral transmittance of the lens was so different to cause a shift of the white balance of 450K. On films this would lead to very different results, on digital system instead the human visual system is not able to appreciate differencies (worst deltaE 2000 is 1)
Link: http://www.photoactivity.com/Pagine/Articoli/052ResaCromaticaObiettivi/Resa_cromatica_degl i_obiettivi_ENG.asp
For my studies and my experience at this moment I think the best way to find the faithfull to the scene with a safe semi-universal profile is using the calibration sliders in D50 condition. From the linked experience below this gives faithfull from tungsten light (2600K) to above 10000K, of course this last only in daylight.
Link: http://www.photoactivity.com/Pagine/Articoli/023%20Calibratori%20al%20sole/Calibratori%20a l%20sole_en.asp
In this context I still use the script of Tindemans but it is time (many years now) that Adobe produces his matrices tweaker (XRite Passport stresses the matrices as far as possible before creating some sort of table)
I hope that I'm not boring
Ciao
Marco

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.

DNG Profile problems..

Similar Messages

Maybe you are looking for