VIG_OPTIMIZE("1")
π VIG_OPTIMIZE("1") β the photometric glow-up page
okay bestie, welcome to vig_optimize, section 1 of the manual (a command-line tool, iykyk) π
β¨ NAME β¨
vig_optimize β Optimise photometric parameters. that's it, that's the whole vibe. it makes your numbers look better π
π¦ SYNOPSIS π¦
vig_optimize [options] -o output.pto input.pto
literally that's the shape of it. options, then -o output.pto, then input.pto. slay π
πΈ DESCRIPTION πΈ
okay so Photometric calculation can be performed on the command-line with the vig_optimize tool. and the way this functionally is configured? through 'v' variable lines in the .pto project file β same energy as the autooptimiser tool. fr fr π«Ά
the camera response curve is simplified using the EMoR sensor model, which reduces the variation to five numbers. those are the Ra, Rb, Rc, Rd & Re image (i) parameters β and the default values of 0.0 are equivalent to an 'average' generic sensor. no cap β¨
the vignetting model is represented by a polynomial with four parameters: Va (this is always 1.0 and doesn't need to be optimised, she's perfect) and Vb, Vc & Vd (which default to 0.0 β equivalent to no vignetting). the vignetting centre can also be different from the geometrical centre, and that's specified by Vx & Vy (both default to 0.0) π
Exposure (EV) is represented by a single value Ev (defaults 0.0, equivalent to no-change). short and iconic π
the white balance is represented by multipliers for the red and blue channels: Er and Eb (the defaults of 1.0 are equivalent to no-change) π
a typical 'v' variable line configuration would look like this β i.e. optimise camera response curve and vignetting for image 0 and exposure for images 1, 2, 3 and 4:
v Ra0 Rb0 Rc0 Rd0 Re0 Vb0 Vc0 Vd0
v Ev1 Ev2 Ev3 Ev4
(vignetting centre and white balance are left unchanged β we're respecting their boundaries π)
π₯ OPTIONS π₯
π General options:
-o fileβ Write results to output project. the whole point tbh β¨-vβ Verbose, print progress messages. she's chatty, we love her π¬-p nβ Number of points to extract.-rβ Extract random point (faster, but less accurate). speed vs accuracy, the eternal struggle π-s levelβ Work on downscaled images, every step halves width and height. tiny images, babygirl energy π§-hβ Display help summary.
π οΈ Expert and debugging options:
-i fileβ Read corresponding points from file.-w fileβ Dump corresponding points to file.
π AUTHORS π
Written by Pablo d'Angelo. Also contains contributions from Douglas Wilkins, Ippei Ukai, Ed Halley, Bruno Postle, Gerry Patterson and Brent Townshend. a whole squad, honestly π«Ά
This man page was written by Cyril Brulebois <cyril.brulebois@enst-bretagne.fr> and is licensed under the same terms as the hugin package itself.
and that's the page, babes π Version 2025.0.1, dated 2026-09-22 β bestie the HUGIN crew really said "here's the whole thing, periodt." go optimise something gorgeous πΈπ
β¨
π¦ where this page comes from
- arch rolling: hugin 2025.0.1-5 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms