Color artifacts in DNG files

Hi, I've got a major issue with Adobe PS Lightroom DNG import on my Mac from my Canon EOS 5D Mark III. Any image converted to DNG file format is showing heavy color artifacts around edges, whereas the color of the object in focus is abruptly replaced by a grey border and the missing color is repeated after the edge. I know this sounds weird and I've already spoken to experts and even sent my camera to Canon for a check-up. Now I realized that this issue doesn't occur in the proprietary Canon CR2 RAW image files but in the DNG files in Lightroom only. Has anybody at Adobe a faint idea how to solve this?

Those gray halos on the edges of green and purple areas are from the Defringing lens-corrections area, so check your Defringing settings in ACR for the camera you’re using.
The Defringing function can’t tell the difference between purple and green halos caused by lens problems and purple and green edges of the subjects, themselves, so you have to be careful with it and probably shouldn’t Defringing on by default.
The Defringing slider of the Adjustment Brush can be used to reverse extra defringing that shouldn’t have occurred like you’ve pictured, or the Adjustment Brush with a positive Defringing amount can be used to reduce fringed areas visibility if you don’t want to use the automatic Defringing sliders.

Similar Messages

Assigning color space to dng files

I use pe5. I can't assign a color space to my dng files. I have to convert them to jpg or tiff before I print them.
In LR, can I assign color spaces directly to the dng file and thus can I print from the dng file?
Andy

-->The RAW file when printed from LR is in the Pro Photo space Well kind of <g> http://www.ppmag.com/reviews/200701_rodneycm.pdf When using Draft mode, they are sRGB from the thumbnails.

Artifacts in DNG files converted from NEF

On two occasions, I've encountered artifacts in my photos that I've converted from NEF (using Nikon D7000) to DNG format in Lightroom 3.6. Is there a "fix" for this?

Yes, you're correct. It sounds perfectly feasible to keep a checksum in the database for other file types. I voted for your idea.
Here's an interesting article: http://dpbestflow.org/data-validation/dng-validation
Currently, the only way to check a large number of DNGs is to run the free DNG converter on them, which can take a long time and requires disk space for the second copies. The Adobe SDK has a function for checking the checksums, so it sounds like a relatively easy task to write a small app that would validate an entire directory tree containing DNGs. That could be quite fast and would be a good thing to run periodically.
Hal

DNG files display artifacts in Lightroom but not in Camera Raw

I've been scratching my head over this one for a few days so hopefully someone here can help. Some of my dng images are showing artifacts in Lightroom 3, see attached file as an example. However, if I open these images in Camera Raw 5.7 the artifacts are gone! The artifacts are also gone when I view the DNG in Windows Live Photo Gallery. The images are stored on a gigabit network server with the LR catalog file on the local Win 7 PC. One other thing I noticed is that for some images (not all) the artifacts will show up in the Library module but disappear when viewed in the Develop module. There are no "damaged file" error messages for Lightroom when viewing the affected files. I tried clearing out the Camera Raw Cache but nothing changed.
So my questions are: Are these files damaged or not? Is there a way to fix this problem. Why are they showing up fine in other image programs? Is there a utility that can verify the integrity of a suspect DNG file?

Dennis-H wrote:
Is there a utility that can verify the integrity of a suspect DNG file?
his page explaines how to do that usingAdobe DNG Converter:
http://www.dpbestflow.org/node/382

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.

Color change in RAW file from CR2 to DNG

I recently got a new Canon camera, the 60D and when converting from the CR2 file format to the DNG format using the latest 7.2 version of DNG Converter I notice a color change between the original image (CR2 file) to the new DNG file. Once I open it into Camera RAW (version 4.6 with CS3) the color issues go away and if I save it as a JPEG the color issue is no longer a problem but if I were to resave the DNG file to another DNG file it reverts back to the color changed view in MacOS. Is this something that I need to be concerned with for future use of the RAW files or is it a display issue in MacOS and iPhoto. The DNG file also shows the color change in iPhoto. Below are the two screen caps.
RAW CR2 file straight from the camera
Converted RAW CR2 to DNG using DNG converter
This issue only appears to occur in preview mode or in iPhoto.
Thanks,
Nathan

