NEF conversion to DNG

Is there a maximum number of raw files that can be converted to DNG in one operation in Lightroom 5.
I can convert multiple folders with about 100 files OK, but if I try to convert 3000+ files over night Lightroom stalls.
Also when Lightroom is set to delete the raw file after conversion should it also delete the sidecar file.

I don't know of a limit, I suspect the hardware, OS, RAM and other factors play a role. Yes, the sidecar files will eventually be deleted in my experience but it's not instantaneous by a long shot.

Similar Messages

NEF vs. DNG : Different renderings in Capture One 4

I've just observed that -- when I convert a D200 NEF > DNG, and then import both to Capture One 4, the renderings are slightly different ... both of them with default settings.
I select ICC profiles for NEF > D200 Generic , DNG > Neutral.
DNG is darker than NEF.... not uniformly daker, but just some parts... like different curves applied.
Same Kelvin values (WB) applied to both files give different results -- DNG needs lower Kelvins degrees to look like the NEF.
NEF Reds are orang-ish in DNG. DNG yellows are orang-ish in NEF.
Something I'm not sure how to describe, but it looks like differences in color brilliance between the two files.
If I select ICC profile for DNG > D200 Generic , then the same applies, only that now DNG looks more saturated than NEF.
For reference, Lightroom renders both files exactly identical.
So ... is this something related only to how C1 renders both files (C1 not knowing how to manipulate a DNG), or is it related to the DNG conversion itself (adobe playing god with the raw data) ?

Honestly, I can infer from your posts by SIMPLE READING only that you are confused and speculating a lot.
I try to put the results in cleartext:
1. C1 creates result A from the native raw file.
2. C1 creates result B from the DNG file converted from the raw. B is different from A.
3. C1 created result C from the modified DNG file. C is different from A AND from B.
If the above is right, then we can say, that
a. C1 CAN work with the pure DNG data, which includes the color conversion Adobe's way. The modified DNG differs from the original DNG in that the camera name (maker and model) has been changed, AND the MakerNote tag has been made unaccessible, and this file has been accepted by C1.
This is in contrast to some other raw processors, which accept a DNG file only if they know the camera's characteristics; see the thread "Is DNG a universal raw format?" down below.
b. C1 DOES take some information from MakerNote if available, otherwise these two version would yield the same result.
The originating question was, why the "native" and DNG result are different. Based on the above test, I can not answer it with certainty, it is not clear, what C1 uses from MakerNote.
Now, to the question of "DNG - standard or not".
The DNG specification tries to put many aspects of a raw image in a uniform shape. However, there are two distinct areas posing problems:
1. Camera specific options. The Exif specification provides for a way of recording sharpness, contrast, saturation and white balance, but the specification has been created very short-sightedly and became useless. Other options, like Picture Style has not been envisioned at all. Such options are coming in series, the DNG specification does not cover them.
These options are available in the native raw file as well as in DNG, but programs have to make extra gymnastics to extract them from DNG; NOT DNG is to blame in this point.
Some raw processor go the extra way, others don't. ACR does not make anything, which can not be seen in DNG format as well, i.e. it does not support these options.
2. The other problem area is the color transformation. There is *no* generally accepted way to describe the sensors' behaviour. Most raw processors adopted camera and model specific solutions; Adobe defined a way in DNG, which is an *approximation*. Others don't share the enthusiasm, with some justification. It is not by chance, that camera makers' own converters give the best colors of their cameras.
So, a raw processor can process a DNG file using the hard-coded knowledge of the sensor - like Aperture does - or going ACR's way of color transformation.
C1 may take some setting(s) from the native raw file, while not doing so with a DNG, even if the data is available (but differently). This may be the reason for the difference between the results of the NEF and DNG conversion.
Note, that it is not necessary to access the MakerNote for identifying the camera.

Converting NEF files to DNG

I have recently purchased the Nikon D800. I am having a difficult time converting the RAW NEF files to DNG so I can view them in Photoshop Elements 6 and Photoshop CS6. I do not understand why Nikon would make it so difficult to upload into Photoshop. Very frustrated. Any information would be appreciated.

Are you using the latest version of the DNG Converter, at least 7.1? There is also a Release Candidate (beta) version, 7.2 RC1.
What do you mean by having "a difficult time converting"? What happens when you try?
Are you aware that the DNG converter works only on folders and not on individual files? You must point the DNG Converter to the folder that contains the files, not at the files themselves.
How are you getting the files to your computer? There have been many reports that the Nikon Transfer (or Nikon Transport) utility damages the files. Try just dragging them from the card to your computer instead.
Are you on Macintosh or Windows? What exact version of the OS?
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

