On July 30, 2011 01:55:41 PM MatatTHC wrote: > I'm using 2 computers. One is a fresh install and the other upgraded > over many ubuntu version with preinstalled hugin. On both computers > hugin was not working per default.
"per default" as described in your report is ambiguous and might be related to your specific configuration beyond Hugin's control. First question: what version of Hugin are you using, and from where: - the one that is distributed via the standard Ubuntu repositories? - the stable Hugin from the Hugin PPA [0]? - the nightly Hugin from the Hugin PPA [0]? - Hugin from another source / self built - please specify the details? > No control points were found. Was Hugin responsive after the CP finding attempt? Did Hugin return an error message? If yes what? >From the information available I can not say what went wrong. Assuming it was on the program's end, it could be one of the following: 1- Hugin does not find the selected CP detector 2- The selected CP detector does not find any CP 3- Hugin or the selected CP finder crashed 4- Hugin or the selected CP finder hangs / becomes non-responsive Since you state that autopano worked, I assume that it is not an issue on the images end. However, if the selected CP detector does not find any CP, I would like to investigate why it does not work as expected. This could be the an issue with the image file format, with meta data, or even (unlikely but possible) with the image content itself. Can you please attach to this ticket the .pto project file generated by Hugin when it does not find any CP, as well as the one generated with autopano? > As far > as I remember autopano was selected - but maybe I did this. I can't > remember 100% for sure. The CP detector selected in the preferences is the one that Hugin uses by default, and the selection can be overridden by manually selecting different CP detector settings on the Images tab. The user controls both. The preferences are stored in the file ~/.hugin. If the file does not exist, it is created when Hugin is launched using the application's default. If it is created by Hugin 2010.4.0 [1] or later, the application's default points to Hugin's CPFind and autopano is not a mandatory dependency. I can't tell what is the preference in your system. Hugin does not overwrite existing preferences, but existing preferences can be overwritten, e.g. with a backup/recovery of the user's directory or with deliberate user action on the file. If you want a diagnosis of your current preferences, please attach the file ~/.hugin to this ticket. > After installing the autopano package it worked. Historically Hugin supports many third-party CP detectors including autopano by means of a plug-in interface. Since the introduction of CPFind in Hugin 2010.4.0 this interface has become less important. The project will not break it intentionally, but it is also unlikely that it will get further development attention and could break in the future. > How should hugin be used per default, i.e. what should be selected in > the control point detection panel? Hugin is FLOSS and as such does not tell you how you should use it. If autopano works for you, good for you. By default Hugin 2010.4.0 and later installs its own CP finder CPFind and does not depend on autopano or other third-party tools. CPFind was introduced in release 2010.4.0 and improved in release 2011.2.0. Although no complete scientific comparison has been presented to the public yet, there is plenty of evidence that points toward CPFind's superiority over the tools previously plugged into Hugin, including autopano. The Hugin project does not endorse nor support third party CP finders. You can tell Hugin to use CPFind by default or specify what CP finding tool installed on your system to use for your specific project. To set the default preference, go to the menu "File" -> "Preferences". In the "Control Points Detectors" tab select "Hugin's CPFind" from the list and hit the "Set default" button. If you do not see a reference to "Hugin's CPFind" in the list, hit the button "Load Defaults". To use a specific tool in your project, go to the "Images" tab. Choose "Hugin's CPFind" from the list of "Settings" under the header "Feature Matching", adjust the number of "Points per Overlap" if necessary and hit the "Create control points" button to trigger the tool of your choice. I hope this information helps you making the most of Hugin for you; and that it helps you understand why the Hugin package has no autopano dependance defined. If you need further assistance, feel free to communicate it via this tracker ticket. [0] https://launchpad.net/~hugin [1] http://hugin.sourceforge.net/releases/2010.4.0/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/817889 Title: hugin autopano dependance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/817889/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
