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.

Similar Messages

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!

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.

NEF-Dateien der Nikon D 800 werden bei CS 6 nicht erkannt

Sowohl bei CS 5 mit Camera Raw 6.7 as auch bei CS 6 mit Camera 7.1 aus den Labs kann PS die NEF-Dateien der Nikon D 800 nicht erkennen. Habe schon alles komplett deinstalliert, wieder installiert, alles vorherige rausgeworfen, aber kein Erfolg... Habe Win 7, i7 auf 64 bit (an sich schon ein Problem) aber das hier ist schon sehr ärgerlich.... Wer kann mir bei dem Problem helfen..
auch gern unter [email protected]
Ach so: Auch bei Lightroom 4 mit Camera Raw 7.0 werden die NEF´s der D 800 nicht erkannt...!!!
hendrik

I cannot understand German, but tried Google Translate without much success, so I'm guessing your problem.
Have you looked here? http://labs.adobe.com/technologies/photoshop/

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.

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

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 D600 NEF/RAW files/DNG 8.4 still cannot read

Hi all, I just tried installing several versions of the DNG plug in for CS6 and it still cannot read the Nikon D600 NEF/RAW files on a 2014 MacBook Pro. Any suggestions? I have searched previous questions, but cannot find one on this very topic. Cheers, Paul.

What version of Photoshop do you have installed. If you have CS6 make sure you use CS6 menu Help>Updates. To make sure you have the latest updates. If you have CS6 preternatural you should see version 13.0.6 when you use menu Help>About Photoshop if you hace a Creative cloud subscription you should see version 13.1.2 using menu Help>About Photoshop.
If ACR 8.6 is installed correctly it installs in a common place that is used by both Bridge CS6 and Photoshop CS6.
When you open a RAW file in Phoroshop or in ACR from the Bridge the ACR dialog should open and in its title bar you should see version 8.6. You should not need to create DNG RAW file for your NEF RAW files just to used ACR. You only need to do that if your using an older Photoshop version and an older ACR. version that does not support your Nikon Camera NEF RAW format.
If you have CS6 and the ACR title bar does not show 8.6 you do not have all the CS6 updates installed. If menu Help>Updates doe not install ACR 8.6 try downloading it manually from the CC updates site and see if the manual update works All the Adobe CC Updates: The Direct Download Links for Mac OS | ProDesignTools
or Adobe - Adobe Camera Raw and DNG Converter : For Macintosh
Version 8.6
Name
Size
Date
Adobe DNG Converter 8.6
210.7MB
7/30/2014

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

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.

I have Elements 12 and a Nikon D3300 Camera I am having trouble converting Nef files to DNG can anybody please help? Geoff

I didn't realise there was such a wide range of RAW files

The D3300 requires DNG converter 8.4 or newer. That version of the DNG converter requires Windows 7 or newer. Lightroom isn't an option because it requires Windows 7 or newer. It looks like it's time for new computer.

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.

Ich habe meinen Gutschein eingelöst und alles ist gut gelaufen aber als ich auf Artikel kaufen gerückt habe reagierte es nicht.

Ich habe meinen Gutscheincode eingegeben und alles war so wie immer. Doch als ich mir einen Titel kaufen wollte habe ich auf kaufen gedrückt und nichts ist passiert.es reagierte nicht. Das geht jetzt schon 2 Tage so !?!!!!!???????

Falls Sie nicht wissen, ist ein Mavericks v10.9 5.35GB Datei und requries ein Hochgeschwindigkeits-Breitband-Internet-Verbindung.
Langsamer Download-Geschwindigkeiten werden in der Datei abbricht, bevor es zu beenden führen kann.
Stellen Sie sicher, dass Ihr Mac kann Mavericks laufen > OS X Mavericks: System Requirements

Hi, was muss ich machen, damit (wie früher auch) bei der Photobucherstellung automatisches einrichten mehr als ein Bild pro Seite eingerichtet wird?

Hallo, ich bekomme es nicht mehr hin, wie früher, das ich bei einer Photobuchbestellung mehr als 100 Bilder in ein Buch bekomme. Der ordnet mir immer nur 1 Bild pro Seite an!! Was mache ich da falsch? Oder was hat sich geändert denn ich habe schon viele Photobücher erstellt da ging es immer ohne Probleme?
Bitte helfen, es ärgert mich sowas von..mypat

Hallo Sabine !
Höchst interessant Dein Beitrag. Gilt in Deutschland nicht grundsätzlich die Unschuldsvermutung bis zum Beweis des Gegenteils?
Die Art und Weise mit der ADOBE hier nach Gottes Gnaden denkt, und meint, man sei das kleine böse Menschlein, läßt mir den Draht aus der Mütze springen. Ein Unternehmer muß bereit sein, Risiko zu tragen. Das gilt auch für ADOBE.
Da sollte man ja grundsätzlich gewappnet sein, und zukünftig bei einem Anruf zunächst ertmal das Einverständnis für die Aufzeichnung des Telefonates beim Customer Support einholen, und wenn dann wieder derartige Ungheuerlichkeiten geäußert werden, sofort, ohne jede Umschweife und ohne jede Vorankündigung den Klageweg beschreiten. (Klage auf Unterlassung; üble Nachrede etc.)
Sabine - derartige Anwürfe wie Du sie erleben mußtest, würde ich keinesfalls auf mir sitzen lassen. Und wenn der Support in Schottland oder was weiß ich nicht wo die sitzen nicht in der Lage ist seine eigenen Programe zu bedienen, dann darf zu keiner Zeit zu Lasten eines Kunden gehen.
Klaus W. aus H.

[Flash Pro] Maus Events verhalten sich je nach veröffentlichung unterschiedlich

Hallo,
ich hab ein Problem.
Ich habe eine Cloud Mitgliedschaft und somit Flash CC als auch CS6.
Wenn ich mein Flash Spiel in der Entwicklungsumgebung veröffentliche ( egal welche der Beiden) wird das RIGHT_MOUSE_UP event nicht erkannt.
Wenn ich den selben Code allerdings im Browser veröffentliche funktioniert alles wunderbar.
Soweit ich es erkennen kann müssten alle Flashplayer, sowohl die der beiden Enwicklungsumgebungen als auch mein Browser version 11.7 haben.
Hat irgendjemand eine Ahnung was da los sein könnte?
Vielen Dank im Voraus

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

Similar Messages

Maybe you are looking for