RAW + old photoshop generated .XMP file conversion to DNG

I have a set of camera raw files (.mos) and .xmp side car files that were generated in photoshop several years ago. I am thinking about converting all of the files and side cars to DNGs because Leaf Capture software is no longer being updated.
Before I do I want to confirm that Lightroom can read both the raw AND the corresponding side car files and convert them into single dngs. I also want to know if the .xmp information is extractable after the dng is created in the same way that the raw/original file is extractable.
I've been trying to test lightrooms ability to read .xmp files on my own. I added a .mos file in a folder with a corresponding .xmp file and a .mos file in a folder without a corresponding .xmp file. Lightroom reads similar adjustment information for both images but only generates a preview that more closely resembles a finished retouched .PSD of the added .mos file that does not have the .xmp file in the folder it was added from. I'm at a bit of a loss regarding how to proceed.

nonovsco wrote:
Upate on situation: I followed up with the individuals that created the files and found out that the side car files were in fact generated by leaf and not photoshop. i tried another test and it looks like the folder with a .mos +.xmp file is now reading differently than a .mos file by itself. both suggest that changes were made to the files with modulations in the "develop" section of lightroom.
You can view the XMP file data in Notepad or any other text editor, just select 'Open' and select 'All File Types' so you can see the XMP files. It should be possible to store both C1 and LR develop settings in the same XMP file, but there may be some naming conflcts. Review of an XMP file with both C1 and LR develop settings saved to it should show the two different develop data sets in Notepad. Conversion to DNG should save ALL XMP data, but you may lose some of the (edit) Leaf proprietary data that may be in the raw file's metadata. For now I'd hold onto the raws + XMPs, even if you do convert to DNG.
You can use EXIFtoolGUI to examine the metadata in the new DNG files and compare it to the original XMP file's data. My Canon DSLRs appear to have all of the manufacturer's 'Makers Notes' copied over from the raw file into the DNG metadata.
http://freeweb.siol.net/hrastni3/foto/exif/exiftoolgui.htm

Anyone getting acceptable D700 NEF conversions with Aperture?

I got home from photographing an afternoon wedding today and nearly ****** myself when I pulled up the files in Aperture: most of the pictures taken outside appeared overexposed by a stop or two, looked horribly desaturated, and suffered from serious white balance problems. "Highlight hot zones" lit up half the image in red. I had been keeping my blinkies under control during the shoot, and the images looked fine when I spot checked them during the day, so I suspected that Aperture was doing something wonky. I exported several of the masters and opened them up in Raw Photo Processor, my benchmark raw converter. Sure enough, they looked fine. Aperture is screwing up the raw conversion.
It was particularly interesting how the embedded JPEG that initially popped up looks fine, and then Aperture's subsequent raw conversion looked terrible.
I'm running up-to-date everything: 10.5.5, latest camera raw update, etc.
Is anyone getting acceptable D700 NEF conversions? If so, what are you doing differently?
Thanks,
Andreas

