[hugin-ptx] Command line defish/reprojection of single images in bulk
Hi all, I have a series of individual images taken with a 10-20mm lens at various focal lengths. I'd like to "re-project" each image to eliminate the angular distortion, and was wondering if there's a way to do this in bulk from the command line, using the image's EXIF info (focal length/FOV) as input. I'm quite comfortable with doing this through hugin in a point and click manner (as per http://groups.google.com/group/hugin-ptx/msg/913a550ce4443b6b), and have used this to produce a template .pto for a particular focal length/orientation for command line processing of multiple images via nona, but was wondering if there's a way to remap individual images in bulk? I suppose I could try loading them all in one hugin project with multiple sets of lens parameters and remapping to individual files. Any other ideas? Cheers, - Roger -- 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] What is hugin's best fit?
I've seen hugin report "good fit" and "bad fit" after optimization. Is there anything better? Does it ever say, "Excellent fit"? I bought myself a pano head for Christmas, and today I had a chance to play with it and try to calibrate it. I shot a sequence of 2-row x 4- pic panos of the side of my house, moving the camera out the upper rail 3mm at a time. I'm allowing plenty of overlap between shots, easily upwards of 30% of image width/height on all seams. I saw the errors reported by hugin start out large, get smaller and smaller, then start getting big again as I slid the camera out the rail. So then I shot another sequence of panos around the setting with the smallest error, this time moving the camera 1mm per sequence. The best result I got was Mean error = 3.3 and max error = 17.1. There were still some visible problem spots in the image, but I figured, "Eh, automatic CP generation, I could do better by hand." To verify, I brought my setup inside and shot an indoor pano using the best settings I had discovered outdoors. The initial results were very good, on par with what I got outside: mean error = 2.8 and max error = 13.8 using automatic CP generation. But still some visible problems. So now I've spent the last 3 hours tweaking the control points. The image dislocations seem to move around, but not predictably, and are never completely gone. Qualitatively, 4 hours of work playing with positions of CPs, making a few tentative forays into optimizing lens params, etc., hasn't changed the result at all. If I go hunt around the image and count the problems, the number and size of the dislocations are always approximately the same, no matter what I do. Does anyone have any suggestions where to go with this? What kind of error levels are needed to produce a "perfect" result (which I define as not being able to spot any stitching errors in the final pano)? Is this a calibration issue of the pano head? Play in the tripod/head/ pano head setup... would it cause this? If my error rates seem low enough, what could be other causes of my issues? Complex lens distortions not modeled/correctable by hugin? Or does it just take more practice than this, and this is all easily explained by user inexperience (in which case, what are the beginner problems I'm likely overlooking)? Also, along a different line: I'm shooting with an Olympus E-620 and a Zuiko ED 12-60mm lens at 12mm, which is 24mm in 35mm-equivalent terms (2x crop factor). It's a medium-wide lens, and image elements in the corners of the image can be rather rotated from one image to the next. Often I find the largest errors reported for CPs are in the corners of the images. Autopano-sift-c tends to always find CPs towards the center of the images; usually it's my hand-placed CPs that are out in the corners, and which report large errors. I often can't "fine-tune" the points because the fine-tuner often moves one of the two points somewhere else in the image where it finds a better match. Yet the points are visually dead-on when I place them, on well-defined image features. ??? Does that give anyone a clue what I might be experiencing? Thanks for any ideas... -- 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: - How to extract Control Points alone to compare two images?
On 15 February 2010 18:12, Karthik Kamalakannan wrote: > I'm not sure if I was clear in explaining my concept. This is the process > that I need to do. > *Everything must be done in Command Line. > 1. I have an anchor image (Say Image1.jpg). With this image as reference, I > need to compare some images in a folder (Say Image2.jpg, image3.jpg, etc.,). > 2. Once this is done, I need to obtain a result (Saying Image1.jpg - The > anchor image, and ImageN.jpg are most similar). I think this can be done > using Control Points. > I think CP matching is a bit overkill (and a bit useless in cause in autopano etc. for you). You are not guaranteed that CP's are uniformly distributed so you can get false positives because there is one feature (eg. book) which looks similarly in two completely different images. I don't how you define "similarity" here, but for the case similar images has to be of (approximately) the same exposure, I'd try comparing histograms to get an idea which images can be similar (but two completely different images could have same histograms). Then you may try align_image_stack and count the number of found control point pairs. This tool uses different approach and I think it's more suitable for you. But to be honest I think this is more likely to be computer vision problem. You can take a look at tools like OpenCV. Lukas -- 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: Masking inside hugin
This might be obvious to you, I ask nevertheless: What is masking good for? 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: Masking inside hugin
Small error, inserted text on wrong position; it should be: Creating mask polygon: after selecting "add new mask" left mouse buttons sets one point, finish with right mouse button or left double click Selecting point(s): left mouse click on point or use rubberband; when holding shift the new points are added to an existing selection -- 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] Masking inside hugin
Hi, On 16 February 2010 07:34, T. Modes wrote: > > I hope this feature is helpful > > Thomas > It's absolutely awesome. I can't wait to test it. Lukas -- 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] Masking inside hugin
Hi, I implemented a masking tool inside hugin. It's now in the trunk. Now you can create masks inside hugin, the masks are stored in the pto file. It is possible to use negative and positive masking. The masks are applied during stitching with nona. So also enblend can use them. Some hints for usage of the editor: Creating mask polygon: left mouse buttons sets one point, finish with right mouse button or left double click Select mask: left mouse click inside polygon or use rubberband, works only when there are no points selected; or use the listbox Selecting point(s): after selecting "add new mask" left mouse click on point or use rubberband; when holding shift the new points are added to an existing selection Move point(s): drag with left mouse button Move whole mask: drag with right mouse button Adding points: left click while holding ctrl key on a line segment Deleting points: right mouse click while holding ctrl key on a point or drag with right mouse button and pressed ctrl button a rubber band around the points (the remaining polygon must consist of at least three points, otherwise the deleting is canceled), the delete key deletes the selected points Deleting mask: use delete mask button, the mask is also delete with pressing the delete key when all or none point of the current mask are selected I hope this feature is helpful Thomas -- 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: Announcement: Photoropter lens correction library
On 15 Feb., 19:01, Daniel Reetz wrote: > Hi Robert, > How can a non-developer with good knowledge about optics and sensors > contribute? Well, for one I could use some reference material (i.e., a distorted image with corresponding correction parameters), if possible for different distortion models (there exist more models than just PTLens, and I will implement what I can find; however I currently do not know which ones are actually used 'in the wild'). Also vignetting and especially some test material for chromatic aberrations. Other points are: possible concepts of how to store the camera/lens information in a meaningful and flexible way (including corresponding identification heuristics) so that the user still can easily add custom data (and ideally share it), how to deal with e.g. centre shifts on different cameras, how could/should the user interface look like (though Photoropter is only the backend, this quite directly influences the design) etc.; I have been thinking about these points for quite some time, but there's still plenty of room for discussion. Also detailed information on all sorts of colour transformations would be nice (a topic where my technical knowledge still has a few painful gaps), possibly doing some testing, reviewing parts of the technical background documentation for Photoropter as/when it is written etc. But perhaps we should really shift the discussion to photoropter- users, then. Regards, Robert -- 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] autopano-sift-c (trunk) segfaults
On Mon, Feb 15, 2010 at 2:01 PM, Bruno Postle
wrote:
> On 15 February 2010 07:23, Alexandre Duret-Lutz wrote:
>> This is autopano-sift-c from trunk doing segfault.
>
> The autopano-sift-C trunk is known to be broken with the --projection
> parameter.
>
> If you just want it to work then fetch the 2.5.1 tarball and build that.
I patched trunk as attached. My use of --projection seems to work now.
--
Alexandre Duret-Lutz
--
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-ptxdiff --git a/APSCpp/APSCpp.c b/APSCpp/APSCpp.c
index 2416f26..55624ed 100644
--- a/APSCpp/APSCpp.c
+++ b/APSCpp/APSCpp.c
@@ -377,6 +377,11 @@ KeypointXMLList * GenerateKeyspp( char * imgname, int maxdim, DIinfo * pdi,
hfov = globFov;
WriteLine(" width %d height %d", pic->width, pic->height );
} else {
+ // If globFov is non null, its value was specified by
+ // the user on the command line, so use that.
+ if (globFov > 0.0)
+ hfov = globFov;
+ else
hfov = fovdeg( pdi->flpix, pic->width, pdi->format );
WriteLine(" %s width %d height %d hfov %g ",
formatName( pdi->format), pic->width, pic->height, hfov);
[hugin-ptx] hugin Einführung bei Frankfurt am Main gesucht
Hallo, jemand aus der Nähe von Frankfurt am Main hier? Irgendwie kriege ich den Dreh mit Hugin nicht raus. Wer mag mir in einer persönlichen Einführung zeigen wie es geht? Danke, Jan English: Looking for hands-on hugin introduction nearby Frankfurt am Main, Germany. -- http://www.DIY-streetview.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] Announcement: Photoropter lens correction library
On Mon, Feb 15, 2010 at 2:35 AM, Robert wrote: > Hi all, > > in the hope that this might be of interest to some people on this > list, I am posting this announcement on hugin-ptx. Have a look, and > let me know what you think. If you are interested in Photoropter's > development, you are welcome to join the project mailing list at > > https://lists.berlios.de/mailman/listinfo/photoropter-users Hi Robert, How can a non-developer with good knowledge about optics and sensors contribute? Regards, Daniel Reetz -- 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: - How to extract Control Points alone to compare two images?
I'm not sure if I was clear in explaining my concept. This is the process that I need to do. *Everything must be done in Command Line. 1. I have an anchor image (Say Image1.jpg). With this image as reference, I need to compare some images in a folder (Say Image2.jpg, image3.jpg, etc.,). 2. Once this is done, I need to obtain a result (Saying Image1.jpg - The anchor image, and ImageN.jpg are most similar). I think this can be done using Control Points. Please help me with this as soon as possible! :) On Mon, Feb 15, 2010 at 4:13 PM, bruno.postle wrote: > On Feb 15, 8:29 am, "Karthik.K" wrote: > > > I'm new to Hugin and all the tools used. I have been reading and > > researching a lot about all the control point generators. All I need > > to do now is to calculate and extract the Control points (Only the > > control points) and compare The number of control points between two > > images and tell that they are similar or not, using Command Line. > > See this thread where some scripts were posted: > > https://groups.google.com/group/hugin-ptx/browse_thread/thread/318633a917576dec > > -- > 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 -- Regards, Karthik.K Saying of the lifetime: "You don't fail, until you QUIT" -- 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] Output my own PTO file
Excellent, I think that last explanation is what I was missing. Thanks, nick On Sun, Feb 14, 2010 at 4:12 PM, Bruno Postle wrote: > On Sun 14-Feb-2010 at 15:27 -0500, Nicolas Pelletier wrote: > >> >> As in if you have 10 images, but all "lens" parameters are equals in 3 >> distinct groups (i.e. 3 lens) then optimizing v3 e3 d3 will optimize those >> parameters for only the 3rd set of images sharing the same parameters, and >> keep them with the same value once optimized? >> > > Almost, the number always refers to an image number. The lens number > system (and the similar stack number in the trunk) is a higher level > abstraction presented by the Hugin GUI. > The optimiser and stitcher tools don't need it to do their job, they link > parameters between photos at the lower level of the '=3' notation in the > .pto files. > > So b=3 in an i-line means "b-parameter is the same as image 3". b3 in a > v-line tells the optimiser to "optimise b-parameter of image 3" (and > implicitely use the same value for other images that have b=3 in an i-line). > > > -- > 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 > -- 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] autopano-sift-c (trunk) segfaults
On 15 February 2010 07:23, Alexandre Duret-Lutz wrote: > This is autopano-sift-c from trunk doing segfault. The autopano-sift-C trunk is known to be broken with the --projection parameter. If you just want it to work then fetch the 2.5.1 tarball and build that. -- 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: Announcement: Photoropter lens correction library
On 15 Feb., 12:07, Pablo d'Angelo wrote: > Seems to be very similar to lensfun:http://lensfun.berlios.de/ > > I think lensfun is really good, however, it never really got of the > ground nicely (its used by ufraw though), because adding new lenses etc. > is not as straightforward as it could be. I know lensfun, and while the idea of having a PTLens replacement is a good one, I have certain problems with it which prompted me to start a new project after all. Let's just say I strongly disagree with lensfun's design. It's full of C-isms and hard coding, there's nearly no encapsulation, its programming interface is non-existent, and using it means you essentially even have to write the image transformation loop yourself. I do not want to belittle Andrew's efforts, far from it. But lensfun's design just makes using it unnecessary hard-- which is precisely what Photoropter tries to fix. Then there's the build system (apparently trying to fix autotools' flaws by supplementing it with custom python code) which I also find very problematic. > It would be great if the database storage could be kept similar or > easily convertible, so that both projects can feed of the same data. That used to be one goal, yes. But I am not sure this will be sustainable, since the whole idea of separating 'lens' and 'sensor' (i.e., the camera body) data is problematic. Importing and exporting of parameter sets itself is trivial, but one cannot load a set of lens parameters, maybe even determined at a different crop factor and hope to achieve any meaningful results (even if the library can compensate for different crops, as Photoropter and lensfun both can). The only way to reliably correct for image flaws of a given system in a physically 'correct' way is to identify the optical system as a whole (this means sensor _and_ lens). The most one can do really is to regard the lens database as a set of templates. However, at the moment Photoropter is not concerned with the lens database part at all (yet). For a little while, this will remain on the todo list. Regards, Robert -- 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: Announcement: Photoropter lens correction library
Robert wrote: === Announcement: Photoropter lens correction library === Seems to be very similar to lensfun: http://lensfun.berlios.de/ I think lensfun is really good, however, it never really got of the ground nicely (its used by ufraw though), because adding new lenses etc. is not as straightforward as it could be. It would be great if the database storage could be kept similar or easily convertible, so that both projects can feed of the same data. 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: - How to extract Control Points alone to compare two images?
Hi, Thank you for the help! Will definitely have a look at it and get back to you if I have some queries! You guys rock! On Mon, Feb 15, 2010 at 4:13 PM, bruno.postle wrote: > On Feb 15, 8:29 am, "Karthik.K" wrote: > > > I'm new to Hugin and all the tools used. I have been reading and > > researching a lot about all the control point generators. All I need > > to do now is to calculate and extract the Control points (Only the > > control points) and compare The number of control points between two > > images and tell that they are similar or not, using Command Line. > > See this thread where some scripts were posted: > > https://groups.google.com/group/hugin-ptx/browse_thread/thread/318633a917576dec > > -- > 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 -- Regards, Karthik.K Saying of the lifetime: "You don't fail, until you QUIT" -- 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: - How to extract Control Points alone to compare two images?
On Feb 15, 8:29 am, "Karthik.K" wrote: > I'm new to Hugin and all the tools used. I have been reading and > researching a lot about all the control point generators. All I need > to do now is to calculate and extract the Control points (Only the > control points) and compare The number of control points between two > images and tell that they are similar or not, using Command Line. See this thread where some scripts were posted: https://groups.google.com/group/hugin-ptx/browse_thread/thread/318633a917576dec -- 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] [Urgent] - How to extract Control Points alone to compare two images?
Hi, I'm new to Hugin and all the tools used. I have been reading and researching a lot about all the control point generators. All I need to do now is to calculate and extract the Control points (Only the control points) and compare The number of control points between two images and tell that they are similar or not, using Command Line. Please help me out in this issue as soon as possible. It's urgent! Thanks in advance! Karthik.K -- 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] Announcement: Photoropter lens correction library
Hi all, in the hope that this might be of interest to some people on this list, I am posting this announcement on hugin-ptx. Have a look, and let me know what you think. If you are interested in Photoropter's development, you are welcome to join the project mailing list at https://lists.berlios.de/mailman/listinfo/photoropter-users Regards, Robert === Announcement: Photoropter lens correction library === Photoropter is planned as a generic image transformation library with a strong emphasis on lens correction. It already supports PTLens correction and Hugin-compatible vignetting compensation (more to come). The interface is (hopefully) clean C++, allowing for easy integration into existing projects. To further that goal, the license of Photoropter is the MIT/X11 license (i.e., a permissive license which is compatible with the GPL and more or less every other license on the planet). In the (hopefully not too distant) future, I am also planning a camera- matching module for automatic selection of parameters, but for now I have enough on my plate getting the transformation infrastructure to work properly (and fast!). But a lot of the 'mechanics' is in place, hopefully. What already works: - PTLens & Vignetting correction - Bilinear reconstruction/interpolation of the image (Lanczos will be next) - Oversampling of the result - Multithreading via OpenMP - Handling of arbitrary gamma correction functions: generic gamma, sRGB gamma and EMOR are currently implemented - Automatic conversion of correction parameters based on crop factor and image aspect - Region of interest support More to come: especially more geometric and colour correction functions (i.e., chromatic abberation, exposure shift etc.). If you think that Photoropter might be useful to you, please visit the project website at http://photoropter.berlios.de/ for further information. -- 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
