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.

Similar Messages

IMac/Snow Leopard choosing wrong color profile?

Hey guys,
I am a wedding photographer and I calibrated my iMac twice a month with a Spyder 3 calibrator. I have noticed a few times, that even though I have chosen the color profile I have created with the Spyder 3, sometimes my iMac does NOT have that color profile selected. It seems like it reverts back to the standard iMac color profile at times - with no explanation. Is this a bug, or am I the user doing something to cause this to happen: log out, shutdowns, etc.
I am really unsure, so if anyone has a solution or explanation for this that would be great! Once I retouched a whole session using the wrong color profile (I didn't know it had changed) and it was a disaster.

The file that holds which monitor profile is being used may be corrupt. You can remove this file from the Preferences folder of your user account:
com.apple.systempreferences.plist
Place it in the trash, or just to the desktop and restart. Or log out and log back in. The OS will create a new preference file.
This file holds various settings, so you may notice other items in the System Preferences back at their defaults.
As to your calibration habits, every other week is overkill for LCD monitors. This was the case with CRTs where every other week, or at minimum once a month was normal. CRTs drift from their settings much faster than LCDs. Every other month with an LCD is more than sufficient.

How do I get an SVG file to the same color profile as my illustrator file (U.S. Web Coated (SWOP) v2 and what would be the correct color profile for printing on a shirt?

How do I get an SVG file to the same color profile as my illustrator file (U.S. Web Coated (SWOP) v2 and what would be the correct color profile for printing on a shirt?
Thank you.

dadanas wrote:
Hi Simcah, I have a similar problem. Have you found out any solution?
thanks, dan
You need to ask the printing service provider. Dealing with color totally depends on the printing process involved and of course the machines used.

Can't open DNG files created with Mac CS5 downloader in Mac CS4 Photoshop

I recently installed CS5 on my mac but I kept CS4 installed as well. I notice that I cannot open DNG files created with CS5 in Photoshop CS4. Bridge CS4 shows the files only as icons - no image thumbnails. I am able to open these same files on a Windows version of CS4. Is there some plugin for my mac CS4 that will enable me to access the DNG files created with CS5? Is there a way to use my CS5 downloader when converting my raw files from my camera to DNG files that will make them compatiple with PS and Bridge CS4?

rr3rd wrote:
Is there a way to use my CS5 downloader when converting my raw files from my camera to DNG files that will make them compatiple with PS and Bridge CS4?
Well, yes...but you'll need to modify your DNG Converter prefs to allow for that. You''ll need a recent (ideally current DNG Converter 6.4.1 or above) and click on the DNG Converter preferences and select the correct DNG Converter options. Check DNG Converter 6.4.1 (the current version) and click on "Change Preferences" to be sure select Camera Raw 5.4 and later then make sure CS4 is updated to ACR 5.7 (which is the last version of ACR for CS4) However, the changes made to ACR 6.x really should be adopted since IQ for ACR 6.4.x is a lot better...

DNG files created with LR4 do not show thumbnails

Hi,
When using LR3 to create DNG files from my RAW files, those files would show me thumbnails of my image in Windows Explorer. I am running Windows/7 (64) and have installed a CODEC from "Fast Picture Viewer" that allows thumbnails from RAW & DNG files to be shown. It seems, however, that the thumbnails do not show for DNG's created with LR4.
To Remedy this I uninstalled the CODEC. Downloaded the most recent version and installed it but this did not fix the problem.
I then went to the user forum for the CODEC product and searched for my problem. I found a thread who's solution is to turn off "Embed Fast Load Data" when exporting to DNG and it fixes the problem. I tried this and indeed it did fix it. The responder went on to say ".....When this option is enabled the files created are no longer DNGs (just an undocumented private format of Adobe that no one else can read to this date)". This statement surprised me as it is counter to what I understand Adobe created DNG to be. Can I get some input on this comment as if true it is very troubling.
My second question is that I see where to turn off the "Embed Fast Load Data" in the LR Export module, but where do I do the same thing in the Import module when I'm selecting import mode "Copy to DNG"?
And, my thrid question is this. If indeed the DNG files created by LR4 are proper DNG files and this CODEC is just flawed in some way, does anyone have a better way to allow image thumbnails to be shown in Windows Explorer?
Thanks -- Dan

Hi David,
You testing does not coincide with mine. I have consistently kept "Use
lossy compression" turned off. With lossy turned off, it seems that using
Fast Data Load prevents the thumbnails from displaying whereas turning off
"Fast Data Load" allows the thumbnail to be shown.
Below is comment from Adobe confirming that they have yet to release the
spec containing "Fast Data Load".
From: Ian Lyons [email protected]
Sent: Tuesday, June 05, 2012 12:29 AM
To: Califdan
Subject: DNG files created with LR4 do not show
thumbnails
Re: DNG files created with LR4 do not show thumbnails
created by Ian Lyons in Photoshop Lightroom - View the full discussion

PSE 11 - How save image with printer color profile?

I use an outside service to make prints. How can I save an image in PSE 11 in either TIFF or JPEG format with the color profile for the outside lab's printer? Thanks.

You can print a photo using the correct printer profile for the lab printer. In the print dialog box , go to "Page Option>Color Management" and then choose Color Handling as "Photoshop Managers color". Now click the printer profile dropdown and choose the profile for your lab printer. If you are not able to find the profile for you printer then choose "Printer Manages Color"
To your second question the answer is that you cannot save the image with the correct colors for printing. You can only convert the profile of your image to Adobe RGB which matches gamut of most printer profiles using "Image Menu>Convert Color Profile and choose Adobe RGB.

Wrong color profile after export - what am I doing wrong?

I'm a beginner in color management and color profiles and I have a problem with my exported files from AE CS6 (german version):
In my project settings I've set the working space to "adobe RGB (1998)" which is the same like my footage (JPEG Image-Sequence).
In my Output Module Settings I've set it also to the working space "adobe RGB (1998)".
I' ve tried to export it as h.246 and AVI.
And now the Problem: the exported clips are too bright and washed out. First I thought it is a problem with the Windows Media Player, but I imported the clips again to after effects and the showed Profile is now "HDTV (Rec. 709) Y'CbCr". This is the case with the h.246-clips. The AVI-Clips showed the profile "sRGB IEC61..." So the settings from the Output Module didn't seem to work.
The washed-out-effect disappeared after I set everything to HDTV, but I don't think this is the right way to go..
Thank you for any help

Simple, really: You are using a) a wrong color space b) your system is not calibrated, but you have color management enabled and c) use formats that don't support color management. This is simply wrong from stem to stern, especially with regards to b) and c). Why would you even use Adobe RGB when video works on Rec 709 or even more generic sRGB? I think you do not even understand the point of CM on a fundamental level. you don't dictate the color space by your source files, you simply import them into your working color space - regardless of whatever it is set to. The color metrics engine will apply any corrections necessary based on the associated/ embedded profiles, which ultimately is the whole point. Conversely, enabling CM for output will require a format that actually uses those corrections, which comes down to only a handful. so to cut a long story short: Unless you are willing and technically able to establish a proper CM workflow simply leave it off and just use the default sRGB that AE ever has used.
Mylenium

