From: D M G. <dm...@uv...> - 2011-01-20 15:03:04
|
Tom> Reviewing & correcting my formulas for converting PT coefficients to portable Tom> ones, I realize that the first order coefficient for the portable form can no Tom> longer be set to 1 - a - b - c, as the present libpano code does in several Tom> places. Tom> The portable a, b, c can be adjusted to make the first order coefficient 1, so Tom> that no new coefficient value need be stored in the project script. But if we Tom> are going to add a keyword, its value could be the first order coefficient. If Tom> that is 1, we have a portable (or null) correction, if 1 - a - b - c, a Tom> traditional one. If something else, something else. Tom> Alternatively we could give the new keyword an integer value that encodes the Tom> correction type: 0 = traditional, 1 = portable converted from traditional, 2 = Tom> portable optimized directly, ... I can't think of many meaningful variations Tom> at present, but more might be discovered later. I have been thinking about adding a variable to specify if the correction parms should preserve the horizontal (default) or vertical depth of field, or shortest-width, or largest width. We could use this parameter for your purposes too. So let me use the first 4 values (from zero for default, and 1, 2, 3) and use any number after for your purpose. Does that suit you? Tom> -- Tom -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . |