DNG editor color profile

I have created color profiles in the DNG Profile Editor, saved the recipe and exported the recipe to
C:\Documents and Settings\Dan\ApplicationData\Adobe\CameraRaw\CameraProfiles
When I go to the calibration tab in Lightroom, these profiles do not show.
Using Windows XP.
Thanks for any suggestions as to what I am doing incorrectly.
Dan

Dan,
It should work, it does for me.
Are the cameras supported by LR? You say there is a separate profile for each and I guess you mean these are existing in LR. If I am correct then it should work and I am out of ideas.
Just thought of one other thing. You could try putting your new profile into the existing file folder for your camera type. You should find the folder here:
C:\Documents and Settings\All Users\Application Data\Adobe\CameraRaw\CameraProfiles\Camera
Dave.

Similar Messages

Aperture 2.1.4 to PS CS4 External Editor Color Profile issues????

Anyone else experience this?
I shoot Nikon D700 and D90 with sRGB color space. When I send a file to CS4 via external editor, PS prompts that my embedded color space is Adobe 1998. ***??????
I immediately went and checked all my settings on my camera and they're fine. Is this Aperture's doing? PS? maybe even SL?
Dazed and Confused
Message was edited by: rtd2870

Aperture uses the Adobe 1998 color space as it has a wider color gamut than sRGB. Like most things in Aperture, you choose your color space on export.
sRGB is used primarily for the web, and some printers that accept RGB files ask for sRGB because their printers can't match the Adobe 1998 Gamut.
If your camera is capable of shooting Adobe 1998, you should, but it doesn't really matter when shooting RAW.
DLS

Create DNG Profile - Why does it look different in the DNG Editor vs LR/ACR?

Hi everyone, I am sorry if this has been covered before -- perhaps you could give me a link to the relevant info.
I have a client who shoots with a Leica DMR. The reds are way to saturated and magenta. We created a new camera profile in the DNG editor using a color-checker chart, shot at D6500 and Tungsten. Looks great, and Lightroom recognizes it. The issue: when we look at a photograph in the DNG editor with this profile, it looks much better. When we look at the same photograph in LR/ACR with the profile selected, the reds are still too saturated and magenta (though way better than without our profile). Why would a photo look different in the two applications, with the same profile?
As shown in DNG Editor:
As shown in LR:
Thank you for any light you can shed on this.
Laura Shoe

Here is an additional comparison further highlighting the magenta issue (amongst others). Shot with Leica R9 w/DMR(firmware1.3) using Leica Vario-Elmarit-R 35-70mm at ISO 100, f/4.8, 1/60. Manual WB=4912K, no Exp Comp.
Here is screen shot of same DNG image. Un-altered in either app., no presets, no sharpening, or noise reduction. CaptureOne (v4.8.3) on the left, and LR2 (v2.6)
Here is what the above screen shot looks like thru CS3:
you must click on image to see CS3 rendering - browser is not accurate
Anyone no what's going on?
PS the images were shot just shy of perfect focus to test sharpening in both apps, same levels applied to both images (C1 on left, LR on right). Here are the results:

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.

Problem with DNG Color Profiles in Lightroom 5.4

Hello folks,
I recently updated from LR 5.3 to Lightroom 5.4 and since then I am having problem when using dng color profiles which were created with Colorchecker Passport. Every time I use such a profile which was created for my Nikon D 800 I get very greenish tones in the pictures.
I use Windows 7 Pro on a HP Z 210 Workstation. The monitor is a hardware-calibrated Quato which was recently calibrated.
Does anyone have this problem too and - if yes - know how to fix it?
Thanks!
Yours, Albert
PS: As English isn't my mother tongue I apologize for any mistakes in the text above.

Hello Andrew,
I do have a Nikon D 800 and a Fuji X-E1. I haven's noticed a problem with the Fuji so far. I think I will recalibrate my monitor tomorrow and see if the problem still exists.
I can supply raws and DNG profiles but I don't know where I should upload them - I suggest I could do it on my own webspace. Would that be ok?

Converting RGB to DNG without affecting color profiles

