Re: [hugin-ptx] idea for CP deletion
Bruno, If i'm not mistaken, the -p in cpclean only optimizes each pair of images according to the standard deviation you specify - if you are still at risk of removing all CP's between images, right? -- 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] Michel Thoby projection for the Nikkor 10.5
A look at the wiki and I see the new projections have not been added. where, exactly? :) maybe i'm looking in the wrong place... -- 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] Michel Thoby projection for the Nikkor 10.5
I haven't committed the code, since it requires more changes than just the projection functions. Expect that soon. There will be a new projection, called the Thoby projection, with two optional parameters (the two coefficients that default to the Nikkor). The Nkkor is not truly orthographic, but that projection will remain untouched, for compatibility purposes. --dmg On Tue, Jan 4, 2011 at 10:13 AM, Jeffrey Martin 360cit...@gmail.com wrote: A look at the wiki and I see the new projections have not been added. where, exactly? :) maybe i'm looking in the wrong place... -- 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 -- --dmg --- Daniel M. German http://turingmachine.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
Re: [hugin-ptx] Re: Product Vision (was:An idea to expand HDR)
I also think this is a very good idea. FWIW, in terms of Hugin UI/UX, I think it is mostly already good enough. But, and it is a big but, there are a bunch of little annoying things that make the process sort of non-intuitive. Where is the best place for me to report such stuff? Jeffrey Re: [hugin-ptx] Re: Product Vision (was:An idea to expand HDR) Other recipients: On Fri, Dec 31, 2010 at 05:20:22PM +, Bruno Postle wrote: I think there is a case for having an expert mode, or rather having a central place where XYZ mosaic and HDR/bracketing/fusion is enabled per project. The confusion where the assistant is placed by the GUI at the same level as the the other tabs has been noted before. A solution suggested by Pablo would be to move the assistant to the preview window, make the preview the 'main' application window and make the everything else secondary - to the extent that only the preview is visible during a normal workflow. This approach is now practical since we got background loading of photos, the question is, do we want it? I think this is very good idea. It makes the application more widely usable for a wider audience, while at the same time allowing deeper access for the more advanced users. It fits in my vision for Hugin, so I'm all for it. But does it fit in yours? -- 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: Product Vision (was:An idea to expand HDR)
We are reaching a point in the discussion where it is appropriate to compare ptgui and autopano pro. ptgui has the hugin-type UI while Autopano Pro has the preview window-type UI. APP is geared better towards people who don't want to understand the technical aspects of stitching. the UI is excellent. Likewise, PTGui is geared towards people who want to understand the technical aspects of stitching. Also, both programs do a very good job of doing a fully automatic stitch. It's when that doesn't work, that the usage of the programs is very different. It would be interesting to offer both types of UI, in my opinion. We already have the technical one, and it only needs small fixes before I'd call it very good. Jeffrey -- 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] ptmender or nona?
They both use the same transformation code (libpano). PTmender is simply a transformation program. It does not do anything else (you need other tools to do other tasks, such as masking, compositing, etc). I consider it to be the testbed for new code that goes into libpano. Nona is more refined and is capable of outputting different formats. PTmender is, I presume, 4-5 times faster than nona. --dmg On Tue, Jan 4, 2011 at 10:14 AM, Jeffrey Martin 360cit...@gmail.com wrote: I was under the impression that Nona is better. Are they equivalent, or is one superior? Or does it depend on what you want to do? thanks, Jeffrey -- 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 -- --dmg --- Daniel M. German http://turingmachine.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
Re: [hugin-ptx] Re: Product Vision (was:An idea to expand HDR)
Yuval, I think you are a crack smoker. ;-) Hugin is a panorama stitcher. It has some options that let you do it in a few different ways. It's not like a bloody office suite!! :-P On Sunday, January 2, 2011 3:37:42 PM UTC+1, Yuv wrote: Hugin is like an Office suite. In an office suite you have a Word Processor, a Spreadsheet, a Presentation, a Database. All in different interfaces. In Hugin you have simple panoramas, HDR panoramas, mosaics, lens calibration, hand held panoramas, etc. All in the same interface. -- 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] Michel Thoby projection for the Nikkor 10.5
On 2011-01-04 2:17 PM, dmg wrote: There will be a new projection, called the Thoby projection, with two optional parameters (the two coefficients that default to the Nikkor). The Nkkor is not truly orthographic, but that projection will remain untouched, for compatibility purposes. --dmg That is even more cool. -- Jim Watters http://photocreations.ca -- 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] ptmender or nona?
If PTMender is 4-5 times faster than Nona, and you use it only for remapping normal images (no stacking, hdr, etc.) then it seems there is no reason to use Nona? -- 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] ptmender or nona?
If you need the speed, and are willing to deal with TIFF output only, then yes. Otherwise still to nona. On Tue, Jan 4, 2011 at 11:21 AM, Jeffrey Martin 360cit...@gmail.com wrote: If PTMender is 4-5 times faster than Nona, and you use it only for remapping normal images (no stacking, hdr, etc.) then it seems there is no reason to use Nona? -- 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 -- --dmg --- Daniel M. German http://turingmachine.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
Re: [hugin-ptx] ptmender or nona?
oh, if I remember correctly, nona does multithreading. But I am not an expert, so I'll let Pablo and those who know nona describe it. On Tue, Jan 4, 2011 at 11:23 AM, dmg d...@uvic.ca wrote: If you need the speed, and are willing to deal with TIFF output only, then yes. Otherwise still to nona. On Tue, Jan 4, 2011 at 11:21 AM, Jeffrey Martin 360cit...@gmail.com wrote: If PTMender is 4-5 times faster than Nona, and you use it only for remapping normal images (no stacking, hdr, etc.) then it seems there is no reason to use Nona? -- 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 -- --dmg --- Daniel M. German http://turingmachine.org -- --dmg --- Daniel M. German http://turingmachine.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: ptmender or nona?
Am 04.01.2011 20:24, schrieb dmg: oh, if I remember correctly, nona does multithreading. But I am not an expert, so I'll let Pablo and those who know nona describe it. Yes, nona is multithreaded. As far as I know, ptmender doesn't perform the photometric (vignetting white balance) corrections as nona does. ciao Pablo -- 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: ptmender or nona?
Yes, nona is multithreaded. As far as I know, ptmender doesn't perform the photometric (vignetting white balance) corrections as nona does. ciao Pablo This is correct. PTmender simply does remapping and nothing else. -- --dmg --- Daniel M. German http://turingmachine.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] How to fill black areas of a panorama?
Hi, I'm now shooting almost only handheld panoramic pictures. One side effect is the lack of precision while shooting pictures. Then, it appears sometime that my pictures are not fully covering the area of the final image. There some parts at the top or the bottom of the image that are fully black and without information. In any case, the approach would go threw the following steps: 1) Fill black areas with other parts of the image 2) Blend the addition from the previous step with the image to produce the final image. I wonder what is the best approach/tools to execute the second step? I did some manual tests with a picture editor (photoshop) but, maybe because of lack of expertire, I didn't succeeded to get an invisible blend. It seems the lastest version of photoshop elements provide a function to fill empty part of an image. As anyone experimented that? I would think that enblend or a similar tool could be used to do the merge automatically? Thanks for your help PH -- 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 coordinate system
Hi Joshua,
Sorry I haven't replied to you earlier. Once my email piles up, it takes
some time for me to go over it.
We basically have two translations. The one implemented by Pablo, and
used by Hugin, and the one implemented by Dev and I, which is not
directly available from Hugin.
I don't think we have this well documented, but let me try to explain
you how it works.
Any photo is mapped to the sphere, from the sphere, it is then remapped
to the corresponding output projection. This imposes a big limitation in
linear panoramas: they are not really linear, they are slices of the
sphere.
In a previous message I listed the order in which the remapping
happens. Remember, it is done backwards (any point of the output
projection is mapped back to each point in the source images.
In the panotools model (also used by Nona and Hugin), the center of a
photo is the center of the world, with X and Y in the usual
direction, and normalized according to their field of view and input
projection with respect to the area it would cover in the sphere.
I really don't know the way the Tr[XYZ] parameters work, but the code is
easy to read, and Pablo can probably answer any questions you have:
plane_transfer_from_camera is the inverse, if I remember correctly.
Some notes:
* mp-distance is a used to normalize the distances in the image (to a
unit sphere).
* the pointer variables are the outputs, and the non-pointers, the
inputs.
/** transfer a point from the master camera through a plane into camera
* at TrX, TrY, TrZ using the plane located at Te0 (yaw), Te1 (pitch)
*/
int plane_transfer_to_camera( double x_dest, double y_dest, double * x_src,
double * y_src, void * params)
{
// params: distance, x1,y1,z1
double plane_coeff[4];
double p1[3];
double p2[3];
double intersection[3];
// compute ray of sight for the current pixel in
// the master panorama camera.
// camera point
p1[0] = p1[1] = p1[2] = 0;
// point on sphere.
cart_erect(x_dest, y_dest, p2[0], mp-distance);
// compute plane description
cart_erect(DEG_TO_RAD(mp-test[0]), -DEG_TO_RAD(mp-test[1]),
plane_coeff[0], 1.0);
// plane_coeff[0..2] is both the normal and a point
// on the plane.
plane_coeff[3] = - plane_coeff[0]*plane_coeff[0]
- plane_coeff[1]*plane_coeff[1]
- plane_coeff[2]*plane_coeff[2];
/*
printf(Plane: y:%f p:%f coefficients: %f %f %f %f, ray direction: %f
%f %f\n,
mp-test[0], mp-test[1], plane_coeff[0], plane_coeff[1],
plane_coeff[2], plane_coeff[3],
p2[0],p2[1],p2[2]);
*/
// perform intersection.
if (!line_plane_intersection(plane_coeff, p1, p2, intersection[0])) {
// printf(No intersection found, %f %f %f\n, p2[0], p2[1],
p2[2]);
return 0;
}
// compute ray leading to the camera.
intersection[0] -= mp-trans[0];
intersection[1] -= mp-trans[1];
intersection[2] -= mp-trans[2];
// transform into erect
erect_cart(intersection[0], x_src, y_src, mp-distance);
/*
printf(pano-plane-cam(%.1f, %.1f, %.1f, y:%1f,p:%1f): %8.5f %8.5f -
%8.5f %8.5f %8.5f - %8.5f %8.5f\n,
mp-trans[0], mp-trans[1], mp-trans[2], mp-test[0],
mp-test[1],
x_dest, y_dest,
intersection[0], intersection[1], intersection[2],
*x_src, *y_src);
*/
return 1;
}
/** transfer a point from a camera centered at x1,y1,z1 into the camera at
x2,y2,z2 */
int plane_transfer_from_camera( double x_dest, double y_dest, double * x_src,
double * y_src, void * params)
{
double phi, theta;
double plane_coeff[4];
double p1[3];
double p2[3];
double intersection[3];
// params: MakeParams
// compute ray of sight for the current pixel in
// the master panorama camera.
// camera point
p1[0] = mp-trans[0];
p1[1] = mp-trans[1];
p1[2] = mp-trans[2];
// point on sphere (direction vector in camera coordinates)
cart_erect(x_dest, y_dest, p2[0], mp-distance);
// add camera position to get point on ray
p2[0] += p1[0];
p2[1] += p1[1];
p2[2] += p1[2];
// compute plane description
cart_erect(DEG_TO_RAD(mp-test[0]), -DEG_TO_RAD(mp-test[1]),
plane_coeff[0], 1.0);
// plane_coeff[0..2] is both the normal and a point
// on the plane.
plane_coeff[3] = - plane_coeff[0]*plane_coeff[0]
- plane_coeff[1]*plane_coeff[1]
- plane_coeff[2]*plane_coeff[2];
/*
printf(Plane: y:%f p:%f coefficients: %f %f %f %f, ray direction: %f
%f %f\n,
[hugin-ptx] Re: help with Control Point Detector Programs settings
Ok I figured out what's going on. I did a test with less images and it worked perfectly. So then I went back to the pano I was working on and started removing images thinking maybe it was too many in the row. I had one stack that it couldn't find any CPs, as soon as I removed that stack then it ran step 4 from the wiki. It looks like the code exits out if not all the images are connected to at least one other image. It would seem better to just go ahead and try to do step 3 (alignment for determining overlap) and running step 4 (CP finder between overlapping imges) even when there is an image or stack that can't be paired with another image. -- 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] How to fill black areas of a panorama?
On Tue 04-Jan-2011 at 13:17 -0800, panhobby wrote: I'm now shooting almost only handheld panoramic pictures. One side effect is the lack of precision while shooting pictures. Then, it appears sometime that my pictures are not fully covering the area of the final image. There some parts at the top or the bottom of the image that are fully black and without information. 1) Fill black areas with other parts of the image Yes, this is how I patch missing areas of sky and ground, you can do it all in Hugin. So for a hole in the sky I would select a photo that is already in the project with a lot of sky and add this again to the project (you can have the same photo in one project multiple times), but use the Crop or Mask tab to remove everything but the sky from this image. Drag it around in the Preview until it covers the hole, but before you stitch set the enblend parameters to '-l 29'. This panorama has the sun (actually my hand shading the sun) and my shadow removed using this technique, there has been no post-processing or retouching: http://www.flickr.com/photos/36383...@n00/5321872706/ ..this ought to be a tutorial :-( -- 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] idea for CP deletion
On Tue 04-Jan-2011 at 09:57 -0800, Jeffrey Martin wrote: i don't see a -p option for cpclean here http://wiki.panotools.org/Cpclean where is this documented? The wiki pages can be just a general description. Usually the definitive guide to any of these tools is given on the command-line, e.g: $ cpclean -h cpclean: remove wrong control points by statistic method cpclean version 2010.4.0.a26eaba2eda3 Usage: cpclean [options] input.pto CPClean uses statistical methods to remove wrong control points Step 1 optimises all images pairs, calculates for each pair mean and standard deviation and removes all control points with error bigger than mean+n*sigma Step 2 optimises the whole panorama, calculates mean and standard deviation for all control points and removes all control points with error bigger than mean+n*sigma Options: -o file.pto Output Hugin PTO file. Default: 'filename_clean.pto'. -n num distance factor for checking (default: 2) -p do only pairwise optimisation (skip step 2) -w do optimise whole panorama (skip step 1) -h shows help This is definitive because this is the bit written by the programmer. If there is more relevant but technical info then it could also be in a man page or on the wiki (or both sometimes). -- 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] idea for CP deletion
On Tue 04-Jan-2011 at 10:06 -0800, Jeffrey Martin wrote: If i'm not mistaken, the -p in cpclean only optimizes each pair of images according to the standard deviation you specify - if you are still at risk of removing all CP's between images, right? No it should only remove some of the points with an error-distance greater than the average, you will always have some points left. -- 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: Product Vision (was:An idea to expand HDR)
On Tue 04-Jan-2011 at 10:30 -0800, Jeffrey Martin wrote: But, and it is a big but, there are a bunch of little annoying things that make the process sort of non-intuitive. Where is the best place for me to report such stuff? https://bugs.launchpad.net/hugin The more specific the report the more likely it gets fixed, e.g something like this would be good: EXIF display shows Aperture and Shutter Speed but not ISO. -- 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] How to fill black areas of a panorama?
On 4 January 2011 22:17, panhobby panho...@gmail.com wrote: Hi, I'm now shooting almost only handheld panoramic pictures. One side effect is the lack of precision while shooting pictures. Then, it appears sometime that my pictures are not fully covering the area of the final image. There some parts at the top or the bottom of the image that are fully black and without information. In any case, the approach would go threw the following steps: 1) Fill black areas with other parts of the image 2) Blend the addition from the previous step with the image to produce the final image. I wonder what is the best approach/tools to execute the second step? I did some manual tests with a picture editor (photoshop) but, maybe because of lack of expertire, I didn't succeeded to get an invisible blend. It seems the lastest version of photoshop elements provide a function to fill empty part of an image. As anyone experimented that? I would think that enblend or a similar tool could be used to do the merge automatically? Thanks for your help PH http://liquidrescale.wikidot.com/ does a rather good job at filling smaller areas with missing data. -- 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
