[hugin-ptx] Re: Why not ask for directions?
Bruno OK, now I see the (multirow/stacked) CP option. I tried it out on an 8-shot fisheye spherical pano. It ran pretty slow (mainly because of the poor k-d tree implementation in autopano), could not place the zenith and nadir shots, and aligned the others badly, but with the right arrangement. The default alignment using APSCpp was a little faster and produced a fully connected but even worse aligned pano. PTGui generated a perfectly aligned pano in about 1/5 the time of either Hugin method. So we still have a way to go. Perhaps it is not fair to test a 'multirow' algorithm on an image set with one 'row' and two 'caps'. But a practical 'grid' method ought to handle spherical arrangements as well. Cheers, Tom Is this implemented within hugin or as an external command or script? Regards, Tom On Jun 10, 5:58 pm, Bruno Postle wrote: > On Thu 10-Jun-2010 at 13:35 -0700, Tom Sharpless wrote: > > > > >This 'multirow' option sounds like a big step in the right direction. > >But perhaps it needs better publicity. > > It needs testing and the wiki needs to be updated too. > > >I'm looking at a pretty recent Hugin build ( 2010.1.0.5063 ) and can't > >see anything that looks like a "multirow panorama option". Should I? > > In Preferences -> Control Point Detectors there should be an > 'Autopano-SIFT-C (multirow/stacked)' option, if not then you might > have to 'Load Defaults'. > > This is pre-configured to use generatekeys/autopano as a two-step > detector, and align_image_stack for stacks. You can change it to > autopano-sift-c or panomatic as a one-step detector, but this is > less efficient since features will be classified multiple times. > > You should also be able to change it use a different two-step > detector such as Pablo's libpanomatic (untested). > > How it works is by using various strategies to match just the > subsets of the photos that are extremely likely to overlap, then > merging the resulting projects. It doesn't require any user input, > you get very few 'bad' connections, it scales to any size of > project, and it supports real-world shooting situations: > > - Zig-zagging rows (left-to-right, then right-to-left, etc...). > - Rows with different numbers of photos in each. > - Odd row ordering (middle-row, top-row, then bottom-row etc...). > > The 'prealigned panorama' option is related, but available as a > separate type of control-point generator. > > -- > Bruno -- 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: Why not ask for directions?
Hi Bruno This 'multirow' option sounds like a big step in the right direction. But perhaps it needs better publicity. I'm looking at a pretty recent Hugin build ( 2010.1.0.5063 ) and can't see anything that looks like a "multirow panorama option". Should I? If so, where? Cheers, Tom On Jun 6, 6:01 pm, Bruno Postle wrote: > On Sun 06-Jun-2010 at 14:29 -0700, Yuv wrote: > > > > >yes, the optimizer should look into the template and try to generate > >CPs only for images that are overlapping. If I am not mistaken Bruno > >has a perl tool for this in his PanoTools? > > Also in the current Hugin trunk, but better because Thomas Modes has > added genuine overlap detection that calculates area of overlap. > > You can match a roughly prealigned project, either by starting with > a template or by dragging the photos around in the preview first. > Hugin will then only compare pairs of photos that overlap. > > -- > Bruno -- 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: Why not ask for directions?
On Thu 10-Jun-2010 at 13:35 -0700, Tom Sharpless wrote: This 'multirow' option sounds like a big step in the right direction. But perhaps it needs better publicity. It needs testing and the wiki needs to be updated too. I'm looking at a pretty recent Hugin build ( 2010.1.0.5063 ) and can't see anything that looks like a "multirow panorama option". Should I? In Preferences -> Control Point Detectors there should be an 'Autopano-SIFT-C (multirow/stacked)' option, if not then you might have to 'Load Defaults'. This is pre-configured to use generatekeys/autopano as a two-step detector, and align_image_stack for stacks. You can change it to autopano-sift-c or panomatic as a one-step detector, but this is less efficient since features will be classified multiple times. You should also be able to change it use a different two-step detector such as Pablo's libpanomatic (untested). How it works is by using various strategies to match just the subsets of the photos that are extremely likely to overlap, then merging the resulting projects. It doesn't require any user input, you get very few 'bad' connections, it scales to any size of project, and it supports real-world shooting situations: - Zig-zagging rows (left-to-right, then right-to-left, etc...). - Rows with different numbers of photos in each. - Odd row ordering (middle-row, top-row, then bottom-row etc...). The 'prealigned panorama' option is related, but available as a separate type of control-point generator. -- Bruno -- 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] Hugin source code visualization
Very nice! 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] Hugin source code visualization
Hey all. Now that hugin recently switched to Mercurial for Code revision, I thought I could try something fun with it: Recently I stumblede over gource [1] a nice tool for the visualization of sourcecode. I've used gource to visualize the progress of my PhD-Thesis ([2], which was handed in a week ago btw) and thought I'd do this for hugin. It turned out to be a little bit of a challenge, but let me walk through to the end-result: On OS X it's pretty easy to install all the necessary things to make the resulting movie, just make sure you've installed MacPorts [3] and issue $ sudo port install mercurial ffmpeg gource in Terminal.app to install the necessary stuff. Then drink a coffee, because this takes a long time :) Using a simple $ hg clone http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin hugin in a directory of choice downloads hugin's source code. Again, do this in the Terminal.app. "Cd" into hugins directory and enter the following command: gource -800x600 --disable-progress --stop-at-end --bloom-multiplier 1.25 -a 0.05 --output-ppm-stream - | ffmpeg -y -b 3000K -r 60 -f image2pipe -vcodec ppm -i - -vcodec libx264 -vpre default hugin.mp4 This command instructs gource to make a 800x600 pixel movie with some tweaks, outputs this to a ppm-stream and converts this stream with ffmpeg to a resulting movie, hugin.mp4. Go and have another coffee, since this can take even longer than the command above... After you've marveled at the nearly 3 GB, two-hour (!) long movie (or maybe not :) you wonder how to present this movie. Fiddling around with iMovie [4] in the end you get this: http://vimeo.com/12442226 It's beautiful! My way of saying "Thank you" to all the developers and coders of hugin. You've done a great job, I love to use hugin. Keep it up! Greetings from Switzerland Habi [1]: http://code.google.com/p/gource/ [2]: http://habi.gna.ch/2010/05/14/codevisualisierung-mit-gource-so-arbeitete-ich-an-meiner-diss/ [3]: http://www.macports.org/ [4]: http://www.apple.com/ilife/imovie/. The fiddling with iMovie involved conversion of the movie to alter its speed, since iMovie can only speed up to 2000%, which was not enough to go from +2 hours to 4 minutes in one step. Since I've had a nice song as a background, I had to to multiple exports and imports to speed the movie up to the necessary 4.5 minutes, -- 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 based camera tracker
Helmut, That sounds excellent! We would really appreciate if you would like to open that souce. I hope you find it :-) /O 2010/6/3 H.Dersch > > > 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 > -- /O -- 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
