[hugin-ptx] Re: Hugin based camera tracker
Hi Helmut I would second (or is it third?) Terry's and Yuv's request. I've long wanted to see 'morph-to-fit' -- meaning a more general mesh based warping engine -- added to Hugin's repertoire. If PTStereo showed the way to that, it would be a very good thing. In fact the 'fast transform' code now in libpano is almost a mesh warper, but restricted to a regularly spaced flat rectangular mesh. It would be great to have a general 3D triangular mesh, with an appropriate coordinate interpolator and perspective projection onto the picture plane, as in OpenGL. Of course some mesh generating functions would be needed too, but far less complex than what is now common in 3D modeling. As you know, my Panini warps images by projecting a mesh using OpenGL. After developing Panini, it has become clear to me that this would an excellent way to prepare images for stitching: very general, and, if implemented on 3D rendering hardware, very fast too. My only hesitation is the low order of pixel interpolation offered by current GPU languages -- but that will probably change as the next generation hardware becomes common, and I suppose it is already possible to get better interpolation with a pixel shader program. Regards, Tom On Jun 3, 6:42 am, "H.Dersch" wrote: > On 3 Jun., 08:47, Oskar Sander wrote: > > > For old-scool Hugin, it may sound far-fetched. But as you may have seen, > > Hugin (with panotools) has evolved into also providing a basic mosaic mode > > wiich includes camera coordinates & attitude in the model. However this > > model is limited in the assumption of a perfectly flat reality. > > > Here, I am sure there is great potential in fusing back your PTstero work, > > it would fit the Hugin mosaic model. The calculated camera positions fit > > directly into the current mosaic mode and the 3D mesh will become the > > "projection plane". > > Using a 3D mesh as projection plane is mathematicaly equivalent to the > morphing feature of old PTStitcher (which never made it into one of > the current clones, neither open source nor commercial). The morph- > points are the corner points of the triangles. > > > In this way it is possible to generate perfect corrected "ortographic" > > mosaics similar arial photography maps! > > As an additional feature, PtStereo (and PTStitcher) support the > orthographic projection. That means one of the source images for the > optimizer might be a map, and the feature points can be marked in this > map. The optimizer then calculates the height data. > > Helmut Dersch -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] custom install package
Hi - first post here in this group. As many of you know it was our pleasure to support the last two Google Summer of Code events. We were given a Special Edition package for distribution to those purchasing our product. We included this free of charge on a CD to customers buying our product. It was actually very cool - had our logo and said "Special Edition - for distribution with a Nodal Ninja only. Unfortunately we were unable to pass many out because our CD duplication machine broke. Well we have a new one now and preparing a new CD. The old package (v 0.7.0.3242SVN-Yuv) no longer installs because it's out of date. Can anyone help in developing a new install package for us? Hugin is very valuable to those that cannot afford to buy other software. Many thanks Bill Bailey -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: Hugin & parallelization
On 5 June 2010 13:40, markku.kol...@iki.fi wrote: > > OpenMP isn't supported in the Express edition of VisualC++, you need > at least the Professional version to use it: > http://msdn.microsoft.com/en-us/library/hs24szh9%28VS.100%29.aspx > This will cause problems for Windows users that want/need to compile > Hugin. > > -- > Markku Kolkka > markku.kol...@iki.fi > I think this is a valid reason not to use OpenMP. On 5 June 2010 14:24, Yuv wrote: > Hugin depends on Enblend which in turn depends on OpenMP, so you would > not be adding an extra dependency. But you don't have to compile enblend yourself. You can compile hugin but use enblend binary downloaded somewhere else. Moreover as Harry pointed out it's not enabled by default. > Bottom line: the decision to use OpenMP or boost::thread should IMHO > be driven purely by performance considerations and not by the free- > ride consideration of MSVC Express vs. Professional. I can do some tests but my guess that the speed difference will be minimal. Computation demands certainly overweights possible overhead in both OpenMP and boost:thread. Thank you all for your opinions! Lukas -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin & parallelization
Harry van der Wolf wrote: > 2010/6/5 Yuv >> On Jun 5, 2:33 am, Lukáš Jirkovský wrote: >> > Thank you. I'm still considering the boost::thread. If it is not too >> > complicated to use boost thread I'll use it because OpenMP adds >> > another dependency. But certainly it's good to know that it's OK to >> > stick with OpenMP. >> Hugin depends on Enblend which in turn depends on OpenMP, so you would >> not be adding an extra dependency. > Not completely true. OpenMP is by default off. You need to add the compiler > flag to compile enblend/enfuse with OpenMP support. > Therefore hugin should also get an extra compiler flag to enable OpenMP or > not (default). enblend/enfuse is a special case. OpenMP conflicts with --enable-image-cache. Enabling OpenMP is a win on multiprocessor systems with (relative to the amount of RAM) non-huge panoramas. If hugin's OpenMP capabilitly does not have this or a similar downside there will be no reason for not enabling it by default. imho. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: Hugin & parallelization
Hi all, 2010/6/5 Yuv > On Jun 5, 2:33 am, Lukáš Jirkovský wrote: > > Thank you. I'm still considering the boost::thread. If it is not too > > complicated to use boost thread I'll use it because OpenMP adds > > another dependency. But certainly it's good to know that it's OK to > > stick with OpenMP. > > Hugin depends on Enblend which in turn depends on OpenMP, so you would > not be adding an extra dependency. > > Not completely true. OpenMP is by default off. You need to add the compiler flag to compile enblend/enfuse with OpenMP support. Therefore hugin should also get an extra compiler flag to enable OpenMP or not (default). > > On Jun 5, 7:40 am, "markku.kol...@iki.fi" > wrote: > > OpenMP isn't supported in the Express edition of VisualC++, you need > > at least the Professional version to use it: > http://msdn.microsoft.com/en-us/library/hs24szh9%28VS.100%29.aspx > > This will cause problems for Windows users that want/need to compile > > Hugin. > > IIRC there were some workarounds posted on the web. If Windows users > really want/need to compile Hugin for their platform, they can afford > to spend money on a Microsoft compiler license like they do on a > Microsoft operating system license. > > Bottom line: the decision to use OpenMP or boost::thread should IMHO > be driven purely by performance considerations and not by the free- > ride consideration of MSVC Express vs. Professional. > > Yuv > > Like mentioned above: Hugin should get an extra compiler flag to enable OpenMP or not (default). Despite my reservations here to make OpenMP default for Hugin, I would really like to see more parallellization in Hugin. Please continue on this path. Hoi, 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin & parallelization
On Jun 5, 2:33 am, Lukáš Jirkovský wrote: > Thank you. I'm still considering the boost::thread. If it is not too > complicated to use boost thread I'll use it because OpenMP adds > another dependency. But certainly it's good to know that it's OK to > stick with OpenMP. Hugin depends on Enblend which in turn depends on OpenMP, so you would not be adding an extra dependency. On Jun 5, 7:40 am, "markku.kol...@iki.fi" wrote: > OpenMP isn't supported in the Express edition of VisualC++, you need > at least the Professional version to use > it:http://msdn.microsoft.com/en-us/library/hs24szh9%28VS.100%29.aspx > This will cause problems for Windows users that want/need to compile > Hugin. IIRC there were some workarounds posted on the web. If Windows users really want/need to compile Hugin for their platform, they can afford to spend money on a Microsoft compiler license like they do on a Microsoft operating system license. Bottom line: the decision to use OpenMP or boost::thread should IMHO be driven purely by performance considerations and not by the free- ride consideration of MSVC Express vs. Professional. Yuv -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Blending-fusing problem when saving as JPG
On Jun 5, 2:40 am, Lukáš Jirkovský wrote: > It certainly shouldn't happen only because of change of output format. what ICC profiles are in the input files? Chris recently fixed some of the confusion / bugs around the color space used for blending. Yuv -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin & parallelization
On 5 kesä, 09:33, Lukáš Jirkovský wrote: > Thank you. I'm still considering the boost::thread. If it is not too > complicated to use boost thread I'll use it because OpenMP adds > another dependency. But certainly it's good to know that it's OK to > stick with OpenMP. OpenMP isn't supported in the Express edition of VisualC++, you need at least the Professional version to use it: http://msdn.microsoft.com/en-us/library/hs24szh9%28VS.100%29.aspx This will cause problems for Windows users that want/need to compile Hugin. -- Markku Kolkka markku.kol...@iki.fi -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