Try changing the CAMERA’S color-profile settings from sRGB to Adobe RGB or from Adobe RGB to sRGB, switch to the opposite one, and see if the previews are any closer for new CR2 you convert to DNGs. The theory is that the preview is in terms of the camera Color Profile setting (sRGB vs Adobe RGB) and when the image is converted to DNG that profile is lost for iOS to see, and it is defaulting to the wrong profile.
In the end , what matters is how Camera Raw converts the file.
Also DNGC 7.3 is the latest version: http://www.adobe.com/downloads/updates/

Strange artifact in some NEF and .dng files

Using a Nikon D80 with 4 GB Sandisk Extreme SDHC card; shooting full resolution NEF; Mac G5, Mac OS X 10.4.10, images are run through Adobe DNG Converter 4.1. Image is opened in Camera Raw 4.1 (and now 4.2) window within Photoshop CS3 Extended.
In some photos with dark areas, there is a single, tiny, transient on-screen artifact in form of a red dot, either two or three pixels square, which always appears in the same location against, say, a dark sky or trees. It can persist or literally disappear on its own after about two seconds. If the file is reopened in the same session, the red dot may not be there at all. If the loupe tool is used, it always disappears within the loupe after about two seconds, even though it may persist in the unmagnified screen. The good news is that opening the image as a .psd in Photoshop shows no sign of this anomaly, no matter how greatly magnified.
Note: It can also appear if I drag the NEF or .dng file over to Preview. But in this case, it does not disappear.
Does anyone have a clue what may be causing this?
A screen shot comparison from Camera Raw 4.1 is attached below. The left image shows the dot in place in the section of the photo and with the loupe.The right image shows the dot gone, but persistent in the unmagnified image.
Neil

Again, thanks, Thomas. Most, um, enlightening! <g> I've been shooting raw exclusively over the past six months or so. Camera Raw apparently did its job, which would explain why the pixel disappeared after a couple of seconds. I'll probably run the same image through Lightroom to see what happens. However, I can still see using .jpg once in awhile (family and friends snapshots destined for email or postcard-size prints). But then, the question begs, if other pixels are compensating for the bad pixels, does that materially affect overall resolution or appearance of the images? Although I've been aware of annoying "stuck" pixels on LCD monitors, I never really thought about how DSLRs deal with this. Neil

Linking dng files with jpegs

Hello all
Back in my Powerbook G4 days I had a habit of shooting cr2 with my Canon 5D but converting the cr2 file to DNGs and importing the latter into Aperture 1./2. But they were very slow to load so in the end I abandoned a raw workflow but still choose to keep the raw files. I shot jpeg+cr2, converted the cr2 files to dng, deleted the cr2s and imported the jpegs to Aperture. The DNGs were just kept on my external but never imported into Aperture.
Fastforward to 2012 and I have a highend RMBP and thought it would be fun to reimport those old dngs and wondered if these could be matched with the jpegs and treated as one file (with options to work with RAW or JPEG). Is there a way to do this? I thought I read somewhere that in Ap 3 you can break up and re-pair raw+jpegs. Just not sure if I can do that with dng+jpeg when the original combination was cr2+jpeg. The exif data will be the same but the DNG file created/modified/opened dates in Finder are all based on when they were converted.
I experimented with importing two of them into the same project as the original jpegs. When I sort by date they do not show up but when I sort by file you can see them beside the jpegs. Sorted by date I can only click on the jpeg file and right clicking does not give options of new version from master/jpeg so it is not linking them.
Any thoughts on how to do this or how best to fudge it?
Thanks
Ross

