Bug 455226

You downloaded an old Hugin version. Is Hugin 2021 not available for MacOS?

Maik

If digiKam searches for pto2mk, a hugin version < 2015 must have been found.
Maybe you have 2 Hugin versions installed in your system?

Maik

Steve,

 I already trying to install hugin on my mac to use with panorama tool and it sound like not all binary programs are not packaged in DMG.

Please report this problem to hugin project :

https://bugs.launchpad.net/hugin

Gilles Caulier

It appears that version 2019.2.0.b690aa0334b5 built by Niklas Mischkulnig is available for MacOS.



Steve

> On Jun 13, 2022, at 4:41 PM, Maik Qualmann <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=455226
> 
> Maik Qualmann <metzpinguin@gmail.com> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                 CC|                            |metzpinguin@gmail.com
> 
> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---
> You downloaded an old Hugin version. Is Hugin 2021 not available for MacOS?
> 
> Maik
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

Dr. Steven Bishop, Ph.D.
100 Lakebreeze Way
Fredericksburg, VA 22406
+1-540-429-1842

Created attachment 149680 [details]
attachment-30897-0.html

Gilles,
I’ve subsequently learned that I can use TIF files (and not JPG) directly with the Hugin application to make a panorama. So that’s a work around for now. 

Sure, be glad to make the bug report as you suggest later today. 

Thanks!


Steve 

Sent from my Steve's iPad

> On Jun 13, 2022, at 4:55 PM, bugzilla_noreply@kde.org wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=455226
> 
> --- Comment #3 from caulier.gilles@gmail.com ---
> Steve,
> 
> I already trying to install hugin on my mac to use with panorama tool and it
> sound like not all binary programs are not packaged in DMG.
> 
> Please report this problem to hugin project :
> 
> https://bugs.launchpad.net/hugin
> 
> Gilles Caulier
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

Hugin for MacOS is only available as version 2019 - OK. I unpacked the DMG, the hugin_executor file is included. It is probably not found by digiKam, but the other files are probably in the same directory, strange.

Maik

Created attachment 149689 [details]
attachment-19556-0.html

Maik,
I thought DigiKam 7.6.0 is looking for pto2mk and not Hughin_executor.

Steve

Sent from my Steve's iPad

> On Jun 14, 2022, at 11:39 AM, Maik Qualmann <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=455226
> 
> --- Comment #6 from Maik Qualmann <metzpinguin@gmail.com> ---
> Hugin for MacOS is only available as version 2019 - OK. I unpacked the DMG, the
> hugin_executor file is included. It is probably not found by digiKam, but the
> other files are probably in the same directory, strange.
> 
> Maik
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

No, whether digiKam searches for pto2mk depends on which Hugin version was detected. Hugin < 2015 trying to find pto2mk, Hugin > 2015 trying to find hugin_executor. We can in principle remove support for old Hugin versions < 2015.

Maik

Exactly it depends on the returned version of "autooptimiser". As you can see it is 2019.2 in your screenshot. So it is very strange that digiKam is looking for pto2mk. A debug output from the terminal would be interesting.

Maik

Created attachment 149706 [details]
attachment-516-0.html

Maik, 
	I suspect having run Hugin directly yesturday made some changes in my computer.  Today I was able to run the application but with a couple tweaks.  I also downloaded the most recent version of Hugin available just to make sure I had it (2019.2.0.b690aa0334b5 built by Niklas Mischkulnig).

1. See the attached Panorama Creator Wizard screenshot where pto2mk is replaced by hugin_executor but there is no version number.
2. I ran digikam again but got an error message that it could not find enblend.  See the second screenshot and the messages citing having to revert to system path.
3. So I modified my zsh path to include /Applications/Hugin/tools_mac and that made some progress.

sbishop@MacBook-Pro ~ % echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Apple/usr/bin:/Applications/Hugin/tools_mac
sbishop@MacBook-Pro ~ % 

4. But what actually worked and rendered a panorama is starting digikam from the terminal command line rather than from the digikam icon on my Launchpad.

sbishop@MacBook-Pro ~ %  /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam &


But this approach which is likely wrong way to do it, pops up a bunch of warning messages and Error # 11 because of my Affinity Photo images (.afphoto) file type.  See the terminal messages in the attached file.

So it appears to me that the digiKam 7.6.0 installation on Apple MacBook Pro running Monterey 12.4 might need some execution path changes to ensure Hugin’s tools_mac directory is found.  Note: This was an interesting exercise since I haven’t work with Unix commands in quite a while.


Sincerely,

Steve









Steve

> On Jun 14, 2022, at 12:39 PM, Maik Qualmann <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=455226
> 
> --- Comment #9 from Maik Qualmann <metzpinguin@gmail.com> ---
> Exactly it depends on the returned version of "autooptimiser". As you can see
> it is 2019.2 in your screenshot. So it is very strange that digiKam is looking
> for pto2mk. A debug output from the terminal would be interesting.
> 
> Maik
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

Dr. Steven Bishop, Ph.D.
100 Lakebreeze Way
Fredericksburg, VA 22406
+1-540-429-1842

Created attachment 149707 [details]
attachment-516-1.html

Created attachment 149708 [details]
attachment-516-2.html

Created attachment 149709 [details]
attachment-516-3.html

Created attachment 149710 [details]
Screen Shot 2022-06-14 at 4.09.54 PM.png

Created attachment 149711 [details]
Screen Shot 2022-06-14 at 4.12.13 PM.png

Created attachment 149712 [details]
digikam-cli-startup-messages.txt

It is normal that hugin_executor does not show a version number, the tool has no option for it.

It works launched from the terminal but not via the icon?

Maik

Created attachment 149743 [details]
attachment-31640-0.html

While the DigiKam app starts up and runs via the icon I found that it is the updated system PATH and use of the terminal cli that enables the Hugin to work correctly.  Have I done something wrong?

Steve

Sent from my Steve's iPad

> On Jun 15, 2022, at 3:52 AM, Maik Qualmann <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=455226
> 
> --- Comment #17 from Maik Qualmann <metzpinguin@gmail.com> ---
> It is normal that hugin_executor does not show a version number, the tool has
> no option for it.
> 
> It works launched from the terminal but not via the icon?
> 
> Maik
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

@Steve,

Well i don't understand you last comment. What do you mean exactly ?

Also, digiKam 8.0.0 is out. This entry still valid with this release ?

Best regards

Gilles Caulier

@Steve,

Did you seen my last comment ?

Also, digikam 8.2.0 pre-release have been rebuilt using last Qt 5.15.11 + KDE 5.110
frameworks. Installer is available at usual place :

https://files.kde.org/digikam/

Can reproduce the problem with this version?

Thanks in advance

Gilles Caulier

Maik, 

I install Hugin 2019 on my macbook pro. As it's a bundle, at least the 3 program provided must be grant to run to the Mac config panel, else executable cannot be found.

So, after that, it's work to start Panorama tool : 

https://i.imgur.com/y5FStw3.png

...but later, if i try to process a set of files to assemble, hugin report errors :

https://i.imgur.com/vFW2wTE.png
https://i.imgur.com/z3qSwU0.png

Gilles