 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Hi,
I know that we can corect a lot of errors manualy, but i found strange behevior in APP. I tryed many positions from my pano head, i even take photos with 1mm step. And always the same... A little error on top, or more. Only few pixels but always.. Other soft that i tryed dont have this error. More strange is that i shot all from the same position of tripod, and with the same head steps, but this error can appears in 2 difrent places, Somtimes i have 3-4 such errors on panoramas. All samples cames from 1mm steps in nodal point corrections. And 4 shot is from my best nodal point place - im sure of it.
Offline
What camera, lens, pano head and shooting technique are you using?
Are these 360x180 shoots?
Can you put an image set up on the Web somewhere so we can download and test stitch?
My first thought is that your camera body/ sensor is not (quite) at 90 degrees to the arm of your pano head.
Last edited by mediavets (2008-12-16 20:43:33)
Offline
Thx for response.
Olympus E-3 with Zuiko 8mm / Pano-Maxx / 6 shots horizontal
But on 8 shots 6+T+B, i have the same error and always on top of image
Im pretty sure that my camera is on 90 i always check it with libella. And also Easypano and PTGui stich those images without this error.
Sample photos:
http://www.8host.pl/e300/ostrosc.rar
Last edited by sirwiz (2008-12-16 22:09:05)
Offline
Here's a crop from a stitch I rendered using the spline 36 interpolator and Smartblend blender.
This shows the only small stitching error I spotted.
This scene is one that could cause APPs auto CP detection system some problems because there is a lot of plain white wall and ceiling which lacks features for APP to place CPs.
I didn't edit CPs at all but I did force APP to recalculate the focal length by changing one value for focal length defined by the EXIF data - I think that may have helped. I have some recollection that APP does this anyway when dealing with shots taken with FE lens.
I also had to set the lens type to fisheye manually because it seems that info is not provided in the EXIF. I guess you spotted that?
Hope this helps.
I doubt it is anything to do with NPP - as long as your camera/sensor is 90 degrees to the arm. FE lenses have no single NPP anyway and Hans Nyberg has demonstrated that moving the camera back and forth on the upper arm by as much as 5-10mm has little effect if using a FE lens.
Last edited by mediavets (2008-12-17 00:32:46)
Offline
This scene is one that could cause APPs auto CP detection system some problems because there is a lot of plain white wall and ceiling which lacks features for APP to place CPs.
Hopefully the V2.0 of APP giga to be announced next week should be able to handle such images better.
Offline
mediavets wrote:
I didn't edit CPs at all but I did force APP to recalculate the focal length by changing one value for focal length defined by the EXIF data - I think that may have helped. I have some recollection that APP does this anyway when dealing with shots taken with FE lens.
I also had to set the lens type to fisheye manually because it seems that info is not provided in the EXIF. I guess you spotted that?
Yes i know, APP dont recognized zuiko lenses. I manualy edit lenses db to have it by default.
This trick with recalculating focal works at 7.4 i have no misteke. but have some disortion in the middle of image, but it looks better then slashed window.
digipano wrote:
Hopefully the V2.0 of APP giga to be announced next week should be able to handle such images better.
I hope ;] cos i must buy some soft and still testing, cos easypano panoweaver that we buy a lot of time ago gives me low quality, low posibilites of shooting technics and many many more "low's" 
Thanks for advise.
Last edited by sirwiz (2008-12-17 13:05:27)
Offline
I've installed a trial of PTGui 8.02 and I agree that it gave a better rendered pano than APP, even with a very good stitching as Mediavets done with APP.
I think that CP detection is not the only step that can change the result in the final rendered picture. I've imported the .pts file from PTGui in APP v1.4.2, asking to just keep the panotools CPs. APP said the RMS was very good but the rendered picture under APP showed one mistake, not at same place as shown by Mediavets.
I guess that, after CPs detection, lens distortion algo and smartblend work may differ between PTGui and APP that can explain differences between rendering with PTGui or APP
Offline