On July 26, 2011 02:41:20 PM Chris Brack wrote: > **Hugin version 2010.2.0 can detect control points just fine, even in > Lion.** > > When I wrote this, what I meant is that something must have changed > between version 2010.2.0 and version 2011.0.1 to break the feature. I > thought it might be helpful for finding the cause of the issue.
Thanks for the clarification. I did not know that a previous version of Hugin works on OS X Lion. Can you please test with Hugin 2010.4.0? http://sourceforge.net/projects/hugin/files/hugin/hugin-2010.4/hugin- mac-2010.4.0.dmg/download There have been significant changes in terms of CP detection: 2010.2.0: technically speaking, Hugin did not detect CP. A third party tool did. Most user used Autopano-SIFT-C. Some users used a lesser known and faster tool, Panomatic. Both tools are encumbered by patents, it is the user's responsibility to make sure that they are allowed to use them in their jurisdiction. 2010.4.0: first release of Hugin's own CP detector, cpfind. 2011.0.0: cpfind improved and AFAIK it is superior to any tool previously used with Hugin. The problems you are experiencing are likely to be related to bug 792896. Probably a threading issue. * Autopano-SIFT-C does not use multi-threading * Panomatic uses zthreads for multi-threading * cpfind uses zthreads for multi-threading If you can report success/failure at running these tools on your machine and O/S, you will help us understand. Moreover: * Hugin 2010.4.0 uses boost threads for the ImageCache, and is known to be the latest version of Hugin not to display the threading problems. Or at least not enough to motivate users to file bug reports. * All versions of Hugin thereafter are affected by bug 792896. It only become apparent under specific circumstances and we are still working with users to collect information. If you can report success/failure at running these versions of Hugin on your machine and O/S, you will help us understand. Last but not least: I guess that you have upgraded to OS X Lion (as opposed to bought a new Mac that came with it). Do you still have access to Snow Leopard on that same machine? If yes, can you please run the same tests as requested above for both Lion and Snow Leopard and report results/discrepancies? If you don't have access to Snow Leopard, do you have memories? Every data point helps. We will also need help from OS X experts to understand if there are differences in how Lion handles multiple threads compared with Snow Leopard. I have an (unverified) feeling that what you are experiencing is related to bug 792896 and if I am right, once it will be fixed you will be able upgrade to the latest Hugin and go about your panorama making. Until then, unfortunately, I have no better solution than to nag you for details because I don't have access to a Mac to test/confirm your observations. Sorry. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/814301 Title: Control Point Detectors Broken in OS 10.7 Lion Status in Hugin - Panorama Tools GUI: Incomplete Bug description: The Control Point Detectors do not work when using Hugin Version 2011.0.1 in Mac OS X Lion. I have tested all the Detectors I have installed. Align_image_stack is usable (both "linear" and "FullFrameFisheye"), but it is abnormally slow and only works on half the images I've tested. The Detectors I have installed are: Pablo's patent free Panomatic Autopano-SIFT-C Panomatic Align_image_stack (both "linear" and "FullFrameFisheye") **Hugin version 2010.2.0 can detect control points just fine, even in Lion.** To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/814301/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~hugin-bug-hunters Post to : hugin-bug-hunters@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-bug-hunters More help : https://help.launchpad.net/ListHelp
