On Thu, 20 Oct 2011 22:09:15 +0100, Bruno Postle wrote: > Can you add this to the launchpad tracker as a feature request? It > would also make a good 'patch' for a Summer of Code application so > can you also 'tag' it with 'gsoc'.
Two other related control point features I'd like to see, which could probably be implemented as a single feature: 1) I'd like to have the option to see all control points on an image (not just between a pair of images) in the control point tab, not just the preview. One way this might work would be for the second image to be the image containing the currently selected control point (or the first selected control point). 2) I'd like a more convenient way to delete all control points in a region in an image, with a choice of just deleting all points in that region between a pair of images or all control points. The current method requires me to create a mask in the mask tab, then go back to the control point tab, delete all control points in the region (which I can't see, much less edit, in the control point tab), and then go back to the mask tab and remove the mask. The use case I have for this is that I frequently take hand-held landscape panoramas where the foreground is not in alignment (and even with a tripod, without a pano head that can put the nodal point over the axis of rotation, this problem still exists). After adding control points, I have to laboriously remove the foreground points, image pair by image pair. Often cpfind puts so many points in the foreground that the worst error is in the background points -- the ones that I know are good. So I can't simply remove outliers at that point. What I have to do is go to each image pair in turn and go through each point, deleting the ones I don't want. Once I get rid of enough of the foreground points, the remaining ones become the outliers, and then things move much more quickly. Unless there's a particularly strong texture in the foreground (like a crack in the rock), these panoramas usually stitch very well, despite very large error in the foreground. So there's no point in having any points at all in the foreground. I could use a mask on each image in turn, but that's not a lot less tedious. > On Thu 20-Oct-2011 at 10:56 -0700, Brent wrote: >>When working with complex panoramas, it's always tricky to figure out >>what control points exist between pairs of images, particularly when >>there are some in regions that are undesirable (such as around a >>moving object, or one close to the camera with parallax). The fast >>preview window's control point display is a great help, but would be >>even better with one small change. When hovering over an image >>number, it currently highlights the image area and blanks the display >>of any control points that are in that area. Better would be if it >>blanked display of all control points, except ones that occur in the >>highlighted image. That way, we could quickly see what control points >>a particular image has. -- Robert Krawitz <[email protected]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton -- 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
