I am having an output issue with SU 5.7.
If you click on the url below , you will notice a rectangular clipping from the stonework which has been randomly pasted into the upper left area of the image
 
[http://72.249.12.87/Misc_Data/Stitcher_5.7_Bug.jpg]
 
Despite a number of new usage problems with SU 5.7, it has been producing good results up until today and now I am getting these artifacts appearing very consistently.
 
I'm not so sure that the upgrade was a step forward in this case but I am trying to remain open minded about it.  Has anyone else experienced this problem and if so, found a solution?
 
Alan

Dear sir,
can you tell us more about your configuration ?
 
- platform (Windows, MAC) ?
- operating system/version/service pack ?
- amount of RAM ?
- graphic board / driver version ?
- type of screen (diagonal in inch, dual screen) ?
- number and resolution in pixels of input images ?
- format of input images (tiff, jpgs,...) ? 8 or 16 bits ?
- type of render: planar, cylindrical, spherical, QTVR...?
- render format (tiff, jpg, PSD, mov...) ?
- size of the render in pixels ?
 
if you can reproduce the problem with low res images, please send them to stitchersupport@autodesk.com.
 
THANKS A LOT

- platform: Windows
- operating system: XP SP2
- amount of RAM: 2.8 ghz
- graphic board: RADEON 9600 series
- type of screen: 22" LCD
- number and resolution in pixels of input images:1296 x 1936
- format of input images JPG 8 bit
- type of render: spherical
- render format: JPG
- size of the render in pixels: 5212 x 2606

Hi,
that seems to be a standard configuration.
As I said, if you can reproduce the problem with low res images, please send them to stitchersupport@autodesk.com.
 
 
thanks

Dear Alan,
 
can you provide the source-images for download?
I'd like to give it a try.
PS: Nice pano! :-)
 
Best regards
Tim

I don't believe that this problem has anything to do with the input images as I have had no such problems in the past and nothing has changed recently in my work flow.  It is beginning to look , however like it is a memory related issue as I seem to be able to produce this effect when my hard drive is within a few gb of full.