[hugin-ptx] Re: getting strange blending errors for a very wide panorama
It is an enblend problem. In the past week we tested a lot of enblend versions starting with the svn3176 version (which is an enblend "3.1" version) from my website. This svn3176 version is actually an incorrect name as it was a load of hugin tools and enblend/enfuse at the time of Hugin svn3176. Kunlun121 tested, I made enblend builds. The "3.1" version is the only one not having this issue. All 3.2 and newer versions (both from Andrew Mihal and from Christoph Spiel) have this same issue and apparently on multiple OSes. Kunlun121already filed a bug on enblend.sourceforge.net. I will expand the bug report. Another observation is that older enblend use/calculate the number of seams "equal" to the number of images. Newer versions create/calculate lots of seams. This might actually be the problem: that lots and lots of "false" seams are created, resulting in these weird seams in the final result. Harry 2009/5/27 Bruno Postle > > On Sat 23-May-2009 at 02:51 -0700, Kunlun121 wrote: > > > >However, I believe the cause is with Hugin, not enblend. I have > >stitched and blended the exact same panorama many times before (even > >over the years) with both PTGui and Hugin, always using different > >versions of Enblend to create the final result and this never > >happened. > > The way to tell if it is a hugin or enblend problem is to enable > Remapped images in the Stitcher tab. If the remapped images don't > display the problem then it is a bug in the enblend you are using. > > -- > 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: hugin-0.8.0_rc1 released
On Sat 09-May-2009 at 02:11 +0200, Guido Kohlmeyer wrote: > >> * In constructor GLPreviewFrame glewInit() fails on my machine (return >> code is 1), but the call to glewInit() in GLViewer::GLViewer returns >> Ok. > >Right, I guess the missing OpenGL context is a problem. The GLViewer >seems to have a context and glewInit() will work properly. I have to >analyse it ... I had a second machine where hugin segfaulted at startup as reported by others. It seems that glewInit() can only be called once depending on how glew is built: http://glew.sourceforge.net/advanced.html So I removed the call to glewInit() in GLPreviewFrame.cpp and it seems to work ok. I've committed this, though probably there is a better solution. In particular I still don't have 'difference mode' available in the fast preview, even though this did work about a month ago. Both machines have no hardware acceleration, so the difference mode worked fine with Mesa software rendering, but now it is disabled. -- 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: Fusing before or after
On 26 May, 11:23, paul womack wrote: [SNIP] > IF the bracketed shots were taken using a (good) tripod, > the images can be fused prior to stitching. > > However, this makes subsequent use of exposure optimisation > in hugin "questionable", since the numerical basis of the optimisation > is destroyed by the (clever and generally desirable) things enfuse does. > > The other possibility is that fusing is on a PER shot basis, and may > create edge conditions between successive shots in the panorama > that might cause difficulties for enblend. > > However, post-fusing requires the shots to be aligned. > One way round this is to create a hugin project of the > "middle" exposure in the bracket set, and then use this > as a template for the more extreme exposures. This avoids > the difficulties of placing control points on the extreme > exposures at the ends of the bracketing. This only works > for tripod-taken sets. I'm getting some weird results when using enfuse directly in Hugin: http://cnqo.phys.strath.ac.uk/~daniel/Photos/Examples/Pre-fused.jpg I've followed the tutorial given at http://hugin.sourceforge.net/tutorials/enfuse-360/en.shtml, except for manually aligning the three stacks. I aligned the middle exposures as normal, then each bracketed shot with the middle exposure shot. I tried without and with photometric optimisation but got weird results both times. In comparison, I stitched and blended each exposure layer, then enfused the three pannoramas and got this much better result, http://cnqo.phys.strath.ac.uk/~daniel/Photos/Examples/Post-fused.jpg. Source images were taken on tripod, -2EV, 0EV and +2EV exposure at each position (6+1+1). Cheers, Daniel. --~--~-~--~~~---~--~~ 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: problems with seams
I played around with my setup and found that 10 horizontal, 6 at +50, 6 at -50, zenith and nadir will also cover the sphere comfortably. Going to +60 you might be able to eliminate the zenith giving you 22 shots without nadir or 23 with. Cheers, Daniel. --~--~-~--~~~---~--~~ 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: getting strange blending errors for a very wide panorama
On Sat 23-May-2009 at 02:51 -0700, Kunlun121 wrote: > >However, I believe the cause is with Hugin, not enblend. I have >stitched and blended the exact same panorama many times before (even >over the years) with both PTGui and Hugin, always using different >versions of Enblend to create the final result and this never >happened. The way to tell if it is a hugin or enblend problem is to enable Remapped images in the Stitcher tab. If the remapped images don't display the problem then it is a bug in the enblend you are using. -- 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: Fusing before or after
On Tue 26-May-2009 at 22:54 +0200, Benjamin Schnieders wrote: > >but everything align_image_stack can give me is a complete .hdr, (which >is, as far as i know, bad input to enfuse) a set of remapped images >(which i don't need as i want to remap them later, aligned in total) or >a pto file that holds information about the image offsets. > >seems that the latest is just what i need, but then, is there a method >of merging these pto files together in a way that the images will "stick >together"? Yes, you could use ptomerge (from Panotools::Script) to join all the projects created by align_image_stack with a project created by autopano-sift-c or panomatic. >to get proper results, atm i only see one solution: > >- take the brightest set of images, generate control points, align them >- starting from the brightest image, use align_image_stack to align each >whole stack to a .pto file >- manually add up the translations calculated by align_image_stack to >all further images and insert them into the big .pto from the beginning This is exactly what the match-n-shift --stacks option does (also from Panotools::Script). i.e. something like this in the hugin preferences should do what you want: AutopanoExe=match-n-shift Args=-b -a -f %f -v %v -c -p %p -o %o %i -- 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: Panotools::Script 0.22 released
On Tue 26-May-2009 at 16:47 +0200, Oskar Sander wrote: > >regsrv32 c:\xx\perl58.dll > >But get the error "perl58.dll was loaded but the DllRegisterServer entry >point was not found." I don't know enough about Windows to know what regsrv32 does. I expected that you would just copy all the files from the archive into the Program Files\hugin\bin folder. Though apparently all the .exe files included version 0.13 of the library instead of 0.22 (oops), I've now updated the archive: >>> https://sourceforge.net/project/showfiles.php?group_id=96188&package_id=293927 -- 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: Fusing before or after
Hi Benjamin, I deal with enfuse and bracketed sets with a patch I wrote: http://ultrawide.wordpress.com/2008/11/16/hacking-hugin-part-1/ I load the first set of images, generate control points and align, then send the pano to batch. Then on the images panel, click 'bracket up' to switch to the next bracketed set, but keeping the control points/alignment from the first bracket set (this solves the problem when the set is too bright/dark to find CPs). Save and send to batch, then repeat for remaining bracketed sets. At the end, all the panos should have been warped in the same way. Then I enfuse them from the command line. Cheers, Tim Benjamin Schnieders wrote: > hi all, > actually i'm having a problem with exactly that question right now. > > > i have a series of image stacks i'd like to stitch and fuse, so stack1_0 > .. stack 1_6 until stack7_6. the thing is, the images are pretty dark, > so automatic control point generation does a very bad job using all the > images. align_image_stack however manages to align my stacks pretty well > (they are shot with a bad tripod, so a little alignment is needed) > > but everything align_image_stack can give me is a complete .hdr, (which > is, as far as i know, bad input to enfuse) a set of remapped images > (which i don't need as i want to remap them later, aligned in total) or > a pto file that holds information about the image offsets. > > seems that the latest is just what i need, but then, is there a method > of merging these pto files together in a way that the images will "stick > together"? > > to get proper results, atm i only see one solution: > > - take the brightest set of images, generate control points, align them > - starting from the brightest image, use align_image_stack to align each > whole stack to a .pto file > - manually add up the translations calculated by align_image_stack to > all further images and insert them into the big .pto from the beginning > - run enfuse and enblend. > > definitely not the best way. are there scripts oder other tricks that > will help? > > thanks, > Benjamin > > > > --~--~-~--~~~---~--~~ 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] Fusing before or after
hi all, actually i'm having a problem with exactly that question right now. i have a series of image stacks i'd like to stitch and fuse, so stack1_0 .. stack 1_6 until stack7_6. the thing is, the images are pretty dark, so automatic control point generation does a very bad job using all the images. align_image_stack however manages to align my stacks pretty well (they are shot with a bad tripod, so a little alignment is needed) but everything align_image_stack can give me is a complete .hdr, (which is, as far as i know, bad input to enfuse) a set of remapped images (which i don't need as i want to remap them later, aligned in total) or a pto file that holds information about the image offsets. seems that the latest is just what i need, but then, is there a method of merging these pto files together in a way that the images will "stick together"? to get proper results, atm i only see one solution: - take the brightest set of images, generate control points, align them - starting from the brightest image, use align_image_stack to align each whole stack to a .pto file - manually add up the translations calculated by align_image_stack to all further images and insert them into the big .pto from the beginning - run enfuse and enblend. definitely not the best way. are there scripts oder other tricks that will help? thanks, Benjamin --~--~-~--~~~---~--~~ 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 installer for Windows Vista SVN 3884
Hi, A new hugin installer for Windows Vista/XP based on SVN 3884 can be found at http://hugin.huikeshoven.org/. A dedicated site has been set up for these posting using a dedicated domain using Google Apps. However, the link for the file will point to a pbworks.com domain, where .exe files can be hosted, and where no 10MB file maximum attachment limit exists. I posted a short blog entry as well on http://ad.huikeshoven.org/ . ad AT huikeshoven DOT org --~--~-~--~~~---~--~~ 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: GSoC development blogs
> So here's my blog (it may be slow, I thing they limits trafic outside > of Czech Republic): Unfortunately it's so slow that my browser decided to stop loading. It would probably help a lot if you host the images elsewhere. You could also resort to a free service like Blogger/Blogspot and just link that inside your website to keep everything together. As a bonus, you'll get Atom/RSS feeds for free ;) Best, Bart --~--~-~--~~~---~--~~ 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: problems with seams
thanks a _lot_ to all that have replied. i have done a full blown run with 'perfect' results. the only change from my previous attempts is optimizing for 'v'. next step is to tune the number of shots i need to take and to start working with aeb shots. thanks! --~--~-~--~~~---~--~~ 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: problems with seams
> i have noticed that i can exclude about half the shots when p=+60 and > p=-60, however I haven't tried not including them for initial control > point creation yet. I use a 17mm rectilinear on a 1.5 crop camera which gives a slightly smaller HoV as your set-up. I find that 10 shots at 0 degrees pitch, 8 shots at +50, 8 shots at -50, zenith and nadir works quit well. I usually align and optimise the horizontal row first together with vertical control pairs. After they've been optimised, I add the upper and lower rows and optimise these. Finally I add the zenith and nadir. I do my optimisation in stages. Sometimes, assigning different lenses (different optimisation parameters) to the nadir and zenith helps match up with the other images. Cheers, Daniel. --~--~-~--~~~---~--~~ 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: problems with seams
initial results are great. i tried optimizing with 'v' and the sample set of 12 images in my example above is stitched perfectly. i am now stitching the full set of 60 images to see how it turns out. if there are seams i will try your suggestions carl. i'm going to try your suggestion of taking fewer shots, no horizon shots but rather tilted up and down. unfortunately, the furtherest i can tilt the camera up is about 70 degrees (due to the physical size of the lens), luckily 60 degrees is enough to get the zenith. i have noticed that i can exclude about half the shots when p=+60 and p=-60, however I haven't tried not including them for initial control point creation yet. thanks a lot for the help/advice! On May 26, 2:00 am, Carl von Einem wrote: > Hi, > > >> On Mon, May 25, 2009 at 8:22 PM, slaterson wrote: > > >>> i was optimizing for the y, p & r. i have a, b & c parameters for my > >>> lens, so i wasn't optimizing for them. i will try this again, > >>> optimizing for 'v' as well. > > Make sure you have some vertical CPs in several areas of the room. I'd > try to optimize the horizontal row first and deselect all others. Maybe > in your case I would try to first of all only generate CPs for those > images that were shot with p=0. Only select those in the lens tab and > click the 'generate control points' button. As a first step I mostly > only optimize for y and v, after that I add p, then also r. From time to > time have a look at the CP table to identify bad CPs. Have a look at the > preview to see if some bad CPs lead to freaky results (you could always > reset the miscalculated values in the lens tab if something very strange > happens). As soon as your first row is sort of stable, add the other > frames one row after the other... > > While checking for bad CPs I often enough see areas that are worth > adding some CPs manually. > > Even if you have once calculated a, b and c for your lens: do it again > for this project. I mostly deselect y, p and r and then optimize first v > and b, after that a and c. Next, optimize also for shift (d and e, but > not together). Now again optimize for y and v, after that add p, then > also r. > > It's not really a simplified 'point and shoot' technique but it works > for me. > > >>> i'm using a canon > >>> 5d body, at 24mm, the hfov is 53 degrees, so i think i am ok with > >>> overlap. i initially tried taking shots at 20 degree steps, however > > 9 or 10 images in the center row should be enough to get a 25 to 30 % > overlap. This should suffice for rooms unless they consist of mostly > huge white walls. The upper and lower rows will surely need less frames, > just simulate that in hugin with dummy images (with a frame so you can > see the ca. amount of overlap in the preview). > > Just another idea: try a different matrix of shots that have two rows at > the horizon: one tilted up about 25-30 deg., the other tilted down the > same amount. That way you might need about 4 rows the full sphere: > 9x p=30 deg. > 9x p=-30 deg. > 6x p=80 deg. > 6x p=-80 deg. > -> it should work with just 30 images :-) > > Carl --~--~-~--~~~---~--~~ 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: Panotools::Script 0.22 released
I am rusty, I don't manage to run the scripts. I'll try to register the perl dll: regsrv32 c:\xx\perl58.dll But get the error "perl58.dll was loaded but the DllRegisterServer entry point was not found." What am I doing wrong? Cheers O 2009/5/25 Oskar Sander > Ta, > > I will try and report back. > > Cheers > /O > > 2009/5/25 Bruno Postle > > >> On Mon 25-May-2009 at 16:00 +0200, Oskar Sander wrote: >> >If anyone here has compiled these for Windows XP already (or is about >> to), I >> >would be really thankfull for a download link! >> >> There is a zip archive with .exe versions of the command-line tools >> in the sourceforge download area: >> >> >> https://sourceforge.net/project/showfiles.php?group_id=96188&package_id=293927 >> >> These are completely untested, it would be intereting to find out if >> they work. >> >> -- >> Bruno >> >> >> >> > > > -- > /O > -- /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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: GSoC development blogs
Hey Lukáš > I thing it would be nice to have some thread where everyone who works > for hugin in GSoC post his/her development blog so everyone could stay > informed about progress of project. I think that's a great idea, then it would even be possible to generate some kind of "planet", where all dev-blogs are linked together (something like the miro-people do on http://planet.getmiro.com/). [snip] > So here's my blog (it may be slow, I thing they limits trafic outside > of Czech Republic): Slowness woulnd't be an issue for me, 'cause I prefer to read blogs via my newsreader. But this is not possible with your blog, since there is no RSS-feed which i could subscribe to. Could you provide one, or if not, "switch" to a blogging system that does? cheers habi (who just returned from holidays and is gonna test the newest builds of hugin with some fresh panoramas soon :) --~--~-~--~~~---~--~~ 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: Fusing before or after
DaveN wrote: > I don't know if this has been asked before (hard question to ask in a > search) but why don't people fuse their images before making > panoramas? By that I mean the software for making panoramas (the > hugin clone ptgui and autopano pro) seem to remap all the images to > create differently exposed panoramas and then blend the panoramas. > Wouldn't it be more efficient to exposure fuse the images and then > make the panorama? There are a number of pros and cons. IF the bracketed shots were taken using a (good) tripod, the images can be fused prior to stitching. However, this makes subsequent use of exposure optimisation in hugin "questionable", since the numerical basis of the optimisation is destroyed by the (clever and generally desirable) things enfuse does. The other possibility is that fusing is on a PER shot basis, and may create edge conditions between successive shots in the panorama that might cause difficulties for enblend. However, post-fusing requires the shots to be aligned. One way round this is to create a hugin project of the "middle" exposure in the bracket set, and then use this as a template for the more extreme exposures. This avoids the difficulties of placing control points on the extreme exposures at the ends of the bracketing. This only works for tripod-taken sets. Finally, pre fusing IS computationally efficient; if you repeatedly "tweak" your panorama project, having all the fusing done as a pre-stage is clearly efficient. Further, fusing a bracketed set of stitched panoramas is a massively RAM intensive activity, whereas fusing the shots separately might well fit in RAM. BugBear (pre fuser, on balance) --~--~-~--~~~---~--~~ 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: problems with seams
Hi, >> On Mon, May 25, 2009 at 8:22 PM, slaterson wrote: >> >>> i was optimizing for the y, p & r. i have a, b & c parameters for my >>> lens, so i wasn't optimizing for them. i will try this again, >>> optimizing for 'v' as well. Make sure you have some vertical CPs in several areas of the room. I'd try to optimize the horizontal row first and deselect all others. Maybe in your case I would try to first of all only generate CPs for those images that were shot with p=0. Only select those in the lens tab and click the 'generate control points' button. As a first step I mostly only optimize for y and v, after that I add p, then also r. From time to time have a look at the CP table to identify bad CPs. Have a look at the preview to see if some bad CPs lead to freaky results (you could always reset the miscalculated values in the lens tab if something very strange happens). As soon as your first row is sort of stable, add the other frames one row after the other... While checking for bad CPs I often enough see areas that are worth adding some CPs manually. Even if you have once calculated a, b and c for your lens: do it again for this project. I mostly deselect y, p and r and then optimize first v and b, after that a and c. Next, optimize also for shift (d and e, but not together). Now again optimize for y and v, after that add p, then also r. It's not really a simplified 'point and shoot' technique but it works for me. >>> i'm using a canon >>> 5d body, at 24mm, the hfov is 53 degrees, so i think i am ok with >>> overlap. i initially tried taking shots at 20 degree steps, however 9 or 10 images in the center row should be enough to get a 25 to 30 % overlap. This should suffice for rooms unless they consist of mostly huge white walls. The upper and lower rows will surely need less frames, just simulate that in hugin with dummy images (with a frame so you can see the ca. amount of overlap in the preview). Just another idea: try a different matrix of shots that have two rows at the horizon: one tilted up about 25-30 deg., the other tilted down the same amount. That way you might need about 4 rows the full sphere: 9x p=30 deg. 9x p=-30 deg. 6x p=80 deg. 6x p=-80 deg. -> it should work with just 30 images :-) Carl --~--~-~--~~~---~--~~ 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] GSoC development blogs
Hello everyone, I thing it would be nice to have some thread where everyone who works for hugin in GSoC post his/her development blog so everyone could stay informed about progress of project. There was similar thread in GSoC students mailing list, but I'm not sure if it's open to public and moreover there were plenty of people so finding the ones which work on hugin would be fairly difficult. So here's my blog (it may be slow, I thing they limits trafic outside of Czech Republic): http://stativ.kx.cz/src/index.php?menu_id=5 Lukáš "stativ" Jirkovský --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