Andreas,
If Preview is showing the same behaviour, then it's not Aperture itself but rather the Camera Raw 2.2.
To clarify the "similar output" statement I made with respect to the RAW conversions:
ViewNX - straight off it looked like what I wanted with minimal tweaking, as it read the NEF file secret sauce instructions such as tweaked saturation. Was not as good at fixing highlights and shadows though in the case of problematic shots but produced excellent detail
ACR - produced good middle-of-the-road that by comparison to ViewNX was a little under-saturated or lacked "pop" (but I couldn't finger any particular aspect). By cranking up the saturation and laying with white point, black point etc could arrive at a similar appearance outcome to ViewNX.
Aperture - seemed to produce a shot more like ViewNX and allowed big latitude in adjustments, especially pulling detail out of shadows without blowing out the photo. Auto exposure was surprisingly useful. Level of detail perhaps not quite as good as ViewNX, but had to be looking at 400% blowup onscreen to pick it, and even then the diff could have been put down to the level of default sharpening.
I hadn't heard of RPP, but will give it a go.
Meanwhile, you're stuck in no-man's land... Here's hoping Apple fixes the 2.2 bug in 2.3 and you can finally do the RAW processing!
Regards,
Calx

Lightromm importiert zuert als .nef bevor in .dng umgewandelt wird, dadurch werden Dupplikate nicht erkannt; Schlechte Performanc.

Lightroom CC ist markannt langsamer als LR 5.7!
Beim Importieren werden die Dateien zuerst als Original .nef importiert obwohl .dng ausgewählt ist. So werden auch Duplikate nicht erkannt. Danach wird in.dng umgewandelt. Das dauert gegenüber der Version 5.7 3x länger!!
Export von 450 Dateien dauert 3 Std. 45 Min. Das ist doch nicht normal!!
Was läuft hier falsch?
Bin für jeden Tipp dankbar.

Also bei mir ist das ganz genauso. LR-CC importiert zuerst die NEFs und konvertiet anschliessend in DNG. Da ich beim Import gleich 1:1 Vorschauen rendern lasse, werden nach dem Import 2 Processe gestartet (DNG-Konvertierung und 1:1 Vorschau rendern). Alleine die DNG konvertierung benotigt ca. 4-5x länger als in LR5.
Tja echt ein Rückschritt. Wenn ich nicht auf LR-CC angewiesen wäre (neue Nikon D7200) würde ich glatt wieder die 5.7 verwenden.
Evtl. werde ich die NEFs zuerst mit dem DNG-Converter konvertieren und anschliessend erst in LR-CC importieren.
Auch der Export und das Veröffentlichen dauert wesentlich länger und der Rechner (I7-3770, 32GB-RAM, GTX-770, LR-Katalog auf SSD 1TB) ist während des Import/Export stark ausgelastet und teilweise nicht mehr bedienbar. Unter LR-5 lief alles deutlich flüssiger.
Also Adobe, behebt das mal bitte schnell.

I have converted some NEF files to DNG without compression but the conversion were performed WITH compression!

How to avoid it?
Bernard

As LR5user correctly notes, dng ALWAYS uses compression. You can only choose whether you want lossy compression or lossless compression. If you did not check the lossy compression checkbox, it will use a lossless algorithm. You do NOT want to avoid this as you are only wasting disk space if you don't use that compression. There is no loss of information. You should end up with files that are somewhat smaller than native raw files as the compression is somewhat more efficient than what camera makers use in their cameras in general.

Convert NEF 14bit to DNG with Lr4 (or 3)

I converted all my NEF (nikon D700) 14Bit to DNG using Lightroom 4.
The file size of NEF is 22-26Mb
The file size of the DNG is 11-15
I think is to lower becaus I was told that the DNG is 20% smoller than the RAW.
So I think that Lightroom is converting in 8Bit
thnx
Alberto

Forrest61,
First, there is absolutely no need to shoot in uncompressed raw on the D700. Change the settings to "lossless compressed", and your raw files will only be about 14 MB each. You'll be able to fit more shots on each card, the images will download faster, and you'll save on disk space. The resulting images are mathematically identical to an uncompressed raw.
Yes, a DNG places the 12-bit or 14-bit data into a 16-bit container, so no data is discarded when you do a lossless conversion. It is only when you opt to use lossy compression or downsize the image when some data obviously needs to be thrown out.
Once the image is opened in Photoshop, it will not show whether the source was 12-bit or 14-bit. Photoshop documents exist as 8-bit, 16-bit or 32-bit documents. There are no in-between bit depths, since they operate in multiples of 8 (8 bits in a byte). So whether you open a 12-bit or a 14-bit NEF, they will appear in Photoshop as either 8-bit or 16-bit documents, depending on your settings.

Nikon D5200 - Convert NEF (14bit) into DNG (only 12bit?!)

Hello,
I have a problem concerning the DNG converting process of my NEF (RAW) files of my Nikon D5200 to DNG files. NEF file should have 14 bit color space (according to the manual`s on p. 234 - - http://www.nikonusa.com/pdf/manuals/dslr/D5200RM_NT(11)01.pdf - the camera does ONLY capture NEF file as 14 bit file, not in 12 bit files; there is no setting like in den D7100 to change this e.g. to 12 bit). My problem in lightroom is that when I convert my NEFs in lightroom in DNGs it shows me that the DNGs are only 12 bit?! If I go to library > right toolbar > metadata > DNG > "Bit pro sample" it says 12 and NOT 14
How could that be? Is there any chance to fix this and if so, which way to correct this?
Many thanks for your help!

I read the EXIF data with RawDigger (many thanks to ssprengel!) and it seems that the "bits per sample" (RawDigger > EXIF) are the SAME in ALL DNG files (= 16 bit), no matter if I converted a 12 bit lossy or lossless or a 14 bit lossy or lossless NEF file. What I was able to seen in the EXIF data of the DNG files was if the "NEF compression" is lossy or lossless, although is was a DNG file. So I was able to "reconstruct" if this DNG file was once (= before the conversion) a lossy or lossless NEF file, but nit if it was once a 14bit or 12bit NEF file.
As soon as I opened the NEF file in RawDigger I was able to read if the file is a 12 bit lossy, 12 bit lossless, 14 bit lossy, 14 bit lossy. But when I compared the e.g. 12 bit lossless NEF file with the equivalent DNG file, I WAS NOT ABLE to see any difference in terms of quality. Both are exactly the same in terms of their image quality, the e.g. 12 bit lossless NEF file and the converted DNG file. The only differnce between the both is size. The equivalent DNG files are a lot smaller (and it seems the Adobe has a much better compression algorithmus without compromising the image quality):
12 bit lossy NEF (10,9 MB)               = equivalent DNG (7,4 MB)            --> 32% less
12 bit lossless NEF (12,2 MB)          = equivalent DNG (7,5 MB)            --> 39% less
14 bit lossy NEF (13,8 MB)               = equivalent DNG (12,2 MB)          --> 12% less
14 bit lossless NEF (16,2 MB)          = equivalent DNG (12,7 MB)          --> 22% less
So, to summarize, the good news is that no matter what option you chose to save your NEFs in your camera (12 bit lossy, 12 bit lossless, 14 bit lossy, 14 bit lossy) when you convert them in DNGs the quality DOES NOT change. The only downfall is that the metadata in lightroom is somewhat missleading and confusing:
12 bit lossy NEF           = 10 "bits per sample" DNG (in lightroom`s metadata: right toolbar > metadata > DNG), but exactly the same image quality as the 12 bit lossy NEF
12 bit lossless NEF      = 12 "bits per sample" DNG (in lightroom`s metadata: right toolbar > metadata > DNG), but exactly the same image quality as the 12 bit lossless NEF
14 bit lossy NEF           = 12 "bits per sample" DNG (in lightroom`s metadata: right toolbar > metadata > DNG), but exactly the same image quality as the 14 bit lossy NEF
14 bit lossless NEF       = 14 "bits per sample" DNG (in lightroom`s metadata: right toolbar > metadata > DNG), but exactly the same image quality as the 14 bit lossless NEF
Many thanks to all of you and hopefully this help someone who has the same "troubles".

Mac: No preview in the Finder after conversion to DNG

Mac OS 10.6.8
Lightroom 4.4
My Ricoh GR creates DNG files that have previews in the Finder. But because the file sizes are big (and I don't need them so big), in Lightroom I reconvert them to Lossy DNG (using compatibility with Camera Raw 7.1 or later). Now, after this conversion, these new DNGs don't have any previews in the Finder anymore.
So, the problem must be with the DNG converter in Lightroom!

I was going to refer you to this thread but then I saw you were the original poster there also.
http://forums.adobe.com/message/4508116

Converting Nikon NEF files to DNG without adding Chromatic Aberrations?

Used Adobe converter 7.4.0.137 and got Cyan and Magenta abberations on all high contrast edges. NEF files were from a Nikon D7100 and look great using ViewNX 2 software. Is there a better converter?

The DNG Converter embeds a thumbnail and preview in the DNG that are rendered with whatever the Camera Raw defaults are set to do for the camera the DNGs are from, which if CA is automatically being removed by default, then the preview should have it removed, otherwise it won't. Again, we'd need to understand what Adobe defaults are in effect for the camera when the DNGs are opened in the Camera Raw plug-in before understanding if this is a CA-no-on-by-default issue or a CA is not the type that can be corrected by the Adobe engine.
The Nikon engine might easily be masking narrow fringes of color by over-aggressive sharpening or via some automatic fringe-removal.
If the OP would post an example photo that exhibits the fringing, then others could test and comment on what can be done or not done to mitigate the issue in Adobe products.

Single Raw file conversion to .dng

Sorry if this has been asked but I can't find any tutorial on .cr2 file to .dng file conversion. I usually shoot RAW+jpeg on my Canon 50d. I am using CS3 and understand the need to convert my Canon Raw to the Adobe Dng format for PS processing. I downloaded and installed the free dng converter. I just can't seem to find a way to convert a SINGLE raw file into a SINGLE .dng file, it only wants a whole folder full for conversion. And am I correct in that Adobe isn't writing a plugin to let CS3 do the conversion? Thanks and Happy Thanksgiving!

You could copy the single CR2 file into a folder all by itself, then run the DNG converter on it. And I'm not completely sure, but I think I've heard of the ability for the tool to convert a lone file by providing the file path on a command line. Thus you could drag a single file to the DNG Converter icon if you had it on the desktop.
And you're correct - you're not going to get new camera support in the Camera Raw 4.x series that works with Photoshop CS3. Adobe stops adding new camera support when a new major version of Photoshop is released. But they do provide the (less convenient) DNG Converter for free.
-Noel

Question about Aperture and NEF...NEF conversion to match embedded jpeg

I just bought a D3 and will be getting Aperture soon. I understand that Aperture will not utilize the in camera settings in a NEF file (white balance, vivid and saturation, etc), and that the Nikon software will utilize the camera settings in the NEF file during the conversion process. I also understand that the NEF file has an embedded JPEG for thumbnail and preview, and this embedded JPEG is processed in the camera using the in camera settings. So, if Aperture was able to automatically compare the embedded JPEG to the raw NEF image, it could then create, or reverse engineer the conversion settings to match all of the in camera settings. Maybe this has been talked about before, I don't know. Does anyone else have and idea about this? Thanks
-Eric

Oh..OK I'm glad there's been talk about this. Maybe this would be a cool feature for Apple to put into future Aperture technology.
-e

Conversion to DNG in LR alters settings to worse

After adjusting the images to the desigered look (exposure, recovery, fill light and midtone contrast) I converted to DNG using the build in LR conversion. Most of the images look the same, but about 1/4 of the images have become dull and grayish looking.
I see that LR have sett every setting to zero on these pictures, and the only way of recovery is the readjust the picture. The changes to the bad have also affected the embedded JPEG version.
I have experienced this two times before. Are there any way of salvation, so I can avoid readjusting the images?
I am also interested in, why this happens in LR, is the DNG converter bad in ver. 1.0 or is it simply the DNG format I should avoid and sti ck with the Canon CR2 RAW format?
Kind regards
Klaus

Just found out, that if you in the develop mode selects "copy before's setings to after" then the damage is restored. It is almost like LR is looking at the alteration it has done when converting to the DNG as a user requested operation (not the dng conversion but the alteration of colours and so forth)
This doesn't particually make be comfortable using the DNG instead of Canons CR2.

Cannot read or extract NEFs from some DNG files

Hi, I'm hoping someone can help.
I've got a subset of DNG files from an older shoot that have somehow become undreadable. There are 119 bad files out of 1436 total images from the shoot. All of the bad files are in a consecutively numbered range (e.g., they are not randomly distributed).
I'm on a 64-bit Windows 7 system. The bad files do not open in Bridge, Photoshop, CaptureOne, etc., nor will the images thumbnail in Windows Explorer using either the Adobe or Ardfry DNG codecs. I have no idea when or how the corruption occurred, whether is came about from use of a software program, or had something to do with a bad file copy operation. But my current backups are also corrupted.
However, I always embed the original NEFs or CR2s in my DNGs, and so I was hoping to extract the originals. However, the DNG Converter refuses to operate on these files, though they appear to be of the right size.
Does anyone know of a way to salvage the original RAW NEFs from these damaged files? Is anyone at Adobe looking for a little science project? :-) I would be grateful for any suggestions...
Thanks very much,
Gary

I will attach a link to a troubleshoting document for this issue. If this does not resolve the issue you could TRY a restore to befor the issue started occurring, or a recovery MIGHT do the trick if it is not an actual hardware failure in the optical drive. The clicking concerns me that it might be a hardware issue... is it the typical clicking that you will hear when a disc is initially being read or is it a more aggressive clicking??
There is a fix in this link http://support.microsoft.com/kb/982116 that has you go in and delete the upper and lower filters in the registry. It is a little tricky, so I suggest you follow it WORD for WORD once you are actually in the registry.
I have seen deleting the upper and lower filters resolve most optical drive issues that were not hardware related.
I work for HP

NEF conversion to DNG

Similar Messages

Maybe you are looking for