Lightroom 5.6 crashes when images with some color profiles are in import

I am a recent subscriber to Adobe CC. I run LR 5.6 64bit on my Win 7 PC. Whenever I seek to import images previously processed in iPhoto or LR elements into my catalog, ACC Lightrom crashes. I suspect it is because the original editing program used a different color profile. Adobe techs will not give me an answer when I ask for an overall cure. Are their any technical documents on the web that would enable me to deal with this issue? If so, I cannot find them, and I do not want to call Adobe again and again to get LR 5.6 restored.
David J. Krupp

my-wedding-foto.de wrote:
Lightroom 5.6 Win8 64 import of some photos are not possible: the photos are grey, the file name of the photos are already excisting in the catalog, older different photos, don’t Import Suspected Duplicates is not selected. There is no difference selected or not, the photos (Import are not possible) are always grey with the notice: These photos would be already imported! All other photos could be imported and gets grey.
When Lightroom greys out a photo in the Import dialog box, it means the photo is already in the catalog. It doesn't mean that it is matched with an older photo with the same name ... in order for there to be a match, the file name and capture date and file size must be identical.
So Lightroom thinks you have already imported the photos, and you think the photos have not been imported. Now I'm sure you are a very nice person, but I believe Lightroom. What you need to do is to find the photos in your Library Module and use them there. The photos can be found by searching for them by file name, after turning off all filters, and after clicking on All PHotographs in the Library Module.

Ordering Prints Online with Embedded Color Profiles

Problem: I have imported about 100 photos into iPhoto (7.1.1) that have embedded ProPhoto RGB profiles. When Ordering Prints (from Apple/Kodak) online, the prints delivered were horribly desaturated. After research, discovered that the ProPhoto RGB (which is really high-end professional color space, even bigger than Adobe RGB) is not compatible with sRGB printing services. Essentially, sRGB is a much smaller color space and color is lost in process. What's the best way to resolve this?

