I downloaded the AutoPano Giga trial, repeated the import, got a similar result.  See image below.

I had the detection level set to normal.  I was using tiffs; could that be slowing it down? I have tried it again with jpegs and it doesn't seem that much faster. Dust on the sensor isn't an issue - the E-P2 shakes it off the sensor and I don't see any in the pictures; plus, I am already doing the Papywizard import without optimization.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I don't want to muddy the issue, but I wanted to test Papywizard importing in general, so I ran a series of shots using all of the different presets in Papywizard (with my Rokinon 7.5mm fisheye) and imported them.  The results were, shall we say, interesting.

The Import Wizard preview always showed the correct arrangement of images (just as with the gigapixel in this thread.) I did all imports without optimization.  Most of the detected panos looked normal, but a couple of panos were pretty messed up.

One thing I noticed for all of them, even in the ones that looked OK, was that the angles were not the same as the ones in the Papywizard XML file. The roll for each image in the XML is 0°, but is approximately 90° (but not the same for all) in the detected pano. Is that because the camera was in portrait orientation? Another observation is that the yaw and pitch, though similar to the values in the XML file, are different.  Is some sort of transformation being done on the Euler Angles? In the ones where the detected pano is messed up, the detected angles are are far off from the XML values.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

So, I am still stumped.

mediavets wrote:

Does your camera have an orientation sensor? If it does you may be better off disabling it if that is possible.

It does have one, but I made sure all of the images were oriented the same way in Lightroom.  Still, they would all be the same since the pitch is fairly horizontal for all.  The orientation wouldn't be the cause of the problem here anyhow, as far as I can imagine.  The problem here is that they are all virtually at the same position, despite the fact that I didn't have APP optimize the pano.  They should all be in the position given in the Papywizard XML file.  I checked the XML to be sure that it doesn't have something crazy in it and it seems fine (as seen in the Import Wizard preview too!)

It really seems that the files from Papywizard are fine, but for some reason APP isn't positioning the images correctly.

Still no ideas? Anyone from Kolor  willing to take a look at it? I could upload (reduced-sized if needed) jpegs and the xml file. You don't even really need my jpegs, since it isn't optimizing; you could just use some place-holders.

Thanks - I will do that, once I find the ftp, since I haven't done that before

Last edited by jriley (2012-01-20 00:23:57)

I don't think the ftp site is working correctly. I have tried three different ftp clients plus the Mac Finder to connect with no success. It either never responds or wants a name and password, which shouldn't be needed. I have used ftp plenty of times, so I don't think I am doing it wrong.

FTP is working now and the zip file (containing the papywizard XML and log files, a project file, and reduced-size and highly compressed images) is uploading. If reducing the dimensions of the photos is a problem, I can upload them again - just let me know.

I hope this gets it figured out

AlexandreJ wrote:

I checked this case. The issue is in the XML file because all pitch angle are in the range [-67 -90] meaning you shot the nadir only ( with heavy distortion, etc ).
This doesn't correspond at all with the content of this panorama which looks like standard landscape photography where you can see the horizon.
So that's the issue with this case. The xml should be patched by adding some value to all pitch angle ( doesn't look like at +90° is the right answer ).

Alexandre - I can see how this XML could result from not setting the reference point on the head, maybe. I assume the head takes the position when powered on to be (0,0,0) and, if I then pitched -90° from the stored position to attach the camera, it would think it was at (0,-90,0), even though I have the camera pointed at the horizon. I must have failed to "Set Reference" to tell it that was (0,0,0)

The thing that thew me off from realizing that is that the shots look normal in the import window grid.

Also, can you offer insight into why the positions in the detected panorama were different than the ones in the XML file, even though there was no optimization performed?

Now I have to figure out a way to change all of those pitch values without doing it by hand

A final followup: In the end, after advice Papywizard crowd, I ran a simulation in Papywizard with the same number of rows and columns and it looks pretty good. I haven't optimized yet and it looks like the attached image. I am just glad to avoid editing every one of the 344 pitch values in the XML!