Hi guys
I'm working with the DNG SDK in C++ for some time now. I need to be able to take a raw RGB (not camera raw) and convert it into a dng file. After playing arond with it for a few days, I realized creating the camera profile drastically affects the resulting dng image.
I can't seem to produce a dng file that was identical to the input source. My picture appears very washed out and I end up using the adobe color profiler to try to bring the image back close to it's original color.
I'm trying to find a way to produce dng files without the need to affect the colors in any way, the resulting picture should be bit identical to that of the raw RGB input file.
I'm not even sure if I can do this considering the usage of the dng format.
UPDATE
I've realized that my program is loading the RGB buffer into the fData of the stage3 image object. I have a feeling I need stages1 and 2 but i'm unsure if I need to and if so, then i will probaby need a source DNG to produce those stage1 and stage2 unless I can get stage1 or 2 from stage 3 (appears it works vice versa).
I'm able to do the reverse (DNG to RGB raw) by extracting the buffer from the stage3 render. but in this case, all the metadata has been filled in by the input DNG. However, going from RGB to DNG, I don't have the metadata to fill into stage 1 and 2.

My understanding of the JPG is only middling. I thought I understood that it uses anchor pixels and either a translation table of some sort or difference mapping, using 8 bits per piece of information.
If that were the case, surely changing the translation from CMYK to RGB would be fairly simple.
In this case, the usage is Ebay and they only accept JPG, PNG (and maybe BMP and GIF, I didn't look that closely), but require RGB. I was actually quite surprised to find that JPG allows CMYK since, as you say, anyone dealing with CMYK is going to be dealing with commercial printing and few people who deal with commercial printing would play around with JPG.
I always stick to TIFF or PSD for workflow, but JPG is popular for a reason - when it comes to web, JPG is the only format that can deliver manageable file sizes with full-screen or "large" images for web. Our top level banner photo is 2590x692 and needs to be under 400kb for sane download speeds. PNG couldn't touch that. Even with the aforementioned 1800x1200, PNG is nearly 2mb, while I can maintain very decent quality with a 500kb file with JPG that works well for 'zoom in' type usage.
So there's no way around JPG. It's just annoying that the first person to touch a random selection of the pics was primarily an Illustrator user and saved *some* of the pics in CMYK mode.
It's like that old story about the farmer who didn't want anyone to steal his watermelons, so he cleverly posted a sign "None of these watermelons are poisoned", only to find a note the next day saying "Now, One of these watermelons is...".
Far more work to fix 'some' of the images compared to just doing it right the first time.
But then again, for workers like that, if you can't trust them with an easy job, you could hardly trust them with more complicated jobs...

DNG converter converts RAW Adobe RGB color profile to ProPhoto ??

I have a Canon 5D2. there is an internal switch to shoot RAW files using the Adobe RGB profile. when I open a RAW image in CS4, there is no problem. yet when I open the DNG converted image in CS4, CS4 tells me the image has the ProPhoto color profile. I can convert back to Adobe RGB, but it adds an extra step and (I think probably) loses information. I looked for a switch in the DNG converter to speciy the color profile of the converted image, but could not find it. Any suggestions ?

Hi, Tom.
The real issue here is getting accurate color. You can't get accurate color by setting your monitor profile to sRGB. sRGB is a virtual color space that doesn't describe the exact color gamut of any physical device. But, in order to display sRGB or any color space accurately, you need to get a characterization of your monitor.
Here is an AWESOME way to get access to a colorimeter: http://www.lensrentals.com/rent/pantone-huey-colorimeter Looks like for $32 you can rent this for a week. Go in on this with a friend and profile both of your monitors and hardly pay a thing. If you have a reasonably good quality LCD monitor, this custom profile you make will be fairly accurate for many months. At the very least, this is way more accurate than having no regular calibration at all.
Hope this helps!
Bret

DNG files rendered with wrong color profile?

Does someone else also have a problem with DNG (digital negative) files showing incorrect colors when opened in Apple software (Preview, iPhoto, Aperture..)?
I have a Nikon D750 and currently consider using DNG as archive format for my RAW files.
But the converted DNG files are shown with a wrong color profile when opened via Apple's own camera raw framework...
It works in Adobe software - such as Lightroom - but any software using the OS X internal camera raw framework seems to use the wrong color profile when opening the DNG. Note that the original D750 NEF files are opened and rendered correctly.
I am using OS X Yosemite 10.10.2 with the latest Camera Raw Compatibility Update 6.02 installed.
On the Adobe side, it is Lightroom 5.7 and DNG Converter 8.7.1.
I tried all kinds of different conversion settings. It does not seem to make a difference whether I embed preview images in the DNG or not, whether I shoot in 12 or 14bit RAW, and whether I include the original RAW file into the DNG or not. I also tried to explicitly select the 'Camera Standard' color profile in Lightroom first and then export the DNG, but still on the OS X side the resulting image looks wrong as compared to the original NEF.
Any other Nikon user here who could verify my problems?

A few simple tests on your end may help you better understand:
1. Capture the same image (same camera settings in RAW and JPEG)
2. Open these images in Canon DPP - they will be a close match, this is because Canon DPP and the Canon camera itself use similar RAW processing algorithms
3. Open convert the CR2 to DNG, and open the CR2, DNG, and JPEG in Adobe Camera RAW - the CR2 and DNG should be a very close (if not identical) match if you use the same processing settings for each, since they are both being processed by ACR's algorithms; the JPEG will probably not match as it was processed with Canon's algorithms
What you are seeing is at the HEART of raw processing, and has nothing to do with color spaces or with DNG being at fault. The very nature of RAW processing means every processor (DPP, ACR, CaptureOne, etc) will produce different results by default - that's not to say that with some adjustments you can't match one processor's results to another, but it won't be the case by default.
The choice of RAW processor has FAR more an impact on your results than color space - in fact color space should have virtually no visual impact, though depending on the scene photographed you might have better gradations in some color spaces, better handling of highly saturated colors in some, but the overall look should remain close regardless of color space choice.
Further, as has been pointed out by others, raw files (which includes CR2 and DNG) do not have a color space - raw files are by definition raw image data which has yet to be processed into a color space. When you see color space assignments in RAW processors, that is relevant to the files you create FROM the raw files, not relevant to the raws themselves.
Before bringing inflammatory language and false assumptions to a forum with a high level of expert membership you might want to research the issue, and devise some simple tests (like above) to help you understand the issue first.

Download Canon 7D DNG color profiles

Hello everyone!
I just got a new Canon 7D and I got to say, when I open my photos (I shoot in raw) in Lightroom they don't exactly look like what I see on the back of the camera...so I'm looking for color profiles that would match the 7D's colors but I'm not sure where to look for them.
So my question is, where can I fin Canon color profiles to download?
Thanks for your time!

There is a profile creator provided by Adobe to create specific profiles for your camera in LR/ACR other than that I do non believe there is any option to just stick profiles into LR/ACR.
http://labs.adobe.com/wiki/index.php/DNG_Profiles

Sigma DP2 - no dng color profiles available, only embedded

Converting X3F raw files from the Sigma DP2 a color profile created with the X-Rite Colorchecker Passport doesn't show up in the panel Camera Calibration. Instead custom profiles created for Canon cr2 raw files from a Canon 5D are showing up when working with Canon raw files.
Is this a bug of Lightroom?

Wow, I'm so glad Eric Chan is in this problem... unfortunately it's not the only one :
There is the fact that processing is locked to black and white when the white balance was set to black and white in Sigma Photo Pro (even if the color data is still there).
I know SPP writes in the files, it's bad, but Nikon's Capture NX does it and it doesn't change the way NEFs are treated in lightroom (or at least not to such extent).
Better default profiles for the sigma cameras would be a major plus too.
Take a look here for more (WB problem and bad default profiles) : http://forums.adobe.com/thread/629739?tstart=0

Problem using custom color profiles in Camera Raw

Dear Adobe Community,
I've created a custom color profile using the DNG profile editor, and I've been able to open that custom .dcp file in Adobe Camera Raw (ACR) through Adobe Bridge. However, when I apply the color profile to the same image, I do not get the same results as I get with the profile editor. When I open the "corrected" RAW file in Adobe Photoshop, the colors are the same wrong colors that I have in Bridge, am I missing something here?

Yes, you're missing something.
Camera profiles are meant to account for different spectral distribution in different light sources, which is something else than different color temperatures. You still have to make all the normal adjustments, like white balancing, to get the image right.

Creating color profiles Leica D-Lux 4

When creating color profiles with Colorchecker Passport from X-Rite, DNG profiles Editor shows an error mesage USE A VALID DNG FILE. However I have used the DNG conversion option in Adobe Bridge when importing Leica RWL-files from camera. Can you help me solve th
is problem?
Photoshop Extended
Operating System: Windows XP Professional

What version of Bridge/Photoshop are you running?
Is it X-Rite's Passport software or Adobe's DNG Profile Editor software that is giving the error? I ask this because you talk about using Passoprt to create profiles, but then describe the error has coming from the DNG Profile Editro which is Adobe's software.
What process are you following, starting with the RWL file, that gives the error about not having a valid DNG file?
I know X-rite released an update to their software a few months ago.
You might post one of your RWL files via YouSendIt.com to let others try and duplicate your scenario.

ColorChecker Passport-Color Profiles

Hi there,
I am photographing paintings with Elinchrom flashes with an even light and I use the ColorChecker Passport from X-Rite to keep a reference in order to match the colors.
Till now, I've been using the software DNG profile manager, provided with the ColorChecker Passport from X-Rite, which creates a camera profile that should be helpfull to get the right color. Once I've applied the new camera profile (after restarting lightroom), I do the white balance. It's recommended on the X-Rite tutorial to use the target number 20 called "neutral 8" to do the white balance. I've also tried the target 22 called "neutral 5", and it seems to get slightly better results.
I've noticed that even creating a color profile and doing the white balance the colors don't match. I am using a mac laptop screen that I calibrate quite often, which is not very helpful for obvious reasons, but that helps to keep track of the general look of the image, so that's why I keep the color adjustment to the RGB numbers.
I've downloaded the following PDF; here there is some information about the RGB values of various ColorChekers:
http://www.google.com/url?sa=t&source=web&cd=2&ved=0CB4QFjAB&url=http%3A%2F%2Fwww.babelcol or.com%2Fdownload%2FRGB%2520Coordinates%2520of%2520the%2520Macbeth%2520ColorChecker.pdf&rc t=j&q=ColorChecker%20rgb%20values&ei=wOCdTbG7NIyDhQelj5G8BA&usg=AFQjCNGj3wUpWC_uMxgMCeR3GI yN7kDU0A&sig2=mPf1grSAULxyMs_SanYVNw&cad=rja
Using these values and a selective color layer in photoshop I get close to the real colors, although it is not good enough.
My questions are:
1-Does anybody know the ColorChecker Passport RGB (Adobe 98) values?
2-I've tried to use the DNG profile editor because it seems a precise tool for this, but it doesn't recognise the 5D Mark II files. Is it because this application hasn't been updated? It also seems to work only with 6500K or 2850K, which is not the case of the Elincrhom 600 monoblocks I am using (which I think are around 5000K.
3-Could anybody recommend a workflow that's better to match the colors?
I have more questions, but I think these three are a good start.
Thanks!

Here are color-error analysis plots for several camera calibrations using the fine-art color-checker calibration shot uploaded, earlier.
The three profiles tested were:
1) A custom Elinchrom Flash profile I created from the color-checker using the DNG Profile Editor,
2) The Adobe Standard camera profile,
3) The custom profile provided by Gustov.
My general comment would be that the Adobe Standard profile has about the same error as the custom profile I computed using the DNG Profile Editor but the Adobe profile has a more even distribution of the color error.
The profile Gustov provided seems to be very close in the yellow area, but quite far off in the reds, blues, and violets. This can also be seen as a severe shift toward the green of the WB Tint slider value when the profile is selected for the As Shot WB as compared to the almost zero value when using the Adobe Standard profile.
These color-error plots were created using the ColorCheck module of Imatest Studio 3.7 from www.imatest.com. The program compares the measured color values from a color-checker image to the standard color numbers of the Color Checker then plots the difference on a CIE chromicity diagram, where the squares are the standard color position, the circles are the measured color position, and length of line in between is the color-error. In general, error in-and-out from the center is saturation error, while error around the center is hue error. In a 3D plot luminance error is also shown but harder to visualize without a way to rotate the plot around. Imatest provides this visualization in its Multicharts module.
I used the ProPhotoRGB colorspace when saving the TIF out of ACR because the standard ProPhotoRGB color-checker numbers in Imatest are for D50 lighting whereas the AdobeRGB standard numbers are for D65 lighting. As the image-filenames suggest, I used a linear toning curve and a black-point of 0 when saving out of ACR, but left the brightness at 50 and the contrast at 25. I tried zeroing out the brightness and contrast or using the Medium Contrast toning curve but things were way off. Using a blackpoint of 0 instead of the default of 5 also made things slightly better. There are scripts that can compute the optimal toning values for the gray patches but I was only comparing profiles, not trying to optimize them completely.

