Reply to thread

Message

<blockquote data-quote="BackdoorArts" data-source="post: 97408" data-attributes="member: 9240"><p>Here's my understanding of the &quot;Why DNG instead of NEF&quot; argument.&nbsp; I use Adobe products, primarily Lightroom.&nbsp; When making adjustments to the a DNG file Adobe will store them in the file itself, maintaining all the original data and adding the adjustment information.&nbsp; When making adjustments to an NEF file those adjustments are stored in a separate &quot;Sidecar&quot; file.&nbsp; So you now have 2 files to maintain should you ever need to move the file or pass it off to someone else for work, printing, etc.&nbsp; Granted, most of us never need to do that, and will likely create a Tiff or Jpeg to be sent out for printing, but the idea of making sure that I maintain both the NEF and Sidecar files, keeping them together and making sure they both get moved should I ever change computers/platforms, is the reason I have started converting on my import to Lightroom.</p></blockquote><p></p>

[QUOTE="BackdoorArts, post: 97408, member: 9240"] Here's my understanding of the "Why DNG instead of NEF" argument. I use Adobe products, primarily Lightroom. When making adjustments to the a DNG file Adobe will store them in the file itself, maintaining all the original data and adding the adjustment information. When making adjustments to an NEF file those adjustments are stored in a separate "Sidecar" file. So you now have 2 files to maintain should you ever need to move the file or pass it off to someone else for work, printing, etc. Granted, most of us never need to do that, and will likely create a Tiff or Jpeg to be sent out for printing, but the idea of making sure that I maintain both the NEF and Sidecar files, keeping them together and making sure they both get moved should I ever change computers/platforms, is the reason I have started converting on my import to Lightroom. [/QUOTE]

Verification