I'm using Version 0.7.0-svn3398M and it worked fine for the first pass
through and make a good pano, although it didn't really use any of the
zenith shot information in the final blend there were no serious
errors.
But when I added a few control point for the zenith shot and tried to
optimize, nothing happens. If I ask it to stitch, it will ask for a
file name for the output and the stitching progress window pops up, a
few lines are written and then the progress window closes. No output
file is written to disk.
I took the same .pto file and stitched it with Hugin .061 with no
issues so I think the .pto file is ok. I haven't rebooted yet because
I'm running some other programs I don't want to shut down yet. I'll
try these files on a different machine.

iBook g4 1.33ghz OS 10.5.4

Ian Sights

On Tue, Sep 9, 2008 at 2:39 PM, Steve Rigby <[EMAIL PROTECTED]> wrote:
>
>
> On Sep 9, 2008, at 12:15 PM, Michael Galloway wrote:
>
>>
>> On Mon, Sep 08, 2008 at 02:23:13PM -0400, Steve Rigby wrote:
>>>
>>>    I get the "dreaded" wxExecute error during control point
>>> generation with RC5plus.  I do not get this with RC4.  I am back to
>>> working with and evaluating RC4.
>>>
>>>    Steve
>>>
>>
>> i get some of these too when i use autopano-sift and matchpoint.
>> seems to be
>> related to spaces in paths to the image files.
>
>   Very interesting.  I was using Panomatic as opposed to the
> routines you mentioned.  However, there are spaces in my path names.
> I'll have to look into this.
>
>   Steve
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

Reply via email to