It depends on how you define a raw format. As far as the Camera Raw adjustment controls are concerned, you cannot tell the difference between a linear dng and "raw data" dng, since all the current Camera Raw adjustment controls happen after demosaic step.
(Both Canon and Kodak have cameras that produce demosaiced "raw" file formats in some cases. In Canon's case, the new "sRAW" format is already demosaiced. Some Kodak cameras (e.g. Kodak 14n, etc.) also saved a "lower resolution" raw format that was also demosaiced.)
The dividing line between a "raw" format and a "rendered" format is with whether the data stored in the file is scene referred or output referred. As long as the data is in a scene referred color space, it is easy to change the white balance, exposure, tone curve, etc. Once the data is converted to an output referred color space, it gets much harder to change those parameters without causing artifacts.
That said, it is better to keep the image in mosaic format if possible, since this allows you to take advantage of better demosaic algorithms in the future. For this user, that is not possible because Camera Raw 2.4 does not have a demosaic algorithms that works for the Fuji S5, so using the linear form of dng solves that problem.

DNG Files with Legacy Versions of ACR

In our office, we have 16 staff members currently running Photoshop CS. Although these terminals have the newest version of ACR available for CS, which supports DNG files, I ran into a DNG that I was unable to open today. I converted a Raw file from a Fuji S5 Pro using DNG Converter v 4.3.1 without a problem. However when I tried to open it with Photoshop CS, it did not open ACR. Instead I got a "not the right kind of document" error.
I took the same DNG file to a remote terminal that has Photoshop CS3 installed (with updated ACR as of a couple of weeks ago) and had no problem launching the ACR program and opening the file.
We are in the process of replacing all of our terminals at the staff member desks. But this may not happen until the 2nd half of 2008. At that time we will be upgrading all of the terminals to Photoshop CS3. My hope was that the DNG support for the version of ACR we had would be a bandage for working with these files until we were able to complete the upgrade. We can install the software that came with the cameras, but for the sake of consistency in how we file and archive files, since we'll be using DNG in the future it would be nice to now also. I've been able to work with other 'new' Raw files in this manner, but for some reason not the DNG converted from the S5 Pro Raw.
My assumption was that DNG was the same regardless of the initial Raw file type. Is there something I'm overlooking, or are newer DNG files not able to be converted with this legacy version of Photoshop and ACR?

It depends on how you define a raw format. As far as the Camera Raw adjustment controls are concerned, you cannot tell the difference between a linear dng and "raw data" dng, since all the current Camera Raw adjustment controls happen after demosaic step.
(Both Canon and Kodak have cameras that produce demosaiced "raw" file formats in some cases. In Canon's case, the new "sRAW" format is already demosaiced. Some Kodak cameras (e.g. Kodak 14n, etc.) also saved a "lower resolution" raw format that was also demosaiced.)
The dividing line between a "raw" format and a "rendered" format is with whether the data stored in the file is scene referred or output referred. As long as the data is in a scene referred color space, it is easy to change the white balance, exposure, tone curve, etc. Once the data is converted to an output referred color space, it gets much harder to change those parameters without causing artifacts.
That said, it is better to keep the image in mosaic format if possible, since this allows you to take advantage of better demosaic algorithms in the future. For this user, that is not possible because Camera Raw 2.4 does not have a demosaic algorithms that works for the Fuji S5, so using the linear form of dng solves that problem.

Best workflow using DNG files from Odyssey 7Q in Premiere 8.1

Finally, the magenta highlights issue has been fixed in this new 8.1 version of Premiere - lovely! :-)
I'm wondering though, what the best workflow is when using 2K/4K raw dng image sequences from the Odyssey7Q? In this case, shot on the Sony FS700.
Is there a simple and easy way to batch import a bunch of clips?
The behavior of the Media Browser in Premiere is a little different than the last version... When you choose the individual dng clip folders it now shows one single dng sequence files instead of a bunch of individual png images. But you still have to browse to each clip folder and choose the dng sequence file. If you just choose the root that contains the clip folders or if you choose multiple clip folders, it will import the content of those folders as individual dng image files! Pretty annoying...
Does anyone know of a better way to import where you don't have to choose each clip manually?
Also, how do you bring a PP edit sequence into AE for ACR processing? You can't copy/paste the files and you can't choose "Replace With After Effects Composition" - those two methods will just import one single DNG frame into AE.
You can import a whole PP project into AE but that will just show the entire PP sequence as one single file. You can't access the individual clips or open it in ACR.
The best method I know of is export all the DNG sequences as proxies, edit the material using the proxies on PP timeline, copy/paste that into an AE comp and then manually replace each of the used proxy files with the original DNG files, which will open up the ACR. But that's a bit of a hassle...
Is there any way of taking advantage of the full dynamic range of the DNG files in Premiere? When I bring down and overexposed image using either fast color correction or by right-clicking on a clip and choosing "source settings..." and using the exposure slider, the image looks "flat" but when I do the same thing using the ACR, I can reintroduce the details otherwise lost in the overexposure.
Any info or advice on this will be greatly appreciated

Hi EyelightKasper,
See if this method will work for you: Re: How to import multiple DNG files into Premiere
Thanks!
Kevin

Editing a DNG file and saving it again as DNG using Photoshop

Hi everyone,
I have a set of .dng raw images which I would like to edit using Photoshop and save back out as .dng files. It sounds like a very simple task, but I have been struggling with this for half a day.
To give a concrete example, I have two dng images from the same camera. I want to copy an object from one image and paste it to the other, and then save out the output as a .dng file. This should take me like 2 minutes in Photoshop, right?
Well, when I open the files, it first brings up the Adobe Camera Raw tool, but this only lets me do very basic edits (I can't figure out how to copy an object from one image to another, let alone perform the necessary edits to blend them seamlessly.).
So I click "Open Image" to get them into Photoshop, where I can do all of my necessary edits (copy and paste, brushes, etc.). However, after I am finished and I try to save my edits, Photoshop only lets me save the output in .psd (along with other formats) but not dng. I need to save it back out as .dng, as the next program in our workflow pipeline requires .dng files as input. So how do I do this simple task?
Why can't I save my resulting image back out as a .dng file? I tried saving as .psd and then using Adobe DNG converter to turn it into a dng, but it doesn't seem to be able to do that. I also tried saving as Photoshop RAW, but for some reason the converter can't convert from Photoshop RAW to DNG. It doesn't make any sense to me.
I know that Photoshop knows my camera parameters because it was able to read the original dng files properly in the first place. So why can't I read in the .dng image make some edits and then save it? How are people editing dng files?
Thanks for your help.

Also, there is no way to turn an image back into raw image data after it has been edited in Photoshop. It would be as difficult as uncooking an egg.
I understand that this is difficult if I am doing arbitrary image editing operations, since those operations may not be properly defined in the RAW space. But in this case I am cloning pixels from one .dng image to another. Shouldn't this be possible?
For example, assume we have 2 dng images and we want to take the left half of one and paste it in the same position over the other. I am not familiar with the dng spec, but at some level it should encode the values at each pixel (perhaps with the appropriate camera curve). So I just simply want to overwrite the values of one .dng image with values at the same pixels of the other, and since it's the same camera with the same settings used for both this should be possible, right? In the worst case, I could write a program based on the DNG spec that parses the two dng files, overwrites the necessary pixel information simply using the second image's data, and then writes the dng back out. But this seems like a complicated way to do something that there should be an Adobe tool to do.
Perhaps it would help if I tell you exactly why I need this for. We are capturing raw video using the Blackmagic Cinema Camera which outputs a directory full of 2.5k dng images for each take. We were doing a take of a scene using a tripod, but an otherwise great take was ruined because at one point a crew member poked their head into frame. So I want to use information from the other dng frames to overwrite this portion of this image to hide this problem.
If these were regular images (.jpg, .tif, .exr) it would take us no time in Photoshop to use the information from the other "good" frames to fix this problem seamlessly. However, we would like to keep everything in dng format so that I can then read everything into DaVinci Resolve for color grading correctly. Any idea on how I can do this, if I can't use Photoshop?
Thank you in advance for your help!

Lightroom and Samsung GX-10 DNG files

Hi
i've got a problem with LR and the samsung GX-10 DNG file format.
It semmes that LR does not read correctly this Raw file
at the begin of the rendering, the image has good colors but they change at the end of the rendering. Colors are more dark and finally the photo is not nice.
I've done the same test with raw therapee and the rendering is better.
Have you got informations about.
It's such a pity because LR is great. i like it !
regards

yeah,, I know about raw data , and yes, wrong or not, the rendition of gx-10 pictures are very "bad" compared with other softwares and with my eyes, and I think that you can understand when i said "bad" no?, there aren't a wrong or correct in raw color but the people speaks about the wrong o correct colors all the time, i think that you understand when speak about bad colors, a bad WB , etc.
I know that i can make my own profile but is not easy, to generate a good profile I need a Macbeth ColorChecker or something like that for example and precise sources of light (like a tungsten) and taking account about that samsung cameras are "clones" of the pentax ones and that samsung shoots in DNG format (and not a propietary raw format) seems easy solve the problem about color interpretation of GX-10. With time I will buy a color-checker and try, but would be great a correct interpretaion of the own samsung colors
PD2: When i know about samsung "adobe-DNG" capacity, i didn't expect have problems with adobe soft and color intrepretation or something like that.
PD: Sorry , I don't speak english well, and so I can't express me very well , only basics

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

Placing DNG files for Mockup Design in Indesign

Hi there
I am a magazine designer where i get 400-500 photo selections from my photographer. We have finally upgraded to CS5 (yes yes took our time). I used to be able in CS2 Indesign place the DNG files for mockup of the pages, but now in CS5 it says: "Cannot place this file. No filter found for requested operation." Is there a filter available to do this or do I need to convert all of the DNG files to jpg to use in the mockups?

The ability to place Camera Raw images directly into InDesign has been a much requested but exceptionally highly-debated feature request since Photoshop started support for Camera Raw. DNG is actually just a special, TIFF-like standardized version of a raw image format that was an attempt to provide a universal container for common features of the various camera vendors' “raw” formats plus plus a common method of storing the vast amount of the individual camera vendors' and model-dependent “secret sauce” used to decode the raw image data for creating more industry-standard TIFF, JPEG, etc. images.
In many respects, a raw image is the digital equivalent of analog photography's concept of a negative, albeit not reversed in tonalilty and/or color. A significant amount of processing is obtain a usable image from raw image data. When shooting in JPEG mode with a digital camera, this processing is done in-camera and includes significant noise reduction, sharpening, color adjustment, and brightness / contrast adjustments depending upon the cameras' capabilities. All that processing is postponed to Photoshop's Camera Raw feature (or the vendors' own host computer-resident conversion software) when you elect to get raw-only images out of your digital cameras. A very large number of professional and amateur photographers who shoot raw mode always process their own images to TIFF or JPEG before submitting for any editorial review or layout. Trying to directly place the DNG file's raw image data, even for mockups, is like trying to do mockups using the negatives in the old days. Exactly what default settings would you use to use these images and how meaningful would the visual representation of those default settings be?
I have been involved with InDesign ever since the first prereleases of InDesign 1.0 (not CS1) and I don't recall any support ever given for direct placement of DNG or any other raw image format. I don't even know of any third party InDesign plug-ins that ever did that! InDesign itself was never not distributed with the libraries and data used for such conversions.
However, there are many cameras that have a mode by which both a raw image and a camera-created JPEG file are output to the camera's memory card. Perhaps you had some directories of images that had these dual image files. (Also, there are indeed only a handful of very specialized programs that produce DNG files directly. Most professional camera manufacturers have elected to continue to output proprietary “secret sauce” image formats. To get DNG files from such file formats, you need to either run a batch process to convert to DNG or perhaps Adobe's own DNG converter that can convert entire directories of raw image files to DNG.)
- Dov