Ruzicka:
There's an AppleScript to embed the color profile of your choice in selected files. I've modified it to embed the sRGB profile it's available at Toad's Cellar. It's the Applescript version, not the automator version. The automator version adds some jpeg compression in it's process. The script method does not.
Or, you could use Photoshop and create an action to batch convert the files to the sRGB profile. I've used PS but not the batch process. GraphicConverter may be be able to convert them but I've not used it.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

DNG files created with LR4 no longer display thumbnails w/ FastPictureViewer & Win7

I've been using the FastPictureViewer Codec pack so that DNG and camera RAW files show as thumbnails in Explorer for quite some time. Upon upgrading to LR4, DNG files no longer display as thumbnails, but as the generic Windows icon for an image.
Upon researching the issue, and upgrading the Codecs from the supplier (which still did not fix the issue), the supplier tells me the following:
What we solved [in the update] was a crash with the new files. Adobe did not document their
changes, so there is not much we can do except ignore the files. This is
what happens when owners of proprietary formats decide to change stuff
without notice
If you turn off the "fast load" and "lossy" options the DNG will still be
created following the published 1.3 specification and will work with 3rd
party software including ours.
The "new DNGs" are for Adobe private use only at the moment. We don't know
(beyond vague promises on employees personal blogs) if they will ever
document what they did and publish an updated specification, they are
certainly under no obligation to do so. The decision they took not to
release updated DNG specs even before LR4 came out was a deliberate one.
While I resolved the problem by turning "fast load" off, I find it highly disturbing that Adobe has made undocumented changes to the DNG format that break 3rd party software. I thought the whole idea of DNG was that it was an OPEN FORMAT and was to prevent situations such as this. At least this is how they sold it to the public and their argument against "proprietary camera manufactuer RAW formats" that could "change at any time".

JS4653 wrote:
The "new DNGs" are for Adobe private use only at the moment. We don't know
(beyond vague promises on employees personal blogs) if they will ever
document what they did and publish an updated specification, they are
certainly under no obligation to do so. The decision they took not to
release updated DNG specs even before LR4 came out was a deliberate one.
Actually JS, RAW files converted to DNG with fast load checked from LR4.0 are read, thumbnails and full images are displayed in preview and with Finder in OSX Lion 10.7.3, along with keywords, EXIF data etc. I don't know whether the preview is the RAW or the fast loaded jpeg
Not that it helps you
Adobe mentioned that they will be making the 1.3 data specs available in the next couple of months, I canna remember the link offhand, and it was a formal post, not an employee blog
Life changes, things upgrade, that is the way of things, but it is very frustrating.

Photoshop CS3 doesn't open dng-files converted with the adobe dng converter 7.4

Hey Guys,
i got a new camera - sony alpha a57 - which produces arw-files. for being able to work with these pictures on my photoshop cs3 I converted the arw-files to dng-files. now adobe bridge shows only the converted dng-signs, but I can't open them to work on them.
does anyone have an idea what I could do to use these files?
thanx,
rita

Hi,
Sometimes when using the dng converter one needs to set the compatibility settings to the version of camera raw you want to open the files with.

Dng files modified with lightroom 4 that are exported do not open in cs4 with the modifications

When I modify and export dng files in lightroom these modifications do not show up in cs4 when I open the exported file. They do if I export the file in jpg format.

Jim, I appreciate the feedback. I believe the issue is as you stated- I need an update to the camera raw in cs4 in order to view the changes. Unfortunately, I do not think is possible since adobe has decided not to support cs4 anymore. My choices as far as I can tell are 1) read the lightroom file out as jpg which has the changes, 2) update to cs6 which probably has the correct camera raw version, or 3) do this cloud thing with adobe which is what they want you to do. I like to print my photos in large format, 17X22 etc, and since my set up prints out nicely from cs4, and pretty much looks terrible from lightroom, I probably will just read out the jpg files and print them in cs4. The reason I use lightroom is that it seems to correct highlights and such much more effectively than cs4. Any thoughts would be welcomed. mike

Prints coming out with wrong colors

I am currently running win 7 64 with lightroom 4.3and an Epson Stylus Pro 3880 networked. I also have a HP 2610 as local. When printing to the Epson I get print with a lot of red to the point it looks pink or purple. This is with the color management driver set to custom and color management turned off or vice versa with color controlled by printer. If I print to the HP colors look great. I really need help with this problem. I have tried different paper outputs with no luck. I also have the same problem in CS5. So I would think its something I am missing.
Ron

