wxExecute Error with autopano-sift-c

[icysubdweller]

Hi. I'm completely new to panorama generation and completely new to
hugin. Technically, I'm a software guy in embedded development, and
I've been a competent film photographer in past lives, but I'm pretty
new to digital photography. I'm running an older PowerPC based iMac
with Leopard 10.4.11 installed. This week, I picked up the hugin
0.7.0 compiled binaries and started playing with the package. I'm
impressed so far, but I'm having an odd little problem.

I installed the autopano-sift-c plugin that came with hugin. Every
time I click the align button on the Assistant tab of hugin, autopano-
sift-c seems to run correctly, but then afterward, hugin pops up a
dialog box with the following message:

wxExecute Error

Could not execute command: /Users/rodney/Library/Application Support/
Hugin/Autopano/Autopano-SIFT-C 2.5.huginAutoCP/Contents/MacOS/autopano-
sift-c --maxmatches 50 /private/var/tmp/folders.501/TemporaryItems/
ap_reswy01Tg "/Users/rodney/Pictures/Test/974-1.jpg" "Users/rodney/
Pictures/Test/975-1.jpg"

After that, the control points that autopano-sift-c found are not
loaded, and I can only generate panos by plugging in control points
manually.

It doesn't matter which images I'm using or how many images I have
loaded, I always get this message. When I go to directory /private/
var/tmp/folders.501/TemporaryItems and look at the named output file,
it is there and it looks like autopano-sift-c was happy. It even puts
a smiley face in the comment at the end. If I go type the same
command in at a prompt in a Terminal window, the output looks fine
(see the P.S. after my post, sorry if I'm breaking protocol, please
let me know a better way).

So if anyone's seen this error, or can give me some hints how to get
autopano-sift-c and hugin talking to each other correctly on a Mac
running Leopard, I would be much obliged!

Thanks in advanced!
Rodney


P.S. Here's what happens when I run autopano-sift-c manually:

rodney%
rodney%
rodney% ./autopano-sift-c --maxmatches 50 /private/var/tmp/folders.501/
TemporaryItems/ap_restiESGS "/Users/rodney/Pictures/Test/974-1.jpg" "/
Users/rodney/Pictures/Test/975-1.jpg"

APSCpp, enhanced Autopano-sift-c
Filename /Users/rodney/Pictures/Test/974-1.jpg
width 800 height 600

===============================================================================
The use of this software is restricted by certain conditions.
See the "LICENSE" file distributed with the program for details.

The University of British Columbia has applied for a patent on the
SIFT
algorithm in the United States. Commercial applications of this
software may
require a license from the University of British Columbia.
===============================================================================

1828 keypoints found

Filename /Users/rodney/Pictures/Test/975-1.jpg
width 800 height 600
1766 keypoints found

15.4 seconds to find keypoints

Matching; ransac off, ANNmatch on...
ANN kd-tree: 3594 keypoints, cutoff depth 213
100.00%, 3594/3594
Global match search yielded 165 matches
Created 1 match partitions, max l = 1

Filtering... (/Users/rodney/Pictures/Test/974-1.jpg, /Users/rodney/
Pictures/Test/975-1.jpg)
A. Join Filtration: 141 to 141
B. Score Filtration: 141 to 50
Filtered partition [0,1] from 141 matches down to 50

2.0 seconds to match keypoints

Connected component check...
Connected component identification resulted in 1 component:
component 1: /974-1.jpg, /975-1.jpg

Creating output file "/private/var/tmp/folders.501/TemporaryItems/
ap_restiESGS"

You can now load the output file into hugin.
Notice: guessed image format and field-of-view, please check and
adjust.
rodney%
rodney%
rodney%
rodney%
rodney% cd /private/var/tmp/folders.501/TemporaryItems
rodney% cat ap_restiESGS
# Hugin project file generated by APSCpp

p f2 w3000 h1500 v360 n"JPEG q90"
m g1 i0

i w800 h600 f0 a0 b-0.01 c0 d0 e0 p0 r0 v180 y0 u10 n"/Users/rodney/
Pictures/Test/974-1.jpg"
i w800 h600 f0 a=0 b=0 c=0 d0 e0 p0 r0 v=0 y0 u10 n"/Users/rodney/
Pictures/Test/975-1.jpg"

v p1 r1 y1

