Bug 286382 - panorama stitcher doesn't run and asks for autooptimizer despite hugin is installed
Summary: panorama stitcher doesn't run and asks for autooptimizer despite hugin is ins...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-Panorama (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on: 286018
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-12 01:04 UTC by Petr Zmek
Modified: 2016-07-10 05:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Zmek 2011-11-12 01:04:58 UTC
Version:           2.3.0 (using KDE 4.7.3) 
OS:                MS Windows

When trying to stitch some pictures the stitcher doesn't run and writes

"Unable to find autooptimiser executable.
This program is required to continue.
Please install it from Hugin package provided by your distributor
or download and install the source.
Note: at least, autooptimiser version 2010.4 is required."

instead. Hugin is installed in the latest version, digikam 2.3.0 runs on Win7-32bit and is installed from windows install package from sourceforge (with KDE 4.7.3).

In case of more questions I will try to answer if I'll able to.

Reproducible: Always

Steps to Reproduce:
1. Select few pictures
2. Run Panorama stitcher

Actual Results:  
Panorama stitcher doesn't run

Expected Results:  
Panorama stitcher is working

OS: WindowsNT (i686) release Windows 7
Compiler: cl.exe
Comment 1 Ananta Palani 2011-11-12 18:05:14 UTC
It runs for me and finds Hugin + associated apps just fine (although it doesn't stitch properly, but that seems to be a different issue which we can figure out after).

Have you installed Hugin to default location? 

   C:\Program Files (x86)\Hugin
or
   C:\Program Files\Hugin
?

I had 2010.4 installed, which the panorama plugin found fine. I then installed latest (2011.2) and it found that as well.
Comment 2 Petr Zmek 2011-11-12 18:49:01 UTC
No, I didn't installed it in the default path because of my partitions configuration. I'm not on my pc now, I'll try it in upcoming days. but still - shouldn't it be set to work with various paths? It could be more variable for most users.
Comment 3 Petr Zmek 2011-11-14 17:12:51 UTC
Ananta: I reinstalled Hugin 2011.2 to its default location. No change.

Unable to find autooptimiser executable.
This program is required to continue.
Please install it from Hugin package provided by your distributor
or download and install the source.
Note: at least, autooptimiser version 2010.4 is required.

Any idea?
Comment 4 Ananta Palani 2011-11-14 20:40:00 UTC
Petr,

Did you restart your computer between the time you tried using Hugin from digiKam and the time when you reinstalled Hugin?

I'm not sure how the path is determined, but it is possible that this search may have been cached by KDE helper apps that are launched by digiKam.

If you didn't restart your computer, try restarting. Also, try deleting any 'kipi-panorama-*' folders from here:

C:\Users\<your windows username>\AppData\Roaming\.kde\tmp-<your computer name>\

if that still doesn't work, maybe the plugin author can chime in. If I have time I will try to find out how the plugin determines the location of hugin.
Comment 5 Ananta Palani 2011-11-14 20:42:59 UTC
Also, I just noticed you said you are using KDE 4.7.3, but the version installed by the digiKam package from sourceforge is 4.7.2. Can you go to 'About KDE' under the 'Help' menu in digiKam and confirm your version of KDE?
Comment 6 Benjamin Girault 2011-11-14 22:42:27 UTC
(In reply to comment #4)
> if that still doesn't work, maybe the plugin author can chime in. If I have
> time I will try to find out how the plugin determines the location of hugin.

I do not have a clue about how KDE and Windows interact with respect to that matter. There is currently a patch pending that is linked to this issue and which solves it on MacOS (see the mailing list, or bug #286018 if you want to try it). However, I do not have time right now to review and commit it (I'll have time in approximately one month).
Comment 7 caulier.gilles 2011-11-27 11:01:19 UTC
Ananta, 

Do you tried patch from bug #286018 ?

Gilles Caulier
Comment 8 Ananta Palani 2011-11-28 22:59:03 UTC
(In reply to comment #7)
> Do you tried patch from bug #286018 ?

Yes, I did try it. It will fix this bug but I think it needs some work, as I mention on the patch page.
Comment 9 Ananta Palani 2011-11-30 12:42:32 UTC
(In reply to comment #3)
Petr, there is a work-around for your problem that you can use in the next version (2.4.0) until Benjamin has time to include patch from bug #286018. You can simply add the Hugin bin directory to your computer's PATH environment variable on Windows.

However, adding the path is not enough in 2.3.0 because pto2mk (part of Hugin) crashes. I just committed a fix that will be in 2.4.0. This won't solve your specific problem, but it allows panoramas to be stitched on Windows once digiKam can find Hugin, which will be possible if you manually edit your PATH, or after Benjamin has time to review the patch I mentioned.