Nick Fan wrote:Any one has a comparison of performance between the Merlin and other more precise motorized head ? Is the stitching speed affected in regard to "creation of templates for automated detention and stitching"?
AlexandreJ wrote:The second kind of panorama without log file is handled this way.
We only know how the shoot has been done, but we don't have any location. With the structure in the shooting, we can have a potential list of pair of image linked too. That's easy. We do detection on them. The optimizer do a standard optimization without coping with unlinked picture. The remaining unlinked picture are then patched with the knowledge of the structure in the shooting stage ( we don't have the location, we have relative information : this image is on the top of this one which is linked : for example ). It's harder to patch but it works many time.
AlexandreJ wrote:Type 2 - Panorama heads that don't create any log file ( gigapan )
mediavets wrote:What do you do in the case where the user has paused the shoot and moved the head back in the sequence to reshoot at one or more shooting positions?
Paul wrote:AlexandreJ wrote:Type 2 - Panorama heads that don't create any log file ( gigapan )
I mean in this case, it does not mention wether the head is motorized or not.
If there is a way that a user could input some basics of the shooting pattern it must be helpful to shorten the detection.
Like:
x by y rows
sequence column by column or row by row, bottom up or top down
movement zigzaged or not
direction from left to right or right to left
spherical or not
Nick Fan wrote:I want to know if the detetion is limited to e.g. 20x20 px for more precise head or 200x200 px for less precise head, will there be a great difference in stitching speed?
AlexandreJ wrote:For the second case of panorama, the current algorithm should work even in this case ( I think that the gigapan stitching solution doesn't handle such case because of a strong matrix assumption in the shooting ).
BTW : If you have a sample set to share, I can check that.
AlexandreJ wrote:mediavets wrote:What do you do in the case where the user has paused the shoot and moved the head back in the sequence to reshoot at one or more shooting positions?
For the second case of panorama, the current algorithm should work even in this case ( I think that the gigapan stitching solution doesn't handle such case because of a strong matrix assumption in the shooting ).
BTW : If you have a sample set to share, I can check that.
mediavets wrote:I think you should have a Merlin/Papywizard system - you'd love it.
AlexandreJ wrote:mediavets wrote:I think you should have a Merlin/Papywizard system - you'd love it.
I have one. Never got the time yet to play with itI'm currently playing with our Clauss Rodeon only.
AlexandreJ wrote:No fma38. It's not the same because you have a log and gigapan don't. So stopping such kind of matrix doesn't create a new entry.
AlexandreJ wrote:( I think that the gigapan stitching solution doesn't handle such case because of a strong matrix assumption in the shooting ).
Users browsing this forum: No registered users and 0 guests