# automatically generated control points
c n0 N1 x692.286658 y273.783341 X188.825598 Y289.833334 t0
c n0 N1 x702.930146 y239.047101 X200.318823 Y255.874947 t0
c n0 N1 x694.512599 y291.906592 X190.017811 Y307.849922 t0
c n0 N1 x662.307164 y336.795666 X157.090958 Y351.748051 t0
c n0 N1 x692.286658 y273.783341 X188.825598 Y289.833334 t0
c n0 N1 x690.664842 y274.440166 X187.078981 Y290.473482 t0
c n0 N1 x586.071731 y273.775529 X80.374393 Y285.780819 t0
c n0 N1 x690.664842 y274.440166 X187.078981 Y290.473482 t0
c n0 N1 x538.233989 y324.530273 X28.729940 Y336.741398 t0
c n0 N1 x588.711660 y344.756937 X81.165763 Y358.798181 t0
c n0 N1 x700.717003 y223.507501 X198.150590 Y240.290186 t0
c n0 N1 x684.590358 y253.771256 X181.882317 Y269.707670 t0
c n0 N1 x684.590358 y253.771256 X181.882317 Y269.707670 t0
c n0 N1 x573.996686 y258.430236 X68.999662 Y269.698787 t0
c n0 N1 x700.393831 y254.101587 X197.249667 Y270.730102 t0
c n0 N1 x767.330943 y112.071337 X265.909035 Y136.181244 t0
c n0 N1 x772.477728 y124.888451 X270.450617 Y149.121116 t0
c n0 N1 x535.464690 y268.270213 X27.380806 Y278.397861 t0
c n0 N1 x544.622813 y298.285661 X36.187768 Y310.313786 t0
c n0 N1 x717.834337 y166.804077 X216.294175 Y186.627938 t0
c n0 N1 x693.296448 y436.295722 X183.646340 Y450.733098 t0
c n0 N1 x728.921583 y312.027501 X222.688441 Y328.357736 t0
c n0 N1 x718.831682 y325.428211 X212.563486 Y341.394828 t0
c n0 N1 x630.459286 y198.766699 X129.668938 Y211.988165 t0
c n0 N1 x574.081456 y107.428467 X91.425042 Y115.516716 t0
c n0 N1 x707.256873 y332.613529 X201.308719 Y348.143565 t0
c n0 N1 x539.717254 y291.121184 X31.124793 Y302.408873 t0
c n0 N1 x563.237604 y271.884965 X58.096814 Y282.863282 t0
c n0 N1 x695.950630 y214.359275 X194.488912 Y230.905187 t0
c n0 N1 x728.921583 y312.027501 X222.688441 Y328.357736 t0
c n0 N1 x618.867735 y334.614560 X112.807718 Y348.895808 t0
c n0 N1 x716.322652 y141.102326 X215.888465 Y160.362514 t0
c n0 N1 x657.034736 y274.948210 X153.763001 Y289.741315 t0
c n0 N1 x605.794795 y220.351447 X103.428930 Y232.512214 t0
c n0 N1 x563.893857 y234.464433 X58.976167 Y244.767076 t0
c n0 N1 x544.638849 y234.065469 X38.411378 Y243.357306 t0
c n0 N1 x655.718150 y370.261115 X148.923116 Y385.205694 t0
c n0 N1 x643.929877 y307.291368 X139.045100 Y321.847583 t0
c n0 N1 x587.071231 y335.221781 X79.699599 Y349.025760 t0
c n0 N1 x673.303233 y460.469858 X163.705342 Y475.482711 t0
c n0 N1 x604.046144 y235.374174 X101.266429 Y247.694497 t0
c n0 N1 x643.929877 y307.291368 X139.045100 Y321.847583 t0
c n0 N1 x766.285846 y156.748751 X262.915130 Y179.639151 t0
c n0 N1 x682.267854 y237.098909 X180.175619 Y253.144436 t0
c n0 N1 x688.232614 y306.361996 X183.324521 Y321.905283 t0
c n0 N1 x623.743131 y260.664649 X120.832034 Y274.201052 t0
c n0 N1 x645.213362 y274.924198 X141.787756 Y289.124296 t0
c n0 N1 x642.174002 y406.711498 X133.715690 Y421.859603 t0
c n0 N1 x588.142925 y323.150037 X79.830768 Y336.558439 t0
c n0 N1 x776.472041 y157.409951 X272.747611 Y180.637054 t0

# :-)

rodney%

[akse...@gmail.com]

Until this problem is fixed, use one of Harry's older Hugins were the
auto control points works ( 3364 ) and then use the latest for the
remainder of the tasks. One side benefit I discovered with this
technique is that both Hugin versions can run at the same time. Let
one crank the automatic tasks while you use the other for the
interactive tasks.

Allan Seidel

[icysubdweller]

Ooh, that sounds like a good idea. Thanks!

-Rodney

[Kyle]

I've had what seems to be precisely the same problem as Rodney (see
previous posts). This leaves me with two concerns about the autopano-
sift-c:

