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