Am Dienstag, 8. März 2016, 21:46:05 schrieb Denis Testemale: > Hello! > Following the topic we discussed one month ago (support of xmp files > from the Ramperpro timelapse controller), and seeing that DT 2.0.2 now > supports this functionality (thanks for the very quick integration!), I > gave a try with some files (one sample below, NEF and xmp). The exposure > correction I see in DT after import does not match the value in the xmp > file (in the example below, exposure correction is 0.29048 in the xmp > file, but I read 0.26eV in DT). > I tried several files (4), and I observe that this discrepancy seems to > be always present and the larger the exposure correction the larger the > offset. I didn't do a systematic test, but the offset is about 0.1eV per > exposure correction eV. Is it a normal behavior because maybe LR and DT > exposure do not have the same definition, or a kind of bug?
Looking at the code it seems to be doing that on purpose, I can't see any reasoning for that though (no comments). Maybe Pascal can tell us more? > Cheers > denis Tobias > NEF file: > https://framadrop.org/r/AhLrVzGhsZ#sPejdKbaiRPbojpBejc4/jjK/+nteiraL+y/FW8UX > r0= > > xmp file: > https://framadrop.org/r/aDVa5sGvS5#+oQ85NMje2HVG4Ud3HuegAMxCIkAkf+5cUA4t+YSO > d4= > ___________________________________________________________________________ > _ darktable user mailing list > to unsubscribe send a mail to [email protected]
signature.asc
Description: This is a digitally signed message part.
