[hugin-ptx] Image alignment help
I have a pair of images which I want to align. They are not a panorama, but rather they are images of the same object, one in natural light, one in fluorescent light. They were taken with a point-and-shoot camera with a cheap tripod and some changeover setup required, so they are not perfectly aligned. After Googling around a bit, I gather that Hugin can help with this, even though I don't care about ending up with a combined image. I just want to apply the geometric transformations required to align my pair of images, getting a pair of modified JPEGs or TIFFs which are aligned. I'm generating all the control points manually, and I think I've done a reasonable job with that. However, I am at a loss about how to use Hugin to get what I want. I tried a few different settings in the optimizer and stitcher windows, but I don't really know what I'm doing. With all the default settings I got a very tiny canvas size, and adjusted that, but the images weren't aligned. I don't really understand which checkboxes on the stitcher tab (or other pages) are the important ones for this use case. Thanks for any help. -- 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] Image alignment help
On 25 October 2011 03:17, Jason Dunham jwdun...@gmail.com wrote: I have a pair of images which I want to align. They are not a panorama, but rather they are images of the same object, one in natural light, one in fluorescent light. They were taken with a point-and-shoot camera with a cheap tripod and some changeover setup required, so they are not perfectly aligned. After Googling around a bit, I gather that Hugin can help with this, even though I don't care about ending up with a combined image. I just want to apply the geometric transformations required to align my pair of images, getting a pair of modified JPEGs or TIFFs which are aligned. I'm generating all the control points manually, and I think I've done a reasonable job with that. However, I am at a loss about how to use Hugin to get what I want. I tried a few different settings in the optimizer and stitcher windows, but I don't really know what I'm doing. With all the default settings I got a very tiny canvas size, and adjusted that, but the images weren't aligned. I don't really understand which checkboxes on the stitcher tab (or other pages) are the important ones for this use case. Thanks for any help. -- 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 I think align_image_stack is the tool you are looking for. 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] Fisheye lenses, exif data and projection
On 16.10.2011, at 16:12, T. Modes wrote: So please post the lens names and the projection Hugin should set automatic. Sigma 8.0 mm on a Nikon D80: Circular Fisheye (iPhoto tells a bit more: http://cl.ly/BFCA) in portrait orientation. Hugin was manually set to Circular Fisheye, the lens.ini is attached below. Habi -- 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 sigma8mmonD80.ini Description: Binary data
[hugin-ptx] Re: Fisheye lenses, exif data and projection
On 16 Okt., 16:12, T. Modes thomas.mo...@gmx.de wrote: Hi all, I added code to display the lens in the GUI. It is using the information stored in the EXIF section to identify the lens (via the exiv2 lib). With this information it would be possible to automatically set the correct projection when adding images to Hugin. But to implement this I need more information. I need the lens type/name (as reported by hugin or exiv2) and the projection you are using for this lens. Hi Thomas! I'm glad my first wish I ever expressed on this ML (which didn't even receive an answer at the time) seems to be getting closer to fulfilment: http://groups.google.com/group/hugin-ptx/browse_thread/thread/cf6bba0d7babb4a5# I haven't given your code a spin yet, but maybe while you're at it you could pick up my suggestion to load a specific lens ini file when the lens model exif tag is present or use default lens ini file if the relevant exif data are missing. I think it should be fairly straightforward to include code along the lines of: - if exif lens type flag is found to be XXX - then load lens file path/XXX.ini - else if lens file path/default.ini exists - then load lens file path/default.ini - else proceed as ever before (ask the user) This would help all users who work with fully manual lenses (like myself, I use a Samyang 8mm which should be fairly common). This is my only manual lens, and it'd save me the patching of the exif data which I still would have to perform using the mechanism you've implemented. The change would be transparent, as it's opt-in, and you wouldn't need to have a database. The lens name can be read inside Hugin (images tab) or you are using exiv2 (run exiv2 -pt image.jpg | grep Lens and search for lens name in the output, depending on the maker a different tag is shown). So please post the lens names and the projection Hugin should set automatic. I think your approach goes along the lensfun road, which is data- intensive, as you have to keep a database somewhere with the lens model - projection relations. Yet again I propose to use a mechanism where a lens ini file is looked for in a predefined place which goes by the name of lens model.ini This way users can put their calibration data in a place where hugin picks them up automatically. This does require the user to produce or acquire the ini file rather than relying on an automatism, but it's the better solution because it is less data-intensive as no database is required. If this approach were taken, not only the projection but also the lens correction parameters the user deems correct would be at hand. Not drawing these from a database is IMHO more appropriate since even if lenses are 'the same' they may differ quite a bit from specimen to specimen, not to mention that they may require quite different calibration data when mounted on different bodies, even of the same type, so a value from a database will usually be inferior to a value a user arrives at by careful calibration of the actual hardware they use. In my experience the lens data taken from databases help some, but they aren't as good as the data I've generated myself by careful calibration - the values simply differ too much for each individual case to successfully cover them with a database record. Of course the mere projection can be derived from a database and will be correct, but why not ge beyond that and use the simple machanism I propose to have it all? And my proposed mechanism would also aloow to handle the absence of the appropriate exif data gracefully. What do you think? Kay -- 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 force CP detection order?
On Saturday, October 22, 2011 1:13:47 AM UTC+2, Bruno Postle wrote:
On Fri 21-Oct-2011 at 11:43 -0700, McFly wrote:
Hi,
I bumped into a problem trying to stitch a panorama with hfov 360° (in
fact
about 4x360° :) )
Starting with the next photo after 360°, hugin detects the same objects as
in the first photo, so the resulting panorama will be 360° with 4
layers.
This is normal but I'd like the panorama to continue beyond 360° (to show
evolution of the objects and scenery in time -if you were wondering why)
A panoramic scene isn't a simple flat strip that you can stretch out
beyond 360°.
I suggest you treat this as four 'layers', stitch them separately,
and stick them together in an image editor later. You can do this
with a single Hugin project by turning the photos on and off
individually in the preview before stitching.
... Or you can keep them in one project (such that similar features get a
perfect overlay), and stitch this project file several times, with different
images enabled/disabled. You can do so in the Fast Preview window. I suggest
you keep an overlap between each of the 360 degree panos, e.g.:
- select (enable) the images you'd like to show up on the leftmost part, and
stitch;
- enable the next set of images, but keep a small overlap with the previous
ones (e.g., you only move 270 degrees);
- iterate until at the end.
- merge the files using either an image editor, or using command line tools.
For Smartblend the last step would be something like this:
smartblend -o final.tiff pano1.tiff -x {offset for pano2} pano2.tiff -x
{offset for pano3} pano3.tiff ...
Make sure to post your result here! :)
--
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: Fisheye lenses, exif data and projection
Autoloading of .ini files is a great idea -- would make life much easier. It could also use camera serial number as a lookup parameter, if that's included in the exif data. One other detail though, is that the 'lens' is really a combination of a lens and a body. Some of the 'lens' parameters, such as the photometric scaling, and perhaps the lens shift parameters, are really a function of the body not the lens. In the longer term view, it may be appropriate to separate those as different ini files... Brent On Oct 25, 3:06 am, kfj _...@yahoo.com wrote: On 16 Okt., 16:12, T. Modes thomas.mo...@gmx.de wrote: Hi all, I added code to display the lens in the GUI. It is using the information stored in the EXIF section to identify the lens (via the exiv2 lib). With this information it would be possible to automatically set the correct projection when adding images to Hugin. But to implement this I need more information. I need the lens type/name (as reported by hugin or exiv2) and the projection you are using for this lens. Hi Thomas! I'm glad my first wish I ever expressed on this ML (which didn't even receive an answer at the time) seems to be getting closer to fulfilment: http://groups.google.com/group/hugin-ptx/browse_thread/thread/cf6bba0... I haven't given your code a spin yet, but maybe while you're at it you could pick up my suggestion to load a specific lens ini file when the lens model exif tag is present or use default lens ini file if the relevant exif data are missing. I think it should be fairly straightforward to include code along the lines of: - if exif lens type flag is found to be XXX - then load lens file path/XXX.ini - else if lens file path/default.ini exists - then load lens file path/default.ini - else proceed as ever before (ask the user) This would help all users who work with fully manual lenses (like myself, I use a Samyang 8mm which should be fairly common). This is my only manual lens, and it'd save me the patching of the exif data which I still would have to perform using the mechanism you've implemented. The change would be transparent, as it's opt-in, and you wouldn't need to have a database. The lens name can be read inside Hugin (images tab) or you are using exiv2 (run exiv2 -pt image.jpg | grep Lens and search for lens name in the output, depending on the maker a different tag is shown). So please post the lens names and the projection Hugin should set automatic. I think your approach goes along the lensfun road, which is data- intensive, as you have to keep a database somewhere with the lens model - projection relations. Yet again I propose to use a mechanism where a lens ini file is looked for in a predefined place which goes by the name of lens model.ini This way users can put their calibration data in a place where hugin picks them up automatically. This does require the user to produce or acquire the ini file rather than relying on an automatism, but it's the better solution because it is less data-intensive as no database is required. If this approach were taken, not only the projection but also the lens correction parameters the user deems correct would be at hand. Not drawing these from a database is IMHO more appropriate since even if lenses are 'the same' they may differ quite a bit from specimen to specimen, not to mention that they may require quite different calibration data when mounted on different bodies, even of the same type, so a value from a database will usually be inferior to a value a user arrives at by careful calibration of the actual hardware they use. In my experience the lens data taken from databases help some, but they aren't as good as the data I've generated myself by careful calibration - the values simply differ too much for each individual case to successfully cover them with a database record. Of course the mere projection can be derived from a database and will be correct, but why not ge beyond that and use the simple machanism I propose to have it all? And my proposed mechanism would also aloow to handle the absence of the appropriate exif data gracefully. What do you think? Kay -- 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] Image alignment help
On Tue, 25 Oct 2011 12:17:52 +1100, Jason Dunham jwdun...@gmail.com wrote: I have a pair of images which I want to align. They are not a panorama, [snip] After Googling around a bit, I gather that Hugin can help with this, even though I don't care about ending up with a combined image. I just want to apply the geometric transformations required to align my pair of images, getting a pair of modified JPEGs or TIFFs which are aligned. If I understand your requirement correctly, you will get two aligned images by optimizing then stitching, and in the stitcher tab deselect 'Panorama Outputs: Exposure corrected, low dynamic range', and instead select 'Remapped Images: Exposure corrected, low dynamic range'. Ensure that your Preferences Programs, Nona does NOT have 'Create cropped images by default' selected. The output will be two tiff images which are aligned. Cheers, -- Regards, Terry Duell -- 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] hsi on Windows 32 bit
I am new to Python scripting with Hugin and would like to try it out. My installed version, however does not seem to have hsi or hpi available. The Run python script.. menu item is greyed out and when I type import hsi in the Python command line I get No module named hsi. I installed from HuginSetup_2011.2.0_32bit_Windows.exe. Do I need to install something else? -- 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
