![]() The branch still exist in Hugin’s repository but has been superseeded. The project provided experience and insights, but performance was not as hoped. In 2008, Onur Küçüktunç built a feature descriptor, mentored by Alexandre Jenny of Autopano Pro. In February 2008 Bruno Postle’s built match’n’shift on top of it by using an intermediary projection to improve the quality of the generated CPs. Paired with existing autopano code, this yielded matchpoint. In 2007, during our first Summer of Code participation, Zoran Mesec implemented a feature matcher with the mentoring help of Herbert Bay (inventor of the SURF algorithm that is implemented in Panomatic). How does it know what version to download and whether there is already a previously installed instance that interferes with the new one?Įver since accepted as a Google Summer of Code mentoring organization, the number one priority has been a patent-free CP generator that can be shipped with Hugin. ![]() To make matters worse, packagers may be packing older versions of the CP generators with newer (incompatible) versions of Hugin.Įven the new installer that downloads the CP generators from their original locations is not free of these troubles. Hugin ships with pre-configured parameters, but Hugin can’t determine if the CP generator is of a version equivalent to the pre-configured parameters. But the changes in the CP generator need to be coordinated with the changes of parameters in Hugin. Users rightly complain about the difficulties of configuring a CP generator, and indeed it should not be that difficult. No active work was done on fixing 2.5.2, and the command line interface (and thus the string that goes into Hugin’s preferences) has been a moving target as well. The recommendation is to use 2.5.1 until the problems with 2.5.2 are fixed. For example Autopano-SIFT-C version 2.5.2 (that has not even been released) is broken. My more than two years old overview of available CP generators is outdated. So what can be recommended to packagers/distributors and users? Enblend-Enfuse for blending), but the interface to CP generators is a particularly tricky one because there are (too) many third party CP generators they take different arguments on the command line none of them is absolutely superior and last but not least they are encumbered by patents, limiting what they can be used for and where and how they can be distributed. ![]() Other functions of the panorama production process in Hugin are also performed by third-party tools (e.g. The packages did not help to lift the misconception, and brought a whole set of problems with them. Despite advanced control for CP placement, many users find Hugin without CP generator to be of limited use. Packagers (including myself when I was a Windows packager) who ship Hugin for platforms without proper package management (notably: Windows and OSX) have in one way or another bundled CP generators in the past to help making the downloaded package useful. Every time CP generation fails they perceive it to be a failure of Hugin. Contrary to popular belief, until last week Hugin did not have a CP generator.īecause CP generation is critical to the process of panorama creation and because Hugin is an interface to the panorama creation process users misunderstand Hugin for the whole. The biggest user misconception about Hugin is with control point (CP) generators.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |