> > Let's start with the toughest one: Lensfun makes no distinction > between lens and calibration. This means that we may have one lens > multiple times in the database. While we can certainly deal with > that (it is only unelegant), Lensfun is currently unable to take > calibration data from different calibration entries for one lens. > This means that in a lot of cases, data is there but cannot be used! > Yesterday, I added data to the database submitted by a user, which > absurdly enough meant that he lost vignetting correction for his > lens (which he had before). This must not happen. >
Good point, this really is a problem. What about a solution similar to this? http://sourceforge.net/p/lensfun/features/19/ Sebastian ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Lensfun-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lensfun-users
