Re: [hugin-ptx] Re: Translators requested for Hugin 2012.0 release
I'm just working on the last few strings (using the new changeset) and stumbled over Removes all control points, which are in masks. Do we need a comma here, Don't know exactly. Maybe a native speaker can help. Ah, I thought I suggested that in my first round of typos. Yes, the comma should go away. I'm torn whether it should be which or that though, but leaning toward that. Gareth -- 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: Translators requested for Hugin 2012.0 release
Okay, there were no objections. So I committed the fixes. I'm afraid I missed a few minor ones: https://bugs.launchpad.net/hugin/+bug/1034122. I've also tweaked en_GB with a few I missed: https://bugs.launchpad.net/hugin/+bug/1034120. Gareth -- 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: Translators requested for Hugin 2012.0 release
I'll get to work on this over the next couple of days. Okay, en_GB translations are at https://bugs.launchpad.net/hugin/+bug/1032993, and my suggested typos etc. are at https://bugs.launchpad.net/hugin/+bug/1032991. Gareth -- 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: Translators requested for Hugin 2012.0 release
en_GB.po 52 translated messages, 4 fuzzy translations, 1277 untranslated messages. I'll get to work on this over the next couple of days. Not that en_GB is ever a particularly major job... I expect I'll report a few typos or inconsistencies too as usual. Gareth -- 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: 回覆：Re: [hugin-ptx] Failed exposure fusion?
Hi, On 11 July 2011 02:14, EwingKang 可愛滴蜥蜴 f039281...@yahoo.com.tw wrote: So you mean that hugin can't create an exposure fusion image that all of the photo were taken only in one perspective? I regularly use Hugin for just that. It may not be the best tool but it works for me. Some tips: - Use rectilinear for the output projection to keep a rectangular image. - For the geometric alignment (if needed), use the align_image_stack control point detector. Anchor one image completely. Optimize only image positions, not lens distortions. - For the photometic alignment, only optimize response, or nothing at all. Certainly not vignetting or exposure. Gareth -- 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] auto straighten changes yaw by 180 degrees
i'm noticing that the straighten feature will sometimes not change the pitch/roll of the pano, but it will change the yaw by 180º. Is this with a 360deg panorama? I've not noticed it with straighten, but centring often flips the yaw by 180deg with 360deg panoramas. (Yes I have tried to centre a 360, I'm that smart...) Gareth -- 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] Stitching and enfusing a handheld panorama with several exposures
Hi, - first, on my machine (developer preview of Hugin built on Jan 23rd and the control point detection settings you set me) the distance column in the control points table always contains distances (some numbers 1) while, after fine tuning, it is supposed to contain correlation coefficients (should always be 1). After the fine-tuning, the numbers should always be correlation coefficients. Sometimes they are indeed a little 1. (I don't know why, my memory of how such things work mathematically is a bit faded these days!) Pixel distances early on would be much 1 though. How do you select points by correlation in steps 8 and by distance in step 9, since the distance column should only contain one of those two? Can you switch between the two? Pressing select by distance (and using negative threshold values) should just do the right thing after fine-tuning. I don't know of any way of switching between correlation and distance other than to rerun the fine-tuner or optimizer. - you say that you first do a position only optimisation, then remove problematic points and then do further optimisations. These are still position only right? I normally optimize the positions (incremental from anchor); then straighten and centre in the preview; then calculate optimal size in the stitcher tab; then re-optimize the positions; then add view (for 360deg or multiple lenses); then barrel b; then d, e, a and c; and finally X, Y and Z (narrow scenes with no/implicit stacks). I remove obviously wrong points (mismatched features, or 50 pixels) as soon as they become visible in the preview, but I don't start trimming the smaller control point distances due to parallax until the end, repeating the final optimization till I'm happy with it. This is just habit; you can probably go straight from the position optimization to the final optimization without the intermediate runs, and repeat it whilst trimming control points. - it seems the align button in the assistant tab does more than position optimize + photometric optimization. Indeed, If I create the control points, then optimize them in the Optimizer tab and finally do photometric optimization in the exposure tab, the assistant still says Images or control points have changed, new alignment is needed. What is missing? What else does it do? I don't know what else the assistant does, but I assume (hope!) that all its functionality is available in the other tabs. The ...new alignment is needed message appears for me too after photometric optimization, but since I've already aligned everything at that point and I can't see how photometric alignment can alter the geometric alignment, I just regard it as a quirk of the way the assistant tracks changes to the image metadata. Maybe someone else here can enlighten us about that? - when performing photometric optimisation, I need to use HDR, fixed exposure to avoid having hugin correct the under and over exposed images, right? Yes, leave the exposure for Enfuse/hdr_merge to deal with. Thanks in advance for the help. No problem, I just hope it is help - I don't know if my way is the best way... Gareth -- 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] Stitching and enfusing a handheld panorama with several exposures
Hi, Markku Kolkka wrote: Don't use stacks with hand-held images. Hugin believes that images in a stack are pre-aligned perfectly. Explicit stacks do help with some other things though (cpfind+align_images, whole-stack masking etc.) Just remember to uncheck the link checkbox in the images tab for all the stacks (it's in the image orientation section). This allows images to be aligned within a stack, at least in angular space. (There seems to be a bug with XYZ alignment not being properly unlinked even though the optimizer assumes it is, but I haven't investigated that yet to report it, and XYZ isn't an issue for wide panoramas anyway. XYZ does help a little for parallax on flat-ish ground with less than 180deg though, so in that case I unstack the images after creating control points.) My method (working hand-held) is to take the photos with the camera settings basically as you do. Then in Hugin 2010.04: 1) Set up *unlinked* stacks. 2) Mask moving people etc. 3) Temporarily mask out any obviously parallaxed foreground. (Assuming that you prefer the background to be properly aligned.) 4) Run cpfind (multirow/stacked) on all. As far as I can tell this uses align_image_stack within stacks and normal cpfind between stacks. Cpfind seems to be aware of the masks, but align_image_stack isn't - deal with that in step 5. I then remove bad control points: 5) Edit-Remove control points in masks - this eliminates the masked out foreground and moving objects. Remove the temporary foreground masks now. 6) Run Celeste if there are clouds. 7) Clean control points button to remove outliers. 8) Edit-Fine tune, then remove points with 0.8 correlation. 0.9 works well if you only use align_image_stack, but cpfind creates lots of points with lower correlations for me. 9) During optimizing, I remove control points in stages between rerunning the optimizer, based on their mismatch distance (e.g. 10, 5, 2, 1). Sometimes I need to manually add points between stacks. After the initial positions-only optimization and straightening and centring the preview, I use calculate optimal size in the Stitcher tab so that the pixel mismatches are accurate for successive optimization passes. For stages 8 and 9 use View-Control point table to select and remove points with low correlation and high pixel mismatch. Then I mask lens flares etc., do photometric optimization and blending as described. If the foreground looks too bad I crop it out. It's a bit overly complex, but for hand-held panoramas taken in the wind at the top of a mountain, computers just aren't yet clever enough to automate the process fully... I too welcome any suggestions of course, but this method at least is working well for me. Gareth -- 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
