Search results

Jump to navigation Jump to search
  • ...ma, at the very least this involves [[optimization|optimising]] the camera positions and then rendering the output. == Optimising positions and geometry ==
    20 KB (2,958 words) - 18:34, 17 April 2017
  • ...you deselect this option, it will create the stacks but will not link the positions of the images (e.g. when shooting free hand).
    11 KB (1,738 words) - 20:48, 3 March 2023
  • In the [[Hugin Preview tab]], you have options to check your images and positions, the white balance, control points (equal points in two overlapping images)
    6 KB (877 words) - 17:59, 5 January 2019
  • # The optimizer tries to determine the images positions (without actually looking at the images) such that the mean error between c # The image positions are written back in the script file.
    12 KB (1,844 words) - 14:35, 21 November 2022
  • determine image positions, correction parameters, and automatically suitable Graphic program (eg move the layers and set seam positions),
    14 KB (2,051 words) - 09:58, 22 May 2011
  • ...on, it would make no sense since the images are from different overlapping positions inside the same image circle of the lens which has not moved between shots.
    5 KB (963 words) - 15:54, 25 May 2017
  • * '''--set=y=0,p=0,r=0''' will reset all image positions.
    6 KB (989 words) - 10:15, 31 May 2020
  • ...[[roll]] and [[pitch]] of the input images without changing their relative positions, levelling the panorama in the process. This normally produces good result ...al transform''' to rotate the input images without changing their relative positions - Effectively this rotates the entire panorama. Enter [[roll]], [[pitch]] a
    16 KB (2,731 words) - 14:23, 24 February 2013
  • * Edit the positions of the images in the final panorama
    8 KB (1,194 words) - 10:57, 25 December 2018
  • ...point adjustment, since you can then set control points at fractional grid positions.
    8 KB (1,304 words) - 22:17, 17 March 2007
  • ...ed, 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
    9 KB (1,514 words) - 08:56, 30 May 2015
  • ..., '''Top''', '''Right''' and '''Bottom''' where you can manually enter the positions of the four edges. The origin is top-left and numbers indicate the distanc
    8 KB (1,409 words) - 19:58, 31 October 2014
  • ...dn't vary much for future projects. The advantage of this is that if only positions are being optimised in the [[hugin Optimizer tab]], then as few as two or t
    11 KB (1,716 words) - 14:02, 26 January 2013
  • This setting is for finding control points in panorama, in which the rough positions of the images are already known (e.g. when using a template or when generat
    11 KB (1,721 words) - 18:12, 29 January 2024
  • ...d then hugin will group the input images into exposure stacks by comparing positions, any images with more than 70 % overlap are grouped like this. Each of the
    12 KB (1,761 words) - 14:34, 21 November 2022
  • ...method''' to run [[cpclean]], this will try to remove control points with positions that are not credible under pairwise optimisation.
    19 KB (3,054 words) - 17:26, 6 March 2024
  • ...ve before the second shot is taken, they will appear in slightly different positions on the two images. The result will be TWO shadowy images, with the backgrou
    18 KB (3,211 words) - 21:40, 11 September 2010

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)