* Timur Irikovich Davletshin <[email protected]> [04-04-18 09:40]: > On Wed, 2018-04-04 at 09:27 -0400, Patrick Shanahan wrote: > > * Timur Irikovich Davletshin <[email protected]> [04-04-18 > > 08:46]: > > > 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/c > > > amer > > > a-support/ > > > > do you not really read what you cite? > > <quote> > > Cameras that produce DNG files should be supported even if they are > > not > > on the list but samples are still appreciated. > > </quote> > > says nothing about supporting dng which is not native out-of-the- > > camera. > > > > This is why I wrote 'native or converted' in my previous letter. Dear > Patrick, I'm not here for the purpose of your religious war against DNG > which is *not* standard. I think this is just an obvious bug which can > be easily fixed.
and I have serious doubts the dev's will be concerned as they have repeatedly stated that altering an original raw is WRONG. why would they commit work to support it? I am not for or against dng, don't use it, don't care, don't understand why one would endure the extra effort and time required. your perception, not mine. and would only be considered a bug if that feature was to be supported, otherwise it would be a feature request. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to [email protected]
