#367 Lensfun correction(s) auto-activated with ufraw-batch and legacy .ufraw files

closed
Udi Fuchs
5
2015-02-10
2014-03-03
Volker
No

Steps to reproduce:

  1. Get a blah.ufraw file created with a pre-lensfun enabled version of UFRaw, i. g. 0.15. This will have no <Lensfun></Lensfun> tag whatsoever.

  2. Run an UFRaw version with lensfun enabled (0.19.2-2) using: ufraw-batch --conf=blah.ufraw *.nef.

  3. Result: Lensfun corrections will be used. This can cause trouble since depending on the crop size black borders will be visible.

  4. Conclusion: Recent versions of UFRaw (containing Lensfun) should treat configuration files from legacy versions of UFRaw as if the user explicitly decided to deactivate Lensfun.

Discussion

  • Volker
    Volker
    2014-03-05

    I've played with UFRaw a bit more and whatever I try, I seem not to be able to reproduce the issue above. If the

    <Lensfun>
        [...]
    </Lensfun>
    

    section is missing from the .ufraw recipe, it doesn't matter what value the

    <LensfunAuto></LensfunAuto>
    

    entry in .ufrawrc has. No Lensfun correction, neither with ufraw, nor with ufraw-batch. Sorry for the confusion, I really can't say what happened.

     
  • I close this bug report since the OP cannot reproduce the problem.

    Regards,
    Niels Kristian

     
    • status: open --> closed