This problem goes back to mid December 2009 and has affected every OSX issue since then including 2010.5.0-4886_a1cb4a2efa65. On OSX Intel Snow Leopard machines it manifests itself when using the Hugin stitcher when the pto file has already been saved as would be the case when re- stitching an existing project. Stitching on Leopard PPC machines fails also but without any shell residue to follow. Perhaps it is for the same reason. Note that in both cases the PTBatchGUI does not have the problem stitching.
What appears to be happening is that when the pto already exists Hugin suggests a filename that includes the full path of the existing pto file where the hyphen character "-" is substituted for every instance of the normal path separator character in the full pto pathname and also as the first character. It looks like this name is subsequently passed not as a quoted string to enblend, which in turn thinks the first hyphen indicates an enblend parameter "-U" because all the described above substituted full pathnames would start with "-User". It is interesting that this does not happen on Intel Leopard machines when the pto is not existing or when a different name is types in that does not start with "-". However on Leopard PPC machines the stitch fails no matter what, even when on a totally fresh pto condition. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/700283 Title: enblend: error when first filename starts with - Status in Enblend: New Status in Hugin - Panorama Tools GUI: Confirmed Bug description: I get the following error msg using hugin 2010.4.0 on Mac OS 10.6.5. Here's from the log: ... enblend: unknown option "-U" Try "enblend --help" for more information. gnumake: *** [-Users-Volker-Desktop-Hugin Test-DSC_0067-DSC_0074.jpg] Error 1 At this point, hugin has written the modified source pictures for the panaorama to the desiered directory, you can put them together manually using the gimp or something. I also tried successfully to start emblend out of the hugin package via terminal and make it do the job from there. Worked fine, too. to me it seems that the emblend gets a wrong input within hugin. I am not into the depth of any programming, so this is as far as I could get. HTH. _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
