https://wiki.panotools.org/api.php?action=feedcontributions&user=Mfwitten&feedformat=atomPanoTools.org Wiki - User contributions [en]2024-03-29T06:11:29ZUser contributionsMediaWiki 1.35.3https://wiki.panotools.org/index.php?title=Time_lapse_stabilization&diff=15629Time lapse stabilization2014-06-03T20:08:16Z<p>Mfwitten: /* post processing */ Fixed shell code</p>
<hr />
<div>== Time Lapse stabilization ==<br />
<br />
Remember the shaky videos of rockets being launched from the old days?<br />
<br />
Did you see the modern NASA videos , where the FRAME bounces around<br />
the object being filmed, while the rocket remains perfectly stable in<br />
view? Thats' what you'll be able to do after reading this tutorial. <br />
<br />
=== Why and when? ===<br />
<br />
Sometimes you find yourselves with some time on your hand, a nice<br />
camera, a nice scene that would look nice in a time lapse movie, but<br />
no tripod and/or computer to take shots in exactly the same position<br />
in an exact time-sequence.<br />
<br />
Just point the camera at what you want in your timelapse, and take<br />
shots, at regular intervals, as consistent in time delay and direction<br />
as you want/can.<br />
<br />
You can play a sequence of jpgs using mplayer with:<br />
<br />
mplayer -mf fps=12 mf://\*.jpg<br />
<br />
If you put the shots together like this the image will bounce and<br />
shake a lot, because you didn't point the camera in exactly the same<br />
direction every time.... This is where tripods excel above humans.<br />
<br />
So, hugin to the rescue!<br />
<br />
=== preparing the images ===<br />
<br />
First, I reduced the size of all the jpgs by a factor of 4 in each<br />
direction. This gave me frames of about video quality, greatly<br />
reducing the amount of CPU time required to process the many images.<br />
<br />
mkdir small<br />
for i in *.jpg; do<br />
echo "$i"<br />
djpeg "$i" | pnmscale 0.25 | cjpeg > small/"$i"<br />
done<br />
cd small<br />
<br />
Two of my images (Scaled to 0.4 of what I worked with):<br />
<br />
[[image:Timelapse_pre1.jpg]] [[image:Timelapse_pre2.jpg]]<br />
<br />
=== Steps in hugin === <br />
<br />
I then started up hugin and loaded all the images.<br />
<br />
Now to match all the images I have to do the control points manually,<br />
because this is not the "normal" use of hugin. However, for someone<br />
intimate with the workings of Hugin and the surrounding tools, it<br />
should be quite possible to modify one of the tools to allow doing<br />
this automatically in the future.<br />
<br />
On the control-points tab, select image 0 on the left, and image 1 on<br />
the right. Now match two or three points in the image.<br />
<br />
Next, you would normally match image 1 to image 2, and so on. In this<br />
case I recommend you match every image to image 0. So next you create<br />
several controlpoint matches on images 0 against image 2.<br />
<br />
Configure the project to produce only the individual remapped images;<br />
if the output's filename has been set to "test.tif", then the remapped<br />
image files will be named something like "test????.tif" (where the "????"<br />
represents some number).<br />
<br />
=== post processing ===<br />
<br />
You can convert the remapped images to JPEGs with:<br />
<br />
for i in test????.tif; do<br />
tifftopnm "$i" | cjpeg > "$i".jpg<br />
done<br />
<br />
now you can play them with:<br />
<br />
mplayer -mf fps=12 mf://\test\*.tif.jpg<br />
<br />
The bouncing should be greatly reduced!<br />
<br />
Here are two of the resulting images. <br />
<br />
[[image:Timelapse_post1.jpg]] [[image:Timelapse_post2.jpg]]<br />
<br />
Next, you can trim off some of the bouncy edges. I used pnmcut while<br />
the files are in PPM format in the last conversion: <br />
<br />
for i in test????.tif; do<br />
tifftopnm "$i" | pnmcut -top 120 -left 50 -right -60 -bot -120 | cjpeg > "$i".jpg<br />
done<br />
<br />
And after trimming: <br />
<br />
[[image:Timelapse_tpost1.jpg]] [[image:Timelapse_tpost2.jpg]]<br />
<br />
I then encoded the sequence of frames using: <br />
<br />
mencoder -mf fps=12 mf://test\*.tif.jpg -ovc lavc -lavcopts vcodec=mpeg4 -o timelapse_final.avi<br />
<br />
<br />
And here is the final 160 frame avi file: http://prive.bitwizard.nl/timelapse_final.avi<br />
<br />
=== final words === <br />
<br />
The inline scripts in this page are written in "bash". If you use tcsh, <br />
the syntax is slightly different. If you're on MS Windows, I don't know<br />
how you achieve such operations. <br />
<br />
This tutoral was written by R.E.Wolff@BitWizard.nl . Feel free to Email me<br />
with suggestions or ways to do this easier. As this is a WIKI you could<br />
also edit this directly.<br />
<br />
In newer versions of hugin, an application "align_image_stack" is available. <br />
This is not yet released, but a windows application executable is available. <br />
Unix users will have to get and compile from the subversion source. <br />
<br />
I tried it, and found that the results of "align_image_stack" are worse than <br />
what I started with. My test case had lots of clouds, and it apparently was <br />
finding points on the clouds instead of on the mountains that remain stable. <br />
<br />
=== Other Examples === <br />
[http://imgur.com/a/3qfWQ TheodoreFunkenstein tutorial of stabilizing a movie clip]<br />
<br />
[[Category:Tutorial:Specialised]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Time_lapse_stabilization&diff=15628Time lapse stabilization2014-06-03T20:06:21Z<p>Mfwitten: Removed crusty rambling</p>
<hr />
<div>== Time Lapse stabilization ==<br />
<br />
Remember the shaky videos of rockets being launched from the old days?<br />
<br />
Did you see the modern NASA videos , where the FRAME bounces around<br />
the object being filmed, while the rocket remains perfectly stable in<br />
view? Thats' what you'll be able to do after reading this tutorial. <br />
<br />
=== Why and when? ===<br />
<br />
Sometimes you find yourselves with some time on your hand, a nice<br />
camera, a nice scene that would look nice in a time lapse movie, but<br />
no tripod and/or computer to take shots in exactly the same position<br />
in an exact time-sequence.<br />
<br />
Just point the camera at what you want in your timelapse, and take<br />
shots, at regular intervals, as consistent in time delay and direction<br />
as you want/can.<br />
<br />
You can play a sequence of jpgs using mplayer with:<br />
<br />
mplayer -mf fps=12 mf://\*.jpg<br />
<br />
If you put the shots together like this the image will bounce and<br />
shake a lot, because you didn't point the camera in exactly the same<br />
direction every time.... This is where tripods excel above humans.<br />
<br />
So, hugin to the rescue!<br />
<br />
=== preparing the images ===<br />
<br />
First, I reduced the size of all the jpgs by a factor of 4 in each<br />
direction. This gave me frames of about video quality, greatly<br />
reducing the amount of CPU time required to process the many images.<br />
<br />
mkdir small<br />
for i in *.jpg; do<br />
echo "$i"<br />
djpeg "$i" | pnmscale 0.25 | cjpeg > small/"$i"<br />
done<br />
cd small<br />
<br />
Two of my images (Scaled to 0.4 of what I worked with):<br />
<br />
[[image:Timelapse_pre1.jpg]] [[image:Timelapse_pre2.jpg]]<br />
<br />
=== Steps in hugin === <br />
<br />
I then started up hugin and loaded all the images.<br />
<br />
Now to match all the images I have to do the control points manually,<br />
because this is not the "normal" use of hugin. However, for someone<br />
intimate with the workings of Hugin and the surrounding tools, it<br />
should be quite possible to modify one of the tools to allow doing<br />
this automatically in the future.<br />
<br />
On the control-points tab, select image 0 on the left, and image 1 on<br />
the right. Now match two or three points in the image.<br />
<br />
Next, you would normally match image 1 to image 2, and so on. In this<br />
case I recommend you match every image to image 0. So next you create<br />
several controlpoint matches on images 0 against image 2.<br />
<br />
Configure the project to produce only the individual remapped images;<br />
if the output's filename has been set to "test.tif", then the remapped<br />
image files will be named something like "test????.tif" (where the "????"<br />
represents some number).<br />
<br />
=== post processing ===<br />
<br />
You can convert the remapped images to JPEGs with:<br />
<br />
for i in test????.tif; do<br />
tifftopnm $i | cjpeg > $i.jpg<br />
done<br />
<br />
now you can play them with:<br />
<br />
mplayer -mf fps=12 mf://\test\*.tif.jpg<br />
<br />
The bouncing should be greatly reduced!<br />
<br />
Here are two of the resulting images. <br />
<br />
[[image:Timelapse_post1.jpg]] [[image:Timelapse_post2.jpg]]<br />
<br />
Next, you can trim off some of the bouncy edges. I used pnmcut while<br />
the files are in PPM format in the last conversion: <br />
<br />
for i in test????.tif ; do<br />
tifftopnm $i | pnmcut -top 120 -left 50 -right -60 -bot -120 | cjpeg > $i.jpg<br />
done<br />
<br />
And after trimming: <br />
<br />
[[image:Timelapse_tpost1.jpg]] [[image:Timelapse_tpost2.jpg]]<br />
<br />
I then encoded the sequence of frames using: <br />
<br />
mencoder -mf fps=12 mf://test\*.tif.jpg -ovc lavc -lavcopts vcodec=mpeg4 -o timelapse_final.avi<br />
<br />
<br />
And here is the final 160 frame avi file: http://prive.bitwizard.nl/timelapse_final.avi<br />
<br />
=== final words === <br />
<br />
The inline scripts in this page are written in "bash". If you use tcsh, <br />
the syntax is slightly different. If you're on MS Windows, I don't know<br />
how you achieve such operations. <br />
<br />
This tutoral was written by R.E.Wolff@BitWizard.nl . Feel free to Email me<br />
with suggestions or ways to do this easier. As this is a WIKI you could<br />
also edit this directly.<br />
<br />
In newer versions of hugin, an application "align_image_stack" is available. <br />
This is not yet released, but a windows application executable is available. <br />
Unix users will have to get and compile from the subversion source. <br />
<br />
I tried it, and found that the results of "align_image_stack" are worse than <br />
what I started with. My test case had lots of clouds, and it apparently was <br />
finding points on the clouds instead of on the mountains that remain stable. <br />
<br />
=== Other Examples === <br />
[http://imgur.com/a/3qfWQ TheodoreFunkenstein tutorial of stabilizing a movie clip]<br />
<br />
[[Category:Tutorial:Specialised]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Time_lapse_stabilization&diff=15627Time lapse stabilization2014-06-03T14:46:30Z<p>Mfwitten: /* preparing the images */ Fixed shell</p>
<hr />
<div>== Time Lapse stabilization ==<br />
<br />
Remember the shaky videos of rockets being launched from the old days?<br />
<br />
Did you see the modern NASA videos , where the FRAME bounces around<br />
the object being filmed, while the rocket remains perfectly stable in<br />
view? Thats' what you'll be able to do after reading this tutorial. <br />
<br />
=== Why and when? ===<br />
<br />
Sometimes you find yourselves with some time on your hand, a nice<br />
camera, a nice scene that would look nice in a time lapse movie, but<br />
no tripod and/or computer to take shots in exactly the same position<br />
in an exact time-sequence.<br />
<br />
Just point the camera at what you want in your timelapse, and take<br />
shots, at regular intervals, as consistent in time delay and direction<br />
as you want/can.<br />
<br />
You can play a sequence of jpgs using mplayer with:<br />
<br />
mplayer -mf fps=12 mf://\*.jpg<br />
<br />
If you put the shots together like this the image will bounce and<br />
shake a lot, because you didn't point the camera in exactly the same<br />
direction every time.... This is where tripods excel above humans.<br />
<br />
So, hugin to the rescue!<br />
<br />
=== preparing the images ===<br />
<br />
First, I reduced the size of all the jpgs by a factor of 4 in each<br />
direction. This gave me frames of about video quality, greatly<br />
reducing the amount of CPU time required to process the many images.<br />
<br />
mkdir small<br />
for i in *.jpg; do<br />
echo "$i"<br />
djpeg "$i" | pnmscale 0.25 | cjpeg > small/"$i"<br />
done<br />
cd small<br />
<br />
Two of my images (Scaled to 0.4 of what I worked with):<br />
<br />
[[image:Timelapse_pre1.jpg]] [[image:Timelapse_pre2.jpg]]<br />
<br />
=== Steps in hugin === <br />
<br />
I then started up hugin and loaded all the images.<br />
<br />
Now to match all the images I have to do the control points manually,<br />
because this is not the "normal" use of hugin. However, for someone<br />
intimate with the workings of Hugin and the surrounding tools, it<br />
should be quite possible to modify one of the tools to allow doing<br />
this automatically in the future.<br />
<br />
On the control-points tab, select image 0 on the left, and image 1 on<br />
the right. Now match two or three points in the image.<br />
<br />
Next, you would normally match image 1 to image 2, and so on. In this<br />
case I recommend you match every image to image 0. So next you create<br />
several controlpoint matches on images 0 against image 2.<br />
<br />
Next, I selected "equirectangular" for both the source images (under<br />
the "camera and lens" tab) and the destination (under the "stitcher" tab) <br />
(this may acutally not be the best selection, as hugin might also correct <br />
for lens distortion on the way. But at least it keeps things simple...)<br />
<br />
Current "best practise" suggests that "rectilinear" for both the source<br />
("camera and lens" tab), and the destination ("stitcher" tab), is the best<br />
combination. However, the FOV or focal length better not be too far off. <br />
<br />
Next, click "optimize now".<br />
<br />
Next, I selected "high quality tiff" and "nona" as the stitcher. This<br />
triggers the creation of intermediate TIFF files which we're<br />
interested in.<br />
<br />
Next click: "calculate field of view" in the stitcher tab, and<br />
"calculate optimal size".<br />
<br />
Next, click "stitch now". In my case, the final enblend step crashed<br />
due to an installation error. This is ideal: We don't need<br />
it. Consider making the binary not executable for the duration of this<br />
project, or putting another program of the same name in your path, or<br />
configuring hugin to call some program that doesn't exist.<br />
<br />
Actually, it's better to choose "Multiple TIFF files" in currently released hugin version, and "Remapped images" in current trunk - that way only remapped images are created and hugin does not try to run enblend or other programs.<br />
<br />
=== post processing ===<br />
<br />
After entering the name "test.tif" as the output file, you will be<br />
left<br />
with realigned tiff files called test????.tif! You can then convert<br />
these to jpeg with:<br />
<br />
for i in test????.tif ; do<br />
tifftopnm $i | cjpeg > $i.jpg<br />
done<br />
<br />
now you can play them with:<br />
<br />
mplayer -mf fps=12 mf://\test\*.tif.jpg<br />
<br />
The bouncing should be greatly reduced!<br />
<br />
Here are two of the resulting images. <br />
<br />
[[image:Timelapse_post1.jpg]] [[image:Timelapse_post2.jpg]]<br />
<br />
Next, you can trim off some of the bouncy edges. I used pnmcut while<br />
the files are in PPM format in the last conversion: <br />
<br />
for i in test????.tif ; do<br />
tifftopnm $i | pnmcut -top 120 -left 50 -right -60 -bot -120 | cjpeg > $i.jpg<br />
done<br />
<br />
And after trimming: <br />
<br />
[[image:Timelapse_tpost1.jpg]] [[image:Timelapse_tpost2.jpg]]<br />
<br />
I then encoded the sequence of frames using: <br />
<br />
mencoder -mf fps=12 mf://test\*.tif.jpg -ovc lavc -lavcopts vcodec=mpeg4 -o timelapse_final.avi<br />
<br />
<br />
And here is the final 160 frame avi file: http://prive.bitwizard.nl/timelapse_final.avi<br />
<br />
=== final words === <br />
<br />
The inline scripts in this page are written in "bash". If you use tcsh, <br />
the syntax is slightly different. If you're on MS Windows, I don't know<br />
how you achieve such operations. <br />
<br />
This tutoral was written by R.E.Wolff@BitWizard.nl . Feel free to Email me<br />
with suggestions or ways to do this easier. As this is a WIKI you could<br />
also edit this directly.<br />
<br />
In newer versions of hugin, an application "align_image_stack" is available. <br />
This is not yet released, but a windows application executable is available. <br />
Unix users will have to get and compile from the subversion source. <br />
<br />
I tried it, and found that the results of "align_image_stack" are worse than <br />
what I started with. My test case had lots of clouds, and it apparently was <br />
finding points on the clouds instead of on the mountains that remain stable. <br />
<br />
=== Other Examples === <br />
[http://imgur.com/a/3qfWQ TheodoreFunkenstein tutorial of stabilizing a movie clip]<br />
<br />
[[Category:Tutorial:Specialised]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Straight_line_control_points&diff=12313Straight line control points2010-04-09T08:38:36Z<p>Mfwitten: optimiser -> optimizer (to be consistent)</p>
<hr />
<div>{{Glossary|[[Control points]] that define a straight line in the output [[projection]].}}<br />
The panorama tools optimizer understands various different schemes for<br />
aligning photos using [[control points]]:<br />
Normal points are '''t0''' points, [[horizontal control points]] are '''t1''' points,<br />
[[vertical control points]] are '''t2''' points, and straight line control points are '''t3''' points.<br />
<br />
'''Straight line control points''' were added later and have a similar effect to horizontal<br />
and vertical points, except that the straight line can be at any angle. They have two main uses:<br />
Lining up linear features that don't have identifiable detail, such as the edges of a room or<br />
overhead cables; and calibrating [[lens distortion]] using a single<br />
[[rectilinear Projection|rectilinear]] photograph of a grid or building.<br />
<br />
Although two points are sufficient to define a horizontal or vertical line, more are<br />
required for these lines at arbitrary angles. Since the script file format only supports 'pairs' of<br />
points, a straight line is generally defined with four, six or eight etc... control points.<br />
<br />
Some of the [[GUI front-ends]] support placing these '''straight line control points''', see this<br />
tutorial on [http://www.erik-krause.de/verzeichnung/distort_en.htm correcting lens distortion with ptgui].<br />
<br />
Otherwise if you edit a [[PTOptimizer]] script and make more than one pair of existing points<br />
'''t3''', then the optimiser will try to line them up as a straight<br />
line in the output image. You can keep going, with '''t4''', '''t5''' etc... for each group of points<br />
that you want in different 'straight lines'.<br />
<br />
[[Category:Glossary]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Vertical_control_points&diff=12312Vertical control points2010-04-09T08:35:37Z<p>Mfwitten: straight line control points are t3 points</p>
<hr />
<div>{{Glossary|[[Control points]] that define a vertical line in the output [[projection]].}}<br />
The panorama tools [[PTOptimizer|optimizer]] understands various different schemes for<br />
aligning photos using [[control points]]:<br />
Normal points are '''t0''' points, [[horizontal control points]] are '''t1''' points,<br />
vertical control points are '''t2''' points, and [[straight line control points]] are '''t3''' points.<br />
<br />
The main use of '''vertical control points''' is to change the perspective of the output panorama such that the marked structures are vertical in the output [[projection]]. In a multi image panorama this is only possible if the [[optimization]] of [[Roll]] and [[Pitch]] is allowed for all images and of [[Yaw]] for all but the anchor image.<br />
<br />
You set '''vertical control points''' on a vertical structure as far apart from each other as possible.<br />
<br />
Please note that all real world vertical lines only stay vertical in [[rectilinear]], [[cylindrical]] and [[equirectangular]] projections. In [[fisheye]] projection only the vertical line through the image center stays vertical.<br />
<br />
More details in [[Perspective correction]] and [[Panotools internals#Line_control_points|Panotools internals]], a tutorial using vertical line control points: [[Leveling a Finished Panorama]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Straight_line_control_points&diff=12311Straight line control points2010-04-09T08:34:43Z<p>Mfwitten: No need to link to oneself.</p>
<hr />
<div>{{Glossary|[[Control points]] that define a straight line in the output [[projection]].}}<br />
The panorama tools optimiser understands various different schemes for<br />
aligning photos using [[control points]]:<br />
Normal points are '''t0''' points, [[horizontal control points]] are '''t1''' points,<br />
[[vertical control points]] are '''t2''' points, and straight line control points are '''t3''' points.<br />
<br />
'''Straight line control points''' were added later and have a similar effect to horizontal<br />
and vertical points, except that the straight line can be at any angle. They have two main uses:<br />
Lining up linear features that don't have identifiable detail, such as the edges of a room or<br />
overhead cables; and calibrating [[lens distortion]] using a single<br />
[[rectilinear Projection|rectilinear]] photograph of a grid or building.<br />
<br />
Although two points are sufficient to define a horizontal or vertical line, more are<br />
required for these lines at arbitrary angles. Since the script file format only supports 'pairs' of<br />
points, a straight line is generally defined with four, six or eight etc... control points.<br />
<br />
Some of the [[GUI front-ends]] support placing these '''straight line control points''', see this<br />
tutorial on [http://www.erik-krause.de/verzeichnung/distort_en.htm correcting lens distortion with ptgui].<br />
<br />
Otherwise if you edit a [[PTOptimizer]] script and make more than one pair of existing points<br />
'''t3''', then the optimiser will try to line them up as a straight<br />
line in the output image. You can keep going, with '''t4''', '''t5''' etc... for each group of points<br />
that you want in different 'straight lines'.<br />
<br />
[[Category:Glossary]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Straight_line_control_points&diff=12310Straight line control points2010-04-09T08:33:42Z<p>Mfwitten: straight line control points are t3 points</p>
<hr />
<div>{{Glossary|[[Control points]] that define a straight line in the output [[projection]].}}<br />
The panorama tools optimiser understands various different schemes for<br />
aligning photos using [[control points]]:<br />
Normal points are '''t0''' points, [[horizontal control points]] are '''t1''' points,<br />
[[vertical control points]] are '''t2''' points, and [[straight line control points]] are '''t3''' points.<br />
<br />
'''Straight line control points''' were added later and have a similar effect to horizontal<br />
and vertical points, except that the straight line can be at any angle. They have two main uses:<br />
Lining up linear features that don't have identifiable detail, such as the edges of a room or<br />
overhead cables; and calibrating [[lens distortion]] using a single<br />
[[rectilinear Projection|rectilinear]] photograph of a grid or building.<br />
<br />
Although two points are sufficient to define a horizontal or vertical line, more are<br />
required for these lines at arbitrary angles. Since the script file format only supports 'pairs' of<br />
points, a straight line is generally defined with four, six or eight etc... control points.<br />
<br />
Some of the [[GUI front-ends]] support placing these '''straight line control points''', see this<br />
tutorial on [http://www.erik-krause.de/verzeichnung/distort_en.htm correcting lens distortion with ptgui].<br />
<br />
Otherwise if you edit a [[PTOptimizer]] script and make more than one pair of existing points<br />
'''t3''', then the optimiser will try to line them up as a straight<br />
line in the output image. You can keep going, with '''t4''', '''t5''' etc... for each group of points<br />
that you want in different 'straight lines'.<br />
<br />
[[Category:Glossary]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Horizontal_control_points&diff=12309Horizontal control points2010-04-09T08:31:45Z<p>Mfwitten: straight line control points are t3 control points</p>
<hr />
<div>{{Glossary|[[Control points]] that define a horizontal line in the output [[projection]].}}<br />
The panorama tools [[PTOptimizer|optimizer]] understands various different schemes for<br />
aligning photos using [[control points]]:<br />
Normal points are '''t0''' points, horizontal control points are '''t1''' points,<br />
[[vertical control points]] are '''t2''' points,<br />
and [[straight line control points]] are '''t3''' points.<br />
<br />
The main use of '''horizontal control points''' is to change the perspective of the output panorama such that the marked structures are horizontal in the output [[projection]]. In a multi image panorama this is only possible if the [[optimization]] of [[Roll]] and [[Pitch]] is allowed for all images and of [[Yaw]] for all but the anchor image.<br />
<br />
You set '''horizontal control points''' on a horizontal structure apart from each other. However, be careful in a [[cylindrical]] or [[equirectangular]] panorama not to set them 180° apart, since this won't level the horizon.<br />
<br />
Please note that all real world horizontal lines only stay horizontal in [[rectilinear]] projection. In [[cylindrical]], [[equirectangular]] and [[fisheye]] projections only the horizon itself stays horizontal. <br />
<br />
More details in [[Perspective correction]] and [[Panotools internals#Line_control_points|Panotools internals]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=File:Field-of-view.svg&diff=12308File:Field-of-view.svg2010-04-09T07:22:38Z<p>Mfwitten: uploaded a new version of "File:Field-of-view.svg": Actions I took in inkscape resulted in a transformed text object, which rsvg cannot currently handle; hence, text was missing in the rendered PNG version. This corrects the problem by using a 'plain'</p>
<hr />
<div>A field of view of 2 meters</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Field_of_View&diff=12307Field of View2010-04-09T06:39:03Z<p>Mfwitten: Add Field-of-view.svg image</p>
<hr />
<div>{{Glossary|The angle in degrees that a projection covers.}}<br />
The '''angle of view''' of a photograph or camera is a measure of the proportion of a scene included in the image. Simply said: How many degrees of view are included in an image. A typical fixed lens camera might have an angle of view of 50°, a [[Fisheye Projection|fisheye]] lens can have an angle of view greater than 180° and a full [[equirectangular]] or [[cylindrical panorama]] would have an angle of view of 360°.<br />
<br />
Most people speak of '''field of view''' when in fact they mean '''angle of view'''. Field of view is the distance covered by a projection at a certain distance. So if an image exactly shows a 2 meter wide object at 1 meter distance, then the field of view is 2 meter (and the angle of view is 90°).<br />
Angle of view is also known as '''angle of coverage'''.<br />
<br />
[[image:Field-of-view.svg|center]]<br />
<br />
From here on and on the rest of the wiki we will only speak of field of view (although we should speak of angle of view).<br />
<br />
Field of view is often abbreviated as '''FoV'''.<br />
Usually '''field of view''' refers to the '''horizontal field of view''' (hFoV) of an image. Some applications make use of the '''vertical field of view''' (vFoV) which can be calculated from the [[Aspect Ratio]] of the image:<br />
<br />
For rectilinear images:<br />
<br />
<math>Aspect Ratio = \frac{tan(\frac{hFoV}{2})}{tan (\frac{vFoV}{2})}</math><br />
<br />
For fisheye images (approximation):<br />
<br />
<math>Aspect Ratio = \frac{hFoV}{vFoV}</math><br />
<br />
== Conversion from focal length ==<br />
<br />
The other standard measure of the ''width'' or ''narrowness'' of a lens is [[Focal Length]].<br />
<br />
Assuming a [[Rectilinear Projection|rectilinear]] lens, the field of view can be calculated like this (<math>size</math> being either width or height for the respective FoV):<br />
<br />
<math>FoV = 2 * atan \left(\frac{size}{2 * Focal Length} \right) </math><br />
<br />
Please note that this is an approximation. The exact values depend on the location of the [[entrance pupil]]. More information on that in [http://www.janrik.net/PanoPostings/NoParallaxPoint/TheoryOfTheNoParallaxPoint.pdf Rik Littlefield's paper].<br />
See [[Fisheye Projection]] for formulas for [[Fisheyes]].<br />
<br />
== Conversion from horizontal to vertical and vice versa ==<br />
<br />
For fisheye (approximation) and equirectangular images:<br />
<br />
<math>vFoV = hFoV * \frac{height}{width}\ </math><br />
<br />
<math>hFoV = vFoV * \frac{width}{height}\ </math><br />
<br />
For rectilinear images:<br />
<br />
<math>vFoV = 2 * atan \left( tan \left(\frac{hFoV}{2} \right) * \frac{height}{width} \right)</math><br />
<br />
<math>hFoV = 2 * atan \left( tan \left(\frac{vFoV}{2} \right) * \frac{width}{height} \right)</math><br />
<br />
[[Category:Glossary]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=File:Field-of-view.svg&diff=12306File:Field-of-view.svg2010-04-09T06:22:03Z<p>Mfwitten: A field of view of 2 meters</p>
<hr />
<div>A field of view of 2 meters</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Hugin_Control_Points_tab&diff=12305Hugin Control Points tab2010-04-09T01:57:38Z<p>Mfwitten: Woops! Forgot to change 'cursor keys' to 'arrow keys'.</p>
<hr />
<div>[[Control points]] are central to [[Panorama Tools]] and [[hugin]], because they are used to estimate the position of image position and lens parameters described above.<br />
A control point specifies a corresponding point between two images. Using these corresponding points, the [[hugin Optimizer tab]] can estimate the image position and lens parameters.<br />
It is therefore important that the control points are accurate and usually at least 3 well distributed control points should be used to estimate the image position ([[yaw]], [[roll]] and [[pitch]]) and maybe the [[Field of View|HFOV]].<br />
For accurate estimation of the a,b,c distortion parameters, many well distributed control points, and a large overlap (up to 50%) are required.<br />
<br />
The Tab consists of two image displays and associated pull-down lists to switch images to be edited.<br />
The bottom contains a list view where Points can be selected and some fields to edit a selected point.<br />
Points can also be selected by clicking or dragging on them in the images.<br />
It is possible to zoom out to show the full image.<br />
<br />
Entries in the pull-down lists have a coloured block indicating the average quality of the control-points between the selected photos, a short red block indicates a 'bad' alignment, whereas a larger green block indicates a 'good' alignment. No coloured block indicates that there are no control-points between the photos.<br />
<br />
Adding a control point works by selecting one point in the left or right image, and then clicking onto the corresponding point in the other image.<br />
If '''auto add''' is not set, the points can be moved by clicking at some other place in the images.<br />
They are added to the list of control points by pressing the '''right mouse button''', the '''a''' key or by pushing the '''Add''' button.<br />
If you press the '''right mouse button''' when only one point is selected, the point selection will be aborted.<br />
'''auto add''' adds the control point as soon as both points have been specified.<br />
<br />
If the images are zoomed out (fit to window), the first click zooms to a temporary 100% view to give you the chance to refine your selection.<br />
Note that only the second click will trigger the auto estimate.<br />
<br />
For good results, the [[control points]] should be as accurate as possible. However, it is often tedious to select a particular point exactly, and it may be helpful to use the '''arrow keys''' (''left'', ''right'', ''up'', and ''down'') to nudge the selection point in various directions pixel-by-pixel (users of X11 may need to ensure that a particular image pane has the focus by placing the mouse cursor within its bounds). Once a point pair has been roughly selected, the '''fine tune''' function of [[hugin]] can be used to estimate the corresponding point up to one tenth of a pixel.<br />
The keyboard short cut for the '''fine tune''' function is the '''f''' key.<br />
Fine tune only search in a small neighbourhood of the currently selected points.<br />
The size of this neighbourhood can be controlled by opening the [[Hugin Preferences]] panel and setting the '''Local area search width'''.<br />
<br />
Note that the fine tune function estimates the translation of the patch around the point selected in the other image with respect to the current image.<br />
This works well if the rotation between the images is small and narrow angle lenses have been used.<br />
If wide angle or [[Fisheye Projection]] images are used, rotation search should be activated in the [[Hugin Preferences]] panel.<br />
Then [[hugin]] also searches for rotated occurrences of the patch around the selected point.<br />
<br />
The image can be scrolled by pressing the '''middle mouse button''' or the '''CTRL''' key while moving the mouse.<br />
If the '''shift''' key is pressed instead, both images will be scrolled.<br />
This is very useful if [[control points]] are set using the 100% zoom level.<br />
<br />
Control point creation is also influenced by the following check boxes:<br />
<br />
* '''auto fine tune''' [[hugin]] helps you to find the second point by looking for it in a search region (shown by a rectangle around the cursor). This might not always work, but usually is reliable, if the image distortions are not too big. Try and play with it.<br />
* '''auto add''' A control point is automatically added when both points are known. You won't have time to refine the selection before adding the point.<br />
* '''auto estimate''' Tries to estimate the position of the second point by estimating the translation between the two images. This is very crude and probably only works for single row panoramas created from [[Rectilinear Projection]] images.<br />
<br />
All these flags can be combined. I typically use '''auto fine tune''' and '''auto estimate''' at the same time.<br />
Then [[hugin]] usually automatically selects the second point correctly, at least for normal, [[Rectilinear Projection]] images that are not rotated too much.<br />
<br />
[[hugin]] also includes an experimental [[control points]] creation algorithm.<br />
It can be invoked by pressing the '''g''' key. Corners in the currently selected image are detected, and corresponding control points are set based on the current relative positions of the two images. The images need to be approximately aligned already for this to be useful. Note that these points then need to be aligned by eye, with the '''Fine-tune''' button or with the '''Fine-tune all Points''' function in the Edit menu of the [[Hugin Main window]].<br />
<br />
== Control point mode ==<br />
<br />
Use the '''mode''' pull down menu to change the type of an existing pair of [[control points]].<br />
<br />
=== normal control points ===<br />
<br />
The '''normal''' control point mode is used to align pairs of overlapping photos by matching<br />
identical features in both photos.<br />
<br />
=== vertical line and horizontal line control points ===<br />
<br />
Pairs of [[vertical control points]] and [[horizontal control points]] are different from<br />
'''normal''' control points since they are used to align input images to particular alignments<br />
in the output panorama rather than simply stitching images together.<br />
<br />
Select two points along a feature that you want to be aligned vertically or horizontally in<br />
the final panorama. If these are in the same photo, [[hugin]] will usually detect that you are<br />
trying to create ''horizontal'' or ''vertical'' control points and set the mode appropriately,<br />
if they are in different photos then you will need to set the mode manually.<br />
<br />
Typically ''horizontal'' and ''vertical'' points are used either to [[Leveling a Finished Panorama|level a spherical panorama]]<br />
or to [[Perspective correction|correct perspective]].<br />
<br />
=== Straight line control points ===<br />
<br />
Adding [[straight line control points]] is basically the same as<br />
creating '''horizontal control points''' and '''vertical control points''', except that you<br />
need more than just one pair to make up a straight line.<br />
<br />
Create a pair of points in the '''hugin Control Points tab''', then pick<br />
'''Add new line''' in the '''mode''' pull-down. This first line will be called<br />
'''Line 3''', you can assign more pairs of points to it using the same<br />
'''mode''' pull-down.<br />
<br />
== Keyboard shortcuts ==<br />
<br />
Here is a summary of the keyboard shortcuts available in the Control Point tab:<br />
<br />
Key Function<br />
<br />
* '''a''' add a new point that has been selected in both images, and the '''auto add''' is switched off.<br />
* '''f''' fine tune currently selected control point pair. Same as the '''Fine Tune''' button<br />
* '''g''' experimental control point generation algorithm.<br />
* '''Del''' Remove currently selected control point.<br />
* '''0''' Zoom out to full view.<br />
* '''1''' 100% view.<br />
* '''arrow keys''' nudge a selection point or selected control point around pixel-by-pixel.<br />
* '''shift + arrow keys''' scroll both images at the same time.<br />
<br />
Mouse function Function<br />
<br />
* '''control key + mouse movement''' Scroll image under cursor<br />
* '''shift key + mouse movement''' Scroll both images<br />
* '''left button''' Use left mouse button to select new points or drag existing points.<br />
* '''right mouse button''' Add control point, if '''auto add''' is switched off<br />
* '''middle mouse button''' Scroll image under cursor<br />
* '''shift + middle mouse button''' Scroll both images<br />
<br />
__NOTOC__<br />
[[Category:Software:Hugin]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Hugin_Control_Points_tab&diff=12304Hugin Control Points tab2010-04-09T01:56:57Z<p>Mfwitten: Only shift+<arrow key> seems to move the image panes around as stated. Plain <arrow key> moves around a selected control point .</p>
<hr />
<div>[[Control points]] are central to [[Panorama Tools]] and [[hugin]], because they are used to estimate the position of image position and lens parameters described above.<br />
A control point specifies a corresponding point between two images. Using these corresponding points, the [[hugin Optimizer tab]] can estimate the image position and lens parameters.<br />
It is therefore important that the control points are accurate and usually at least 3 well distributed control points should be used to estimate the image position ([[yaw]], [[roll]] and [[pitch]]) and maybe the [[Field of View|HFOV]].<br />
For accurate estimation of the a,b,c distortion parameters, many well distributed control points, and a large overlap (up to 50%) are required.<br />
<br />
The Tab consists of two image displays and associated pull-down lists to switch images to be edited.<br />
The bottom contains a list view where Points can be selected and some fields to edit a selected point.<br />
Points can also be selected by clicking or dragging on them in the images.<br />
It is possible to zoom out to show the full image.<br />
<br />
Entries in the pull-down lists have a coloured block indicating the average quality of the control-points between the selected photos, a short red block indicates a 'bad' alignment, whereas a larger green block indicates a 'good' alignment. No coloured block indicates that there are no control-points between the photos.<br />
<br />
Adding a control point works by selecting one point in the left or right image, and then clicking onto the corresponding point in the other image.<br />
If '''auto add''' is not set, the points can be moved by clicking at some other place in the images.<br />
They are added to the list of control points by pressing the '''right mouse button''', the '''a''' key or by pushing the '''Add''' button.<br />
If you press the '''right mouse button''' when only one point is selected, the point selection will be aborted.<br />
'''auto add''' adds the control point as soon as both points have been specified.<br />
<br />
If the images are zoomed out (fit to window), the first click zooms to a temporary 100% view to give you the chance to refine your selection.<br />
Note that only the second click will trigger the auto estimate.<br />
<br />
For good results, the [[control points]] should be as accurate as possible. However, it is often tedious to select a particular point exactly, and it may be helpful to use the '''arrow keys''' (''left'', ''right'', ''up'', and ''down'') to nudge the selection point in various directions pixel-by-pixel (users of X11 may need to ensure that a particular image pane has the focus by placing the mouse cursor within its bounds). Once a point pair has been roughly selected, the '''fine tune''' function of [[hugin]] can be used to estimate the corresponding point up to one tenth of a pixel.<br />
The keyboard short cut for the '''fine tune''' function is the '''f''' key.<br />
Fine tune only search in a small neighbourhood of the currently selected points.<br />
The size of this neighbourhood can be controlled by opening the [[Hugin Preferences]] panel and setting the '''Local area search width'''.<br />
<br />
Note that the fine tune function estimates the translation of the patch around the point selected in the other image with respect to the current image.<br />
This works well if the rotation between the images is small and narrow angle lenses have been used.<br />
If wide angle or [[Fisheye Projection]] images are used, rotation search should be activated in the [[Hugin Preferences]] panel.<br />
Then [[hugin]] also searches for rotated occurrences of the patch around the selected point.<br />
<br />
The image can be scrolled by pressing the '''middle mouse button''' or the '''CTRL''' key while moving the mouse.<br />
If the '''shift''' key is pressed instead, both images will be scrolled.<br />
This is very useful if [[control points]] are set using the 100% zoom level.<br />
<br />
Control point creation is also influenced by the following check boxes:<br />
<br />
* '''auto fine tune''' [[hugin]] helps you to find the second point by looking for it in a search region (shown by a rectangle around the cursor). This might not always work, but usually is reliable, if the image distortions are not too big. Try and play with it.<br />
* '''auto add''' A control point is automatically added when both points are known. You won't have time to refine the selection before adding the point.<br />
* '''auto estimate''' Tries to estimate the position of the second point by estimating the translation between the two images. This is very crude and probably only works for single row panoramas created from [[Rectilinear Projection]] images.<br />
<br />
All these flags can be combined. I typically use '''auto fine tune''' and '''auto estimate''' at the same time.<br />
Then [[hugin]] usually automatically selects the second point correctly, at least for normal, [[Rectilinear Projection]] images that are not rotated too much.<br />
<br />
[[hugin]] also includes an experimental [[control points]] creation algorithm.<br />
It can be invoked by pressing the '''g''' key. Corners in the currently selected image are detected, and corresponding control points are set based on the current relative positions of the two images. The images need to be approximately aligned already for this to be useful. Note that these points then need to be aligned by eye, with the '''Fine-tune''' button or with the '''Fine-tune all Points''' function in the Edit menu of the [[Hugin Main window]].<br />
<br />
== Control point mode ==<br />
<br />
Use the '''mode''' pull down menu to change the type of an existing pair of [[control points]].<br />
<br />
=== normal control points ===<br />
<br />
The '''normal''' control point mode is used to align pairs of overlapping photos by matching<br />
identical features in both photos.<br />
<br />
=== vertical line and horizontal line control points ===<br />
<br />
Pairs of [[vertical control points]] and [[horizontal control points]] are different from<br />
'''normal''' control points since they are used to align input images to particular alignments<br />
in the output panorama rather than simply stitching images together.<br />
<br />
Select two points along a feature that you want to be aligned vertically or horizontally in<br />
the final panorama. If these are in the same photo, [[hugin]] will usually detect that you are<br />
trying to create ''horizontal'' or ''vertical'' control points and set the mode appropriately,<br />
if they are in different photos then you will need to set the mode manually.<br />
<br />
Typically ''horizontal'' and ''vertical'' points are used either to [[Leveling a Finished Panorama|level a spherical panorama]]<br />
or to [[Perspective correction|correct perspective]].<br />
<br />
=== Straight line control points ===<br />
<br />
Adding [[straight line control points]] is basically the same as<br />
creating '''horizontal control points''' and '''vertical control points''', except that you<br />
need more than just one pair to make up a straight line.<br />
<br />
Create a pair of points in the '''hugin Control Points tab''', then pick<br />
'''Add new line''' in the '''mode''' pull-down. This first line will be called<br />
'''Line 3''', you can assign more pairs of points to it using the same<br />
'''mode''' pull-down.<br />
<br />
== Keyboard shortcuts ==<br />
<br />
Here is a summary of the keyboard shortcuts available in the Control Point tab:<br />
<br />
Key Function<br />
<br />
* '''a''' add a new point that has been selected in both images, and the '''auto add''' is switched off.<br />
* '''f''' fine tune currently selected control point pair. Same as the '''Fine Tune''' button<br />
* '''g''' experimental control point generation algorithm.<br />
* '''Del''' Remove currently selected control point.<br />
* '''0''' Zoom out to full view.<br />
* '''1''' 100% view.<br />
* '''arrow keys''' nudge a selection point or selected control point around pixel-by-pixel.<br />
* '''shift + cursor keys''' scroll both images at the same time.<br />
<br />
Mouse function Function<br />
<br />
* '''control key + mouse movement''' Scroll image under cursor<br />
* '''shift key + mouse movement''' Scroll both images<br />
* '''left button''' Use left mouse button to select new points or drag existing points.<br />
* '''right mouse button''' Add control point, if '''auto add''' is switched off<br />
* '''middle mouse button''' Scroll image under cursor<br />
* '''shift + middle mouse button''' Scroll both images<br />
<br />
__NOTOC__<br />
[[Category:Software:Hugin]]</div>Mfwittenhttps://wiki.panotools.org/index.php?title=Hugin_Control_Points_tab&diff=12303Hugin Control Points tab2010-04-09T01:48:02Z<p>Mfwitten: Arrow keys</p>
<hr />
<div>[[Control points]] are central to [[Panorama Tools]] and [[hugin]], because they are used to estimate the position of image position and lens parameters described above.<br />
A control point specifies a corresponding point between two images. Using these corresponding points, the [[hugin Optimizer tab]] can estimate the image position and lens parameters.<br />
It is therefore important that the control points are accurate and usually at least 3 well distributed control points should be used to estimate the image position ([[yaw]], [[roll]] and [[pitch]]) and maybe the [[Field of View|HFOV]].<br />
For accurate estimation of the a,b,c distortion parameters, many well distributed control points, and a large overlap (up to 50%) are required.<br />
<br />
The Tab consists of two image displays and associated pull-down lists to switch images to be edited.<br />
The bottom contains a list view where Points can be selected and some fields to edit a selected point.<br />
Points can also be selected by clicking or dragging on them in the images.<br />
It is possible to zoom out to show the full image.<br />
<br />
Entries in the pull-down lists have a coloured block indicating the average quality of the control-points between the selected photos, a short red block indicates a 'bad' alignment, whereas a larger green block indicates a 'good' alignment. No coloured block indicates that there are no control-points between the photos.<br />
<br />
Adding a control point works by selecting one point in the left or right image, and then clicking onto the corresponding point in the other image.<br />
If '''auto add''' is not set, the points can be moved by clicking at some other place in the images.<br />
They are added to the list of control points by pressing the '''right mouse button''', the '''a''' key or by pushing the '''Add''' button.<br />
If you press the '''right mouse button''' when only one point is selected, the point selection will be aborted.<br />
'''auto add''' adds the control point as soon as both points have been specified.<br />
<br />
If the images are zoomed out (fit to window), the first click zooms to a temporary 100% view to give you the chance to refine your selection.<br />
Note that only the second click will trigger the auto estimate.<br />
<br />
For good results, the [[control points]] should be as accurate as possible. However, it is often tedious to select a particular point exactly, and it may be helpful to use the '''arrow keys''' (''left'', ''right'', ''up'', and ''down'') to nudge the selection point in various directions pixel-by-pixel (users of X11 may need to ensure that a particular image pane has the focus by placing the mouse cursor within its bounds). Once a point pair has been roughly selected, the '''fine tune''' function of [[hugin]] can be used to estimate the corresponding point up to one tenth of a pixel.<br />
The keyboard short cut for the '''fine tune''' function is the '''f''' key.<br />
Fine tune only search in a small neighbourhood of the currently selected points.<br />
The size of this neighbourhood can be controlled by opening the [[Hugin Preferences]] panel and setting the '''Local area search width'''.<br />
<br />
Note that the fine tune function estimates the translation of the patch around the point selected in the other image with respect to the current image.<br />
This works well if the rotation between the images is small and narrow angle lenses have been used.<br />
If wide angle or [[Fisheye Projection]] images are used, rotation search should be activated in the [[Hugin Preferences]] panel.<br />
Then [[hugin]] also searches for rotated occurrences of the patch around the selected point.<br />
<br />
The image can be scrolled by pressing the '''middle mouse button''' or the '''CTRL''' key while moving the mouse.<br />
If the '''shift''' key is pressed instead, both images will be scrolled.<br />
This is very useful if [[control points]] are set using the 100% zoom level.<br />
<br />
Control point creation is also influenced by the following check boxes:<br />
<br />
* '''auto fine tune''' [[hugin]] helps you to find the second point by looking for it in a search region (shown by a rectangle around the cursor). This might not always work, but usually is reliable, if the image distortions are not too big. Try and play with it.<br />
* '''auto add''' A control point is automatically added when both points are known. You won't have time to refine the selection before adding the point.<br />
* '''auto estimate''' Tries to estimate the position of the second point by estimating the translation between the two images. This is very crude and probably only works for single row panoramas created from [[Rectilinear Projection]] images.<br />
<br />
All these flags can be combined. I typically use '''auto fine tune''' and '''auto estimate''' at the same time.<br />
Then [[hugin]] usually automatically selects the second point correctly, at least for normal, [[Rectilinear Projection]] images that are not rotated too much.<br />
<br />
[[hugin]] also includes an experimental [[control points]] creation algorithm.<br />
It can be invoked by pressing the '''g''' key. Corners in the currently selected image are detected, and corresponding control points are set based on the current relative positions of the two images. The images need to be approximately aligned already for this to be useful. Note that these points then need to be aligned by eye, with the '''Fine-tune''' button or with the '''Fine-tune all Points''' function in the Edit menu of the [[Hugin Main window]].<br />
<br />
== Control point mode ==<br />
<br />
Use the '''mode''' pull down menu to change the type of an existing pair of [[control points]].<br />
<br />
=== normal control points ===<br />
<br />
The '''normal''' control point mode is used to align pairs of overlapping photos by matching<br />
identical features in both photos.<br />
<br />
=== vertical line and horizontal line control points ===<br />
<br />
Pairs of [[vertical control points]] and [[horizontal control points]] are different from<br />
'''normal''' control points since they are used to align input images to particular alignments<br />
in the output panorama rather than simply stitching images together.<br />
<br />
Select two points along a feature that you want to be aligned vertically or horizontally in<br />
the final panorama. If these are in the same photo, [[hugin]] will usually detect that you are<br />
trying to create ''horizontal'' or ''vertical'' control points and set the mode appropriately,<br />
if they are in different photos then you will need to set the mode manually.<br />
<br />
Typically ''horizontal'' and ''vertical'' points are used either to [[Leveling a Finished Panorama|level a spherical panorama]]<br />
or to [[Perspective correction|correct perspective]].<br />
<br />
=== Straight line control points ===<br />
<br />
Adding [[straight line control points]] is basically the same as<br />
creating '''horizontal control points''' and '''vertical control points''', except that you<br />
need more than just one pair to make up a straight line.<br />
<br />
Create a pair of points in the '''hugin Control Points tab''', then pick<br />
'''Add new line''' in the '''mode''' pull-down. This first line will be called<br />
'''Line 3''', you can assign more pairs of points to it using the same<br />
'''mode''' pull-down.<br />
<br />
== Keyboard shortcuts ==<br />
<br />
Here is a summary of the keyboard shortcuts available in the Control Point tab:<br />
<br />
Key Function<br />
<br />
* '''a''' add a new point that has been selected in both images, and the '''auto add''' is switched off.<br />
* '''cursor keys''' scroll image under the mouse cursor<br />
* '''shift + cursor keys''' scroll both images at the same time<br />
* '''f''' fine tune currently selected control point pair. Same as the '''Fine Tune''' button<br />
* '''g''' experimental control point generation algorithm.<br />
* '''Del''' Remove currently selected control point.<br />
* '''0''' Zoom out to full view.<br />
* '''1''' 100% view.<br />
* '''arrow keys''' nudge a selection point around pixel-by-pixel.<br />
<br />
Mouse function Function<br />
<br />
* '''control key + mouse movement''' Scroll image under cursor<br />
* '''shift key + mouse movement''' Scroll both images<br />
* '''left button''' Use left mouse button to select new points or drag existing points.<br />
* '''right mouse button''' Add control point, if '''auto add''' is switched off<br />
* '''middle mouse button''' Scroll image under cursor<br />
* '''shift + middle mouse button''' Scroll both images<br />
<br />
__NOTOC__<br />
[[Category:Software:Hugin]]</div>Mfwitten