I tried out the submitted poly3 model: <distortion model="poly3" focal="3" k1="0.01419"/> and I found it didnt really correct the distortions. Perhaps a typo? decimal point in the wrong place?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ahhhhhhh, I removed it because I was using darktable (2.0.6 I think) and it complained about the version 2 xml format, so I stripped out the extra stuff thinking it wasn't essential. There isn't a way to convert a k1 v2 value to a k2 version 1 value by any chance? Or what software do you use/should I use to read version 2 format? (windows/linux don't mind). Thanks!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, I dl-ed and built lensfun 0.3.2, and linked it to darktable, and ran lensfun-update-data that dl-ed a version=1 actioncams.xml with the gitup entry including aspect-ratio into .local. Ran on darktable and tried the fisheye correction - still only see a slight correction to the curvature. I'm doing this with jpgs if that has any bearings.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've worked out where I was going wrong. The target geometry in darktable had defaulted to thoby fisheye, once I had set it to rectilinear my photos straightened up nicely! In hugin, I noticed I had both target and source geometry set to rectilinear. Once I changed source to equisolid, things looked better there too. A quick play with the optimizer and I got a b/k1 of around 0.016, close to yours, so I knew I was now doing it right. Many thanks!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are welcome. The “thoby problem” is due to a binary incompatibility between Lensfun versions. Actually, DT needs to be re-compiled. But nobody has reported crashes so far, only the thoby problem, and this is annoying but harmless.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
fwiw, here are my results:
I tried out the submitted poly3 model: <distortion model="poly3" focal="3" k1="0.01419"/> and I found it didnt really correct the distortions. Perhaps a typo? decimal point in the wrong place?
I don't know whether this solves your issue, but your entry is missing the aspect-ratio tag.
Ahhhhhhh, I removed it because I was using darktable (2.0.6 I think) and it complained about the version 2 xml format, so I stripped out the extra stuff thinking it wasn't essential. There isn't a way to convert a k1 v2 value to a k2 version 1 value by any chance? Or what software do you use/should I use to read version 2 format? (windows/linux don't mind). Thanks!!!
The aspect-ratio tag is available also in version 1 of the DB. So, unless you have a really old Lensfun version, just leave it in and use version="1".
Ok, I'll try it when I get home later.
So, I dl-ed and built lensfun 0.3.2, and linked it to darktable, and ran lensfun-update-data that dl-ed a version=1 actioncams.xml with the gitup entry including aspect-ratio into .local. Ran on darktable and tried the fisheye correction - still only see a slight correction to the curvature. I'm doing this with jpgs if that has any bearings.
I've worked out where I was going wrong. The target geometry in darktable had defaulted to thoby fisheye, once I had set it to rectilinear my photos straightened up nicely! In hugin, I noticed I had both target and source geometry set to rectilinear. Once I changed source to equisolid, things looked better there too. A quick play with the optimizer and I got a b/k1 of around 0.016, close to yours, so I knew I was now doing it right. Many thanks!!!
You are welcome. The “thoby problem” is due to a binary incompatibility between Lensfun versions. Actually, DT needs to be re-compiled. But nobody has reported crashes so far, only the thoby problem, and this is annoying but harmless.