Olympus OM-D EM-5 color profiles

I guess that people at Adobe are super busy with working on compatibility with the never ending stream of new cameras.
Since the OM-D is so popular however, I would like to know why it didn't get a set of camera specific color profiles - just the Adobe Standard profile. At least a set of the basic ones (Vivid, Neutral, Muted, Portrait) would be great.
The EM-5 has a highly praised color rendition, especially for skin tones and I am sure many users would love to get these colors in Lightroom.
Is there any chance this could be added in?

richardplondon wrote:
That is interesting, and I fully understand your points. My comments were aimed at the rather common focus that some people seem to have, of exactly matching the camera JPG. The important point for me, is: can we get the picture that we want, from the Raw - and whether that is the same, or different, compared to a JPG may be completely secondary.
I am coming to this from the viewpoint of a Pentax owner - where the in-camera JPG treatment is something that divides opinion, rather than getting general approval as with your camera. People talk about the "Pentax greens", and these do seem to get intensified in a way that some people love (and that is hard to simulate using for example Adobe Standard) but that I personally dislike. Adobe Standard gives a much better starting point for me with the K-5, and also with other cameras, so I have consistently tried to make that work.
It is also worth making the point that these profiles are (naturally enough) implemented with different amounts of success and consistency on different cameras, even where they are targeting the same output and appearing under the same name. So "Adobe Standard" may be liked for one model's Raw, and disliked for another model's Raw, by the same person. These are in reality quite independent of each other. Also some Adobe-supplied profiles have been systematically "off" at first, but later improved in product updates (e.g. the Nikon D7000, as I understand it).
What I have done, and it took only a couple of minutes, is to extract embedded profiles using the DNG Profile Editor - out of DNGs taken with the Pentax camera set to Neutral, Portrait, Vibrant or whatever - and then to save these named suitably, into my profiles list in LR. So they are now available if I want them - even though Adobe may never provide these AFAIK.
I agree that to manually tweak colours "by eye" within the DNG profile editor, is going to be quite difficult and unpredictable. On the other hand, we have camera calibration sliders inside LR also. These can be used and developed more interactively, right inside LR, to our satisfaction, and then included into our Develop default - or else into one or more develop presets. Perhaps if you can isolate out what exactly is going on with the skin tones, you can make use of such adjustments on top of a profile that you already have. These will then become live parameters of each image, allowing variation as desired - rather than needing to always conform to the setup of one centrally stored profile.
regards, RP
How did you extract the profiles from the DNG files? That is exactly what I want to do. Are there any pointers on how to do this? I'm somewhat familar with DNG profile editor but I don't see how to do this.

Light room 3.3 color profiles

Where do I go and delete color profiles that I no longer need in Adobe lightroom 3.3

Chrichey1 wrote:
Where do I go and delete color profiles that I no longer need in Adobe lightroom 3.3
You go to the Photoshop Lightroom forum - this is the feature request forum. Hint: forum choice is presented when you click New -> Discussion.
And, it might be worth mentioning which profiles you want to get rid of: e.g. your DNG Profile Editor edited profiles, or some that came with Lightroom...
R

DNG editor color profile

Similar Messages

Maybe you are looking for