On Wed, 2018-04-04 at 08:21 -0400, Patrick Shanahan wrote: > * Timur Irikovich Davletshin <[email protected]> [04-04-18 > 08:01]: > > On Wed, 2018-04-04 at 13:36 +0200, Tobias Ellinghaus wrote: > > > Am Mittwoch, 4. April 2018, 13:15:39 CEST schrieb Timur Irikovich > > > Davletshin: > > > > Hello everybody! > > > > > > > > Just decided to play with DNG converter and discovered problem > > > > related > > > > to lens data interpretation by DT (2.4.2). > > > > > > > > 1. NEF file loaded by DT applies correct lens parameters. > > > > Lens info shown by DT: Nikon AF-S DX Nikkor 18-55mm > > > > f/3.5-5.6G > > > > VR II > > > > > > > > 2. DNG file cannot apply it because wrong EXIF information is > > > > used > > > > (short lens name vs. full). > > > > Lens info shown by DT: 18.0-55.0 mm f/3.5-5.6 > > > > > > > > 3. Focus information also is lost in DNG. > > > > > > That's why we tell everyone to never convert to DNG. > > > > > > Tobias > > > > > > [...] > > > > I believe problem is Nikon/DT related not DNG. Canon files I tried > > work > > as expected. Another example Nikon D1X files converted to DNG are > > useless because there is no way turn pixel scale module on > > manually. > > simple, don't convert native files to dng. the dng format is not > provided > by Nikon and cannot know the proprietary secrets that Nikon uses to > generate its raw files. dng is *not* a standard. dng makes changes > the > the original (raw). why convert your raw twice? >
DNG made from Canon, Olympus works, Nikon's doesn't... meanwhile EXIF data is there. Looks like it's not a problem of DNG itself. Whether we like it or not but DNG files (native or converted) are quite common. Especially when DT documentation declares some sort of DNG support in very first line of https://www.darktable.org/resources/camer a-support/ ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to [email protected]
