[digiKam-users] Can't find tools for panorama

[Guy Rutenberg]

Hi,

I'm running 6.0beta using the appimage. It seems that digikam fails to find the binaries needed to create panoramas or stacked images. Those are autooptimiser, cpclean, enblend, enfuse, make, none etc. Oddly enough it does find cpfind... All those binaries are installed and available in /usr/bin. Trying to click on the "Find" button and point it to the right binary doesn't work.

Any ideas?

Thanks,

Guy

[Gilles Caulier-4]

Which Hugin version did you install on your system ?

Gilles Caulier

Le lun. 8 oct. 2018 à 18:25, Guy Rutenberg <[hidden email]> a écrit :

Hi,

I'm running 6.0beta using the appimage. It seems that digikam fails to find the binaries needed to create panoramas or stacked images. Those are autooptimiser, cpclean, enblend, enfuse, make, none etc. Oddly enough it does find cpfind... All those binaries are installed and available in /usr/bin. Trying to click on the "Find" button and point it to the right binary doesn't work.

Any ideas?

Thanks,

Guy

[Guy Rutenberg]

Hi,

---------- Forwarded message ----------
From: Gilles Caulier <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>
Cc: 
Bcc: 
Date: Mon, 8 Oct 2018 22:36:03 +0200
Subject: Re: [digiKam-users] Can't find tools for panorama

Which Hugin version did you install on your system ?

I have hugin 2017 running on Debian Stretch.

Thanks,

Guy

Gilles Caulier

Le lun. 8 oct. 2018 à 18:25, Guy Rutenberg <[hidden email]> a écrit :

Hi,

I'm running 6.0beta using the appimage. It seems that digikam fails to find the binaries needed to create panoramas or stacked images. Those are autooptimiser, cpclean, enblend, enfuse, make, none etc. Oddly enough it does find cpfind... All those binaries are installed and available in /usr/bin. Trying to click on the "Find" button and point it to the right binary doesn't work.

Any ideas?

Thanks,

Guy

[Gilles Caulier-4]

There is no version limitation in pano tool source code about hugin detection.

Which version did you use exactly ? I see that hugin has renamed the 2017.0 as 2017.0.0. This typo is important while detection.

Just run one hugin executable from CLI to see how the version is printed on the console. Mine :

[gilles@localhost manager (master)]$ cpfind --version
Hugin's cpfind 2016.2.0.be8da0221960
based on Pan-o-matic by Anael Orlinski

Gilles Caulier

Le mar. 9 oct. 2018 à 14:11, Guy Rutenberg <[hidden email]> a écrit :

Hi,

---------- Forwarded message ----------
From: Gilles Caulier <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>
Cc: 
Bcc: 
Date: Mon, 8 Oct 2018 22:36:03 +0200
Subject: Re: [digiKam-users] Can't find tools for panorama

Which Hugin version did you install on your system ?

I have hugin 2017 running on Debian Stretch.

Thanks,

Guy

Gilles Caulier

Le lun. 8 oct. 2018 à 18:25, Guy Rutenberg <[hidden email]> a écrit :

Hi,

I'm running 6.0beta using the appimage. It seems that digikam fails to find the binaries needed to create panoramas or stacked images. Those are autooptimiser, cpclean, enblend, enfuse, make, none etc. Oddly enough it does find cpfind... All those binaries are installed and available in /usr/bin. Trying to click on the "Find" button and point it to the right binary doesn't work.

Any ideas?

Thanks,

Guy

[Guy Rutenberg]

---------- Forwarded message ----------
From: Gilles Caulier <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>
Cc: 
Bcc: 
Date: Tue, 9 Oct 2018 17:03:20 +0200
Subject: Re: [digiKam-users] Can't find tools for panorama

There is no version limitation in pano tool source code about hugin detection.

Which version did you use exactly ? I see that hugin has renamed the 2017.0 as 2017.0.0. This typo is important while detection.

Just run one hugin executable from CLI to see how the version is printed on the console. Mine :

[gilles@localhost manager (master)]$ cpfind --version
Hugin's cpfind 2016.2.0.be8da0221960
based on Pan-o-matic by Anael Orlinski

Gilles Caulier

I have hugin 2017.0.0 (I backported it to Debian Stretch).

$ cpfind --version
Hugin's cpfind 2017.0.0.eac5e8cc546e
based on Pan-o-matic by Anael Orlinski

Thanks,

Guy

[meku]

I'm seeing this issue in the most recent 6.0beta and hugin v2018. Bug
created: https://bugs.kde.org/show_bug.cgi?id=403269



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Gilles Caulier-4]

hi,

Yes, probably the CLI tool from huggin has changed the console trace finger print or the options as arguments.

I need to take a look...

Best

Gilles Caulier

Le mer. 16 janv. 2019 à 13:57, meku <[hidden email]> a écrit :

I'm seeing this issue in the most recent 6.0beta and hugin v2018. Bug
created: https://bugs.kde.org/show_bug.cgi?id=403269



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html