Hi Harry, is there a possibility that the enblend and enfuse in the bundle are not the OpenMP versions? They consistently use only a single tread on my MacPro. I restored the old "extra" folder and that SL64ML version uses all my cores.
I also noticed a UI glitch; it is difficult to reproduce, but resetting the lens parameters under the "Camera and Lens" tab will sometimes leave the lower parameter area garbled. Regards, Martin On Jun 25, 10:53 pm, Harry van der Wolf <[email protected]> wrote: > Hi mac users, > > Another new 32/64-bit bundle including all extra command-line tools. > > Tiger users should use the Tiger versions of enblend/enfuse as can be found > in the "enblend-enfuse-4.0" folder in the dmg. (Snow)Leopard users can > stick to the builtin enblend/enfuse version. These builtin (Snow)Leopard > versions are 32/64bit openMP builds. > > New users or users switching from 2009.2 and below: If you want to use > autopano-sift-c and/or panomatic yous should download and install the > correct versions (see (2)). The bundle comes pre-configured for > autopano-sift-c and panomatic but without the actual programs due to > patent/license restrictions. > > What has changed: > - Considerable redesign of the XCode project(1). > - I removed the static 64bit enfuse/enblend builds from the "extra" > enfuse/enblend folder in the dmg. The builtin versions are 32/64bit OpenMP > versions and are fine for every purpose. The external standalone versions > are not HDR enabled (still don't know why it will not link against openexr). > - Used the latest panotools from svn instead of the 2.9.17-beta2. All panini > projections now work (As a matter of fact: I tested all projections and all > work, at least for me). > > If you look at the versioning you might think it is an older version as the > previous bundle mentioned svn-5156 where this version mentions > 4091:bc6fc8081244. This is the new Mercurial "version stamp". We switched > some time ago from svn to Mercurial. > If you download from my site (let me know if you find another ;) ), just > watch the "release" dates. > > (1): At a certain moment I started to add extra tools to the bundle (see the > Hugin Tools folder inside the dmg). I modified the bundle to enable that. > Everything fine. Than I started to release a 32/64bit build. Seemed to be OK > but contained already errors. Than I released a 32/64bit bundle with all > tools in it. That's when the shit hit the fan. The internal XCode copy > function isn't build for making changes inside the project when changing > build architectures from different source folders. A lot of internal library > So, the XCode project has now undergone some big changes. > > (2): Check > <http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin> > for further info about autopano-sift-c and panomatic. > > As always: Information and binaries via my website > <http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>. > > (The binaries themselves are served from hugin.panotools.org who kindly > provide the disk space and bandwidth). > > Harry -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