It seems that is a problem that a few people had with the Epson 3880.
Red or magenta prints indicate double color management, i.e. in Lr and in the printer driver.
Check your settings carefully. If you let the printer manage colors you have to select "Managed by Printer" in Lr/ Print Module / Print Job / Color Management / Profile.
If I recall correctly one poster found that an old print preset that was created for a different printer was creating the problem.
There are lots of threads on this forum regarding problems with the Epson 3880. Do a search by entering "Epson 3880" in the search field where it says "Ask a question".

Are .dng files compatible with iPhoto?

I recently purchased a Panasonic Lumix dmg G2 camera. I have iPhoto '09 on my iMac, running OS 10.6.8. I was unable to load the RAW images from this camera to iPhoto, so I converted them to .dng files. I even downloaded the latest version of the dng Converter, but I am still unable to download them to iPhoto. I get the following error message:
"Unreadable Files: 1
The following file could not be imported. (The file is in an unrecognized format.)"
I am pretty sure I was able to download .dng files in the past. Has something changed, or are .dng files just not compatible with iPhoto?
JB

Not all dng-files are alike. I have used dng with iPhoto before, without problems. I could not find any documentation for dng in iPhoto, but for Aperture it is documented that dng works for "DNG files generated by the Adobe DNG Converter with the 'Convert to Linear Image' option turned off". Probably the same will hold for iPhoto.
In Snowleopard the following cameras are supported:
Mac OS X v10.6: Supported digital camera RAW formats

PDF files with wrong colors

Hi All,
I apologize if this has already been discussed, but I probably cannot guess the right search string to find the relevant thread.
I've recently upgraded from FM6 Mac to FM9 Win. My old FM6 documents have two kinds of problems in FM9:
1) replaced fonts horizontally scaled to 80%
2) colors looking good on the display, but bad when converted to PDF
As for issue #1, I couldn't do other than editing all the paragraph styles. But eventually I could solve it in a way or the other.
But issue #2, I cannot seem to come to an end with it. The original color was a Pantone swatch, that I can also find in the Win version of FM. In fact, when opening the FM file, it looks at it used to do on the Mac.
However, either I save as PDF from the File > Save to PDF menu command, or print a file using the PDF driver (with the Press Quality selected), the resulting color is wrong. What used to be a Grey-Blue Pantone 191-7, is now some sort of Cyan. Tones change slightly whether I convert using the Print > Do not save file trick, or use Acrobat Distiller 8 on the Mac with different settings; but the original color is never reproduced.
Oddly, an EPS file in the same FM file looks perfectly good - the original color is there. What a contrast with the oddly-colored text and lines in the remaining parts of the document!
Maybe someone has already gone through this issue, and has a solution for me. I'm literally loosing my sleep to try to solve this issue.
Thank you in advance!
Paolo

Paolo Tramannoni wrote:
Obviously, before spending a considerable price for additional software, I would like to see if I can solve the problem with what I have.
Paolo,
I've done some in-depth color testing with FM9, and the results can be downloaded here: http://www.meissner-dokuteam.de/Files/Frame/colortest_fm9_p250_FM_elements_EN.pdf
In short words, for the "Save as PDF" CMYK version:
- Spot colors from imported definitions are converted to CMYK
- Spot colors from FM Pantone library are correctly output as Pantone colors *
- Spot colors in imported EPS files are always correctly output
* I was able to nail down the spot color bug: The critical element is the "Name of color" entry in the color definition dialog (below the dropdown/entry field "Name"). If there is a name, then the color will be correctly output as a pantone color. You can see this, if you define a color taken from the FM library, they all contain a "Name of color" entry. Self-defined colors or colors which came in by graphics import don't contain a name there, and are output as CMYK colors.
You can fix this behaviour, if you save your FM files as MIF, and add the required lines at the color definitions yourself. I for example used self defined spot colors, and added the lines
<ColorLibraryFamilyName `WambaSamba self-defined'>
<ColorLibraryInkName `WambaSamba Blue'>
Now even self-defined spot colors work. You can see this in this pdf: http://www.meissner-dokuteam.de/Files/Frame/colortest_fm9_p250_FM_elements_EN_MIFedit2.pdf
and download the editet MIF file (for analyzing) here: http://www.meissner-dokuteam.de/Files/Frame/colortest_fm9_p250_FM_elements_EN_MIFedit.mif. zip
One more bug, but this time in Acrobat: Spot color tints are always displayed at 100%, when you open the PDF, unless you enable Output/Overprint preview.
Regards,
Bernd

DNG files rendered with wrong color profile?

Similar Messages

Maybe you are looking for