hugin-devs team mailing list archive
-
hugin-devs team
-
Mailing list archive
-
Message #00562
[Bug 688380] Re: Assistant / Align unable to run control point detector
It seems that you have unpacked Hugin into a c:\bin\Hugin... folder and
not used the Installer provided on SourceForge.
Since you mention 2009.4: many things have changed in the preferences
and the Installer takes care of them.
There is a button to reset the settings in the preferences. Can you try
to hit that and see what happens?
If it does not help, would you mind trying to use the installer to
install Hugin into standard location rather than unzipping the binaries
into a custom folder? after that install worked, try again your custom-
location binary (and it should work too).
Or, last but not least, can you start RegEdit on your system and delete
the Hugin registry key?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/688380
Title:
Assistant / Align unable to run control point detector
Status in Hugin - Panorama Tools GUI:
Incomplete
Bug description:
I've used 2009.04 successfully on this machine, so intended to give the current 2010 beta a try. Alas, Assistant / Align doesn't work at all. I've installed and configured autopano-sift-c.exe (File/Preferences/Control Point Detectors displays the correct path), but it seems that the assistant isn't able to start any Control Point Detector at all. The .exe isn't called at all.
Unfortunately, a Window displaying some messages is flashed up for only a very short time, so that I am unable to read more than a few words after trying for a few times. It may say something about Create Process failed/File not found, using a typical temporary file name like F:\temp\hamBA28.tmp (got this inspecting hugin.exe using procmon.exe, not by looking at the window). After the window is popped up and destroyed, another windows says "Error / Warning 2 unconnected image groups found [o] [1]". No control points have been detected, that is.
When creating a queue instead, I get the output
process_begin: CreateProcess(NULL, echo Finding control points..., ...) failed.
make (e=2): Das System kann die angegebene Datei nicht finden.
make: *** [all] Error 2
when running the queue. The German sentence says "System couldn't find that file".
After digging somewhat deeper, I noticed that hugin probably tries to run its own make on a temporary makefile.
After replacing make.exe by something which just stops and running
c:make_old -f ham35A4.tmp all
in the temp directory, I get
process_begin: CreateProcess(NULL, echo Finding control points..., ...) failed.
make (e=2): Das System kann die angegebene Datei nicht finden.
c:makeweg: *** [all] Error 2
which looks remarkably similar to what I believe to see flashing by in the aforementioned window.
"echo Findding control points" in CreateProcess looks suspicious, so I removed all @echo links in the
temporary makefile and try again:
F:\temp>c:makeweg -f ham35A4.tmp all
"c:/bin/Hugin_2010.4.0-beta2/bin/icpfind" -o "f:/temp/ha35A3.tmp" "f:/temp/ha35A3.tmp"
004E727C
c:makeweg: *** [all] Error 1
Well, I'm stuck.
Operating System: Windows NT 6.1 (build 7600)
Architecture: 32 bit
Free memory: 1603916 kiB
Active Codepage: 1252 (Western European Windows)
Hugin
Version: 2010.4.0.c379b4821223 built by Matthew Petroff
Path to ressources: c:\bin\Hugin_2010.4.0-beta2/share/hugin/xrc/
Path to data: c:\bin\Hugin_2010.4.0-beta2/share/hugin/data/
References