Hi Allan, Thanks for checking. I have one question more (and sorry that I didn't ask it immediately): After the plugin has crashed, can you do in a terminal window: "tail -25 /var/log/system.log". (tail is to show last lines of....., -25 the number of lines to show) Does the system log mention anything regarding the crash?
Harry 2008/12/6 [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > Harry, > > Here is what I see: > > machine - PowerPC G4(3.3) > os - OSX 10.4.11 > > plugin autopano-sift-c "version 2.5.0 for hugin 0.7" > plugin matchpoint with Autopano version 2.4 > plugin Pan-o-matic "Pan-o-matic 0.9.4 by Amael Orlinski <his email> > my version message:0.1" > > The wxExecute message occurs when using any one of the three plugins > and it occurs just at the very end of each successful plugin > operation even though the last plugin output line goes by too quickly > to read. I am guessing the plugin operations were successful because > I have run each of the plugins manually in Terminal using the same > command arguments reported in the wxExecute error message. I did that > by dragging the plugin application from its shown Package Contents > MacOS folder onto the Terminal command line and then typing in the > arguments displayed in the wxExecute error message. Each appeared to > run successfully. The last output line for each was: > > autopano-sift-c - "Notice: guessed image format and field of view, > please check and adjust." > > matchpoint-complete-mac - Notice: guessed image format and field of > view, please check and adjust." > > Pan-o-matic - "Detection took ... seconds." > > I have also examined the control point files these plugins create at / > private/var/tmp/folders.50x/TempraryItems/. Apparently the control > point match files are created when the wxExecute occurs and these > files are identical to the the files created manually as described > above. I happen to also have an Intel Mac where the plugins work > without any problem. The control point files created manually on it > using the same plugins appear identical to the ones on the PPC. > > The problem appears common for each plugin. I would venture to guess > that whatever telltale signal event Hugin is looking for to indicate > a successful points matching is the wrong thing it should be looking > for on the Mac PPC machine. > > Allan > > > On Dec 1, 2008, at 10:20 AM, Harry van der Wolf wrote: > >> >> There are two issues: >> - plugins run correctly but don't finish correctly on (some?) PPC >> models. >> - autopano-sift-C doesn't seem to work correctly for some users (on >> which hardware and OSX version?) >> >> To gain some more insight: >> - please specify where the autopano plugin breaks (at the start, >> during the run, at the end of the run). >> - specify accurate which mac you have. Not just ppc , but whether you >> have a G3, G4 or G5 (or ..?) >> - specify which version of Tiger or Leopard you run, e.g. 10.4.8 or >> 0.4.11 or .. >> >> Harry >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
