 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Hi there!
I would much appreciate some help with a recurring problem:
I photograph a circular object using, say, 64 shots. APP is unable to merge these into one pano 
When I generate a pano for the upper and the lower half separately, each one of these two panos is stitched flawlessly.
Using the generated pics I tried joining them with Photomerge in CS2. Quite apart from the degradation to 8 bit, the result was miserable (one more reason to stick with APP ;-)
Is there a way to join these panos to a whole again?
Offline
Do you have sufficient overlap between the two rows? I assume it is two rows?
Offline
mediavets wrote:
Do you have sufficient overlap between the two rows? I assume it is two rows?
Hi mediavets,
Thank you for your very rapid response!!
Overlap is sufficient. Maybe I didn't state my problem clearly enough 
Tha pano consists of 8 x 8 shots (using a pano head). When I try to let APP merge these shots into one pano I get no result at all: everything is mixed up
When I split the shots between two pano-files: the top most one consisting of 30 pics, and the bottom one of 42 (for overlap), APP generates two near perfect panos.
My thought was to merge these two panos, which I don't kwow how to accomplish.
Of course, this would be just a crutch, and maybe there is a better method to bring APP to place the individual shots in their correct positions.
Kind regards,
Enkidu
Offline
I see no reason why APP should not be able to handle an 8x8 matrix shot using a pano head.
How large are your images? - could you put the image set on the Web so I could download it and have a look to see what the issue might be? And/orpost reduced size versions of your two 'near perfect' sub-panos on the forum - max. size allowed for posting is 4000x3000 pixels and 800 KB for each image but you may have up to 20 in each post.
I wonder if you have too much overlap or if the subject is an unusal one with perhaps a lot of repeating elements (that can sometimes give APP's auto CP detection a headache)?
I hope you are using APP 1.4.2 and not APG alpha 1.9 - the latter is not ready for prime time and has all sorts of problems with CP detection at this early stage of development.
Last edited by mediavets (2008-10-26 13:26:22)
Offline
Hi Andrew,
* I do use APP 1.4.2
* "subject is an unusal one with perhaps a lot of repeating elements" - that's the case.
* Shots are 10 MPix each and saved as dng's. I could compress the as jpg's and mail them to you if you gave me your email address.
Thanks again,
Jan Willem
Offline
Enkidu wrote:
Hi Andrew,
* I do use APP 1.4.2
* "subject is an unusal one with perhaps a lot of repeating elements" - that's the case.
* Shots are 10 MPix each and saved as dng's. I could compress the as jpg's and mail them to you if you gave me your email address.
Thanks again,
Jan Willem
Have sent you 2 messages via email from your forum profile email link.
Posting reduced size versions of your two 'half panos' on the forum using image upload feature (to be found below message entry box) would provide a very useful 'context' for this discussion.
Last edited by mediavets (2008-10-26 13:47:17)
Offline
Hi Andrew,
Thank you again for all te trouble you're willing to take!
However, I have to interrupt for now as the family needs attention 
Will post the *.pano files here & mail the pics to you tomorrow evening.
Have a nice Sunday!
Jan Willem
Offline
Enkidu wrote:
Hi Andrew,
Thank you again for all te trouble you're willing to take!
However, I have to interrupt for now as the family needs attention
Will post the *.pano files here & mail the pics to you tomorrow evening.
Have a nice Sunday!
Jan Willem
I had a lot of help from others when I started with APP - still need and get help too.
So it's my 'turn' to repay that debt.
*.pano files are not much use to me - they mainly describe the positions of the images in the stitch. What would be good to post here on the forum are reduced size versions of the final stitched images - as jpegs - of the two halves of your pano that you say come out 'near perfect'.
Till later,
Offline
Enkidu wrote:
That pano consists of 8 x 8 shots (using a pano head). When I try to let APP merge these shots into one pano I get no result at all: everything is mixed up
When only 4 shots are used APP sometimes create useless, bad or completly wrong links. When using 8 x 8 = 64 shots the amount of completly wrong links can grow up to a terrible amount!
Two possible solutions are described there http://www.autopano.net/forum/p31366-to … -42#p31366 but using the stack feature as described in this post http://www.autopano.net/forum/t4593-bra … age-stacks would be a better solution.
+1 +-+-+-+-+-+-+-+
| | | | | | | |
0 +-+-+-+-+-+-+-+
| | | | | | | |
-1 +-+-+-+-+-+-+-+
or
+1 + + + + + + + +
| | | | | | | |
0 +-+-+-+-+-+-+-+ <-- better
| | | | | | | |
-1 + + + + + + + +In the future, if what is described above is not enough, another possible solution could be to use the template feature to forbid APP creating those unwanted links.
Last edited by GURL (2008-10-26 19:47:12)
Offline