DNG files not showing thumbnails preview icon on mac, after reduce/resize pixel count. Mavericks 10.9.2, Photoshop CC, ACR 8.4.0.199. Any Solution?

This is driving me crazy. With today's huge file sizes it seem to me that for the majority of pictures a pixel count of 12-16 mega pixels y more than ok size for editing and make printings; for the professional jobs is a good idea to have the biggest file we can. Due to that i was trying to convert some NEF files to DNG, saving some space in the process, But the impossibility to preview the picture's thumbnails and the file size (it displays 0x0) immediately take me to 1984, (Windows 3.11). and those are bad memories.
I don't know if this is an apple's or adobe's error, but it needs to be solved.
Anyone with the same predicament?

Thanks for your insight JimHess. Someone else on another post pointed out how Photoshop changes the color profile and other things and then trying to make this file into a DNG again confuses Mavericks (and, presumably, other flavors of OS X). Admittedly, the process I described is unorthodox and not what may want to do. Thank you.
A.J.: First, I am offended by your suggestion to omit my comment. I was simply trying to provide help in finding a cause of a general problem people are having across the internet. That problem, as you pointed out, is that modifying a DNG in some way in photoshop results in the thumbnail no longer being visible. Your modification is the size. Mine was not. But it was a general modification in photoshop and an attempt to reconstitute the file as a DNG that seems to be common theme, whether this workflow makes sense or not. Additionally, I'm very new to digital photography and tried to be helpful. I would advise you (as an educator who knows the consequences of negative first-time experiences) to be more mindful that not everyone on here is as experienced as you and everyone can benefit from being clearer in their questions and their comments.
Second, as JimHess pointed out, in manipulating a DNG file in any of the programs in a way that alters the actual file (not changing some setting that is ultimately stored in a side-car file or does not actually alter the photo) is probably the root of the problem. Changing the file size by altering pixel count may first require one of your adobe products to physically alter the file information in a way that stops Mavericks from being able to recognize the contents as RAW information. Does this make sense?
Best regards,
Robert

Color artifacts in DNG files

Similar Messages

Maybe you are looking for