hugin 2018 shell scripting

[Christian John]

Hi all,

http://hugin.sourceforge.net/tutorials/hugin-2015.0.0/en.shtml

Many of the commands in this tutorial are not available in the 2018 version of hugin, and I'm wondering if there is an updated approach available somewhere.

When I navigate to the hugin-tools folder and run `ls` these are the available tools:

deghosting_mask fulla hugin_stacker pto_lensstack pto_move tca_correct

enblend hugin_executor pano_trafo pto_mask pto_template vig_optimize

enfuse hugin_lensdb pto_gen pto_merge pto_var

So, `cpfind`, `cpclean`, `linefind`, `autooptimiser`, and `pano_modify` are all missing from my toolkit. Ultimately I don't want to stitch a panoramic, but instead generate a bunch of uncropped files that are aligned with a common origin.

Best,

Christian

[Terry Duell]

Hello Christian,

On Tue, 08 Jan 2019 07:38:27 +1100, Christian John <clj...@gmail.com>
wrote:

[snip]

>
> So, `cpfind`, `cpclean`, `linefind`, `autooptimiser`, and `pano_modify`
> are
> all missing from my toolkit. Ultimately I don't want to stitch a
> panoramic,
> but instead generate a bunch of uncropped files that are aligned with a
> common origin.
>

I am running a build of the current development source (2018.1.0) on
Linux, and all these tools are available here.
What OS are you using, and how did you install hugin?

Cheers,
--
Regards,
Terry Duell

[Christian John]

Hi Terry,

I downloaded hugin using the dmg download from https://sourceforge.net/projects/hugin/files/latest/download. That's just hugin 2018.0.0... Working on a mid-2012 macbook osx 10.13.6. Is there a better way to get the most up-to-date version? 

Best,

Christian

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/op.zu9n8wlyrs0ygh%40localhost.
For more options, visit https://groups.google.com/d/optout.

[Terry Duell]

Hello Christian,

On Tue, 08 Jan 2019 08:55:52 +1100, Christian John <clj...@gmail.com>
wrote:

> Hi Terry,
>
> I downloaded hugin using the dmg download from
> https://sourceforge.net/projects/hugin/files/latest/download. That's just
> hugin 2018.0.0... Working on a mid-2012 macbook osx 10.13.6. Is there a
> better way to get the most up-to-date version?

Those tools have all been part of hugin for some time, so should be in
2018.0.0 which is the latest release.
I'm not sure who does the build and packaging for OSX or whether there
have been any known problems with that dmg.
Have you tried, for example, checking from the command line, 'cpfind -h' ?
Another possible check is to have a look inside the dmg (assuming that can
be done), to see if any of those tools are present and where they are
being installed.
I'm not sure I can be much more help, hopefully someone who uses OSX may
be of more help.

[Christian John]

Hey Terry,

Running `$ cpfind -h` in bash returns the error "bash: cpfind: command not found".

When opening the dmg, the same list of tools that came up with `ls` in the original post appears.

Best,

Christian

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/op.zu9q8f02rs0ygh%40localhost.

[AKS-Gmail-IMAP]

Christian, perhaps you have already figured this out.

The tool files in /tools_mac are alias files pointing to the executable files within the MacOS folder that resides within the Hugin application bundle (not the dmg) and the other application bundles like PTBatcherGUI. Apparently /tools_mac does not have an alias for every executable in the MacOS folders. Furthermore some of the alias files point to the MacOS folder in PTBatcherGUI or perhaps HuginStitchProject. For example the enfuse alias does that.

The other executables you mention, such as cpfind, are in the Hugin application bundle’s MacOS folder. Right click on the Hugin bundle (again, not the dmg) in the finder and select Show Package Contents. You can also right click on one of the tool aliases and select Show Original. Keep in mind when doing it that way you might be shown Hugin’s MacOS folder, HuginStichProject’s MacOS folder or PTBatcherGUI’s MacOS folder. Someone else would need to explain why the aliases point to specific bundles. Some of the executables exist in duplicate, perhaps because they are self-contained.

aks

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAH7u1fb84pekec8PT42FnGuXLdOF_d12stKL99VEW7DV9j7RWA%40mail.gmail.com.

[Christian John]

This resolves the problem - thanks!

C

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/589CB1D1-9F51-4C5A-BBB5-0796A58B1692%40gmail.com.

[Niklas Mischkulnig]

I do the mac building/packaging. I'll add the missing tools aliases in the next release.

Am Dienstag, 8. Januar 2019 01:03:04 UTC+1 schrieb aks:

Apparently /tools_mac does not have an alias for every executable in the MacOS folders.

 

Someone else would need to explain why the aliases point to specific bundles. Some of the executables exist in duplicate, perhaps because they are self-contained.

Hugin itself doesn't need enblend, because the stitching itself is done by PTBatcher.app oder HuginStitchProject.app. Each of these three application contains the tools it needs to function (so PTBatcher and HuginStitchProject contain the exact same tools).

Niklas