Thanks for your reply. If I were to use the exact same "preset configuration" in Papywizard to take six different Gigapixel panoramas in six geographically different locations, won't the number of rows, number of images per row, and the XML data that is sent to Autopano pro be 100% identical for each of the six panoramas? I think Papywizard is generating XML data values by "dead reckoning" and that it's 100% repeatable if the user preset remains the same. If that is not the case, then what "real time" sensor inputs are taken into account?
Some basics: when you shoot a mosaic gigapixel you view at your scene, choose a point where to start and then a point where to end. Right?
The steps between the two points are calculated by the controller depending on where you start and where you end. ThatÂ´s what PapyWizard does and thatÂ´s what the TC does.
Shootings spheres always followes the same pattern, related tà³ the lens and sensor. So you can pre-define a pattern - because a sphere is a sphere. Always and anywhere.
In angle-mode itÂ´s easier: the TC works in a way that it starts from the center of the FOV going left and right and up and down. To fix a center of a scene easily can be done by using a viewing-mask, define a centerpoint, aim the camera to it and start. So you can very well use a pre-defined pattern for that.
A pre-defined mosaic pattern you start on a start- and an end-point - using it on different scenes that means just guessing: you donÂ´t have an exact orientation where to start and where to end - where to aim the camera to. I guess thatÂ´s possible also . . . but i wonder whether you would get what you want . .
So in that case a pre-defined pattern wouldnÂ´t be of any help in my eyes.