1. _Why_ is the error occurring? (and do the developers know about
it)?
2. Would it be possible for you to give a bit more detail on how to
run two versions of Hugin simultaneously? I'm afraid I can't see how
to do that with a single set of images at this point ...

-thanks very much,
Kwill

On Oct 20, 8:03 pm, "aksei...@gmail.com" <aksei...@gmail.com> wrote:

[Harry van der Wolf]

I'm not the developer of autopano-sift-C. I'm one of the packagers.
I will have a look at the issue and if neccessary make a new
autopano-sift-C plugin.
In the mean time try the latest build 3562 (10 days old) and download
and try the panomatic 0.9.4 p1 plugin from my website (August 24 in
the 0.7 table. I should split that table as the plugins are not
related to 0.7 or 0.8). The panomatic plugin should work fine on all
Mac's (hardware) and OSX 10.4/10.5 and is much faster too.

Please let us know.

Hoi,
Harry



2008/11/30 Kyle <will...@gmail.com>:

[akse...@gmail.com]

Not here. All of the three control point plugins error in the same
way. They go through their functions without a hitch. You can see
this in their verbose progress outputs. The error occurs when they
are finished.

Allan

[Harry van der Wolf]

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

2008/12/1 akse...@gmail.com <akse...@gmail.com>:

[Bob Campbell]

Hey Harry. Thanks for everything. Here's my info:

Powerbook G4 1.67 Ghz, OS 10.4.11.

When the wx error first started popping up, I tried changing some of
my environment vars (PATH and LD_LIBRARY_PATH) and running hugin from
a terminal with "open hugin". That made the problem go away for a
bit, and that was a beta or two before the release. Unfortunately, I
didn't track the beta-0.7.0 version where I first noticed the problem,
but it seemed to come and go.

I've been using MacPorts for wxWidgets, enblend, and autopano-sift-c
since the beta for 0.7.0 began.
Currently:
MacPorts 1.600
wxWidgets 2.8.9
enblend 3.0
autopano-sift-c 2.4-2903

I've tried with both the built-in control point generator, and with
MacPorts' autopano-sift-c. Both appear to fail upon completion.

However, I made videos of the process so you can watch it in action:
The plugin version:
http://yourebelscum.com/video/hugin_wx_error.swf
The macports apsc version:
http://yourebelscum.com/video/hugin_wx_error-macport_apsc.swf

(plug - movies made with Jing, I am not affiliated)


Bob Campbell

[Harry van der Wolf]

Hi Bob,

Thanks for your complete reply. I note that you use the Assistant Panel.
Do you experience the same error if you "just" use the non-automatic
workflow, e.g.
- going to the "Images" panel and opening or dragging the images into the table.
- Select the images you need.
- click the "create Control points" button.

(And thanks for bringing Jing to my attention. nice tool).

Harry

2008/12/2 Bob Campbell <thebobc...@gmail.com>:

[Bob Campbell]

On Dec 3, 7:27 am, "Harry van der Wolf" <hvdw...@gmail.com> wrote:
> Hi Bob,

>
> Do you experience the same error if you "just" use the non-automatic

> workflow, [...]

Just tried and yes, the exact same thing happens with both the plugin
and the external apsc.

> (And thanks for bringing Jing to my attention. nice tool).

Yeah, I figured it might come in handy for some tutorials (plus it
runs on Mac and Windows).


I do have Xcode (v 2.5). I could probably try my hand at building a
PPC-only package. Haven't used Xcode to build something of this
complexity, though.


Bob Campbell

[Harry van der Wolf]

2008/12/4 Bob Campbell <thebobc...@gmail.com>:

Please try. We would welcome another mac bundle builder.
Please take a look first at the wiki
<http://wiki.panotools.org/Build_a_MacOSX_Universal_Hugin_bundle_with_Xcode>

If you need any help (and I'm affraid you will), please contact me.

Harry

>
>
> Bob Campbell
>
> >
>

[Bob Campbell]

On Dec 4, 9:55 am, "Harry van der Wolf" <hvdw...@gmail.com> wrote:

> Please try. We would welcome another mac bundle builder.
> Please take a look first at the wiki

> <http://wiki.panotools.org/Build_a_MacOSX_Universal_Hugin_bundle_with_...>

Will do!

> If you need any help (and I'm affraid you will), please contact me.

No doubt. I tried building an early beta-0.7.0 version with Fink and
it's packages. I managed to escape with my sanity. Luckily, I don't
have much to begin with. :)

By the way, thanks for all you've done to support the Mac version.
Ippei, too.


Bob

[akse...@gmail.com]

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

[Harry van der Wolf]

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 akse...@gmail.com <akse...@gmail.com>:

[akse...@gmail.com]

Harry,

Nothing is mentioned in the log regarding the crash.

Allan