@berrinam - I would prefer to see us read it from a "magic variable" instead of a "magic comment." That way we can use the Avisynth scripting language to calculate the AR for us. For example, I often use this function:
Code:
function ResizeAR(clip c, int "dest_x", int "dest_y", string "ar")
{
Assert(!ar.Defined || ar.LCase == "sar" || ar.LCase == "dar",
\ "rb-ResizeAR: If defined, 'print' must be 'sar' or 'dar'.")
dest_x = default(dest_x, c.width)
dest_y = default(dest_y, c.height)
dest_ar = float(dest_x)/dest_y
dar = (float(c.width)/c.height) * (4320./4739)
sar = dar / dest_ar
out = c.LimitedSharpen(dest_x = dest_x, dest_y = dest_y)
return !ar.Defined ? out : out.SubTitle(ar + ": " + string(eval(ar)))
}
It would be great if instead of printing the AR on the screen for manually typing into MeGUI, I could just stick the result into a magic variable.