On Tue 03-Mar-2009 at 17:36 +0100, Oskar Sander wrote: > >According to the sample script in the wiki PTOptimizer have arguments >for receiving XYZ camera positions for the images and also optimizing >using these in the scripts. However with a warning that these are >intended for PTStereo only.
Sorry, PToptimizer doesn't know anthing about X,Y,Z values. PTStereo uses the same file-format, so they are documented together. >Would there be any problem of actually using PTOptimizer to optimize >these parameters by manually adding these to a Hugin generated >project, or is this "dead code" in PT Optimizer? All this 3d code was in the PTStereo executable, but Helmut never released the sources. >I am guessing on the workflow, (maybe it is presented somwhere?) but >after optimizing I guess you need to stitch and re-project the image. PTStereo did the optimisation and the rendering all at once. >And the issue would be that these programs, i.e. PTMender/PTSticher >does not handle these paramters, right? Yes -- Bruno --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
