Vladimir. I have written an app that relies on align-image-stack and your 3D patch to it. The app is for images taken with a mobile phone or a camera, so they won’t be aligned properly and won’t create a 3D image without tedious manual alignment or preferably the use of AIS.
I have recently re-read the documentation https://wiki.panotools.org/Align_image_stack to try to make the most of AIS by using the optimum choice of settings. I found it a bit limited and posted some queries here https://groups.google.com/g/hugin-ptx/c/StZln-rxsGw with the result that it has been improved. The Panotools 3D page https://wiki.panotools.org/Talk:Align_image_stack gives a statement which is clearly wrong: *align_image_stack -i -a AIS_ -S -A -P IMG_????.* - - It only names one input file. - It sets both -A and -P which are contradictory. I have been using the settings you mention in your link above. *align_image_stack -p aligned.pto -a aligned -m -i -P -C right.jpg left.jpg* (It revealed this bug https://bugs.launchpad.net/hugin/+bug/2002813 when using -i which caused AIS to hang when the images were blurry, it’s fixed now.) I have since noticed that you have added a statement to the official page: *align_image_stack -p out.pto -x -s 4 -P -C right.tif left.tif* *T**he options* *-S *Assume stereo images - allow horizontal shift of control points. Adds all control points as "horizontal lines". -A Align stereo window - assumes -S. Adds one "normal" control point that is the nearest point, so that everything will appear behind the display plane. -P Align stereo window with pop-out effect - assumes -S. Adds one "normal" control point that is the nearest point from the border areas, so that the center of the image may appear in front of the display plane. The language is a little ambiguous here - “assumes -S “ Does this mean - “Assumes you have also used the –-S parameter?” If not what would happen? Or - “This will also set/activate/turn-on the -S option.” -m magnification I don’t think the -m is relevant for my application since both L and R images would be taken quickly one after the other. *-i **Optimize image center shift for all image**s* I assume this means “Optimise matching of centre of image, or weight corrections towards the centre rather than the periphery. That seems sensible, however it might attempt to match the x axis and I don't think we want that ‘corrected’ as it has to be different for the 3D effect. *-x *That seems wrong to me as I don't think we want that ‘corrected’, as it has to be different for the 3D effect. Why did you switch to using this? *Optimisation phase* States that yaw pitch and roll are optimised by default. My images are likely to be incorrectly matched in the y axis and in roll, so need correction. I don’t think they should be adjusted in the x axis or in yaw as they are 3D factors. Unfortunately the yaw correction can’t be switched off, as it is automatic and there is no parameter for it. I am going to try align_image_stack -a output.tif -y -P -C right.tif left.tif Would you like to comment on my thoughts? On Monday, January 31, 2011 at 10:55:14 PM UTC Vladimir Nadvornik wrote: > Hi, > > I wrote a tutorial how to use my stereo patches (attached to bug > 679753): > > > http://vndlinuxphoto.blogspot.com/2011/01/stereo-image-alignment-in-hugin.html > > Comments are welcome. > > Vladimir -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/fd7f6286-d140-4729-a2c2-b70797a0fa20n%40googlegroups.com.
