Hello there, lately I´ve been using the Beta and RC versions of APP3 intensively. The versions run stably and I like the added projections but they won´t stop producing stiching errors in every panorama I´ve tried so far (all multi row, consisting of 18 to 90 pictures each, shot with a panohead). The errors consist in the pictures being combined a bit askew. This forced me to switch back to APP2.6 which stiches the same panoramas just perfectly. I have 32GB RAM which all versions manage to utilize completely, RMS is alway between 1,3 to 2,3. If further information is needed please don´t hesitate to ask.
Hello again, Sorry for the delay, I was too busy yesterday. Out of 18 TIFFs I had APP3RC and APP2.6 render a panorama with the same settings: Detection set to `high´, Mercator projection, Spline64, everything else left at default setting. APP2.6 gains an RMS of 1.59, APP3RC 1.99. I´ve found seven stiching errors in APP3RC´s pano. Depending on the extent of shifting, the askew combinded pictures produce a doubling or smearing effect. The cutouts are not cropped, the first one is always APP2.6, the second one APP3RC.
Hi, also with APP3.0.0 I get the same stiching errors and even a new bug: When I choose "File>Select Images" only folders are visible, but no files. I have to use the detour via "Browse Folder" to be able to select my pictures. I´m already uploading the requested files, but be patient - the upload takes about 10h.
I gave a look at your panorama this morning, and I noticed 2 things. First of all, I rendered it with 2.6.4 and 3.0 Autopano versions. There are stitching defaults in the 2 (with the default options). In some pieces of the panorama, the 2.6.4 version is better, and in some other pieces, the 3.0 one is.
But the main issue with this panorama is the number of images. As there are paralax defaults, stitching 6 overlapping pictures is quite challenging, and indeed the whole middle row in your panorama is useless. I tried to remove images 7 to 12, and re-optimize the whole panorama, the rms decrease a little bit further, and I didn't notice defaults in the resulting panorama.
Could you please give it a try to see if we conclude the same ?
Hello Thomas, you´re absolutely right, I can confirm that skipping the middle row really does the trick! I have always assumed, that more overlapping means better results - now I understand, that more than 50% overlapping even harms. My other panos with stiching errors are also affected by to much overlapping. I will try your skipping-remedy on them, too, and inform you about the results. Thanks a lot for this fundamental insight!
I have always assumed, that more overlapping means better results - now I understand, that more than 50% overlapping even harms. My other panos with stiching errors are also affected by to much overlapping.
25- 30% overlap is about 'right' - more is not better.
Andrew Stephens Nikon D40, Nikkor 10.5mm fisheye, Sigma 8mm f3.5 fisheye, Nikkor 18-55/50/35mm lenses, Nodal Ninja 5 Lite, Nodal Ninja 4 with R-D16, Agno's MrotatorTCS short. Nikon P5100, CP5000, CP995, FC-E8, WC-E63,WC-E68, TC-E2, Kaidan Kiwi 995, Bophoto pano bracket, Agno's MrotatorA. Merlin/Orion robotic pano head + Papywizard on Nokia 770/N800/N810 and Windows 8/XP/2K.