Re: [hugin-ptx] Re: Linux on Chromebook -> assert ""cr"" failed in wxPaintDCImpl(): using wxPaintDC without being in a native paint event

[Harry van der Wolf]

Hi Thomas,

Thanks, it is good to know it has already been fixed although there is no
2024 build yet..
The wxwidgets versions on my Chromebook debian linux bookworm version are:
apt list --installed | grep -i wx

libwxbase3.2-1/stable,now 3.2.2+dfsg-2 amd64 [installed,automatic]
libwxgtk-gl3.2-1/stable,now 3.2.2+dfsg-2 amd64 [installed,automatic]
libwxgtk-webview3.2-1/stable,now 3.2.2+dfsg-2 amd64 [installed,automatic]
libwxgtk3.2-1/stable,now 3.2.2+dfsg-2 amd64 [installed,automatic]

So I assume this "error" was introduced as of wxwidgets 3.2.x

I don't know yet whether I want to setup a complete dev environment to
compile a fresh Hugin.
Like said: I just wanted to try once more.

I was wrong though about the app images. I thought the latest would be on
top, but the latest is the bottom one:
Hugin_Panorama_Creator-git-20210522-x86_64.AppImage
,
but it is still old.
That one does work, but the screen handling is terribly slow. CP finding,
aligning, stitching, etcetera works full speed.

Harry

Op zo 19 mei 2024 om 10:48 schreef 'T. Modes' via hugin and other free
panoramic software :

> Hi Harry,
>
> this is the same as https://bugs.launchpad.net/hugin/+bug/2045960
> This is already fixed in the repository.
>
> Thomas
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/71ab4143-22cf-4844-9c5f-2968eceed99en%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptgWo%3DauryJ_cLQmJv%3Dv3e4vBTtU%2BL8b7fw5fokmzThqQ%40mail.gmail.com.

[hugin-ptx] Linux on Chromebook -> assert ""cr"" failed in wxPaintDCImpl(): using wxPaintDC without being in a native paint event

[Harry van der Wolf]

Hi,

I am currently using an i5 Chromebook with the default Linux container
available for the Chromebook. The linux version is Debian and on the
lsterst patches.
uname -a
Linux penguin 6.6.21-01327-gc9107f2d4947 #1 SMP PREEMPT_DYNAMIC Wed, 10 Apr
2024 00:40:09 + x86_64 GNU/Linux
hvdwolf@penguin:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 12 (bookworm)
Release:12
Codename:   bookworm

I just wanted to try Hugin once more.
I have the latest release for Debian bookworm installed being
2022.0.0+dfsg-2.
I also tried the latest Hugin app image which is not new or latest at all
as it is Hugin_Panorama_Creator-2019.0.0-20190407-x86_64.AppImage
Both crash with the same error.
Attached one of the crash logs.

My other, old chromebook has an intel celeron n4120 and is also on the
latest Chromebook and Debian bookworm version and encounters the same issue.

I found some topics where it is advised to use some "Refresh(); Update();"
statements. Being completely ignorant of C++/wx_widgets nowadays, I don't
know if that is valid in this case.

Please consider this as low priority. I just wanted to try once more with
Hugin.
It might just be nice if Hugin would also run on Chromebooks with Linux.

Best,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvMd3cKX5hoVfFirEnqFXaK_VRou3wYwaWLYO0mTy89Cg%40mail.gmail.com.
ASSERT INFO:
./src/gtk/dc.cpp(497): assert ""cr"" failed in wxPaintDCImpl(): using wxPaintDC 
without being in a native paint event

BACKTRACE:
[1] wxPaintDC::wxPaintDC(wxWindow*)
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[8] wxWindow::GTKSendPaintEvents(_cairo*)
[9] g_closure_invoke
[10] g_signal_emit_valist
[11] g_signal_emit
[12] gtk_container_propagate_draw
[13] g_closure_invoke
[14] g_signal_emit_valist
[15] g_signal_emit
[16] gtk_container_propagate_draw
[17] g_closure_invoke
[18] g_signal_emit_valist
[19] g_signal_emit
[20] gtk_container_propagate_draw
[21] g_closure_invoke
[22] g_signal_emit_valist
[23] g_signal_emit
[24] gtk_container_propagate_draw
[25] gtk_container_propagate_draw
[26] gtk_main_do_event
[27] g_signal_emit_valist
[28] g_signal_emit
[29] g_main_context_dispatch
[30] g_main_context_iteration
[31] gtk_main_iteration
[32] wxGUIEventLoop::DoYieldFor(long)
[33] wxEventLoopBase::YieldFor(long)
[34] wxAppConsoleBase::Yield(bool)
[35] wxEntry(int&, wchar_t**)
[36] __libc_start_main

Re: [hugin-ptx] Re: Xpano

[Harry van der Wolf]

It is possible to tweak the opencv algorithms for keypoint
detection, feature matching, descriptors, etcetera for both
panos, blending but also "fusing" layers of images.
I wrote an extremely simple python script to try it out for panos and also
write some python scripts for "fusing".
But to be honest: I don't do panos anymore and neither fusing anymore.

There are many opencv  examples on the internet for C++ and for python.


Op vr 3 mei 2024 om 09:10 schreef Bruno Postle :

> On Thu, 2 May 2024, 16:54 'T. Modes' wrote:
>
>>
>> This is "only" a GUI for the panorama functions in the OpenCV. library It
>> does not implement own panorama stitching algorithms.
>> In my simple tests the results were good for some projects, but for other
>> projects it works not so good.
>> There are no possibilities to manually improve/change the result. So it
>> is a hit or miss.
>>
>
> Multiple tools can be good thing. It would be interesting if any of the
> opencv stuff, like feature matching, was dramatically better than the Hugin
> equivalent.
>
> It is a shame if it takes a "one shot" approach and doesn't allow any
> adjustments, this is the problem with the free Microsoft stitching tool.
> Maybe if it had a PTO export it would be more useful.
>
> --
> Bruno
>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/CAJV99Zj8vtR9eG3Dx6EoOmJyD3gbfLkJb3Xuu9EutB%3DX%2BfeTPw%40mail.gmail.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpubsSQha8Am45uPfOC7Td2ateDwv5m4jGudKUEa_0zOxA%40mail.gmail.com.

Re: [hugin-ptx] lux 1.2.2 released

[Harry van der Wolf]

>
>
> I uploaded a debian package
>  for debian
> 12 stable. It might be usable for other debian-based distros.
>
> Thanks, downloaded, tried it. It installed over the 1.1.6 that was there
> before. Trying to run lux in a terminal gave me this:
>
> lux: error while loading shared libraries: libexiv2.so.28: cannot open
> shared object file: No such file or directory
>
> Bookworm comes with libexiv2-27. I have that installed. I guess the
> libexiv2 version your package is looking for is -28?
>
> Ah, thanks for pointing that out! I used a local build of libexiv2 v. 28,
> and the dependency slipped into the package. Using libexiv2 v.27 is okay,
> but there are some (annoying) API changes with v.28 and switching back to
> v.27 requires some finessing in the build. I'll see to it that the
> dependency is set to v.27 and rebuild and upload the package. Thanks for
> testing!
>

I just wanted to report the same. Also on Debian Bookworm.
I will await the new .deb package.
The AppImage does not run on my Chromebook with beta linux, which is the
reported debian bookworm by the way. It starts flashing and completely
blocks everything. But that could be because it is linux running in a
sandbox on ChromeOS.
My other laptop is an aarch64 laptop and the deb and App image do not run
on it either as they are intel x86_64.

Bye,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPps3DxQdF6Q%2Ba-pe5LavCnze3Teuwb2c1doKUTSkwUAz1A%40mail.gmail.com.

Re: [hugin-ptx] Disappearing posts

[Harry van der Wolf]

Same for me. I saw two identical posts from you about "align_image_stack
parameters"

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuTc1_SaSamn7ES5vRY3Rydyr%3DvYKHO6SO5TK0Bi%2BbLZA%40mail.gmail.com.

Re: [hugin-ptx] opencv based CP detector for use with Hugin?

[Harry van der Wolf]

Which ones do you mean?
In the 4.6 prebuilt libraries WITH the python bindings, I have ORB, SIFT,
ECC, AlignMTB, mergeMertens exposure fusion, stiching, blending..
SIFT is free now, SURF is not, but ORB does a great job for keypoints and
feature detection. Better than the other two (in my opinion).
See for example: https://github.com/brianpinto91/image-stitching
It is for Python though, not C.

There is also the "learnopencv.com" with many examples in both C(++) and
Python.
And on github there are by now also a ton of examples.
Lots to learn and copy from.

Op vr 8 sep 2023 om 19:56 schreef Robert Mahar :

> Looking at the opencv feature detection, the only painful thing will be
> making something that "just works" with stock opencv packages, as the
> feature detection are in 3rd party modules so not normally available if you
> just grab opencv pre-built RPM.   Not so sure how easily sharable such a
> solution would be for average Hugin users if "step one" is build their own
> opencv libraries from source.   But the rest is just a lot of boilerplate
> and it should be easy to wrap it in a way that looks like a typical
> panotools utility.  "cvfind" LOL.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvpzcDyoAMjg9eMwOXHfdvZhJQdGV6-U0zvO7UabP3-7g%40mail.gmail.com.

Re: [hugin-ptx] opencv based CP detector for use with Hugin?

[Harry van der Wolf]

Yes, it is already there in opencv and works pretty well.
There are multiple algorithms can do the "control point find" and multiple
algorithms like the MergeMertens that can be combined as well.
And it also contains blending algorithms.

I did some work in Python. Not in C.

Take a look at
https://www.opencvhelp.org/tutorials/advanced/panorama-creation/

Harry

Op do 7 sep 2023 om 17:07 schreef Robert Mahar :

> Hi,
>
> I've been using Hugin for a decade and for the most part can get it to do
> even difficult projects pretty easily.But I have a couple microchip
> photography projects for which cpfind either finds no control points or a
> pile of extraneous ones.
>
> Before I go crazy trying to make a cpfind like tool that speaks .pto
> files, and so on, I'm wondering if such a thing already exists to enable
> the use of the feature detection / mapping built into opencv.   I cannot
> imagine I am the first person on the planet to want to do this.   ( If I m
> I guess I should start coding. )
>
> -- Bob
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/6e8fafa1-2884-4bfb-8f5f-ab973b0ba669n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpu04OQqV%2BTg9OboHv7DN6U_cM67PsPBsyvX7hZOFHkUCA%40mail.gmail.com.

Re: [hugin-ptx] lux for Linux as AppImage

[Harry van der Wolf]

You use:
$APPDIR/usr/bin/lux -w $APPDIR/usr/share/lux/fonts/NotoSans-Regular.ttf "$@"

Please try with:
$APPDIR/usr/bin/lux -w
$APPDIR/usr/share/lux/fonts/NotoSans-Regular.ttf ${1+"$@"} &

Harry


Op vr 14 jul 2023 om 20:28 schreef Harry van der Wolf :

> Hi,
>
> Using ./lux-1.1.6-x86_64.AppImage
> ~/128GB/Afbeeldingen/1JTG/1tifpanos/2003-0713-0608\
> zomervakantie-Thisted-0725-0728_Thisted-038-Thisted-051-overall.tif
> does work.
>
> Using ./lux-1.1.6-x86_64.AppImage
> "~/128GB/Afbeeldingen/1JTG/1tifpanos/2003-0713-0608
> zomervakantie-Thisted-0725-0728_Thisted-038-Thisted-051-overall.tif"
> doesn't work.
>
> Harry
>
> Op vr 14 jul 2023 om 18:13 schreef 'Kay F. Jahnke' via hugin and other
> free panoramic software :
>
>> I fixed the issue with passing filenames with white space on the CL and
>> built a fresh AppImage on a Kubuntu 18.04 LTS VM, which should make the
>> AppImage usable on even more platforms. You can download the new
>> AppImage here:
>>
>> https://bitbucket.org/kfj/pv/downloads/lux-1.1.6-x86_64.AppImage
>>
>> Kay
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/hugin-ptx/cd48832f-3a07-bf14-8032-93b5d7d08650%40yahoo.com
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpv96uamv0stgi1ANt70RXWqQurLQ40osCtdmf5OBaNDag%40mail.gmail.com.

Re: [hugin-ptx] lux for Linux as AppImage

[Harry van der Wolf]

Hi,

Using ./lux-1.1.6-x86_64.AppImage
~/128GB/Afbeeldingen/1JTG/1tifpanos/2003-0713-0608\
zomervakantie-Thisted-0725-0728_Thisted-038-Thisted-051-overall.tif
does work.

Using ./lux-1.1.6-x86_64.AppImage
"~/128GB/Afbeeldingen/1JTG/1tifpanos/2003-0713-0608
zomervakantie-Thisted-0725-0728_Thisted-038-Thisted-051-overall.tif"
doesn't work.

Harry

Op vr 14 jul 2023 om 18:13 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> I fixed the issue with passing filenames with white space on the CL and
> built a fresh AppImage on a Kubuntu 18.04 LTS VM, which should make the
> AppImage usable on even more platforms. You can download the new
> AppImage here:
>
> https://bitbucket.org/kfj/pv/downloads/lux-1.1.6-x86_64.AppImage
>
> Kay
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/cd48832f-3a07-bf14-8032-93b5d7d08650%40yahoo.com
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsb4j9t0kanbbnjrwHEg_nEkELbw8q00Pgxk5tWAF%2Bs-g%40mail.gmail.com.

Re: [hugin-ptx] lux for Linux as AppImage

[Harry van der Wolf]

Hi,

i tried it on my Chromebook under the builtin linux which is Debian 11. I
tried creating a pano, viewing a pano and did some bracketing. That all
works fine. I completely stopped with panos and bracketing so I had to take
some old series.

One remark: when specifying files or a single pano on the command line, it
doesn't accept spaces in paths or file names. Not even when I enclose them
in double or single quotes.

And the remark about the app image being  "big". Those persons do not
understand that you can create a universal 64bit intel for many platforms
in one go which saves the developer a lot of time when developing
open-source for his users (aa\nd him/herself of course). One developer can
support a lot of users in one app image build run. Obviously they still
work from floppy disks as modern systems have huge amounts of disk space.
And then they produce a single (tif) pano of 200~250 MB based on raw/tif
images of 20~50 MB each. And when you record a 4k movie at a 100 MBps you
have a video of 1GB after a minute.
What is that compared to a "small" appImage?
I have had the same questions/remarks for two of my appImages where users
simply only look at their own environment without even looking at the
"shocking" size of the images and videos they produce.

Harry


Op vr 14 jul 2023 om 08:44 schreef 'kfj' via hugin and other free panoramic
software :

> Ooops... misread the download counter - fourteen so far. So maybe you did
> try?
>
> On Friday, July 14, 2023 at 8:41:36 AM UTC+2 kfj wrote:
>
>> On 14.07.23 00:04, David W. Jones wrote:
>>
>> > So sad to hear this. I've never been able to get AppImages, Flatpaks et
>> > al to work on my Debian 11 system. And the idea of a whole huge
>> AppImage
>> > just for one pretty small application like Lux just seems like way
>> overkill.
>> >
>> > Oh, well.
>>
>> What is this silly lament? Did you try? Actually, I can tell that you
>> did not, because the download counter on my download page is still zero.
>> So you just seem to have preconceived notions. And what do you mean by
>> 'huge'? The AppImage weighs in at 11.7 MB, which is less than the MacOS
>> dmg and the windows installer (both 13.8). In fact, these latter two use
>> a similar technology to the AppImage. The AppImage I distribute was
>> actually built on debian 11, so here's a good chance for you to get your
>> first AppImage to run on your system. Just a hint: after downloading,
>> you have to set the execute permission. Then just execute it.
>>
>> I'm also not sure what you mean by 'a pretty small application'. You
>> surely can't mean it's functionality, so maybe you mean it's size? The
>> Linux binary is 25 MB, and the packaging shrinks the data to less than
>> half, even though it bundles a fair amount of libraries with it.
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/1d48568d-30b7-410c-8c47-4f216f516351n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpu_GaUd09BS0st9z9m5y8nWFYFSd5gYrOp29pkCDGOcoA%40mail.gmail.com.

Re: [hugin-ptx] Re: Command-line tool sequence to emulate GUI process

[Harry van der Wolf]

Hi,

Did you have a look at
https://wiki.panotools.org/Panorama_scripting_in_a_nutshell ?

Op vr 28 apr 2023 om 14:57 schreef PanoSeek :

> I did something similar to stitch 360 panos from my drone.  I wanted to do
> as much scripting as possible to avoid manual work when I have hundreds of
> sets to stitch.  So far this has been working well.   More here -
> https://github.com/RookieITSec/HuginPanoScript
>
> Script -
>
>
> REM 2023-02-03- This script is being built to take a folder full of
> folders containing groups of .jpg photos from the drone 360 photo tool and
> export a 2:1 aspect ration photo to be uploaded to google Maps/Streetview.
> REM Guide followed located here -
> https://wiki.panotools.org/Panorama_scripting_in_a_nutshell#Creating_hugin_projects_on_the_command-line
>
>
> REM Hugin needs to be installed here C:\Program Files\Hugin
> REM - This script is being called by the deployment script. The
> Deployment script copies this to each folder in the specified directory and
> then executes it. All sub-folder tasks will run at the same time, so it
> will take a bit of time when doing many panos.
>
>
> REM - MAKE SURE YOU DO NOT HAVE ANY NON-PANO IMAGES IN THE FOLDER. THE
> SOFTWARE TRIES TO EAT THEM AND ADD TO YOUR PANO.
>
>
> REM - set the name of the variable we will be using. This will be the
> name of the directory the file is in.
> @echo off
> for %%I in (.) do set "current_folder=%%~nxI"
> echo The current folder is: %current_folder%
>
>
> REM Build the PTO file with the contents of the directory we are
> currently in.
> "C:\Program Files\Hugin\bin\pto_gen" *.jpg -o %current_folder%.pto
> REM Figure out how to rename the pto file to the parent folder name.
> Remember to tweak the file name below if this changes.
>
>
> REM Create Control Points in the existing pto file
> "C:\Program Files\Hugin\bin\cpfind" --celeste -o %current_folder%.pto
> %current_folder%.pto
>
> REM Clean up the control points
> "C:\Program Files\Hugin\bin\cpclean" -o %current_folder%.pto
> %current_folder%.pto
>
> REM Find Vertical Lines
> "C:\Program Files\Hugin\bin\linefind" -o %current_folder%.pto
> %current_folder%.pto
>
> REM Optimize
> "C:\Program Files\Hugin\bin\autooptimiser" -a -l -s -m -o %current_folder%.pto
> %current_folder%.pto
>
> REM Optimize Version 2 -
> REM "C:\Program Files\Hugin\bin\pto_var" --opt Vb,Vx,Ra,Eev -o
> %current_sfolder%.pto %current_folder%.pto
> REM "C:\Program Files\Hugin\bin\vig_optimize" -o %current_folder%.pto
> %current_folder%.pto
> REM version 2 was far worse.
>
> REM set output/stitcher options
> "C:\Program Files\Hugin\bin\pano_modify" -o %current_folder%.pto
> --fov=360x180 --center --straighten --canvas=9000x4500 --ldr-file=JPG
> --ldr-compression=100 --output-exposure=AUTO %current_folder%.pto
>
> REM After the pause, it will attempt to stitch.
> REM pause
>
> REM Stitch the output - un-rem the next line if you want the script to
> stitch right away. I had too many at once so I moved over to the batch
> tool, which is the command below.
> REM "C:\Program Files\Hugin\bin\hugin_executor" --stitching
> --prefix=%current_folder% %current_folder%.pto
>
> REM send to batch to run sequentially.
> "C:\Program Files\Hugin\bin\PTBatcherGui.exe" --batch %current_folder%.pto
>
>
> REM Rename the output to the date it was captured to help clarify the
> filename.
> REM "C:\Program Files\Hugin\bin\exiftool" "-filename %Y%m%d_%H%M%S%%-c.pano.%%le pano.jpg
> REM This does not work for some reason?
>
> REM - Figure out how to get rid of black blocks- maybe adding enblend "-l
> 29" will help?
>
> On Friday, April 28, 2023 at 12:48:12 AM UTC-5 patj...@gmail.com wrote:
>
>> I have been studying the multiple command-line tools to try to emulate
>> the sequence of operations in the GUI Assistant mode.
>>
>> Load image (and create .pto)
>> pto_gen -o file.pto xxx*.jpg
>>
>> Align ...
>> cpfind -o file.pto file.pto
>>
>> Create panorama
>> Here I break down and get confused. There seem many options, and many
>> partial solutions. Trying a variety, I do get a pano file, but it is
>> 1/1000th the size of the GUI-produced file.
>>
>> What I have tried is
>> cpclean -o %1.pto %1.pto
>> linefind -o %1.pto %1.pto
>> rem autooptimiser -a -l -s -m -o %1.pto %1.pto
>> rem pano_modify --canvas=AUTO --crop=AUTO -o %1.pto %1.pto
>> nona -m TIFF_m -o %1 %1.pto
>> enblend -o zp_%1.tif %10*.tif
>> enfuse -o zp_%1.tif %10*.tif
>> rem del %10*.tif
>> convert zp_%1.tif -resize 7000x zp_%1r.jpg
>>
>> 1) Is there a way to get the sequence of commands output from the hugin
>> GUI?
>>
>> 2) Is there a standard tool processing algorithm defined somewhere?
>>
>> Paul A. Thompson
>>
> --
> 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 

Re: [hugin-ptx] Hugin 2022.0 beta 1 released

[Harry van der Wolf]

Op zo 27 nov. 2022 om 09:38 schreef T. Modes :

>
>
> @Harry: There is still 1 fuzzy string in your po file. Do you need help
> with the understanding or it is just an oversight?
>
>
Yes, I know. I put the "fuzzy" marker myself :)

It is the
#, fuzzy
msgid "Focus stacked images"

Yes, I didn't quite understand it.
Is this a description? Like: what you see here are "Focus stacked images".

Or does it describe an action? Like, click here to do "focus stacking on
these stacked images"

Best,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptzgCKJUAOPxSaByinanXzi1O8FSbXG%3DNgqMof%2BAW5aMQ%40mail.gmail.com.

Re: [hugin-ptx] PyImageFuser 0.5.0 released

[Harry van der Wolf]

Hi,

It is hard to say. It can be that your (old) image is not entirely correct.
This error occurs when some of the blocks being read of the image is not
correct.
It is supposed to be corrected by adding
"ImageFile.LOAD_TRUNCATED_IMAGES = True"
to the code. I did that but can't reproduce the error.
Can you please share your images? Or the image that gives the error?

best,
Harry

Op zo 19 jun. 2022 om 16:15 schreef J. Schneider* :

> I overlooked: In spite of the error message, there is a result in the
> folder. It's perfect!
> Thank you for that nice tool!
> Would of course still be interested in what that error was.
>
> Best regards
> Joachim
>
> Am 19.06.22 um 16:09 schrieb J. Schneider*:
> > Great! I seldom used stacking, but with a dedicated tool I might do it
> > more often. I just tried with an old project where I wasn't content with
> > the result so far.
> > I got the error message:
> >
> > Traceback (most recent call last):
> >   File "PyImageFuser.py", line 303, in 
> >   File "PyImageFuser.py", line 291, in main
> >   File "image_functions.py", line 671, in displayImageWindow
> >   File "image_functions.py", line 652, in reorient_img
> >   File "PIL\Image.py", line 3677, in __getitem__
> > KeyError: 274
> >
> > Can you tell me what has gone wrong?
> > I'm on Windows 11 Pro.
> >
> > Best regards
> > Joachim
> >
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/d040d0c9-4347-3f75-7038-d1b38990b692%40gmx.de
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptGBb5M7U7xv4U726ZQj2-ozFVL7kFzM9ujbjQNBEUgWA%40mail.gmail.com.

Re: [hugin-ptx] PyImageFuser 0.5.0 released

[Harry van der Wolf]

Hi Don,

Thanks for taking a look at it.
For now I have no idea what is going wrong as I have no experience
whatsoever with an M1.

The app is actually a kick-starter (built with pyinstaller) calling python
and necessary plugins and then starting the main script. This all with
necessary libs included, but no system libs. And this all bundled in a Mac
bundled app.
Your M1 system might support the kickstarter and the x86 python packaged
with it, but maybe my x86_64 package expects x86_64 libraries not on your
system.

I do not know how experienced you are with bundles and the command line. A
MacOS bundle is actually a special kind of folder structure.
If you open a terminal and go to the folder where you have the app.
Can you please cd into the app folder structure and start it "manually".

like:
cd PyImageFuser.app/Contents/MacOs
./PyImageFuser &

and see if you can start it from there.

best,
Harry

Op wo 8 jun. 2022 om 18:32 schreef dgjohnston :

>
>
> > On Jun 7, 2022, at 11:14 AM, Harry van der Wolf 
> wrote:
> >
> > Hi,
> >
> > I now also added an Intel x86 MacOS bundle (stamped as 0.5.0.1). The
> only modification (fix) is in relation to internal bundle PATHs.
> > As I do not have an M1 Mac, I can't build an M1 bundle, but the M1 does
> simulate an x86_64 as still many packages have not yet been converted.
> >
> > Harry
> >
>
> Harry, I have an M1 based MacBook Pro and I have Rosetta 2 install to
> simulate an intel 86. When I try running you PyImageFuser for Mac OS I get
> the error message: "“PyImageFuser.app” is damaged and can’t be opened. You
> should move it to the Trash.”
>
> Don J.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/52006F22-6738-40EC-A257-58113D2871DD%40accesscomm.ca
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptfojyYm9_i199y1eYp7KZ1jbW%2Bos2Q2-kCELGhfj-WRQ%40mail.gmail.com.

Re: [hugin-ptx] PyImageFuser 0.5.0 released

[Harry van der Wolf]

Hi,

I now also added an Intel x86 MacOS bundle (stamped as 0.5.0.1). The only
modification (fix) is in relation to internal bundle PATHs.
As I do not have an M1 Mac, I can't build an M1 bundle, but the M1 does
simulate an x86_64 as still many packages have not yet been converted.

Harry

Op vr 3 jun. 2022 om 12:23 schreef Harry van der Wolf :

> Hi David,
>
> Sorry for my somewhat late reaction.  I had a Go Live of a project and we
> had a few more issues than anticipated.
>
> There are armhf and amd64 packages:
> See below the Assets area of the releases page.
> Don't you see these entries?
>
> Assets 6
>
>- pyimagefuser-0.5.0-amd64.deb
>
> <https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/pyimagefuser-0.5.0-amd64.deb>
>19.1 MB5 days ago
>- pyimagefuser-0.5.0-armhf.deb
>
> <https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/pyimagefuser-0.5.0-armhf.deb>
>17.8 MB5 days ago
>- PyImageFuser-0.5.0-win-x86_64.zip
>
> <https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/PyImageFuser-0.5.0-win-x86_64.zip>
>23.6 MB5 days ago
>- PyImageFuser-0.5.0-x86_64.AppImage
>
> <https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/PyImageFuser-0.5.0-x86_64.AppImage>
>38.2 MB5 days ago
>- Source code (zip)
><https://github.com/hvdwolf/PyImageFuser/archive/refs/tags/0.5.0.zip>
>5 days ago
>- Source code (tar.gz)
><https://github.com/hvdwolf/PyImageFuser/archive/refs/tags/0.5.0.tar.gz>
>5 days ago
>
>
>
> Op wo 1 jun. 2022 om 09:47 schreef David W. Jones :
>
>> Hi, Harry!
>>
>> Sounds fascinating and useful to me!
>>
>> I went to the releases page, it mentions a pyimagefuser-0.5.0-amd64.deb
>> package but only has links to an AppImage.
>>
>> I don't do AppImages. Link for DEB package? I have Debian 11.
>>
>> On 5/29/22 07:04, Harry van der Wolf wrote:
>> > Hi,
>> >
>> > PyImageFuser is a Python3 PySimpleGUI program to exposure fuse
>> bracketed
>> > images, reduce noise in stacks and do focus stacking. It uses
>> > align_image_stack and enfuse to accomplish this.
>> >
>> > github: https://github.com/hvdwolf/PyImageFuser
>> > <https://github.com/hvdwolf/PyImageFuser>
>> > Releases: https://github.com/hvdwolf/PyImageFuser/releases
>> > <https://github.com/hvdwolf/PyImageFuser/releases>
>> >
>> > In 2009-2010 I wrote ImageFuser in Applescript and released that as a
>> > bundled app for MacOS (MacOS/X at that time). After leaving MacOS for
>> > Linux, I also wrote KImagefuser for Linux, but the used Kommander
>> > scripting died.
>> > In the past couple of  weeks I wrote PyImageFuser: a GPLv3 Python3 GUI
>> > frontend for enfuse and align_image_stack (both GPLv2), written
>> > in/using PySimpleGUI. (The tkinter based version)
>> >
>> > Why did I write PyImageFuser? Why not use a few scripts, Hugin or Lux
>> > (pv) for the same purpose? Or use builtin camera/phone HDR options?
>> > - Well, I do use 3 scripts for enfuse and align_image_stack (and lux
>> and
>> > align_image_stack) but they do not allow much tweaking.
>> > - Hugin is for me an excellent panorama tool, but it's like using a 70+
>> > functions swiss army knife when you only need a toothbrush and a
>> > toothpick. Next to that: it doesn't give an as flexible option to tweak
>> > align_image_stack and enfuse if you do not know all command line
>> options
>> > from the top of your head.
>> > - Lux (pv) also does an excellent job, but is also more aimed at "live"
>> > panorama making and I still can't get used to the interface. Tweaking
>> > options for exposure blending are (for me) more difficult, and
>> > align_image_stack, when needed, can only be used from the command line.
>> > - Cameras simply lack the CPU-power to do a good exposure bracketing
>> and
>> > completely lack the power for aligning images. Phones nowadays have
>> > horse power enough to do both on sets of 3 images, but lack features
>> and
>> > still have small sensors.
>> > - And finally: Very simple, I could do it (and even very simple using
>> > PyimpleGUI) and I wanted to have something "dedicated" for this kind of
>> > work.
>> >
>> > I privately only use Linux and Chromebooks. Business wise I use
>> Windows.
>> > Occasionally I touch a Mac. All those systems have their own
>> > shortcut/keyboard combinations, which I by n

Re: [hugin-ptx] PyImageFuser 0.5.0 released

[Harry van der Wolf]

Hi David,

Sorry for my somewhat late reaction.  I had a Go Live of a project and we
had a few more issues than anticipated.

There are armhf and amd64 packages:
See below the Assets area of the releases page.
Don't you see these entries?

Assets 6

   - pyimagefuser-0.5.0-amd64.deb
   
<https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/pyimagefuser-0.5.0-amd64.deb>
   19.1 MB5 days ago
   - pyimagefuser-0.5.0-armhf.deb
   
<https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/pyimagefuser-0.5.0-armhf.deb>
   17.8 MB5 days ago
   - PyImageFuser-0.5.0-win-x86_64.zip
   
<https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/PyImageFuser-0.5.0-win-x86_64.zip>
   23.6 MB5 days ago
   - PyImageFuser-0.5.0-x86_64.AppImage
   
<https://github.com/hvdwolf/PyImageFuser/releases/download/0.5.0/PyImageFuser-0.5.0-x86_64.AppImage>
   38.2 MB5 days ago
   - Source code (zip)
   <https://github.com/hvdwolf/PyImageFuser/archive/refs/tags/0.5.0.zip>
   5 days ago
   - Source code (tar.gz)
   <https://github.com/hvdwolf/PyImageFuser/archive/refs/tags/0.5.0.tar.gz>
   5 days ago



Op wo 1 jun. 2022 om 09:47 schreef David W. Jones :

> Hi, Harry!
>
> Sounds fascinating and useful to me!
>
> I went to the releases page, it mentions a pyimagefuser-0.5.0-amd64.deb
> package but only has links to an AppImage.
>
> I don't do AppImages. Link for DEB package? I have Debian 11.
>
> On 5/29/22 07:04, Harry van der Wolf wrote:
> > Hi,
> >
> > PyImageFuser is a Python3 PySimpleGUI program to exposure fuse bracketed
> > images, reduce noise in stacks and do focus stacking. It uses
> > align_image_stack and enfuse to accomplish this.
> >
> > github: https://github.com/hvdwolf/PyImageFuser
> > <https://github.com/hvdwolf/PyImageFuser>
> > Releases: https://github.com/hvdwolf/PyImageFuser/releases
> > <https://github.com/hvdwolf/PyImageFuser/releases>
> >
> > In 2009-2010 I wrote ImageFuser in Applescript and released that as a
> > bundled app for MacOS (MacOS/X at that time). After leaving MacOS for
> > Linux, I also wrote KImagefuser for Linux, but the used Kommander
> > scripting died.
> > In the past couple of  weeks I wrote PyImageFuser: a GPLv3 Python3 GUI
> > frontend for enfuse and align_image_stack (both GPLv2), written
> > in/using PySimpleGUI. (The tkinter based version)
> >
> > Why did I write PyImageFuser? Why not use a few scripts, Hugin or Lux
> > (pv) for the same purpose? Or use builtin camera/phone HDR options?
> > - Well, I do use 3 scripts for enfuse and align_image_stack (and lux and
> > align_image_stack) but they do not allow much tweaking.
> > - Hugin is for me an excellent panorama tool, but it's like using a 70+
> > functions swiss army knife when you only need a toothbrush and a
> > toothpick. Next to that: it doesn't give an as flexible option to tweak
> > align_image_stack and enfuse if you do not know all command line options
> > from the top of your head.
> > - Lux (pv) also does an excellent job, but is also more aimed at "live"
> > panorama making and I still can't get used to the interface. Tweaking
> > options for exposure blending are (for me) more difficult, and
> > align_image_stack, when needed, can only be used from the command line.
> > - Cameras simply lack the CPU-power to do a good exposure bracketing and
> > completely lack the power for aligning images. Phones nowadays have
> > horse power enough to do both on sets of 3 images, but lack features and
> > still have small sensors.
> > - And finally: Very simple, I could do it (and even very simple using
> > PyimpleGUI) and I wanted to have something "dedicated" for this kind of
> > work.
> >
> > I privately only use Linux and Chromebooks. Business wise I use Windows.
> > Occasionally I touch a Mac. All those systems have their own
> > shortcut/keyboard combinations, which I by now don't use anymore.
> > PyImageFuser is only meant for exposure bracketing, noise reduction and
> > focus stacking using a conventional user interface ;).
> >
> > If you are interested in PyImageFuser
> > <https://github.com/hvdwolf/PyImageFuser/tree/main> you can download it
> > from the Releases <https://github.com/hvdwolf/jExifToolGUI/releases>
> > page. It still needs further tweaking (and undoubtedly bug fixing and
> > platform "hardening"), but it does what I want it to do.
> > /
> > /
> > Best regards,
> > Harry
>
>
> --
> David W. Jones
> gnomeno...@gmail.com
> wandering the landscape of god
> http://dancingtreefrog.com
> My password is the last 8 digits of π.

[hugin-ptx] PyImageFuser 0.5.0 released

[Harry van der Wolf]

Hi,

PyImageFuser is a Python3 PySimpleGUI program to exposure fuse bracketed
images, reduce noise in stacks and do focus stacking. It uses
align_image_stack and enfuse to accomplish this.

github: https://github.com/hvdwolf/PyImageFuser
Releases: https://github.com/hvdwolf/PyImageFuser/releases

In 2009-2010 I wrote ImageFuser in Applescript and released that as a
bundled app for MacOS (MacOS/X at that time). After leaving MacOS for
Linux, I also wrote KImagefuser for Linux, but the used Kommander scripting
died.
In the past couple of  weeks I wrote PyImageFuser: a GPLv3 Python3 GUI
frontend for enfuse and align_image_stack (both GPLv2), written
in/using PySimpleGUI. (The tkinter based version)

Why did I write PyImageFuser? Why not use a few scripts, Hugin or Lux (pv)
for the same purpose? Or use builtin camera/phone HDR options?
- Well, I do use 3 scripts for enfuse and align_image_stack (and lux and
align_image_stack) but they do not allow much tweaking.
- Hugin is for me an excellent panorama tool, but it's like using a 70+
functions swiss army knife when you only need a toothbrush and a toothpick.
Next to that: it doesn't give an as flexible option to tweak
align_image_stack and enfuse if you do not know all command line options
from the top of your head.
- Lux (pv) also does an excellent job, but is also more aimed at "live"
panorama making and I still can't get used to the interface. Tweaking
options for exposure blending are (for me) more difficult, and
align_image_stack, when needed, can only be used from the command line.
- Cameras simply lack the CPU-power to do a good exposure bracketing and
completely lack the power for aligning images. Phones nowadays have horse
power enough to do both on sets of 3 images, but lack features and still
have small sensors.
- And finally: Very simple, I could do it (and even very simple using
PyimpleGUI) and I wanted to have something "dedicated" for this kind of
work.

I privately only use Linux and Chromebooks. Business wise I use Windows.
Occasionally I touch a Mac. All those systems have their own
shortcut/keyboard combinations, which I by now don't use anymore.
PyImageFuser is only meant for exposure bracketing, noise reduction and
focus stacking using a conventional user interface ;).

If you are interested in PyImageFuser
 you can download it
from the Releases  page.
It still needs further tweaking (and undoubtedly bug fixing and platform
"hardening"), but it does what I want it to do.

Best regards,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpv7Ef%3DgAwiagxm4S%3DBEzusxyHdOuCTLH4S9n1U7DMzFzw%40mail.gmail.com.

Re: [hugin-ptx] Re: HUGIN install

[Harry van der Wolf]

Hi,

Why do you say you don't have a zip file?
Your own screenshot shows that a zip file is created containing the debug
report.
We are not talking about a Hugin zip, but a system debug zip in the path
mentioned in your screenshot.

Op vr 6 mei 2022 om 09:19 schreef Josip Puškarić :

> Good morning everyone,
>
> do you think we can find solution or I should forget about Hugin?
>
> Thanks
>
> Dana četvrtak, 5. svibnja 2022. u 15:26:02 UTC+2 korisnik Josip Puškarić
> napisao je:
>
>> i dont have any zip file. Do you recommend to deinstall and install it
>> again (at least 5 times i did this today), to see what happens?
>>
>> Dana četvrtak, 5. svibnja 2022. u 15:11:25 UTC+2 korisnik
>> johnfi...@gmail.com napisao je:
>>
>>> On Thu, May 5, 2022 at 8:48 AM Luís Henrique Camargo Quiroz <
>>> lui...@gmail.com> wrote:
>>>


>
> whatever I click on - happens nothing.
>

>>> It appears you are saying the dialog, for sending or canceling or
>>> viewing the information about the crash,  is frozen.
>>>
>>> But does the .zip file it mentions exist?
>>>
>>> There are several people here (myself included) who could probably solve
>>> the problem with access to the .zip file.  So if you can put that file
>>> somewhere with a public link, you would get a good answer soon.  You could
>>> also email the file directly to me or to one of the Hugin maintainers, if
>>> you prefer.
>>>
>>> Without that file, I don't have any resources for even trying to help.
>>>
>>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/7faaccdc-a37b-49fe-96c0-4f04aa2e250dn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvn_HUk5Y3h80D6NTNP_B0guxOKE%3D%2B377s%3DRnaK8i333A%40mail.gmail.com.

Re: [hugin-ptx] Re: focus stacking tool with Hugin

[Harry van der Wolf]

Op do 8 jul. 2021 om 00:19 schreef 'dkloi' via hugin and other free
panoramic software :

> Hi Michel,
>
> You may want to look at
> https://patdavid.net/2013/01/focus-stacking-macro-photos-enfuse/ Enfuse
> is normally used for exposure blending
> https://patdavid.net/2013/07/automatic-exposure-blending-with-enfuse/ but
> can do exposure stacking as well. There is a standalone enfuse/enblend
> package http://enblend.sourceforge.net/ but it is also included as part
> of Hugin
>
> Daniel
>

There is no standalone package. The link you are referring to contains the
source code. It allows you to build a standalone version of enblend/enfuse.

Lux (previously called PV) can also do focus-stacking.

If your software can do the same then please share it. If it can do that
even better: great!.
We can all learn from each other and software that does something better,
or faster at same quality, than other software is always welcome.


Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptkFRfVja6y1N_SOcAKTmYLEm-pxkBRq9AXYpnz2TLEHA%40mail.gmail.com.

Re: [hugin-ptx] Re: lux - FOSS multiplatform image and panorama viewer

[Harry van der Wolf]

Op ma 7 jun. 2021 om 10:01 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> Am 07.06.21 um 09:28 schrieb David W. Jones:
>
> > Sorry, I don't do flatpack or appimage. I've tried both with a couple of
> > different apps, with complete lack of success, and no interest in
> > figuring out why they didn't work.
>
> Harry's comment about using flatpack or appimage was not directed at
> you, but simply stating the fact that these two methods of installation
> avoid issues with incompatible or inaccessible libraries, because they
> provide an environment where the necessary shared library infrastructure
> is provided bundled with the installation medium.
>
> Indeed. I already had a look at an AppImage as I had made two before. In
this case there is something with libc6 that need to be patched, where you
normally use the lib6c from the system.
aferrero2707 used that same patch for the Hugin app image, but I did not
dive into it yet.
As Kay mentions: using cmake to compile lux makes it now much easier.


> > Doesn't compiling something to use static libs also include everything
> > inside the app?
>
> It, does, but it produces enormous bloat. And if anything relevant in
> one of the libraries changes, you have to recompile, redistribute, and
> make all users reinstall. Linux has decided against this, and for good
> reasons.
>
>
Yeah, well.
With a statically compiled binary you have everything in there that end
users do not have on their system. So that's more space effective. For
developers it is of course not, but they are less than 0,01% once a package
really gets used by an end community.
An AppImage or Flatpack is squash compressed. It delivers a 13~15MB
release.
Upon starting it is uncompressed to a tmp folder and is then ~40MB (and
actually that should even be slightly larger with the extra patching). This
tmp folder is of course removed when you close the app.
When I compile lux on Debian, it is 18MB (!) and that is with uncompressed
libraries even more.
So actually a static binary or an AppImage or Flatpack (never did that one)
is actually more space effective "all the time" for end users. And only
when running the AppImage it temporarily takes slightly more space.
Especially for those users who do not have the development installed, a
static binary or AppImage is more space effective.

On the other hand: Who cares nowadays with bigger SDs?
My camera  makes 14MB images and if I bulk shoot I have even up to 200MB of
images for one sequence. A day of "bird shooting" gives me often 3~5 GB of
images/videos (and afterwards mostly less than 1~2% remains).
4K movies from my camera are 250MB to >1GB (and I'm not even talking about
persons who download movies or series up to 30GB)

So who cares whether an app is 18MB (uncompressed lux), 13MB (compressed
app image) or 35MB?
I do think that AppImages (and Flatpacks) are indeed the way forward now
that Linux more and more gets an "end user" platform.

Next to that: I do have a Chromebook with Linux Beta on it. Every user can
install that. I use it all the time (I hate fans in my laptops) and do all
my development on that Chromebook in Linux Beta.
The java app images I make and lux debs I make can simply be installed in
that Linux beta (by default Debian but you can install any major distro).
If Chomebook users (considering them even more as end users) start to use
AppImages in Linux beta, makes it even more attractive to use these.

But that's my personal view.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsCbeTTbrgDHZ%2Bf_UQaFxMiXOUjT%2Buw70QjWz9Ot_%3DhTw%40mail.gmail.com.

Re: [hugin-ptx] Re: lux - FOSS multiplatform image and panorama viewer

[Harry van der Wolf]

Hi Kay, all,

I created a Lux 1.0.9 app bundle for MacOS and a Lux 1.0.9 distributable
binary version for MacOS.
The first one for the GUI lovers, the 2nd for the command line lovers.

Links via a PM. To be added (if you want to) to your bitbucket download
section.

Harry

Op vr 4 jun. 2021 om 19:16 schreef 'kfj' via hugin and other free panoramic
software :

> Dear all!
>
> I've just released lux 1.0.9. This version does not introduce much new
> functionality, the focus was more on usability and stability. I've uploaded
> a debian package and a windows bundle to the project's download page:
>
> https://bitbucket.org/kfj/pv/downloads/lux-1.0.9-0git-Linux.deb
> https://bitbucket.org/kfj/pv/downloads/lux_for_windows_1.0.9.zip
>
> Hopefully, a mac bundle will be available soon.
>
> Kay
>
> On Tuesday, April 13, 2021 at 11:59:29 AM UTC+2 kfj wrote:
>
>> Dear all!
>>
>> My viewer 'pv' has been renamed to 'lux', and it's seen a lot of
>> development recently. There are two important changes:
>>
>> - lux now builds with CMake, and readymade binaries are available for
>> download
>>
>> - lux can now do stitching and exposure fusion
>>
>> Special thanks go to Kornel for the work on the CMakeLists.txt, and to
>> Harry for providing code to make mac bundles and testing my exposure fusion
>> code, and I'd also like to thank all of you who have accompanied the
>> development process with helpful suggestions and bug reports.
>>
>> You can find bundles for mac OS and windows, and a simple debian package,
>> on the project's download page .
>> There's also documentation
>>  in HTML format, and
>> online on the project's bitbucket page .
>>
>> The binaries currently on offer are all version 1.0.8, which has seen a
>> good deal of testing and should be reasonably stable.
>>
>> Kay
>>
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/79f6491e-c2e3-464f-8603-e1a4691f5444n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuENt7AvZrxrmozTOh9bcchnoP3cRVc31jP1JBDb3bbtQ%40mail.gmail.com.

Re: [hugin-ptx] Re: lux - FOSS multiplatform image and panorama viewer

[Harry van der Wolf]

This happens more often with manually installing debian packages.

So you do a "sudo dpkg -i lux-.dpkg" and get this error.
What you now should do is a:
"sudo dpkg --configure -a"
followed by:
"sudo apt-get -f install"

That should fix it.
And if you had done a simple DuckDuckGo/Google search, you would have found
that as well as it is as old as the world (well, almost as old).

This could be solved by creating a flatpack or appimage which has
everything "inside".

Harry

Op za 5 jun. 2021 om 10:37 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> Am 05.06.21 um 05:31 schrieb David W. Jones:
> > Well, here's what happened when I tried to install it here on Debian 11:
> >
> > Preparing to unpack lux-1.0.9-0git-Linux.deb ...
> > Unpacking lux (1.0.9-0git) ...
> > dpkg: dependency problems prevent configuration of lux:
> >   lux depends on libc6 (>= 2.29); however:
> >Version of libc6:amd64 on system is 2.28-10.
> >   lux depends on libexiv2-27 (>= 0.25); however:
> >Package libexiv2-27 is not installed.
> >   lux depends on libgcc-s1 (>= 4.0); however:
> >Package libgcc-s1 is not installed.
> >   lux depends on libstdc++6 (>= 9); however:
> >Version of libstdc++6:amd64 on system is 8.3.0-6.
> >   lux depends on libvigraimpex11 (>= 1.11.1+dfsg); however:
> >Package libvigraimpex11 is not installed.
> >
> > dpkg: error processing package lux (--install):
> >   dependency problems - leaving unconfigured
> > Errors were encountered while processing:
> >   lux
>
> Thanks for reporting back!
>
> The dependencies are the same as they have been throughout lux 1.0.8;
> this issue is not new with 1.0.9:
>
> I've probably misled you by simply stating that I made a 'debian
> package': I develop lux on ubuntu, here I use ubuntu ubuntu 20.04.2 LTS,
> which should differ quite a bit in the set of packages and their
> versions to your debian 11, which is also quite brand-new and has not
> been released yet. What surprises me is that dpkg can't get hold of
> common packages like libexiv2, libgcc and libstdc++, but these may be
> naming problems, where the ubuntu naming scheme differs from debian's.
> In general, you can't rely on ubuntu-built packages to run on debian.
>
> I'll change the name of the packages I offer for download to make clear
> what the target distro is, to help other users avoid this pitfall. As
> far as ubuntu goes, basing on 20.04 LTS is quite conservative, and the
> dependencies should work on newer non-LTS distros as well - ubuntu
> users, please report back! For now, there are two debian packages I can
> offer:
>
> https://bitbucket.org/kfj/pv/downloads/lux-1.0.9-0-debian10-i32.deb
> https://bitbucket.org/kfj/pv/downloads/lux-1.0.9-0git-ubuntu20.04-amd64.deb
>
> As you can see, the debian 10 package is 32 bits - I currently don't
> have a 64bit install of debian 10 handy, but I just did the CMake build
> here on the debian10 32bit system to verify that it builds and installs
> without problems, so I thought I might as well put it up for download.
> The ubuntu20.04 amd64 package is the same as what I had offered before
> as the 1.0.9 'Linux' package, only with a clearer name. Sorry for the
> confusion.
>
> How about you build a debian package on your machine? Then we can have a
> look at what your system puts into the .deb. Just follow the steps in
> 'Building lux with cmake' given on the bitbucket page. Then I can put
> your package online if you like, to help other debian 11 users. To build
> a debian package, you have to invoke cmake with -DCPACK_BINARY_DEB=ON
> during cmake configuration, and to build the package you have to say
> 'make package'.
>
> Are you dd or involved with the debian project? How about you help
> bringing lux to debian? With an actively maintained lux package on
> debian, we might rely on it trickling down to ubuntu and other
> debian-based distros - I've done this successfully with the vspline
> debian package, but that's already quite a bit of work, and I've shunned
> going through the laborious process for yet another package - especially
> as I don't have dd status and have to bother my mentor whenever I have a
> new version.
>
> @Kornel: Is there a way to provide 'linux bundles' which include all
> shared libraries, as I make them for the Windows stickware version? Can
> CMake output flatpak or a similar format which works on more distros?
>
> The CMake package build produces a package named
> 'lux-1.0.9-0git-Linux.deb', can we influence the naming of the package?
> It might be good to have 'ubuntu' or 'debian' in the package name rather
> than 'Linux', and also the version, like 20.04, and the architecture,
> like amd64 - I've done the naming of the two packages I just put up for
> download manually.
>
> Kay
>
> --
> 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 

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

This PV.icns is actually a MacOS package containing 5 or 6 icons for the
several screen resolutions to use on.
On MacOS you can simply open the package, select one of the icons and
export is as png (or jpg).
I will have a look.
Otherwise you can use the original svg and convert it to png or ico.

Harry

Op do 27 mei 2021 om 10:02 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> Am 27.05.21 um 09:55 schrieb Brian Ims:
> > Hi Kay,
> > I'll have a go but here is some of my ignorance showing - where do I
> > find the scripts folder with the icons?. I have looked in bitbucket but
> > cannot see anything that resembles an icon
>
> Try this one:
>
> https://bitbucket.org/kfj/pv/src/master/scripts/PV.icns
>
> I'm not sure about the format - I managed to get windows to accept it as
> the source for an icon, even though I believe it's a mac format. If you
> can't get it to work, ask again and I'll try and find a different format!
>
> Kay
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/27749d91-b9dd-1028-a1ce-61a153804d36%40yahoo.com
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpssW4aLhGUTfCMtj3tRYcGn4oS_wUQz4jVvixQPBC2Ndw%40mail.gmail.com.

Re: [hugin-ptx] Hugin 20.0 does not see external drive

[Harry van der Wolf]

@Brian,

Like I mentioned in an earlier post. If, in Ubuntu, you add a usb-stick or
SD-card it is automatically mounted under /media/.
In the file explorer it shows up as a shortcut in the left navigation pane.
In Hugin you need to go to /media//.
It is already working for centuries like that in Hugin.

Did you even try that? You do not even report back what you tried after
users here try to help you.
You only repeat your earlier statements.

Op ma 3 mei 2021 om 06:57 schreef David W. Jones :

> Well, I just tested using the same version of Hugin on Debian 10 (not
> Ubuntu). I clicked Add Images and was able to navigate to my external
> hard drive without any problems. But I think I had mounted it earlier
> for other reasons.
>
> On 5/2/21 3:46 PM, Brian Charles wrote:
> > It is available in the normal file explorer rad well as other programs,
> > for example Dark Table, to open files from.
> >
> >
> > On Sun, May 2, 2021 at 5:58 PM David W. Jones wrote:
> >
> > I don't think Hugin has any concept of a drive outside of what the OS
> > mounts as a drive (removable or otherwise). If a drive isn't mounted
> > when Hugin goes to add some images, the drive isn't there at the OS
> > level for Hugin to see.
> >
> > I have a number of SMB drive mounts in my fstab. Debian 10 changed
> > things so SMB drives were no longer mount during the boot process.
> > (Rather, it would try to mount them before the network was up, fail,
> > and
> > not try again.) There was a parameter I had to add to tell it to
> > automount the SMB shares - x-systemd.automount.
> >
> > Have you considered setting your external hard drive to automount?
> >
> > On 5/2/21 8:36 AM, Brian Charles wrote:
> >  > I am updated Hugin to 2020.0.0.2f576e5d5b4a and when I sue the
> "load
> >  > images" button I cannot navigate to my external hard drive. This
> was
> >  > possible in the older version of Hugin that I was running. maybe
> > there
> >  > is a command line entry that I need to add to get Hugin to see
> > external
> >  > drives
> >  >
> >  > Brian
> >  >
> >  >
> >  > On Sat, May 1, 2021 at 11:24 AM Gunter Königsmann wrote:
> >  >
> >  > In the newest Ubuntu USB media might be mounted only after
> > you have
> >  > clicked on it in Nautilus or similar...
> >  >
> >  > Am 30. April 2021 16:58:41 MESZ schrieb Brian Charles:
> >  >
> >  > Thanks. For the suggestions. I may have just
> forgotten which
> >      > directory to look in. I upgraded Hugin and it had
> previously
> >  > been able to navigate to an external usb hd when loading
> > files.
> >  > I will check the media directory.
> >  >
> >  > Brian
> >  >
> >  >
> >  > On Thu, Apr 29, 2021 at 12:54 PM Harry van der Wolf wrote:
> >  >
> >  > I guess you mean you see shortcuts in the left
> navigation
> >  > pane of your file explorer with the name of your usb
> > disk.
> >  > If you want to find that same usb disk via Hugin in
> > Ubuntu,
> >  > you need to go to /media// > disk>
> >  >
> >  > Harry
> >  >
> >  > Op wo 28 apr. 2021 om 13:32 schreef Brian Charles:
> >  >
> >  > I just updated Hugin on my Ubunto distro and it
> > does not
> >  > see my external drive. It is seen in my file
> > explorer.
> >  > Any suggestions?
> >  >
> >  > Thanks.
> >  > Brian
>
>
> --
> David W. Jones
> gnomeno...@gmail.com
> wandering the landscape of god
> http://dancingtreefrog.com
> My password is the last 8 digits of π.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/bc27181c-5cfa-0e4b-0fe6-9dadf2781846%40gmail.com
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvRPFy3cerfRQSMjnbRTbWvNeHpmNgRVgxtyEFFv%3DbEPw%40mail.gmail.com.

Re: [hugin-ptx] Hugin 20.0 does not see external drive

[Harry van der Wolf]

I guess you mean you see shortcuts in the left navigation pane of your file
explorer with the name of your usb disk.
If you want to find that same usb disk via Hugin in Ubuntu, you need to go
to /media//

Harry

Op wo 28 apr. 2021 om 13:32 schreef Brian Charles :

> I just updated Hugin on my Ubunto distro and it does not see my external
> drive. It is seen in my file explorer. Any suggestions?
>
> Thanks.
> Brian
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/02172c49-c820-4b05-9868-fb19701786adn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpt%2BtsTsd7yJTpO8-Z5mwz-1ddYvtq1XwoT0evNxhzak-Q%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Mac users,

I uploaded a new LUX-1.0.8.dmg containing Kay's lux 1.0.8 to mega.nz

link:
https://mega.nz/file/dB8VTK4b#SsbNSPoU_D69ehcQixO3rCyT6iXy2jjYJUhGOhUEsxg
Only very few app bundles support command-line parameters. That has nothing
to do with lux, but how Apple wants to treat their "stupid" users who can't
remember a number of parameters, by providing an app bundle from within you
do everything.
For lux that is really inconvenient.


So for that reason I also created a "distributable binary" (next to the mac
bundle). It consists of a folder LUX containing the lux binary and the
necessary libraries to be able to run it on any Intel Mac.
link:
https://mega.nz/file/1A83BSSK#uvVLvFKrhzjUJF0PuZf2hF41yCnN_2tkU5iizT9n2ik
Unzip it with folders!, meaning that you will get a folder LUX, containing
lux and a subfolder lib containing the libraries.
Start lux from the command line (from inside the folder LUX with "./lux"
with all parameters you want to add), or use some script with your
parameters.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvubaa-JTpW2tFe-VAWv_xoo23xcaBA%2BPeghRz-OtH%3DVA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op za 10 apr. 2021 om 18:42 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> I tested 1.0.8 quite throroughly, so it's probably best if you pick that
> version, just use
>
>git checkout 1.0.8
>
> to get precisely that version.
>
> I had done that and got the exact same results.
The issue was simply the mentioned "-C" for align_image_stack in
combination with the new cropped output. I had not even thought of that.


> p-line processing is quite a recent addition, but it's in 1.0.8 for
> sure. Please let me know if this solves your issue!
>
> Kay
>
>
The functionality now works great.
I will create a 1.0.8 mac bundle.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuDTQ3DZ2OWOWAV203zDXv92bb7whvoDrD0i8_CV3c_%3Dg%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Hi,

I did not forget about lux.
8 days ago the graphics card of my laptop gave up. Yesterday finally my new
laptop arrived after 4 days delay in the warehouse.
This morning I downloaded the latest lux from git and compiled it.
I got in general good results, but also ran it on a series of test images
and got strange effects on the edges. Note that I took a lux version of
8~10 days old which had the same issue but also "dark areas" in the images.
As that is now "solved" in this latest version, I did not include those
images.

I first run align_image_stack on the images which delivers a pto.
Then I run lux with
lux -W \
 --blending=hdr \
 --snapshot_like_source=yes \
 --snapshot_facet=1 \
 --snapshot_prefix="${PREFIX}" \
 --snapshot_extension=$SUFFIX \
 --aeb_auto_brightness=yes \
 --next_after_fusion=yes \
 --build_pyramids=no \
 --build_raw_pyramids=no \
 --quality_interpolator_degree=1 \
 --snapshot_threads=4 \
 "${PTO}"

See attached my luxfuser.sh script, but renamed as luxfuser.txt

In my Google drive you will find 2 examples which were simply taken because
of blue sky, hard lights, a glistening river and dark trees.
See 2 tars: br2.tar and br3.tar.
https://drive.google.com/drive/folders/1j-YKHd8TDP0UvPsVUZrXXJ7dHbDrXDiA?usp=sharing

You will find the source images as *.JPG
the align_image_stack/lux image as lux.jpg
the align_image_stack/enfuse image as -enfuse.jpg
the hugin images (align_image_stack/nona/enfuse) image as _fused.jpg

The lux.jpg has strange "cadres" around the image.

Any idea?

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvTLhQZo%3DajOMfbs4uYR056tCQ%3D14T2gAT30GKCTrnv5Q%40mail.gmail.com.
#!/bin/bash

#lux image fuse script

LUX="/usr/local/bin/lux"
ET="/usr/bin/exiftool"

Info () {
printf "* First give the target file name like 
\"/myluxfused.jpg\" or \"/myluxfused.tif\" or 
\"/myluxfused.exr\"\n"
printf "* Then give the input files. That can be as \"*.jpg\", or as 
\"one.jpg 2.jpg 3.jpg\"\n"
printf "* Examples:\n* /path/to/luximagefuser.sh myluxfused.jpg br1.jpg 
br2.jpg br3.jpg\n"
printf "* Or:\n* /path/to/luximagefuser.sh myluxfused.jpg *.jpg\n\n"
exit
}



## main part ##
# No output given?
if [ "$1" = "" ]
then
Info;
fi
OUTPUT=$1
PREFIX=$(echo $OUTPUT | cut -d"(" -f2 | cut -d"." -f1)
SUFFIX=$(echo $OUTPUT | cut -d"(" -f2 | cut -d"." -f2)
PTO=$(echo $OUTPUT | cut -d"(" -f2 | cut -d"." -f1)".pto"
# Now shift our parameters to exclude our to be created fused image from the 
image processing
shift;

printf "\n\n* Running align_image_stack on our images\n\n"

align_image_stack --gpu -p "${PTO}" -v $@
printf "\n\n* Done with ais; now running lux on our aligned images\n\n"
${LUX} -W \
 --blending=hdr \
 --snapshot_like_source=yes \
 --snapshot_facet=1 \
 --snapshot_prefix="${PREFIX}" \
 --snapshot_extension=$SUFFIX \
 --aeb_auto_brightness=yes \
 --next_after_fusion=yes \
 --build_pyramids=no \
 --build_raw_pyramids=no \
 --quality_interpolator_degree=1 \
 --snapshot_threads=4 \
 "${PTO}"
# If we named our image "myluxfused.jpg", lux will create 
"myluxfused.pto.lux.1.fused.jpg"
# So we will first rename it to our desired name
mv "${PREFIX}1.fused.${SUFFIX}" "${OUTPUT}"
if [[ ! ( "$SUFFIX" == "exr" || "$SUFFIX" == "EXR" ) ]];
then  
  printf "\n\nFinally running exiftool to copy the metadata from our first 
image to our fused image \"${OUTPUT}\"\n\n"
  ${ET} -overwrite_original -TagsFromFile $2 "${OUTPUT}"
  ${ET} -v "-DateTimeOriginal>FileModifyDate" "${OUTPUT}"
fi

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op ma 22 mrt. 2021 om 10:47 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> This is done with --snapshot_magnification=..., as described in my post.
> If your screen is 1920X1080, you work fullscreen,  and you have
> --snapshot_magnification=10, your output on pressing 'p' will be
> 19200X10800
>

Yes, I must admit I skipped too fast over that, but I was looking for a
"screen command". Your command line option requires me to first check the
approximate size of the image, then give the magnification on the command
line, and then press the "p" once you are zoomed out.
How do I do that in the live view without specifying all kind of things on
the command line (which you always need to remember)?

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptZwTMfOSsGv3PradW8qdyvoPQKU%2BAKvcaVoG4j7mkG3Q%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op ma 22 mrt. 2021 om 10:24 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

> Am 22.03.21 um 09:56 schrieb Harry van der Wolf:
> >
> > Op zo 21 mrt. 2021 om 18:17 schreef 'Kay F. Jahnke' via hugin and other
> > free panoramic software  > <mailto:hugin-ptx@googlegroups.com>>:
> >
> >
> > Found the 'black output' bug and fixed it. Please rebuild.
> >
> > The black image is fixed now
>
> Thanks for reporting back!
>
> > but I find it confusing that when I have a
> > wide panorama, I have to zoom out to get the entire panorama in view
> > (without the distortions on the side) before I can press "p" to stitch
> it.
> > And the panorama is for example 1800x355 (to fill the screen), and that
> > is then also the resolution it is saved in.
> > I thought the stitching would take the pto parameters into account.
>
> There are two things going on here. The first is the 'target
> projection'. That is the projection used to display the data on-screen,
> which is also used to produce snapshots, stitches, and fusions. A
> panorama with 1800x355 looks like a stripe panorama, which you may want
> to render in spherical or cylindric projection. Use
> --target_projection=spherical or --target_projection=cylindric. The
> default in lux is to display in rectilinear, as if the user was looking
> at the scene with a 'normal' lens, but you can't use that for very
> wide-angle images.
>
>
That is not what I mean.
The original pano when stitched is indeed a partial stripe like panorama in
the resolution 11000x3600 pixels (just as example. I actually only make
partial panoramas).
Lux creates the pano snapshot of what it is visible in the viewer. As my
screen is 1920x1080, I need to zoom out in LUX to get the picture more or
less "full in view".
If I now press "p", I get a panorama maximum the size of my screen width,
instead of (approximately) the original size.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpteWOmSvCeNy7ohGF5hky1NaMqFqNZM7vb%2B8sBTLh8R7w%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op zo 21 mrt. 2021 om 18:17 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

> Am 21.03.21 um 17:54 schrieb 'Kay F. Jahnke' via hugin and other free
> panoramic software:
>
> > Am 21.03.21 um 13:31 schrieb Harry van der Wolf:
> >> So it only takes image 0 and 1, and then still delivers a black image.
> >
> > I can confirm here that I get black JPG and TIF output, which seems to
> > be a bug. I'll investigate...
>
> Found the 'black output' bug and fixed it. Please rebuild.
>
>
The black image is fixed now, but I find it confusing that when I have a
wide panorama, I have to zoom out to get the entire panorama in view
(without the distortions on the side) before I can press "p" to stitch it.
And the panorama is for example 1800x355 (to fill the screen), and that is
then also the resolution it is saved in.
I thought the stitching would take the pto parameters into account.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvW7dwhF2C4RAC74spbDH%2B3vULJ%3D3zfNugY%2BLUiYMhqww%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op zo 21 mrt. 2021 om 17:54 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> I downloaded the three-image alaska 'panorama'. It uses translation
> parameters, which lux does not process, hence the failure. The image is
> not a panorama: The three partials have been taken from different
> positions, always facing the facades, probably several meters apart.
> It's an attempt to create a 'street view-like' image mosaic from a 3D
> scene (dodgy, mosaics are for 2D content), hence the translation
> parameters to attempt a fit, which works okay-ish because the facades
> are roughly in-plane.
>

The Alaska one is the only one I didn't try.
But I never paid attention to the TrX, TrY and TrZ parameters. My 2 image
pano is a hand-shot pano which I initially used for parallax. And yes: it
needs translation parameters as well.
It is just small and handy and a quick test.
I will take one of my other panos, but lately I don't do much panos.
Only bracketing and noise reduction with ais and enfuse. (burst mode with a
number of photos. I never had nor will buy a full-frame so I sometimes make
burst-mode photos and ais/enfuse them to remove the noise. Works great)
I will test pv/lux as well with noise reduction.

>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpv%3DwJ%2BZ%3DE%2BVErbemqy5Xwnwz7k-YApjoFxwwTWK-ZoNzA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op zo 21 mrt. 2021 om 13:05 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> Fine, so it didn't work. Why don't you just zip the PTO and images and
> mail them to me? I'll have a look.
>
>
The 2 image PTO is from my living room with a lot of "small rubbish" in
there to test on parallax on short distances. I am not going to share that
one ;)

Donald Johnson shared a number of downloadable pano sets for multiblend in this
post .
Or directly:
https://ln2.sync.com/dl/f27685a80/392a24qm-7uudw2mp-4vzsr5eg-qaj852qx
https://ln2.sync.com/dl/310817b80/vxegvztw-7ixx2fqu-8q5h6kr8-8g7789m8
https://ln2.sync.com/dl/380fc1290/x63ceeax-pnft3mpd-fhub63bd-gcasikxn
https://ln2.sync.com/dl/b7d757380/68iyddwc-puc3yr7d-exqjavjv-mpmg4rnh

Note: all rights and credits to Donald Johnson.


> - Then I took a 4 image wide landscape based panorama from one of the
> > multiblend test sets (for which I created the mac binary). The pto loads
> > OK and shows OK. It does a nice live stitch indeed, although it doesn't
> > blend well on the overlap, but you get a nice impression.  when pressing
> > "p" it again creates a black image the size of one image.
>
> Sound like you pressed Shift+P, which is not good for stitches.
>

I definitely pushed "p", but also tried "Shift+P" when "p" did not give the
results. Just like "u" or "shift-u".
 And just did pressing "p" again on 3 of Donalds panoramas, just to be 300%
sure. Again all ending in the same black image.
Note that when pressing "p" I get the following lines on the console:
active facets for stitching job: 0 1
generating partial image and mask for facet 0
merging weighted laplacian pyramid
generating partial image and mask for facet 1
merging weighted laplacian pyramid
generating 'baseline' image
merging weighted laplacian pyramid
Writing user comment EXIF tag: .Projection: Rectilinear (0)
FOV: 53.130102 x 31.417276
saved stitched result as _DSC3060DC - _DSC3066DC.pto.pv.1.pano.jpg

So it only takes image 0 and 1, and then still delivers a black image.


> I'll have to go through the docu. It's a large field, and under current
> development, so please bear with me.
>
>
I fully understand.

I'll try and make the docu better.
>

It is already a great reassurance that loading an aligned, exposed pto or
ini, and pressing "p" is the right thing to do.
Unfortunately for me not with the desired results.


Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpt6QXZJ8kJy%3Dx%2Bwxe%2BUOwAkwB_6ByD4Qa_NehED-O4zaw%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

With regard to the panorama image stitching.
Do I really need a complete pto or ini?
If I need to do all the steps in hugin or via the command line tools, and
then open that in lux and stitch from lux, I currently do not see the
benefit of lux for panorama stitching.
Only as exercise how good lux can do that.

Harry


Op zo 21 mrt. 2021 om 12:22 schreef Harry van der Wolf :

>
>
> Op zo 21 mrt. 2021 om 10:26 schreef 'Kay F. Jahnke' via hugin and other
> free panoramic software :
>
>>
>> This thread announces two new features in lux, namely stitching images
>> and doing exposure fusion with the Burt and Adelson image splining
>> algorithm. Harry has used lux' exposure fusion capabilities, but so far
>> - and quite suprisingly - there are no reports of image stitching, even
>> though all it takes is to press a single key on the keyboard. I had
>> hoped for some sort of 'peer review' of my modified implementation of
>> the B algorithm, and I posted early to give interested people the
>> opportunity to take an interest in ongoing development.
>>
>
>
> I did have a look at stitching some time ago and this morning again, but
> it is not clear to me.
> This morning using the latest lux on my linux box.
>
> - I tried a simple, fully optimised and aligned 2 image pto: I could not
> make that work (while Hugin created a nice pano), and it does not show it
> as a pano, but as 2 badly completely overlying images.
>   I then converted that pto into an ini using your pto2pv.py and loaded
> that one. I had to rotate that one as PV does not recognise the portrait
> like images. It simply shows a very high and small  image
> (Shift-hold-left-click-drag to rotate them 90 degrees counter-clockwise),
> and then pressed "p" to stich it. That gave me a black image the size of
> one image.
> - Then I took a 4 image wide landscape based panorama from one of the
> multiblend test sets (for which I created the mac binary). The pto loads OK
> and shows OK. It does a nice live stitch indeed, although it doesn't blend
> well on the overlap, but you get a nice impression.  when pressing "p" it
> again creates a black image the size of one image.
> - Using the snapshot "button" in the viewer or Shift-snapshot button
> didn't help either.
>
> I also tried by simply loading a panorama images and "monkey like" press
> keys and screen buttons, but that doesn't make it work either. Then it only
> acts as an image viewer.
>
> I re-read your readme a couple of times, but didn't find the right clue on
> how to do it.
> Being busy on a lot of other things as well (with hugin doing a great
> job), I waited for others to report and learn from their experiences.
> But indeed: nobody did. So that was "some time ago".
> This morning I tried again, using the latest lux, but couldn't make it
> work either (via above steps). Maybe it is my ignorance, but the process is
> not clear.
>
> So that is my report ;)
>
> Harry
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvc45gL2GDj8h_OvJxKCTivhufJyXqT%3DLfQG2g5JjQBWA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op zo 21 mrt. 2021 om 10:26 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> This thread announces two new features in lux, namely stitching images
> and doing exposure fusion with the Burt and Adelson image splining
> algorithm. Harry has used lux' exposure fusion capabilities, but so far
> - and quite suprisingly - there are no reports of image stitching, even
> though all it takes is to press a single key on the keyboard. I had
> hoped for some sort of 'peer review' of my modified implementation of
> the B algorithm, and I posted early to give interested people the
> opportunity to take an interest in ongoing development.
>


I did have a look at stitching some time ago and this morning again, but it
is not clear to me.
This morning using the latest lux on my linux box.

- I tried a simple, fully optimised and aligned 2 image pto: I could not
make that work (while Hugin created a nice pano), and it does not show it
as a pano, but as 2 badly completely overlying images.
  I then converted that pto into an ini using your pto2pv.py and loaded
that one. I had to rotate that one as PV does not recognise the portrait
like images. It simply shows a very high and small  image
(Shift-hold-left-click-drag to rotate them 90 degrees counter-clockwise),
and then pressed "p" to stich it. That gave me a black image the size of
one image.
- Then I took a 4 image wide landscape based panorama from one of the
multiblend test sets (for which I created the mac binary). The pto loads OK
and shows OK. It does a nice live stitch indeed, although it doesn't blend
well on the overlap, but you get a nice impression.  when pressing "p" it
again creates a black image the size of one image.
- Using the snapshot "button" in the viewer or Shift-snapshot button didn't
help either.

I also tried by simply loading a panorama images and "monkey like" press
keys and screen buttons, but that doesn't make it work either. Then it only
acts as an image viewer.

I re-read your readme a couple of times, but didn't find the right clue on
how to do it.
Being busy on a lot of other things as well (with hugin doing a great job),
I waited for others to report and learn from their experiences.
But indeed: nobody did. So that was "some time ago".
This morning I tried again, using the latest lux, but couldn't make it work
either (via above steps). Maybe it is my ignorance, but the process is not
clear.

So that is my report ;)

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptEq3azmCY_KPyoMFCiD8xORwNZ6pQFQbVPM%2B0K3GR_9Q%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op za 20 mrt. 2021 om 12:11 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> Okay, if you're both against the mac branch, I'm not too attached to it.
> I've merged it back into master, so now the 'scripts' folder from the
> mac branch is in master. I'll delete the mac branch eventually.
>
> I'm not against it :)
It is a matter of preference.
Thanks.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuJ97%2BynOoc%2BY%2BJcOcSiCJvY_4ejOhZpQOfoCBPF5TZAQ%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op vr 19 mrt. 2021 om 18:53 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> @Harry: what do you think?
>
> Kay
>
>
Although it is only a "git checkout mac", I also prefer one branch. The
power of cmake is that you can combine it. This will allow users to make
packages for the environment.
If you do not agree with this, then the .deb functionality should be
removed as well from the CMakeLists.txt as that is also a platform
dependency.
But it is not a big deal to me.

I just did a git pull two two folders and then
diff -qr maclux/ linuxlux/ | grep -v ".git"
Files maclux/CMakeLists.txt and linuxlux/CMakeLists.txt differ
Files maclux/makefile and linuxlux/makefile differ
Only in maclux/: scripts

So only the makefile and CMakeLists.txt differ and probably because they
are not aligned yet.
The scripts folder could be renamed to mac-scripts or so (git mv scripts
mac-scripts). This will make it clear to every developer/compiler that it
has nothing to do with linux/windows.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptdT4KBUP8M8jHXubO0g%3DsCVoQo_QzSE935ge109c9DDA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op vr 19 mrt. 2021 om 08:41 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

> Am 18.03.21 um 21:21 schrieb Harry van der Wolf:
> > I can't find the question backs, but you asked me about the speed after
> > your improvements.
> >
> > The current version is about 10-15% faster.
>
> Ha, that's nice to hear, Did you look at memory consumption, too? That's
> where I had hoped to see about 30% improvement , because I switched to
> single-float masks.
>
> Yes, that too. The memory usage went from 3.2GB to 2.7GB for the image
sets I used (sets of 5 brackets of 13.5MB).

With regard to the " --snapshot_threads=X".
That still doesn't work for me. I tested on linux on the master repo. I
have a 4-core CPU. no matter whether I set X to 4, 3 or 2. Always all 4
cores are used and it actually creates many more processes.

The command I use from my batch file is:
${LUX} -W \
 --blending=hdr \
 --snapshot_like_source=yes \
 --snapshot_facet=1 \
 --snapshot_prefix="${PREFIX}" \
 --snapshot_extension=$SUFFIX \
 --aeb_auto_brightness=yes \
 --next_after_fusion=yes \
 --build_pyramids=no \
 --build_raw_pyramids=no \
 --quality_interpolator_degree=1 \
 --snapshot_threads=3 \
 "${PTO}"

In this case you see " --snapshot_threads=3", but of course I did vary that
number.

Best,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsUEj_zTgsJvDntE76ZqP6%3D0kNC3gXCUZ_OZG8QPO8q2w%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

I can't find the question backs, but you asked me about the speed after
your improvements.

The current version is about 10-15% faster.

I built with cmake on linux and get a binary lux. sudo make install
installs the font and font readme in /usr/local/share/lux/fonts where lux
can find it.

On MacOS I also build with cmake (cmake .. -D
CMAKE_INSTALL_PREFIX=/opt/local).
But it still builds pv instead of lux.

sudo make install does install pv in /opt/local/bin
It installs the font in /opt/local/share/pv/fonts, but it does not install
the font readme on mac.
pv can find the font on mac.
I will have to look what I need to specify as install prefix to make pv
find the font in the bundle, or that the bundle requires an extra setting
for bundle builds.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuoRCUMYrM3%2B7ejD%2B0eoc7C4fkEyG9kzBsuhQUgOC4eFw%40mail.gmail.com.

Re: [hugin-ptx] Re: Project files

[Harry van der Wolf]

I agree with Thomas.

Why would you even do this?
The AppData/Local/Temp folder contains temporary files (hence the name)
These files contain temporary information while a process is creating other
files, or while a process is doing something and "saving" the process steps
in between.
The files are only there in case the program crashes or windows crashes or
something like that, so that on restart the files can be used again (if you
are lucky) where your program/windows crashed.
Normally, Windows deletes those files once the program closes.



Op wo 17 mrt. 2021 om 19:58 schreef T. Modes :

>
>
> Viktor schrieb am Mittwoch, 17. März 2021 um 18:38:08 UTC+1:
>
>> Hello!
>>
>> I'm just getting started with Hugin, but I encountered a problem: When I
>> saved the project the filenames got incorrect inside the project file. To
>> make it even more interesting it only happens when working inside
>> %localappdata%\Temp folder and aligning already done (there is no problem
>> before aligning or outside of temp folder).
>>
>
> It is now fixed in the repository.
> The TEMP folder should only used for temporary files. It should not used
> IMHO for user data like images. Hugin itself is using this folder for its
> temporary files.
> So this bug is a very rare edge case.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/35ab3e08-a9a6-4fb8-b47a-de24a1f8e376n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsAsb--Zibne%2B70aJJmNZXgyQyoP_D26FSEJPTq_MOaBA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Question of compilation of pv/lux.

Whether you use cmake or simply the makefile based make, compilation takes
quite some time.
When using "make -j 4" to use 4 cores for compilation instead of 1, the
compilation is much faster.
Of course not every software is suitable to do this. At least not (quite)
some years ago (I was Apple maintainer for avidemux which did not support
it) and I really don't know if that has changed in general.
Can I use multiple cores to compile pv/lux?
I did a compilation this evening and so far I did not find issues.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpud5czHbY3g9nxRsMJOJ1WvFcE_r2U73UKR%3DArDVuPR1g%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op ma 15 mrt. 2021 om 11:55 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> Bear with me... it's a python script and the exiv2 module has changed
> quite a bit, I'll need some time to get it running again.
>

No problem. You gave me a hint that I should have thought about myself. So
thanks. Really. :)
I am a heavy exiftool user (both on command line and via my jExifToolGUI)
and in exiftool I can do  "exiftool -S -csv -filename -BracketSettings
-ExposureCompensation -Sequencenumber fz82-br1*.jpg"
which gives me:
SourceFile,FileName,BracketSettings,ExposureCompensation,SequenceNumber
fz82-br1_20210310-01.jpg,fz82-br1_20210310-01.jpg,"5 Images, Sequence
0/-/+",0,1
fz82-br1_20210310-02.jpg,fz82-br1_20210310-02.jpg,"5 Images, Sequence
0/-/+",-1,2
fz82-br1_20210310-03.jpg,fz82-br1_20210310-03.jpg,"5 Images, Sequence
0/-/+",+1,3
fz82-br1_20210310-04.jpg,fz82-br1_20210310-04.jpg,"5 Images, Sequence
0/-/+",-2,4
fz82-br1_20210310-05.jpg,fz82-br1_20210310-05.jpg,"5 Images, Sequence
0/-/+",+2,5

So I can make my own script running over a folder, but I will investigate
it better first. I could use some output options from exiftool to format it
slightly better for easier parsing.
I might even add that to my jExifToolGUI
 as some kind of "export" option
(pushing it to align_image_stack/pv or align_image_stack/enfuse) after
having modified the metadata and keywords..

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsb9SBAo%3D5qbDS_KEvqdxcD1YMep6q7gJb_EiD9Om_GUg%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op ma 15 mrt. 2021 om 08:26 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> I usually work with folders. My workflow is like this:
>
> - initially, all images are in one folder
>
> - I run a script detecting brackets, which puts each bracket in a
> separate folder, named sth. like IMG_0001_IMG_0003. If you're
> interested, I'll share the script.
>
> - next I run the pto-generating script in each of these folders,
> producing a PTO named bracket.pto in each folder.
>
>
Can you share that bracket detecting script?

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptXRutkH46ROHaZ-9jqz5oo-Mh7ip5p2%3DUKTpmvNq44RQ%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Hi,

Thanks for the tip, but that does not really help.

I had mv "${PTO}.pv.1.fused.${SUFFIX}" "${OUTPUT}" in the script.

When I use the --snaphot_prefix="${PREFIX}", I get an image like
${PREFIX}1.fused.${SUFFIX}.

The "1.fused" does not really help in this case as I will now get
"${PREFIX}1.fused.${SUFFIX}" and I still need to do the renaming.
Or accept the "1.fused" and do some "magic" with name shuffling in my
exiftool command, because it is not the name I specified.

I am so stubborn that if I choose an output name, I also want that exact
output name. ;)

Harry

Op zo 14 mrt. 2021 om 19:29 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

> Am 14.03.21 um 14:20 schrieb Harry van der Wolf:
> > Another script for pv for Linux/BSD/MacOS.
> >
> > ...
>
> Harry, you could use --snapshot_prefix=...
>
> if you pass --snaphot_prefix=my_prefix
>
> you get my_prefix.fused.exr
>
> Kay
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/5e886904-4b74-ae78-0965-3ec4195d60c4%40yahoo.com
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpugBJT78nV_NH%3Dd8Lr8VsRgogfZqcTkrRM5V8eRJEW6NA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Another script for pv for Linux/BSD/MacOS.

It uses align_image_stack from hugin tools and it also uses exiftool (if
you have hugin, you almost certainly also have exiftool)
It works for jpg, tif and exr.
It uses "--build_pyramids=no --quality_interpolator_degree=1" as it is
meant for batch use and to decrease memory usage.

if the script is started without parameters, it mentions:
* First give the target file name like "/mypvfused.jpg" or
"/mypvfused.tif" or "/mypvfused.exr"
* Then give the input files. That can be as "*.jpg", or as "one.jpg 2.jpg
3.jpg"
* Examples:
* /path/to/pvimagefuser.sh mypvfused.jpg br1.jpg br2.jpg br3.jpg
* Or:
* /path/to/pvimagefuser.sh mypvfused.jpg *.jpg

It uses exiftool to copy all metadata from the first image into the created
image. This doesn't work for exr images as exiftool does not recognise
these.

See attached. Save it to some location of your liking and do a "(sudo)
chmod +x pvimagefuser" (or whatever you want to name it)
It is a rewrite of my enfuse fusing script.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptJwDC4MAau4JMb3cuXG6o-M1bUAwJqMS3Mc7Zz9NYpGw%40mail.gmail.com.


pvimagefuser
Description: Binary data

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op za 13 mrt. 2021 om 17:20 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
>  If your job requires only 1:1 or
> less, try passing --build_pyramids=no, which should reduce the memory
> footprint and be faster as well.
>


> And you can also try and omit the separate 'quality' interpolator by
> passing ---quality_interpolator_degree=1 - the default of three is to
> give you nice magnifications for still images up to single pixels blown
> up to screen size :D
>
> Using
 --build_pyramids=no \
 --quality_interpolator_degree=1 \

makes it faster and decreases memory from 3.7GB to 3.2GB. It also helps to
not completely block my laptop.

I also used the new --snapshot_threads and set it to 3.
However, pv still uses all 4 cores/threads and when I "time" the command it
is exactly the same as without this parameter.


> The next point to consider is mathematics: if I remember correctly,
> enfuse uses a highly optimized integer-math implementation of the B
> image splining algorithm - and it may even offload work to the GPU,
> which would explain why it blocks up your system less - pv is CPU only,
> and does all calculations in single-precision float, and with pyramid
> levels based on cubic b-splines. That's a lot of CPU load, with the SIMD
> units running on all threads you put to use.
>
>
enfuse/enblend uses OpenMP.


>  I don't look at the
> masks in the PTO yet, but you should now be able to simply feed images
> with unwanted content 'erased' to transparency (should even be best with
> a feathered brush on the erase tool), and as long as the other images
> provide content, the 'ghosts' should become invisible, thanks to the B
> magic.
>

I do not entirely understand what you mean. Do you mean I should erase some
unwanted part in one of my bracketed images? or does pv that? Or do you
have to do that in the live view?
This is really interesting. I personally like sunrises and sunsets. You
mostly need bracketed sets to get a good dynamic range.
They sometimes contain unwanted parts or enfuse (up til now my used
program) does not pick the part I want. I sometimes fall back on hugin for
its use of masks. (enfuse does understand masks, but I do have to create
them in hugin so I can just as well finish in hugin)

So: Do you have such images (with pto) as example that shows this
functionality?

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptuiT3r85ZWEht9dbufuM9Eh5DY_mqRpFiczRUNuMysYA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op za 13 mrt. 2021 om 19:12 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> I sucked in the patch best I could and pushed --all, have a look if
> you're both happy with the state of master and mac branches in the repo
> now. and let's do single-file patches from now on, save me headaches...
>
> Kay
>
>
ohoh :(
Crossing mails!

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvW%2BPkBP0MBD83ARr6XwhNwRLJCAAxR%3Dv2PU4-Gv8qPXw%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op za 13 mrt. 2021 om 18:18 schreef Kornel Benko :

> Am Sat, 13 Mar 2021 17:51:26 +0100
> schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
>
> > Is that okay with you guys?
>
> Yes from my side.
>
>
OK from my side as well.



>
> > You might as well simply trust the user. Most people who've come so far
> > as doing their own builds should know that in-tree builds aren't cool. I
> > think it's best to keep it simple, no need to regulate everything. Just
> > my personal opinion...
>
> I don't trust. The messy things start if one tries to use cmake _and_
> automake-build in
> source. Better to omit the mess, less things that may go wrong.
>
>
> I don't even trust myself for that matter. When I was working on the Apple
I worked in the main folder and when ready modifying the CMakeLists.txt and
adding the CMakeModules folder and content, I tried to do a "cmake .."
which of course didn't work, but an error is easily made.
And it doesn't bother the user at all having it in the script. And if the
user does it wrong, he/she is immediately educated why he/she should not do
that. Keep things neat and tidy I would say.

Please find attached 2 patches.
The cmake.patch is universal and can be applied in all branches. It
contains fixes to the CMakeLists.txt and the CMakeModules (and the
out-of-tree build)
The mac_bundle.patch is only for the mac branch.
Both patches were made with "diff -u" and created from the root source
directory.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptQp8GVowOpABg2iKg0NYgh0JwAsc7E4FWty%3D7Fw_X0%3Dw%40mail.gmail.com.
diff --git a/scripts/make_bundle.sh b/scripts/make_bundle.sh
index 16f73d8..40cd80c 100755
--- a/scripts/make_bundle.sh
+++ b/scripts/make_bundle.sh
@@ -9,16 +9,10 @@
 # This script should be run from the mac-bundle directory and expects the compiled pv
 # in the parent build directory.
 
+# Version 20210312, HvdW, Add version from the pv_version files; use $BINARY more consequent
 # Version 20210306, HvdW, Add version to Info.plist and use version for dmg identification
 
-if [ "$1" = "" ]
-then
-printf "\n\nYou have to provide the version\n\n"
-exit
-fi
-
-Version="$1"
-
+Version="$(cat ../pv_version_first).$(cat ../pv_version_second).$(cat ../pv_version_third)"
 
  Variables ##
 BASE_DIR=$(pwd)
@@ -88,9 +82,9 @@ mkdir -p "${RESOURCES_PATH}"
 printf "* First copy pv, the .ttf, the .icns into our ${APPLICATION_APP_BUNDLE}\n"
 if [ -f ../${BINARY} ];
 then
-  cp ../pv "${APPLICATION_BINDIR}"
+  cp ../$BINARY "${APPLICATION_BINDIR}"
 else
-  printf "\n\n   The pv binary is not available in the parent build directory \n"
+  printf "\n\n   The $BINARY binary is not available in the parent build directory \n"
   printf "   I will exit now \n\n"
   exit 1;
 fi
@@ -101,8 +95,8 @@ printf "* Update the VersionString to $Version and copy Info.plist into our ${AP
 sed -e "s+VersionString+$Version+" Info.plist.base > "${APPLICATION_APP_BUNDLE}/Contents"/Info.plist
 
 
-printf "\n* Now copy the 3rd party libraries and correct the internal rpath in all libraries and in pv\n\n"
-get_libraries ${BASE_DIR}/${APPLICATION_BINDIR}/pv
+printf "\n* Now copy the 3rd party libraries and correct the internal rpath in all libraries and in $BINARY\n\n"
+get_libraries ${BASE_DIR}/${APPLICATION_BINDIR}/$BINARY
 
 
 printf "\n\n* Now we will create the dmg to distribute the app\n\n"
@@ -111,10 +105,10 @@ rm -rf *.dmg
 mkdir -p bundle
 cp ../README.rst bundle/README.txt
 cp ../LICENSE bundle
-cp -a PV.app bundle
+cp -a ${APPLICATION_APP_BUNDLE} bundle
 
 #DATE=$(date +%Y-%m-%d)
 hdiutil create /tmp/tmp.dmg -ov -volname "PV Version ${Version}" -fs HFS+ -srcfolder "./bundle"
 #hdiutil convert /tmp/tmp.dmg -format UDZO -o PV-${DATE}.dmg
 hdiutil convert /tmp/tmp.dmg -format UDZO -o PV-${Version}.dmg
-printf "\n\nDone! You will now find in this folder a \"PV.app\" and a \"PV-${Version}.dmg\"\n\n"
+printf "\n\nDone! You will now find in this folder a \"${APPLICATION_APP_BUNDLE}\" and a \"PV-${Version}.dmg\"\n\n"
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3d561bb..ef37e27 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1,5 +1,5 @@
 #  cmake file for pv
-#  
+#
 #  Copyright Kornel Benko  2021
 #Kay F. Jahnke  2021
 #
@@ -35,12 +35,23 @@
 # cmake ..
 # make
 
+# prevent in-tree building
+if("${CMAKE_SOURCE_DIR}" STREQUAL "${CMAKE_BINARY_DIR}")
+message(FATAL_ERROR "In-source builds are not allowed.")
+endif()
+
+
 set(ENV{CXX} clang++)
 set(ENV{CC} clang)
 
 set(_pv pv)	# 

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op vr 12 mrt. 2021 om 21:28 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

>
> Sorry, I pushed a buggy version: the non-alpha stitching and exposure
> fusion code went into an endless loop. I've fixed that and updated all
> branches in the repo.
>
> I've also made a new bundle for windows, which you can download here:
>
> https://www.magentacloud.de/lnk/f5iohtoR
>
> Password: hugin-ptx
>
> Kay
>
>
And also a new mac bundle, which you can download from here:
https://mega.nz/file/YIsyBAwI#7DbRuJL8aYaPOgrfORkyiw0ZeSiHRqoNPnVdLYra4RQ

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpt%2BHJXP%3D7xx6hqsjhPLrqtT2A9ZJXbtXzZ4F_DgjOcFPA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

I'm sorry.
The linux version is the master branch.
Mac works on the origin/mac branch.

So I should actually create 2 patches.
I simply acted too quickly and combined the two.

So actually the first patch should go on the mac branch, and I should make
a second patch for the master branch.
Or better: Change the makefile in the master branch so that it checks
whether it runs on Apple, gnu linux or win32/win64, and then remove the mac
branch.

And in the CMakeLists.txt file we should have at line 38 something like
# prevent in-tree building
if("${CMAKE_SOURCE_DIR}" STREQUAL "${CMAKE_BINARY_DIR}")
message(FATAL_ERROR "In-source builds are not allowed.")
endif()


Best,
Harry



Harry


Op za 13 mrt. 2021 om 15:30 schreef Kornel Benko :

> Am Sat, 13 Mar 2021 15:11:23 +0100
> schrieb Harry van der Wolf :
>
> > Sorry,
> >
> > I made the patch on my Mac and forgot about the changes for Linux 18.04
> >
> > See attached patch 2 including the changes of the previous patch as well.
> > Do not apply the previous "mac_exiv2_bundle.patch", but only this
> > "mac_exiv2_bundle_2.patch"
> >
>
> We have to wait for Kay anyway. He is ATM the only on I know of who can
> commit.
>
> Applying the patch locally I got errors.
>
> patching file CMakeLists.txt
> patching file CMakeModules/FindEXIV2.cmake
> can't find file to patch at input line 163
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --
> |diff --git a/scripts/make_bundle.sh b/scripts/make_bundle.sh
> |index 16f73d8..40cd80c 100755
> |--- a/scripts/make_bundle.sh
> |+++ b/scripts/make_bundle.sh
> --
> File to patch:
>
> .
> Here, the scripts directory does (of course) not exist.
>
> Apart from that, pv is still compilable. Thanks for the patch.
> (Ask Kay to include your scripts dir)
>
> Kornel
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/20210313153053.14e1dfd3%40admin1-desktop
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuxSy1Pki438P%2ByyNMgz4o%3Dyx%3D5fqo3F8y4pPP0KMQNuw%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Thanks Kay,

I use a likewise script but then using align_image_stack from the hugin
tools (and optimised the pv command with your command. Thanks).
I replace the lines
pto_gen -p0 -o bracket.pto "$@"
pano_modify -p0 --fov=AUTO --canvas=AUTO -obracket.pto bracket.pto
cpfind --sieve2size=5 -o bracket.pto bracket.pto
autooptimiser -p -o bracket.pto bracket.pto
pano_modify -p0 --fov=AUTO --canvas=AUTO -obracket.pto bracket.pto

(Note: I changed "pano_modify -p0 --fov=AUTO --canvas=AUTO -obracket.pto
bracket.pto" to "pano_modify -p0 --fov=AUTO --canvas=AUTO -o bracket.pto
bracket.pto" in the script.)

with one line:
align_image_stack --gpu -p bracket.pto -v "$@"

when using "time pv_fuse.sh" or "time ais_pv_fuse.sh" (my align_image_stack
version), it is twice as fast and with my preliminary tests I do not find
differences.
Next to that: I use the same script with enfuse, meaning align_image_stack
followed by enfuse. Enfuse is currently faster than pv and does not
entirely lock my laptop like pv does. However, the "big wait" is in the
panotools. I don't care about the speed difference between pv and enfuse.
Note also the max amount of memory used by pv versus
align_image_stack/enfuse where ais takes the 0.98GB and enfuse approx.
500MB. All runs using the same five 9.1 megapixel bracketed images and all
creating a jpg instead of an (open)exr image.

Some figures:
pv_fuse (using the pano tools and pv)
real 2m16,020s
user 6m3,251s
sys 0m17,520s
3.7GB

ais_pv_fuse.sh (using align_image_stack and pv)
real 1m22,573s
user 4m2,008s
sys 0m16,343s
3.7GB

enfuse.sh (using align_image_stack and enfuse)
real 0m53,653s
user 1m20,007s
sys 0m4,532s
0.98GB

Both pv and enfuse use all 4 cores in my laptop where pv, for whatever
reason, almost completely blocks my laptop.
I will do further tests.

best,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvLv%2B98m33nLLe8jw21oW4q49Kqqv6KDenJNtFZ4T%3DMFg%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

And a macos bundle with 1.0.7 version which you can download here:
https://mega.nz/file/ZMMmgRCB#5KLXkbNktlOSLLOxTJ1Ecg3Oq3u1x_La5r4w6fsYkZs

Harry

Op vr 12 mrt. 2021 om 11:50 schreef 'Kay F. Jahnke' via hugin and other
free panoramic software :

> Dear all!
>
> I've just released pv 1.0.7, which now has code to stitch and
> exposure-fuse images with alpha channel as well. This makes the feature
> pretty complete. Stitching and fusing alpha channel images should do
> 'the obvious' and look similar to the 'live stitching' and 'live HDR
> blending' which pv displays on-screen. The alpha channel handling is
> quite elaborate: instead of simply discarding all pixels which don't
> have full opacity, I make an attempt of mathematically correct alpha
> blending. The code is fresh and not well-tested, check it out, comments,
> as ever, are welcome.
>
> If your images don't have an alpha channel, but you want to use
> alpha-only features like --facet_fade_out, just start pv with
> --alpha=yes, it will add an alpha channel to the images and produce
> output with alpha channel if your output format supports it (like TIFF
> and EXR).
>
> I've also made a new bundle for windows, which you can download here:
>
> https://www.magentacloud.de/lnk/f5iohtoR
>
> Password: hugin-ptx
>
> Kay
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/6e906c92-8d76-85f0-e98b-329f5c026232%40yahoo.com
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsGwuaQbF9r1RaxdYSn8fAWjusEMnNh2mLTdanhu-hf6w%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Hi,

You released version 1.0.3, but forgot to update the pv_version* files.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuf61JX254dmgBZSQZpmOZ_OgxHABHSpMhZiHyOJy-%2Bvg%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Hi,

I compiled 1.0.3 on my 64bit GalliumOS 3.1 (Ubuntu 18.04 LTS) laptop.
Started pv directly with 5 already aligned tifs. (In Align_image_Stack I
created earlier both a pto and the aligned tifs: align_image_stack -v -p
8X.pto -a 8X P10048x.JPG )

command: pv 8X000?.tif

interpreting trailing args as image files...
image file: 8X.tif
image file: 8X0001.tif
image file: 8X0002.tif
image file: 8X0003.tif
image file: 8X0004.tif


Pressed 'u' and this happened
pv: pv_no_rendering.cc:9063: int inner_main(): Assertion `nfacets' failed.

Started pv again in the same way and pressed 'Shift-U' and exactly the same
error happened.

Then I started pv with the pto as in: pv 8X.pto
Using 'U' or 'Shift-U' now works fine.
I did not do further tests yet.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptgDXAUu3La4LVbmp5c%2BRAA6YG-o5hQ-LA47eLYS%3DhHng%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Sorry. Long mail.

Op za 6 mrt. 2021 om 20:03 schreef yuv :

>
> From far away, it looks like there are four alternatives:
> (a) do nothing;
> (b) distribute pv along Hugin;
> (c) integrate pv's functionalities into Hugin; or
> (d) integrate Hugin's functionalities into pv.
>
>
My vote would be for (b), just like Kay himself also mentions.


> How far is pv from being a replacement to Hugin, and do you see it
> going there?
>
> Not there (yet). Hugin has way more tweaking options to create great
looking panos. Translations for example are not supported by pv (yet?), and
neither are masks.
Next to that: The Hugin assistant makes things way more easy than currently
in pv. Of course: also getting the most out of Hugin, as in pv, requires
some in-depth knowledge.
Also: pv's goal is to also improve your already created images (or
panoramas).


> Conversely, how different is pv from Hugin and how difficult would be
> that integration work?  I suspect that the use of a different GUI
> Toolkit is a major obstacle, but your expertise my intuition wrong?
>
> Which brings us to what I understand is your proposal, to distributed
> pv along Hugin.  The cost to Hugin are "only" more build/distribution
> complexity.  Or am I missing something?  And it does not seem to be
> such a heavy toll, based on Harry's feedback here.  Do the benefits to
> Hugin's users justify the extra build/distribution complexity?  And are
> there things that can be done to reduce that complexity, e.g. moving pv
> from bitbucket to the same repo as Hugin?
>
>
I can't and won't say anything about the difference in code. I leave that
to the experts.
But indeed: I see it as a supplementary tool. At least for the time being.
It can be added to Hugin as an extra app bundle (apple) or as a tool, or as
an extra exe (on windows). Linux is of course the easiest one.
When looking at Hugin, like yuv described, Hugin is really a combination of
all kind of tools.
Enblend and enfuse need to be dragged in (or multiblend for that matter).
libpano13 is often too old and needs to be built as well. Both on windows
and mac almost everything needs to be downloaded and compiled.

For me integration is not one big monolithic binary doing everything, but a
suite consisting of nicely integrated tools via APIs.
If you look at web technology where all kind of technologies need to be
connected, you see that APIs (or interfaces or "command line" parameters on
a local platform, if you like) are the way forward to connect and integrate
different technologies.
This also allows for developments (leaps in developments) in the separate
tools as long as the API or interfaces remains consistent. Adding an extra
option will not break anything.
I am not a programmer (weel, an amateur at best), but in my work we bring a
lot to the cloud where you have saas, paas, iaas solutions on a number of
platforms (AWS, Microsoft, Google to name the biggest ones) which you want
to talk to each other (in a safe and secure way). Nobody nowadays does
everything in one "tool".

Why not pv also? It uses the same libraries as already necessary for Hugin
and all the tools, with one "extra": Vc, and Vc needs to be of high enough
version. Which means it can be treated like libpano.

And with regard to integration: pv started as panorama viewer. In Hugin you
could add as setting: "Open created panorama in pv", just like we do with
another non-C, non WxWidgets, non-integrated tool being exiftool acting on
our created pano from our original images.
Opening pv from Hugin after creation gives you an immediate view on your
results.
And pv can in that case also give you immediate options to tweak your
created panorama.

And in 5 years or 10 years? Who knows.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvdWgtwmO1mDYSju_perkzXisT-n0UUXx-tZDNpNxtxYg%40mail.gmail.com.

Re: [hugin-ptx] Multiblend 2.0 RC1 - better blending and 300x* faster than Enblend

[Harry van der Wolf]

And a distributable macos build for multiblend *2.0rc2*:
https://mega.nz/file/lQtlgKRI#wNYpcmE4-XuZJOsXmxtBkBmB6Ekji-Vp65c38FCaGws
Unzip to a folder of your liking with paths. It should give:
multiblend-dist/
multiblend-dist/Libraries/
multiblend-dist/Libraries/libz.1.2.11.dylib
multiblend-dist/Libraries/libpng16.16.dylib
multiblend-dist/Libraries/libzstd.1.4.8.dylib
multiblend-dist/Libraries/libtiff.5.dylib
multiblend-dist/Libraries/liblzma.5.dylib
multiblend-dist/Libraries/libjpeg.8.2.2.dylib
multiblend-dist/multiblend

Removed a few "sloppy" things from the script:
https://mega.nz/file/FR9CxCpB#ucZGem59Z6n8jVP7NriuqKS9YwGvMtIok9DZqX75vro

Harry

Op za 6 mrt. 2021 om 13:02 schreef Monkey :

> Fixed and updated, plus a fix to ignore (properly) an Enblend parameter
> that was stopping Hugin from successfully calling Multiblend.
>
> http://horman.net/multiblend/
>
> David
> On Saturday, 6 March 2021 at 11:22:47 UTC hvd...@gmail.com wrote:
>
>> Builds fine and runs fine (under Hugin) on my Ubuntu derived box.
>> GalliumOS 3.1 (Ubuntu 18.04 LTS)
>> (Linux edgar 4.16.18-galliumos #1 SMP PREEMPT Sun Jun 23 04:14:45 UTC
>> 2019 x86_64 x86_64 x86_64 GNU/Linux)
>>
>> On MacOS Catalina I had to replace in multiblend.cpp the following:
>> #include 
>> #include 
>>
>> #include "tiffio.h"
>> #include "jpeglib.h"
>>
>> with:
>> #include 
>> #ifdef __APPLE__
>>   #define memalign(a,b) malloc((b))
>> #else
>>   #include 
>> #endif
>>
>> #include "tiffio.h"
>> #include "jpeglib.h"
>>
>> Please correct that before final 2.0 release.
>> With that it builds fine on MacOS and runs fine under Hugin. I now used
>> Macports instead of homebrew, as I needed macports for pv.
>> See attached your modified build.txt.
>> I also created a distributable version:
>> https://mega.nz/file/VEkRlKLY#zt2oymaxcqi1gK-XrKzE0fGiPs8W3lYzXL2yuC89DFM
>> Unzip the zip with paths (!) to some location of your liking. It will
>> create a folder multiblend-dist and inside you will find multiblend and
>> it's 3rd party necessary libraries.
>> In Hugin preferences under programs select "use other enblend program"
>> and give the full path to multiblend.
>>
>> Script to create a distributable multiblend (using macports):
>> https://mega.nz/file/sc8hXIrT#6SYq8Dbei8KZZxocDQ9iSidv__qDJjc7RMaNCwTRFIo
>> Create a "mac-dist" subfolder in your build directory and use the script
>> from there. Read the info in the script before use.
>> Of course this script already expects a compiled multiblend in the build
>> folder.
>>
>> Hoi,
>> Harry
>>
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/2ea613a7-9e0f-4605-961a-63cf504d461dn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpufLeRi8B94HkbSejU3BRGuxUxvxhEp%3DVRBMYOkdr-%3DGw%40mail.gmail.com.

Re: [hugin-ptx] Multiblend 2.0 RC1 - better blending and 300x* faster than Enblend

[Harry van der Wolf]

Builds fine and runs fine (under Hugin) on my Ubuntu derived box. GalliumOS
3.1 (Ubuntu 18.04 LTS)
(Linux edgar 4.16.18-galliumos #1 SMP PREEMPT Sun Jun 23 04:14:45 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux)

On MacOS Catalina I had to replace in multiblend.cpp the following:
#include 
#include 

#include "tiffio.h"
#include "jpeglib.h"

with:
#include 
#ifdef __APPLE__
  #define memalign(a,b) malloc((b))
#else
  #include 
#endif

#include "tiffio.h"
#include "jpeglib.h"

Please correct that before final 2.0 release.
With that it builds fine on MacOS and runs fine under Hugin. I now used
Macports instead of homebrew, as I needed macports for pv.
See attached your modified build.txt.
I also created a distributable version:
https://mega.nz/file/VEkRlKLY#zt2oymaxcqi1gK-XrKzE0fGiPs8W3lYzXL2yuC89DFM
Unzip the zip with paths (!) to some location of your liking. It will
create a folder multiblend-dist and inside you will find multiblend and
it's 3rd party necessary libraries.
In Hugin preferences under programs select "use other enblend program" and
give the full path to multiblend.

Script to create a distributable multiblend (using macports):
https://mega.nz/file/sc8hXIrT#6SYq8Dbei8KZZxocDQ9iSidv__qDJjc7RMaNCwTRFIo
Create a "mac-dist" subfolder in your build directory and use the script
from there. Read the info in the script before use.
Of course this script already expects a compiled multiblend in the build
folder.

Hoi,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptzPVhDz%3DcRJXrhOuuiMpAN6TYGiPm91AWMRLYdZbod0Q%40mail.gmail.com.
The following command should work to build Multiblend on Linux:

  g++ -msse4.1 -pthread -ffast-math -Ofast -o multiblend multiblend.cpp -lm 
-lpng -ltiff -ljpeg

Harry van der Wolf suggests the following for Mac:
- for HomeBrew
  [install home brew]
  brew install jpeg-turbo libjpeg libpng libtiff
  gcc -I/usr/local/opt/jpeg-turbo/include -L/usr/local/opt/jpeg-turbo/lib 
-std=c++14 -msse4.1 -pthread -ffast-math -Ofast -o multiblend multiblend.cpp 
-lm -lpng -ltiff -ljpeg -lstdc++


- for MacPorts
  [install MacPorts using the pkg for your MacOS version]
  sudo port -v selfupdate
  sudo port install jpeg
  sudo port install libjpeg-turbo
  sudo port install tiff
  sudo port install libpng
  gcc -I/opt/local/include -L/opt/local/lib -std=c++14 -msse4.1 -pthread 
-ffast-math -Ofast -o multiblend multiblend.cpp -lm -lpng -ltiff -ljpeg -lstdc++

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

PV 1.0.2 bundle for MacOS.

PV-1.0.2.dmg:
https://mega.nz/file/IFsVTY4a#bp_8dkHXWShNrlkDSd5pLqDCcDD-Ht2I4KeETSPhGKA
Updated script and files to build the bundle and the dmg:
https://mega.nz/file/xMsH1SqA#wutJluOpiWvcWU2AtzpXM0zIseolMdVva3V1IMmd6A0

Harry

Op vr 5 mrt. 2021 om 19:18 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> Am 05.03.21 um 12:43 schrieb Harry van der Wolf:
> >
> >
> > Op vr 5 mrt. 2021 om 11:56 schreef 'Kay F. Jahnke' via hugin and other
> > free panoramic software  > <mailto:hugin-ptx@googlegroups.com>>:
> >
> > In a way I'm surprised that so far nobody has actually reported doing
> > what I propose in this thread, namely performing a stitching job or
> > exposure fusion, using pv's adapted Burt & Adelson image splining
> > algorithm. I admit my documentation isn't so easy to access on this
> > topic, so here's a brief how-to:
> >
> > I did not report anything back and did not do a panorama job, but I did
> > some "enfusing" jobs on bracket images.brackets of 3 images and brackets
> > of 5 images.
> > Using align_image_stack to align them (hand shot images) and let AIS
> > create a pto.
>
> That's a good way of doing it, and sets reasonable Ev values as well as
> doing the registration. Good to batch as well. I tend to collect all
> brackets from a take into separate folders (I have a script for that),
> then make the PTOs one per folder. After that, a pv batch job (or
> several). You can also make HDR-blended images instead of exposure
> fusions, by using
>
> --snapshot_extension=exr --blending=hdr
>
> which you can also batch with
>
> --next_after_snapshot=yes
>
> and you may want
>
> --aeb_auto_brightness=yes
>
> for a batch job, because that does a light balance before blending -
> especially for JPGs, the brightness values from the PTOs aren't always
> optimal.
>
> > Then use pv to open the pto and use "U" and "Shift-U" to fuse them.
>
> It's nice to go through the set 'manually' - also to set the shape of
> the output.
>
> Shift+U simply takes the first image as output template and renders to
> that size and projection. You can actually choose to use any shot of the
> bracket as the template, with --snapshot_facet=...
>
> I sometimes use the darkest shot as frame reference - the second, or
> number 1 as pv counts from zero, for my canon cameras because it's most
> likely to have non-overexposed content all over the frame.
> 'U' - without shift - is to share the current view, with the shape and
> content as the window you see on-screen. Like, you can work with a
> square window and fixed 1000X1000 output size and produce frames for you
> know what.
>
> > I also used these ptos with a complete command-line parameter batch set
> > (from your Readme), but pv does not exit after the last pto.
> > Both on the RPi4 and my Linux laptop.
>
> It should, though...
>
> It's nice if you send the actual command line you used if something
> unexpected happens - makes it easier for me to figure out if something
> is genuinely wrong. But your hint made me look into the logic, and I
> actually spotted and fixed a bug here, which seems unrelated, though.
> Not the last bug...
>
> > I did not report back as I am also a complete newby to pv and first
> > wanted to explore it a bit deeper.
>
> No problem. Newbies tend to come up with problems that 'experts' would
> never manage to produce ;)
>
> > Results are good and completely comparable with enfuse.
>
> I take that as a compliment! With the default settings, pv only uses
> 'exposure_weight' with the standard values for sigma and mu, as proposed
> by Mertens, Kautz and Van Reeth, and also the standard in enfuse. enfuse
> adds the default of .2 saturation weight, which pv does not (yet)
> support. You can vary mu and sigma through command line parameters. I
> also added contrast weighting as an experiment (--contrast_weight=...)
> which I calculate from the gradient squared magnitude of the b-splines
> in the pyramid - the derivative of the splines is easy to get, so this
> is quick and precise, but slightly different to standard B and enfuse.
> I do the GSM separately over the colour channels, and I have the
> impression that mixing in a bit of contrast weight (like .2) makes the
> result more 'vivid'.
>
> > Panos this weekend.
>
> Have fun! And pull and build afresh before you use pv, right now I'm
> pushing new stuff frequently.
>
> Kay
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you a

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op vr 5 mrt. 2021 om 11:56 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> In a way I'm surprised that so far nobody has actually reported doing
> what I propose in this thread, namely performing a stitching job or
> exposure fusion, using pv's adapted Burt & Adelson image splining
> algorithm. I admit my documentation isn't so easy to access on this
> topic, so here's a brief how-to:
>
>
I did not report anything back and did not do a panorama job, but I did
some "enfusing" jobs on bracket images.brackets of 3 images and brackets of
5 images.
Using align_image_stack to align them (hand shot images) and let AIS create
a pto.
Then use pv to open the pto and use "U" and "Shift-U" to fuse them.
I also used these ptos with a complete command-line parameter batch set
(from your Readme), but pv does not exit after the last pto.
Both on the RPi4 and my Linux laptop.

I did not report back as I am also a complete newby to pv and first wanted
to explore it a bit deeper.

Results are good and completely comparable with enfuse.
Panos this weekend.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsfJ2xPP%3DNEd7Ux%2BC2LJiKtBtrbZy2WPvPJ%2BsiiVgnw6g%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op do 4 mrt. 2021 om 21:14 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

>
> And did you check the compiler's version as well?
>

Sorry, yes. I forgot to mention.
clang version 10.0.0-4ubuntu1
Target: aarch64-unknown-linux-gnu
Thread model: posix

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsQaGDnPa__asiL0YRp7KFuv-x78%2Bb90UAdV%3DUJurGq4g%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Compiling pv on my Ubuntu Mate raspberry pi 4.
A very short action:
 make
clang++ -c -Ofast -march=native -std=c++11 -c -fno-math-errno
-Wno-unused-value pv_no_rendering.cc -o pv_no_rendering.o
clang: error: the clang compiler does not support '-march=native'
make: *** [makefile:103: pv_no_rendering.o] Error 1

So it works fine on Debian Buster on my server RPi4, but not on my RPi4
with Ubuntu Mate 20.04 (Ubuntu 20.04.2 LTS; uname -a: Linux ubuntu
5.4.0-1028-raspi #31-Ubuntu SMP PREEMPT Wed Jan 20 11:30:45 UTC 2021
aarch64 aarch64 aarch64 GNU/Linux)

So I removed the -march=native from the common_compiler_flags in the
makefile and started make again.

Now it builds 3 versions which I quickly checked on a partial pano on a
1920x1080 monitor.
See attached txt files.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsAGbPe2qsdXdMCfKOyxeX17P99tpv6mwdjtOpuK7M%3Diw%40mail.gmail.com.
detected path: <./>
initializing user interface
processing command line arguments
no images specified, opening file select dialog
received selection: /media/PUBLIC/Shared Pictures/Picture Library/2011/20110725 
- panos/20110725-013-024.jpg
pushing filename /media/PUBLIC/Shared Pictures/Picture Library/2011/20110725 - 
panos/20110725-013-024.jpg
user selected 1 files
initialization complete
next file from queue: '/media/PUBLIC/Shared Pictures/Picture 
Library/2011/20110725 - panos/20110725-013-024.jpg'
inner_main called: starting display cycle
GUI scaling factor set to 1.0
setup_window: full_screen = 1
reading metadata from /media/PUBLIC/Shared Pictures/Picture 
Library/2011/20110725 - panos/20110725-013-024.jpg
UserComment EXIF tag yields projection: Equirectangular
 hfov: 190 vfov: 124
gleaned projection SPHERICAL from metadata
warning: UserComment EXIF tag for hfov data
 is wrong for cropped images
gleaned source hfov 190.0 from metadata
no vfov data, calculating vfov from hfov 190.0
calculated hfov: 190.0 vfov: 87.10808
assuming that image is horizontally centered
assuming that image is vertically centered
source image set up to:
file:/media/PUBLIC/Shared Pictures/Picture Library/2011/20110725 - 
panos/20110725-013-024.jpg
width:   8956
height:  4106
brightness:  1.0
handicap:0.0
squash:  0
is_linear:   0
orientation: 0
projection:  SPHERICAL
hfov:190.0
hofs:85.0
vfov:87.10808
vofs:136.44596
full_width:  0
full_height: 0
exent:   -1.65806 1.65806 -0.76016 0.76016
ul corner:   (-0.06316, -0.72197, -0.68904)
ur corner:   (-0.06316, 0.72197, -0.68904)
lr corner:   (-0.06316, 0.72197, 0.68904)
ll corner:   (-0.06316, -0.72197, 0.68904)
cone theta:  190.0
x_step:  0.00037
no lens correction
no vignetting correction
reading source image without alpha channel
setting the view's hfov to 70 degrees
view hfov: 70.0
launching rendering thread
on_terminate is called
emptying job queue, halting rendering thread
joining rendering thread
emptying frame queue
displayed 361 frames, which took 60.54596ms on average to create
buffer low events: 356
destroying rgba frames from rgb_queue
memory log traced 378 allocations
memory log balanced, no leaks detected
exiting normally


detected path: <./>
initializing user interface
processing command line arguments
no images specified, opening file select dialog
received selection: /media/PUBLIC/Shared Pictures/Picture Library/2011/20110725 
- panos/20110725-013-024.jpg
pushing filename /media/PUBLIC/Shared Pictures/Picture Library/2011/20110725 - 
panos/20110725-013-024.jpg
user selected 1 files
initialization complete
next file from queue: '/media/PUBLIC/Shared Pictures/Picture 
Library/2011/20110725 - panos/20110725-013-024.jpg'
inner_main called: starting display cycle
GUI scaling factor set to 1.0
setup_window: full_screen = 1
reading metadata from /media/PUBLIC/Shared Pictures/Picture 
Library/2011/20110725 - panos/20110725-013-024.jpg
UserComment EXIF tag yields projection: Equirectangular
 hfov: 190 vfov: 124
gleaned projection SPHERICAL from metadata
warning: UserComment EXIF tag for hfov data
 is wrong for cropped images
gleaned source hfov 190.0 from metadata
no vfov data, calculating vfov from hfov 190.0
calculated hfov: 190.0 vfov: 87.10808
assuming that image is horizontally centered
assuming that image is vertically centered
source image set up to:
file:/media/PUBLIC/Shared Pictures/Picture Library/2011/20110725 - 
panos/20110725-013-024.jpg
width:   8956
height:  4106
brightness:  1.0
handicap:0.0
squash:  0
is_linear:   0

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op do 4 mrt. 2021 om 16:48 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

>
> Is it okay if I add put a link to your script and the bundle on the
> bitbucket page? I'd also like to give you credit for the effort, is it
> okay to mention you by name?
>
> That's OK. I actually wanted to do a pull request so it simply would add a
subfolder to your repo for mac building but then I have to register at
bitbucket, fork it, etc., so I simply zipped it.
In my cross-platform repos I mostly add a folder "packaging" with
subfolders like "macos", "windows", debian (for a .deb") and AppImage, with
scripts in there and "base" files.
I leave it completely up to you what you want.

And with regard to the dmg: Once pv is stable, and thereby your exe
package, the mac bundle, the AppImage of FlatPack, and whatever other
distribution option, you might start to add releases to your repo.


> Anything you would like me to do to help beautifying?
>
>
With beautifying I mean.
- Comment the script a little bit more.
- Make some sed and/or awk steps where you start the script with a version
number and it automatically updates the Info.plist.
- Expand the Info.plist with pto mime document typing. Now only for
jpg,jpeg,tif, tiff, png. (And I forgot openexr. That needs to be added as
well). This allows a user to double-click or right-click an image and use
"open with ...".

Those last 3 steps are 20-30 minutes of work (once the versioning is
implemented) as I will simply copy the structure from my repos.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpspA2kNawnUSVPiHS3cR1czjCacthGC557eXyMkZLydCQ%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

All,

As a lunch activity ;)
Nothing changed in pv. I only added the icon set and rebuilt the bundle and
dmg.
[image: image.png]
(Screenshot in Dutch. Had not noticed that Yesterday :) )

Script and files to build the bundle and dmg:
https://mega.nz/file/1FsGRSaA#1gRTBMYWqpEt_QxT4QqwunFJpvs5SyALjNVDkakDh6U
It needs to be run on a Mac from subfolder mac-bundle inside the pv build
folder.
This is only after you have built pv as binary, but that is part of the pv
build instruction.
This all requires more time and effort to "beautify" it, but it simply
works.

dmg for testing:
https://mega.nz/file/JUkxiQIJ#yrTBE7T-VGdj2j3_o52t5UiwcGf1D__SUPU_ImG8Y2Y
(previous link removed)

@Kay: You will need to add versioning to pv. That can be used to verify the
binary ( pv --version ), and create bundles, exes, debs, appimages, and so
on.
I now simply used 1.0 for the bundle.

Harry


Op do 4 mrt. 2021 om 11:43 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> Am 03.03.21 um 22:20 schrieb Harry van der Wolf:
> >
> > It is not so hard to create a bundle for pv after all. It took me an
> hour.
> > Currently the app does not have an .icns iconpack, so it has a default
> icon
> > It also contains a minimal, strictly necessary Info.plist, but that
> > should be expanded.
> > If you create a nice 512x512x300 dpi or 1024x1024x300 dpi PNG image, it
> > is easy to create an icns icon pack (which shows app icons based on your
> > systems resolution)
>
> I think I would be happy with a readymade image. It's in the public
> domain, from Wikimedia Commons, and depicts Odin's ravens, Hugin and
> Munin, sitting on a branch. I think this is apt. The site has several
> download sizes apart from the SVG, but maybe an SVG is even better to
> make an icon pack? This is the one:
>
> https://commons.wikimedia.org/wiki/File:Odin%27s_ravens_right.svg
>
> I suppose something simple with a stark contrast will also be good for
> lower resolutions, and should be easily recognizable.
>
> Kay
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/534e68e2-9ffa-d215-c078-e5da90663f09%40yahoo.com
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvO8YcDo2gr02gB6jjjEC88%2BukaFwv4r6xiJw9NDZEgPw%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op do 4 mrt. 2021 om 08:47 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

> Am 03.03.21 um 22:20 schrieb Harry van der Wolf:
>
>  > Hi Kay and everyone else interested.
>  >
>  > It is not so hard to create a bundle for pv after all.
>  > It took me an hour.
>
> Wow! Thanks for your work! I did think about building a flatpack for
> linux, but it looked like quite a bit of stuff one had to learn and do,
> so I kept postponing it - and building on Linux is really easy.
>
>
I built 2 Linux AppImages by now (3 if you count my Hugin try a few weeks
ago, but that's an unstable one).
It takes some time to learn how to build an AppImage, but once you know how
to do it is not so difficult (as with most things you have learned). It is
mostly copy and combine the "things" the linux build system already
compiled/built for you. Same for a .deb. Also built two of them but never
offered them to Debian.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvafXBzP76%2BLMU36wRxv4dEapZaX%3D%2B8Keqze33ZN0GKHQ%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Hi Kay and everyone else interested.

It is not so hard to create a bundle for pv after all. It took me an hour.
Currently the app does not have an .icns iconpack, so it has a default icon
It also contains a minimal, strictly necessary Info.plist, but that should
be expanded.
[image: PV.png]
If you create a nice 512x512x300 dpi or 1024x1024x300 dpi PNG image, it is
easy to create an icns icon pack (which shows app icons based on your
systems resolution)
I copied the app bundle, the license and the readme into a distributable
dmg.
[image: dmgpicture.png]



As I can't attach a dmg containing a bundled app (this could be a security
issue), I can't attach it to this mail.
Download from here:
https://mega.nz/file/QQ9FmazK#oUh5Ap92yvJ-c6wnvQcmOdmbwqYMapuvs5UuvNNOBRc

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptLosvb2%3D6uFhdX2GfYcuq1Au2N-DfBj08FGDAVtefkzw%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op wo 3 mrt. 2021 om 10:32 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

>
> > The current Hugin builders on Mac are Niklas Mischkulnig and Bob
> > Campbell. All credits to them (not to me).
>
> Maybe they'll take note of pv and become interested in the mac version -
> after all the branch is already there and you demonstrated that it's
> dead easy to create a binary. Sadly, my work so far has not got much
> attention.
>
>
It should not be too difficult to add it to the Hugin bundle package. The
hugin package consists of 4 separate bundles (Hugin.app,
HuginStitchProject.app, PTBatcherGUI.app, calibrate_lens_gui.app).
If this is not "allowed", it is not too difficult either to build a
separate pv bundle. Not difficult (if you know how to do it), but quite
some work.
I would use macports for this over homebrew. Homebrew uses as much as
possible the libraries available on the system. Macports tries to build as
many libraries itself as it can and only uses the real system libraries.
That macports build process on installing takes much longer as it will
build more libraries. Homebrew uses libiconv, libexpat, libz, liblzma,
etcetera from MacOS. Macports builds these itself.
For a "my system only", homebrew is a more convenient, easier and faster
way to install new ports.
Macports gives you more portabality and MacOS "cross-version" compatibility
if you bundle an app.

Note: Mac bundles do have the Info.plist setting
NSHighResolutionCapable
True

The latest Hugin build had issues with this and those were apparently just
solved by Bob and Niklas (one of the other conversations about the hugin
mac build).
I only have that old Macbook Pro and can't test high resolution
functionality of pv.


> Now it's my turn to be 'a bit sad'. I've spent about seven man years
> creating a b-spline library and a beautiful, powerful panorama viewer
> which now can even do some stitching and exposure fusion on top of
> everything else. It would be sad to just rip it apart and take a few
> bits as helper programs for hugin. Think of pv as a 'preview on
> steroids'. There was a discussion in this group whether it wouldn't make
> sense to work more from the preview window. pv is my answer to this
> discussion: its what used to be called 'wysiwig'. Pretty much everything
> happens immediately, you see all parameter changes 'live'. The only
> things which I can't show 'live' are exposure fusions and stitches,
> because the B algorithm takes a lot of time. I may be able to tweak it
> so that I can produce a few frames per second showing stitches and
> fusions live, but for now they are rendered by a background thread to a
> file on disk. For playing with my stitching and fusion code, this should
> be good enough for now.
>
> I even made it easy to use it as a preview for hugin and the likes: if
> you work on a panorama in hugin, you can just have a pv window open to
> the same PTO. as soon as you save the PTO in hugin, you can simply press
> 'F1' in pv and it will update to the changes in the PTO. I see pv rather
> as a third 'preview' window which hugin etc. can use alongside the other
> two, which are good for some tasks where my code is not - I don't handle
> all panotools projections, I don't deal with control points, I can't
> switch individual imageson and off... - but I sure can give a good view
> at the PTO.
>
> Sorry to make you sad. ;)
You have some very good arguments (at least in my eyes).
Like in all Open Source projects: "if you feel an itch, scratch it". You
simply did what many other developers did (and what I did myself).
Look-alike packages can still have different origins, different goals and
different appliances (and based on your arguments: different technology).
And I did not know of all the effort you already put into it.



> Now for the attempt to port pv to ARM. I have prepared the branch I
> announced yesterday, and you can try if it compiles on your Raspi:
>
>git checkout native
>make
>
> This will try to build three targets: pv_scalar, pv_vspsimd and
> pv_vcsimd - you can also build them separately if you like, it's a phony
> 'all' target compiling the lot. The first one makes no attempt at using
> SIMD code, the second one used vspline's 'implicit' SIMD code, and the arry
> third uses Vc. I think the first two will build on the Raspi, the third
> may or may not.
>

While typing this mail, I compiled your new code on my RPi4 server. All 3
versions compile fine, but as they use (Open)GL code, they won't run in a
VNC window and I didn't setup X on my server.
I will do the same on my other RPi4 with a monitor connected, but I don't
have time for it now.

Harry

-- 
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 

Re: [hugin-ptx] New release for mac?

[Harry van der Wolf]

Hi Yuv,

Nice to see you again here.

Thanks for the extensive, clear answer on this. (and I learned something
from it as well).

Although I do have some serious complaints about Apple, enough to abandon
the platform, I do not see myself picking this up. Especially not from
Europe to an US company. Even the EU has issues getting a grip on Facebook,
Apple and some of the other "evil" companies.
That also means that this isn't the first time. Isn't there a central
committee/foundation that is doing these kind of things?

Best,
Harry


Op do 25 feb. 2021 om 17:26 schreef yuv :

> On Thu, 2021-02-25 at 08:22 +0100, Harry van der Wolf wrote:
> > I hate the MacOS
> > policy and am therefore not a registered developer and certainly not
> > release via the App Store, so my app has the same issue. (Users have
> > to accept that or simply not use my app. I support the MacOS users,
> > not Apple).
>
> Write to your local anti-trust authority / competition commissioner /
> etc.  Anyone has my permission to re-use the text below, on the
> condition that said anyone does not rely legally on it (I am not
> anyone's lawyer,  and in most cases I cannot be).  I am happy to put
> together a more detailed argument/analysis for anyone to use against
> Apple and (adapted accordingly) the rest of BigTech.
>
> Apple is "lessening or preventing competition" (the legal keyword) and
> has gone way too long under the radar screen.  I recently had to set up
> an iDevice (school requirement) and it felt worse than being ordered to
> stay at home under curfew because of the current pandemic.  Apple has
> managed to successfully excercise ownership on users, developers, and
> government.
>
> Anti-trust authorities have given Microsoft users the choice of browser
> at a time when Microsft's conduct was much less detrimental and
> offensive to the market than Apple's current conduct is detrimental to
> the market, no matter how the market is defined (and definition of the
> market is crucial for an anti-trust case).
>
> In your letter, request the following remedies:
> * Apple to give user a choice of cloud services to connect their
> iDevice to on initialization of the iDevice.  Similar to what Microsoft
> had to do with the choice of browser.  This includes choice of app
> store; choice of cloud storage provider; choice of account ID provider.
> * Apple to accept in its stores software built with non-Apple
> toolchains.
> * Apple to give app developers (cloud providers!) access to the same
> API independent of Apple's cloud services that it uses to implement
> iCloud sync and instant messaging.  Right now, Dropbox, Nextcloud, and
> other competitors are at hard disadvantage because they cannot achieve
> feature-parity with iCloud.  Their workaround is to have their app's
> sync triggered on GPS-coordinate change, totally inferior, while on
> Android they have an opportunity to achieve parity with Google's
> services.
> * Apple to implement standard Push API in Safari, for the same reason
> as above.  Currently, Apple requires website operator regi$tration,
> licen$e, and use of an Apple service.  I call this unlawful
> monetization of access to user
> * Apple to give user the choice to replace Apple's root encryption keys
> with the user's own; and to disable the features that prevents software
> unauthorized by the encryption keys owner to run on the iDevice.
> * Ultimate control must rest with the user, not with Apple, and
> ultimate control is not the same as dumping the iDevice on the
> electropile junk.
>
> At the moment, the only reasonable way to describe iDevices is a pre-
> paid lease with an unknown term at the discretion of the landlord on
> zero-day notice.  Unconscionable.  Has been unacceptable for centuries
> in the Western legal systems, and it is time set the record straight
> that it won't be acceptable in the future either.
>
> --
> Yuval Levy, JD, MBA, CFA
> Ontario-licensed lawyer
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/54fd888ebf50778c211ae9e36253dd25a20196ff.camel%40levy.ch
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpti6n-prfcM9R4d28uOOqu18X0_pAsOEcxux9Z%3Djm7iWA%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Op di 2 mrt. 2021 om 11:43 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software :

>
> Thank you for confirmig a mac build! This is great, you're now only the
> third person I know of who's succeeded in building pv on a mac. I don't
> have a mac myself, so it's hard for me to code for it. Please note that
> the mac branch has not yet been updated to contain my new code, I'll do
> that soon-ish. Old macs are like old pcs, they won't have fast SIMD
> units. I routinely build on an old IBM Thinkpad R60e with a core2 Duo,
> to confirm that the code works on 32bit intel hardware with SSE only. It
> works, but it takes forever... My desktop is a Haswell core-i5, which
> has AVX2. This is where it starts being fun :D
>
> Since you're the one who's building hugin on the mac, maybe you can give
> me a hint on how to write a 'port file' to provide a pv package for
> macports? Is that hard? And is it hard to provide a package which users
> can simply download from the app store? I proposed to bundle pv with
> hugin, because it would make a good addition to the suite, what do you say?
>
> Kay
>
>
I was not correct, or at least not clear enough, in my answer. I did take
over from Ippei Ukai, but also mentioned I abandoned Mac in 2012/2013 or
so. I simply never threw my 2008 macbook away.
At that time I also maintained the macports build of hugin and
enblend/enfuse, but that is now also long, long ago. But I will have a look
at it.

The current Hugin builders on Mac are Niklas Mischkulnig and Bob Campbell.
All credits to them (not to me).

I certainly do not have an Apple M1 and will not buy one either. I am a
happy Linux user since 1993 (early adapter) and simply wandered off for a
couple of years, both to Apple and Windows.

Making a package for the MacOS app store is a different thing.
You have to register as a developer at Apple. I did a complete rant some
days ago about how I hate how Apple does things, but also realised at that
time that I had registered around 2008, when I took over from Ippei. And
yes, that still worked.

- So, you have to register at Apple as a developer giving quite some info.
- You have to offer your bundle to Apple where Apple checks for
malware/Apple standards/"other things". That is actually a good thing, but
will take time and sometimes your bundle is rejected while you know it is
perfectly fine. I have a java app which I also packaged as a MacOS bundle.
Apart from the fact that I won't release it via the apple store, it will
not be accepted either as it is built outside Xcode thereby lacking some
controls/standards (and Apple spyware?).

With regard to bundling with Hugin:
I agree with Thomas that where possible we should integrate. You already
explained the big differences in code, so that might not be possible. I
can't judge that as I'm not a C/C++ programmer.
As it is all open source, it might still be possible to migrate/integrate
it. And otherwise: could it be possible to call pv from hugin to run it as
enblend replacement. Just like multiblend can be called from hugin (with a
simpler command set) as enblend replacement?
Also: panomatic was first an external tool and most of it is now integrated
in cpfind.
I hope we see the same for pv blending/fusing functionality if it really is
an improvement.
My personal point of view is to help where I can if "something" can mean an
improvement for all of us. And if it is mature try to integrate it.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptLO9_GLJY8cQaumqPvSc0biNiiYg4t%3DUEaiPHKMK-cQg%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

Hi,

I understand that ARM is different. That's also why I mentioned to not put
too much effort into it.

Yes, I'm willing to cooperate in porting to armhf for the raspberry pi' s.
I also have another rpi4 which runs Ubuntu Mate 20.04 (currently), but my
(headless) server is always on.
But I use the other one for all kind of things, so helping to port pv could
be another option.

I have no idea though how much the "normal" ARM chips vary from the new
Apple Intel M1. That might be a completely different beast (the 8-core is
at least when it comes to performance).
I read that Apple uses the same Rosetta (V2) for running Intel based
programs on the new M1.* (Just like 10-12 years ago when they switched from
PowerPC to Intel to run PowerPC apps on Intel. I also guess the universal
binaries will come to life again. At that time I took over from Ippei Ukai
for building Hugin on Mac. A platform I left in 2012 or so for being too
closed).*
So maybe you do not have to port immediately,but can simply run your intel
based MacOS version on the new M1' s.


On the RPi4 I also did the:
git clone https://github.com/VcDevel/Vc.git
cd Vc
git checkout 1.4
mkdir build
cd build
cmake -DCMAKE_CXX_COMPILER=clang++ -DBUILD_TESTING=0 ..
make
sudo make install
And then tried to rebuild pv, but that doesn' t make a difference. The
exact same error.

==
With regard to Intel MacOS: I had just built multiblend for David on my old
(by now terribly slow) 2008 MacBook Pro, so I tried the same for pv also
using macports (as home brew does not have vigra and I want to keep it
simple).
(install macports using pkg)
(from terminal do a: sudo port -v selfupdate)

Getting dependencies:
sudo port install sfml
sudo port install exiv2
sudo port install vigra -python38 -python39
sudo port install Vc
(This installs a whole lot of other dependencies as well. Note also the
uppercase in Vc )

Get and build pv:
git clone https://bitbucket.org/kfj/pv
cd pv
git checkout mac
git status (to check whether you have the mac branch)
make

It builds fine and I only did some viewing of images until now.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuP2M5wPtx06y1zJX%2B4jUMY5YYw3TEJ%3DqG4nPdOK4%2B-uQ%40mail.gmail.com.

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Harry van der Wolf]

I just build it on a Ubuntu derived 64bit system. It compiles fine. Before
testing further I did the same on my Debian 10 buster armhf Raspberry pi 4.
Now it ends in error.
Don't put too much effort in it. The rpi4 is my server, but I just
wanted to test if it would compile there (and then test it via tightvnc).

clang++ -c -Ofast -std=c++11 -D USE_VC -D VECTORIZE -c -fno-math-errno
-Wno-unused-value pv_no_rendering.cc -o pv_no_rendering.o
clang++ -c -Ofast -std=c++11 -D USE_VC -D VECTORIZE -c -fno-math-errno
-Wno-unused-value pv_initialize.cc -o pv_initialize.o
clang++ -c -D PV_ARCH=PV_FALLBACK -Ofast -std=c++11 -D USE_VC -D VECTORIZE
-c -fno-math-errno -Wno-unused-value pv_rendering.cc -o pv_fallback.o
clang++ -c -mavx -D PV_ARCH=PV_AVX -Ofast -std=c++11 -D USE_VC -D VECTORIZE
-c -fno-math-errno -Wno-unused-value pv_rendering.cc -o pv_avx.o
clang: warning: argument unused during compilation: '-mavx'
[-Wunused-command-line-argument]
clang++ -c -mavx2 -D PV_ARCH=PV_AVX2 -Ofast -std=c++11 -D USE_VC -D
VECTORIZE -c -fno-math-errno -Wno-unused-value pv_rendering.cc -o pv_avx2.o
clang: warning: argument unused during compilation: '-mavx2'
[-Wunused-command-line-argument]
clang++ -c -mavx512f -D PV_ARCH=PV_AVX512f -Ofast -std=c++11 -D USE_VC -D
VECTORIZE -c -fno-math-errno -Wno-unused-value pv_rendering.cc -o
pv_avx512f.o
clang: warning: argument unused during compilation: '-mavx512f'
[-Wunused-command-line-argument]
clang++ -c -D PV_ARCH=PV_FALLBACK -Ofast -std=c++11 -D USE_VC -D VECTORIZE
-c -fno-math-errno -Wno-unused-value pv_combine.cc -o pv_cmb_fallback.o
clang++ -c -mavx -D PV_ARCH=PV_AVX -Ofast -std=c++11 -D USE_VC -D VECTORIZE
-c -fno-math-errno -Wno-unused-value pv_combine.cc -o pv_cmb_avx.o
clang: warning: argument unused during compilation: '-mavx'
[-Wunused-command-line-argument]
clang++ -c -mavx2 -D PV_ARCH=PV_AVX2 -Ofast -std=c++11 -D USE_VC -D
VECTORIZE -c -fno-math-errno -Wno-unused-value pv_combine.cc -o
pv_cmb_avx2.o
clang: warning: argument unused during compilation: '-mavx2'
[-Wunused-command-line-argument]
clang++ -c -mavx512f -D PV_ARCH=PV_AVX512f -Ofast -std=c++11 -D USE_VC -D
VECTORIZE -c -fno-math-errno -Wno-unused-value pv_combine.cc -o
pv_cmb_avx512f.o
clang: warning: argument unused during compilation: '-mavx512f'
[-Wunused-command-line-argument]
clang++ -DUSE_TINYFILEDIALOGS -std=c++11 -c -o file_dialog.o file_dialog.cc
clang++ -std=c++11 -o pv pv_no_rendering.o pv_initialize.o pv_fallback.o
pv_avx.o pv_avx2.o pv_avx512f.o pv_cmb_fallback.o pv_cmb_avx.o
pv_cmb_avx2.o pv_cmb_avx512f.o file_dialog.o -lpthread -lVc -lvigraimpex
-lsfml-window -lsfml-graphics -lsfml-system -lexiv2
/usr/bin/ld: pv_no_rendering.o: in function `__cxx_global_var_init.375':
pv_no_rendering.cc:(.text.startup[_ZN4Vc_16detail12RunCpuIdInitILi0EE3tmpE]+0x18):
undefined reference to `Vc_1::CpuId::init()'
/usr/bin/ld: pv_no_rendering.o: in function
`_GLOBAL__sub_I_pv_no_rendering.cc':
pv_no_rendering.cc:(.text.startup+0x6ec): undefined reference to
`Vc_1::CpuId::s_processorFeatures7B'
/usr/bin/ld: pv_no_rendering.cc:(.text.startup+0x6f8): undefined reference
to `Vc_1::CpuId::s_processorFeaturesC'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make: *** [makefile:33: pv] Error 1


>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuKqBHmkHOLu9byaG3xW2LBiD6mNsG7cE0Fy_9e36GMXg%40mail.gmail.com.

Re: [hugin-ptx] New release for mac?

[Harry van der Wolf]

Having full disk access is not the only point.
Hugin is not released via the App store and not via a registered developer.
That's also why the MacOS Gatekeeper software is blocking it.
You have to right-click every app bundle, click on open and MacOS will test
the contents, say something about the risks,  and asks if it can open it.
After that it works OK, also with upgrades. If you completely remove it and
then reinstall it, you have to do the same again.
Or follow this link to read about it:
https://support.apple.com/en-us/guide/mac-help/mh40620/mac

I do cross-platform open-source development as well and I hate the MacOS
policy and am therefore not a registered developer and certainly not
release via the App Store, so my app has the same issue. (Users have to
accept that or simply not use my app. I support the MacOS users, not Apple).

Harry

Op wo 24 feb. 2021 om 23:38 schreef jmuc...@gmail.com :

> Thanks. This worked.
>
> Now how to get PTBatcherGUI to become the active app when it starts
> running?
> On Monday, 22 February 2021 at 17:51:06 UTC-5 aks wrote:
>
>> The failed to open error is due to Hugin and PTBatcherGUI not having
>> proper access rights. Fixing that is the business of granting Hugin and
>> PTBatcherGUI Full Disk Access at Security & Privacy at System Preferences.
>> I find doing that is required on this recent build running on OS X 10.17.7.
>>
>> On Feb 22, 2021, at 2:55 PM, jmuc...@gmail.com  wrote:
>>
>> Thanks for doing this. I just downloaded and tried it myself.
>>
>> PTBatcherGUI hung the first time, but I force-quit and then opened it on
>> its own to get the "are you sure you want to run this" dialog. Then it ran
>> fine.
>>
>> I do get the same error I did with the last version: 15:51:15: Failed to
>> get the working directory (error 2: No such file or directory)
>>
>> No details on what directory that is, so I'm at a loss.
>>
>> The OpenGL preview works now. :-)
>>
>> On Sunday, 21 February 2021 at 21:39:31 UTC-5 Bob Campbell wrote:
>>
>>> Well, I don’t have it all packaged up nicely, but here’s a tarball of
>>> the build:
>>> http://you-rebel-scum.com/hugin/hugin_test.tar
>>>
>>> Untar’s a hugin_test folder.  You may need to move, remove, or zip up
>>> the Hugin folder in your Applications area for it to get the correct
>>> binaries, though.
>>>
>>>
>>> On Feb 21, 2021, at 4:05 PM, dgjohnston  wrote:
>>>
>>> Hi Bob … I have a MacBook Pro (15-inch, Mid 2012) running Catalina
>>> 10.15.7, Intel Core i7 16GB memory, Intel HD Graphics 4000 1536 MB.
>>>
>>> If you need some additional testing of you build I would be willing to
>>> test it for you.
>>>
>>> Don Johnston
>>>
>>> On Feb 21, 2021, at 1:59 PM, Bob Campbell  wrote:
>>>
>>> Well, I was able to get it built, finally, and tested it out on three
>>> different macs:
>>> iMac Retina 5K 2019, Catalina 10.15.7, Radeon Pro 570X
>>> Mac Mini Late 2012, Catalina 10.15.7, Intel HD 4000
>>> MacBook Pro Late 2011, High Sierra 10.13.6, Intel HD 3000 (the discreet
>>> nvidia chip on this is burned out, so it’s using the onboard Intel gfx chip)
>>>
>>> To get it to build and link correctly, though, I had to update openmp to
>>> version 11.1.0 (instead of 11.0.1).
>>>
>>>
>>> All worked, I’m glad to say, including the hidpi GL preview on the iMac!
>>>
>>>
>>> Unfortunately, I still have the problem on the iMac where PTBatcherGUI
>>> starts the stitching batch job, but nothing happens.  I’ve added Hugin,
>>> PTBatcherGUI, and HuginStitchProject to Full Disk Access in the
>>> Privacy/Security Prefs, but nothing happens.  Oddly, it works fine on the
>>> mac mini with all the same (as far as I can tell) security settings.
>>> PTBatcherGUI on the iMac just opens the stitching window, but nothing
>>> happens in the window.
>>>
>>>
>>>
>>> On Feb 19, 2021, at 6:31 PM, jmuc...@gmail.com 
>>> wrote:
>>>
>>> Guys,
>>>
>>> Thanks for working on this. I too find the missing previews on retina
>>> screens very hard to work around.
>>>
>>> Based on the comments on the release-notes page, (namely "Fixes fast
>>> preview on HiDPI screens under GTK+3 and MacOS"), it seems like was able to
>>> compile it on a Mac, no?
>>>
>>> On Wednesday, 17 February 2021 at 17:20:35 UTC-5 Niklas Mischkulnig
>>> wrote:
>>>
 timoth...@gmail.com schrieb am Mittwoch, 17. Februar 2021 um 12:43:51
 UTC+1:

> How's the build for this going? I'm finding the display issues on
> hidpi screens on the previous version a challenge and hoping we could have
> even a mac alpha soon to try
>

 I've updated the dependencies and pushed that to the repository so that
 it can be compiled with the current Xcode version. But I haven't had time
 to look why the Hugin GL Preview doesn't work.


> On Monday, 8 February 2021 at 18:12:22 UTC Bob Campbell wrote:
>
>> When building exiv2.  Maybe because I have the build target set to
>> 10.13?  I’m building exiv2-0.27.2 - haven’t checked if that’s the most
>> recent release.

Re: [hugin-ptx] Feature requests for Multiblend 2.0?

[Harry van der Wolf]

Hi,

I already built it on MacOS Catalina and reported my findings to David.
I also created a portable version with all dylibs in one zip.
(I also built the MacOS bundle quite some years ago. 2007-2011)

Harry

Op ma 22 feb. 2021 om 05:34 schreef Bob Campbell :

> Now that I’ve got a working 2020 build for mac, I can take a shot at
> building multiblend.
>
>
> On Feb 15, 2021, at 5:28 AM, Monkey  wrote:
>
> Anyone on Mac OS who can check if it compiles if I email a link to the
> source?
>
> On Friday, 12 February 2021 at 16:50:06 UTC bugbear...@gmail.com wrote:
>
>> True as far as it goes.
>>
>> An OS will manage virtual memory, swapping data between RAM and Disc as
>> needed, normally in pages of some fixed size.
>>
>> However, if the application is "naive", some worst case behaviour can
>> emerge. Imagine an application that routinely access the first byte of a
>> page,
>> and then accessed the first byte of every other page before re-accessing
>> the first byte of the first page again.
>> The application is not addressing many BYTES, but it will thrash the
>> virtual memory badly. A typical image rotate will have this behaviour on
>> either source of destination.
>>
>> What you're aiming for is locality of accesses, where multiple accesses
>> all fall within a page. For raster graphics this can be achieved by
>> accessing data in a tiled way, so that adjacent pixels in both X and Y are
>> "near". This can be done WITHOUT a tiled virtual memory system, you just
>> need to access the data in a tiled order.
>>
>> This can be done by finding the pseudo-tile T a (x,y) coord is in (simple
>> divide X, Y by the the tile size), calculate the tile base address of the
>> tile T (T * tile_bytes) and then work out the offset of the data from the
>> tile base (x and y modulo tile side, then multiply the new Y by tile side).
>>
>> I has a fancy 2D Object browser on SunOs that was thrashing, and by
>> simply implementing "address_of_object()" as outlined above, the memory
>> behaviour was immaculate.
>>
>>BugBear
>>
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/78e53b5c-9b93-46e8-a098-07c83e610358n%40googlegroups.com
> 
> .
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/14155AFE-B804-42DB-9E8C-C919E67E433C%40gmail.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpu2ETouFP1Of%2BHqkCgNVeVtx4Rmu%2BEF07ua835jqscSQg%40mail.gmail.com.

Re: [hugin-ptx] Feature requests for Multiblend 2.0?

[Harry van der Wolf]

I still have my old Macbook with a hacked Catalina (as it
officially doesn't support my old firmware) for my java testing.
I can compile it (or try to compile it) for you if there are not too many
exotic dependencies.

Harry

Op ma 15 feb. 2021 om 13:28 schreef Monkey :

> Anyone on Mac OS who can check if it compiles if I email a link to the
> source?
>
> On Friday, 12 February 2021 at 16:50:06 UTC bugbear...@gmail.com wrote:
>
>> True as far as it goes.
>>
>> An OS will manage virtual memory, swapping data between RAM and Disc as
>> needed, normally in pages of some fixed size.
>>
>> However, if the application is "naive", some worst case behaviour can
>> emerge. Imagine an application that routinely access the first byte of a
>> page,
>> and then accessed the first byte of every other page before re-accessing
>> the first byte of the first page again.
>> The application is not addressing many BYTES, but it will thrash the
>> virtual memory badly. A typical image rotate will have this behaviour on
>> either source of destination.
>>
>> What you're aiming for is locality of accesses, where multiple accesses
>> all fall within a page. For raster graphics this can be achieved by
>> accessing data in a tiled way, so that adjacent pixels in both X and Y are
>> "near". This can be done WITHOUT a tiled virtual memory system, you just
>> need to access the data in a tiled order.
>>
>> This can be done by finding the pseudo-tile T a (x,y) coord is in (simple
>> divide X, Y by the the tile size), calculate the tile base address of the
>> tile T (T * tile_bytes) and then work out the offset of the data from the
>> tile base (x and y modulo tile side, then multiply the new Y by tile side).
>>
>> I has a fancy 2D Object browser on SunOs that was thrashing, and by
>> simply implementing "address_of_object()" as outlined above, the memory
>> behaviour was immaculate.
>>
>>BugBear
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/78e53b5c-9b93-46e8-a098-07c83e610358n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpu%2BSzLoKZaQ7_cJ_RGwoCaVdfeTm2fdbHWZ5_cGxDKTSA%40mail.gmail.com.

[hugin-ptx] Re: hugin-2020.0.0 AppImage for Linux x86_64

[Harry van der Wolf]

Now I feel really stupid.

aferrero2707 still builds the appimages. I simply thought the newest would
be on top, but the oldest is. The newest is at the bottom and it seems to
be built once a week.

For those who want a weekly updated, git based hugin appimage:
https://github.com/aferrero2707/hugin-appimage/releases

Harry

Op za 13 feb. 2021 om 18:08 schreef Harry van der Wolf :

> i,H
>
> And I forgot to include enblend and enfuse.
> So a new version with them (and their dependencies).
>
> https://mega.nz/file/JAskwC6B#nC8mB1_4BtSHEs-366jz8yv5LuUtE4MPvZccqlpi0xY
>
> Harry
>
> -- Forwarded message -
> Van: Harry van der Wolf 
> Date: za 13 feb. 2021 om 17:06
> Subject: hugin-2020.0.0 AppImage for Linux x86_64
> To: hugin-ptx@googlegroups.com 
>
>
> Hi,
>
> After quite a long "panorama hibernation" I decided to create some winter
> panoramas.
> I could not find a recent build of Hugin for Ubuntu likes. It also seems
> that aferrero2707 no longer builds Hugin appimages.
> So I downloaded the hugin-2020.0.0 source and compiled it myself.
> And then I decided to try to make an AppImage, so I tried aferrero2707's
> scripts and modified them slightly. (Note: he builds with root rights or in
> a (docker) container, I don't know. I don't want that)
> The appimage is built on a x86_64 GalliumOS 3.0 (Ubuntu 18.04 LTS Bionic
> Beaver derivative), which is an Ubuntu Linux especially for Chromebooks.
> The (probable) backwards compatibility is therefore 18.04 LTS. Maybe it
> works on older Ubuntu-like versions as well.
> It works for me. I hope it works for others as well.
> Please give it a try and please let me know. This appimage does not
> contain the gtk-2 and pixbuf libraries as aferrero2707's appimages do (or
> did). All debian/ubuntu derivatives nowadays come with these libraries,
> even KDE versions (I tried many distributions and versions for my own
> application. I did not do further tests for this appimage)
>
> Download link:
> https://mega.nz/file/dB1whaZA#VgC-9p2jjCmvxaEmClWQTFvKRcpiTUD_-A07ULp1cPc
> Note: when it works correctly I am of course willing to share it with the
> normal repositories, if there is a need/demand for it.
>
> *(My only experience so far with appimages is my jExifToolGUI appimage for
> my own jExifToolGUI. Of course the jar itself is completely cross-platform,
> but the appimage with included jre is for x86_64 linuxes.)*
>
> hoi,
> Harry
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuO8n41U6R_BKYoYin9rtzkJ3fEyEy2ootrghCfeFXYbg%40mail.gmail.com.

[hugin-ptx] Fwd: hugin-2020.0.0 AppImage for Linux x86_64

[Harry van der Wolf]

i,H

And I forgot to include enblend and enfuse.
So a new version with them (and their dependencies).

https://mega.nz/file/JAskwC6B#nC8mB1_4BtSHEs-366jz8yv5LuUtE4MPvZccqlpi0xY

Harry

-- Forwarded message -
Van: Harry van der Wolf 
Date: za 13 feb. 2021 om 17:06
Subject: hugin-2020.0.0 AppImage for Linux x86_64
To: hugin-ptx@googlegroups.com 


Hi,

After quite a long "panorama hibernation" I decided to create some winter
panoramas.
I could not find a recent build of Hugin for Ubuntu likes. It also seems
that aferrero2707 no longer builds Hugin appimages.
So I downloaded the hugin-2020.0.0 source and compiled it myself.
And then I decided to try to make an AppImage, so I tried aferrero2707's
scripts and modified them slightly. (Note: he builds with root rights or in
a (docker) container, I don't know. I don't want that)
The appimage is built on a x86_64 GalliumOS 3.0 (Ubuntu 18.04 LTS Bionic
Beaver derivative), which is an Ubuntu Linux especially for Chromebooks.
The (probable) backwards compatibility is therefore 18.04 LTS. Maybe it
works on older Ubuntu-like versions as well.
It works for me. I hope it works for others as well.
Please give it a try and please let me know. This appimage does not contain
the gtk-2 and pixbuf libraries as aferrero2707's appimages do (or did). All
debian/ubuntu derivatives nowadays come with these libraries, even KDE
versions (I tried many distributions and versions for my own application. I
did not do further tests for this appimage)

Download link:
https://mega.nz/file/dB1whaZA#VgC-9p2jjCmvxaEmClWQTFvKRcpiTUD_-A07ULp1cPc
Note: when it works correctly I am of course willing to share it with the
normal repositories, if there is a need/demand for it.

*(My only experience so far with appimages is my jExifToolGUI appimage for
my own jExifToolGUI. Of course the jar itself is completely cross-platform,
but the appimage with included jre is for x86_64 linuxes.)*

hoi,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpszQx%3D-fz9ie9j38yxsWegQJPN38PxAYorzwQC2Y0VxfA%40mail.gmail.com.

[hugin-ptx] hugin-2020.0.0 AppImage for Linux x86_64

[Harry van der Wolf]

Hi,

After quite a long "panorama hibernation" I decided to create some winter
panoramas.
I could not find a recent build of Hugin for Ubuntu likes. It also seems
that aferrero2707 no longer builds Hugin appimages.
So I downloaded the hugin-2020.0.0 source and compiled it myself.
And then I decided to try to make an AppImage, so I tried aferrero2707's
scripts and modified them slightly. (Note: he builds with root rights or in
a (docker) container, I don't know. I don't want that)
The appimage is built on a x86_64 GalliumOS 3.0 (Ubuntu 18.04 LTS Bionic
Beaver derivative), which is an Ubuntu Linux especially for Chromebooks.
The (probable) backwards compatibility is therefore 18.04 LTS. Maybe it
works on older Ubuntu-like versions as well.
It works for me. I hope it works for others as well.
Please give it a try and please let me know. This appimage does not contain
the gtk-2 and pixbuf libraries as aferrero2707's appimages do (or did). All
debian/ubuntu derivatives nowadays come with these libraries, even KDE
versions (I tried many distributions and versions for my own application. I
did not do further tests for this appimage)

Download link:
https://mega.nz/file/dB1whaZA#VgC-9p2jjCmvxaEmClWQTFvKRcpiTUD_-A07ULp1cPc
Note: when it works correctly I am of course willing to share it with the
normal repositories, if there is a need/demand for it.

*(My only experience so far with appimages is my jExifToolGUI appimage for
my own jExifToolGUI. Of course the jar itself is completely cross-platform,
but the appimage with included jre is for x86_64 linuxes.)*

hoi,
Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptWBS6A1oB8XmDYNUsUMZdKvuKkLY5K48z8U3Ru4cX7qg%40mail.gmail.com.

Re: [hugin-ptx] [patch] typo "normaly"

[Harry van der Wolf]

I saw this one as well, but it actually is not
An equirectangular image has normally an ratio of 2:1

but
An equirectangular image has normally *a* ratio of 2:1

Sorry.

bye,
Harry

Op ma 26 okt. 2020 om 08:23 schreef Andreas Metzler :

> Hello,
>
> find attached a trivial typo fix, generated with
> sed -i -e s/normaly/normally/g  `grep -rl normaly`
>
> cu Andreas
>
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/20201026072233.GA30992%40argenau.bebt.de
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsoxy3NAL7X%2BVMSZ9x1tge9NAKXE1VWwFJNq8H-6CmddA%40mail.gmail.com.

Re: [hugin-ptx] align_image_stack & EXIF data

[Harry van der Wolf]

If you are using a shell script or python script you would probably loop
through the source images and use a counter starting at 0, as the created
tiffs are starting as .
And add the images to an array
===
#!/bin/bash

img_array=()
counter=0
for x in "${@}"
do
img_array+=( "${x}" )
counter+=1
done

align_image_stack -a ais_ "${@}"

for ((i=0;i<=${counter};i++));
do
exiftool -overwrite_original -tagsfromfile  ${img_array[$i]} -all:all
ais_000$i}.tif
done

===

(Completely untested !)

Op ma 20 apr. 2020 om 19:20 schreef John Aldridge :

> OK... I can cope with that. It'll be a bit messy working out (from the
> script) which source image corresponds to which processed one, but I'm sure
> I can sort out a way of doing it.
>
> Thanks!
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/8dca8865-40fb-423d-abe3-a08ba77f2fed%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpv_65EDvDKqBzpx8oyeG912FGsR81nQX33BjomubJ9HeA%40mail.gmail.com.

Re: [hugin-ptx] align_image_stack & EXIF data

[Harry van der Wolf]

Aargh. One too fast copy
The second line should be:
or
exiftool -overwrite_original -tagsfromfile Picture1.jpg -all:all
ais_.tif

There are many more options possible but this will save all your camera
data.
Note that if you have an (older) reflex/system camera and the lens is not
"electronically connected", you will not have lens data in your original
image and neither in your AIS updated tif

Op ma 20 apr. 2020 om 15:48 schreef Harry van der Wolf :

> If you have exiftool on your pc, and I assume you have, you should/could
> do the following.
>
> align_image_stack -a ais_ Picture1.jpg Picture2.jpg Picture3.jpg
>
> Giving you ais_.tif, ais_0001.tif and ais_0002.tif
>
> Then do:
> exiftool -overwrite_original -tagsfromfile Picture1.jpg -exif:all
> -makernotes:all ais_.tif
> or
> exiftool -overwrite_original -tagsfromfile Picture1.jpg -all:all
> -makernotes:all ais_.tif
>
> -all:all might least to errors. Note also that some exif tags might be
> written as xmp tags.
>
> And for all. You can automate this in a script.
>
> Op ma 20 apr. 2020 om 10:47 schreef John Aldridge <
> j.p.s.aldri...@gmail.com>:
>
>> Hello,
>>
>> I'm using align_image_stack with the -a option to align a set of images
>> I've taken over a period of months. This is working well, but loses all the
>> EXIF data from the original images -- the loss of the date and time of the
>> exposure is the one which is causing me a little grief. It would also be
>> nice to preserve the basic exposure parameters: aperture, shutter speed,
>> and ISO.
>>
>> Is there a way to preserve this data in the aligned images?
>>
>> Cheers,
>> John
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/hugin-ptx/76ac7f37-33b9-43cf-a709-a4593379f759%40googlegroups.com
>> <https://groups.google.com/d/msgid/hugin-ptx/76ac7f37-33b9-43cf-a709-a4593379f759%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvmWn-CbK8Vg3zFgqX9av13ApLTxe5_DXLkGt2ptjPPqA%40mail.gmail.com.

Re: [hugin-ptx] align_image_stack & EXIF data

[Harry van der Wolf]

If you have exiftool on your pc, and I assume you have, you should/could do
the following.

align_image_stack -a ais_ Picture1.jpg Picture2.jpg Picture3.jpg

Giving you ais_.tif, ais_0001.tif and ais_0002.tif

Then do:
exiftool -overwrite_original -tagsfromfile Picture1.jpg -exif:all
-makernotes:all ais_.tif
or
exiftool -overwrite_original -tagsfromfile Picture1.jpg -all:all
-makernotes:all ais_.tif

-all:all might least to errors. Note also that some exif tags might be
written as xmp tags.

And for all. You can automate this in a script.

Op ma 20 apr. 2020 om 10:47 schreef John Aldridge :

> Hello,
>
> I'm using align_image_stack with the -a option to align a set of images
> I've taken over a period of months. This is working well, but loses all the
> EXIF data from the original images -- the loss of the date and time of the
> exposure is the one which is causing me a little grief. It would also be
> nice to preserve the basic exposure parameters: aperture, shutter speed,
> and ISO.
>
> Is there a way to preserve this data in the aligned images?
>
> Cheers,
> John
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/76ac7f37-33b9-43cf-a709-a4593379f759%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsfC9Zs356v8bfS3Yj6G%2BSe77NJeiG738xaH9_cgTHCSw%40mail.gmail.com.

Re: [hugin-ptx] Why shouldn't Hugin trust exif data 100% ?

[Harry van der Wolf]

Well,

Earlier my Samsung S5 mini, then my Motorola G5+ and now the Motorola G6+
all do a very fine job when it comes to Exif data. What's more: They also
provide GPS data which my camera doesn't.
And I don't understand why it should be worse than on a phone compared to a
camera which only sometimes gets new firmware.
In all those (stupid) commercials nowadays, it seems that the camera is the
most important feature on a phone, and those phones go in much higher
amounts than cameras nowadays. So I assume the cameras and their
software gets a lot of attention and can be more easily upgraded/fixed than
firmware in cameras.
The only issue is that they only store Exif data and very limited
makernotes.
No XMP, no composite, no icc_profiles. At least not those 3 phones I used
and mentioned.
My panasonic system camera comes with a lot of data in all those areas,
where it sometimes is redundant as XMP combines a lot.

Harry



Op do 16 apr. 2020 om 23:36 schreef David W. Jones :

> On April 16, 2020 9:43:51 AM HST, "Gunter Königsmann" <
> gunter.koenigsm...@gmail.com> wrote:
>>
>> My guess (it's only a guess) is that for most cellphone cameras the
>> manufacturer hasn't cared if the metadata it comes with is any correct.
>>
>> Kind regards,
>>
>> Gunter.
>>
>>
> That's my experience, too.
>
> --
> David W. Jones
> gnomeno...@gmail.com
> wandering the landscape of god
> http://dancingtreefrog.com
>
> Sent from my Android device with F/LOSS K-9 Mail.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/4860DF62-6E08-4784-AF05-85F5265ECB89%40gmail.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsLAMZB7HLQTJqLvnRuZm5kmun636%2BriyoR-ShawXB4aw%40mail.gmail.com.

Re: [hugin-ptx] Convert photo to scanned image

[Harry van der Wolf]

See this tutorial: http://hugin.sourceforge.net/tutorials/scans/en.shtml

Harry

Op wo 1 jan. 2020 om 09:01 schreef Milind Purohit :

> Frequently one needs a nicely scanned image of a document, but only a cell
> phone is handy.
> It seems that Hugin can convert a photo of a page by appropriate
> stretching to a nicely rendered rectangular scanned image.
> Is this possible, and if so how to do it?
>
> Thanks.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/5c24aa5e-62af-4178-b162-0f4606b9c040%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsAtAD6NK9TBEQT%3DsGpZ%3DSTHS5EwUn9_3Nwg23RUVXUew%40mail.gmail.com.

Re: [hugin-ptx] Re: Hugin 2019.2.0 rc1 released

[Harry van der Wolf]

I understand, but actually the "/usr/bin/env" is not a path, but an "alias"
to a path set in the ENVIRONMENT.

So actually we need /usr/bin/python3 for linux, and /usr/local/bin/python3
for BSD.
Note that BSD is Berkely unix (like NetBSD, OpenBSD but also MacOS and many
others) and it is NOT linux (like fedora, debian, ubuntu, suse, redhat,
etc. etc.).
For a windows user that might seem a small difference, but it isn't. (well:
when comparing windows with linux or bsd, the difference compared to
windows is very small)

Harry

Op vr 29 nov. 2019 om 19:26 schreef T. Modes :

> Hi Harry,
>
> Am Freitag, 29. November 2019 19:09:50 UTC+1 schrieb Harry van der Wolf:
>>
>> It means that by using the "/usr/bin/env python3" (or /usr/bin/env
>> javac") to use an "outside PATH" installation.
>>
>> So in the case of "/usr/local/bin/python3", the command "/usr/bin/env
>> python3" can point, and therefore use, the /usr/local/bin/python3.
>>
>
> So I understand the working of env also. But the usage of /usr/bin/env has
> been banned from Fedora...
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/b9dc107f-ff87-4186-9d32-a0ce1f4fe918%40googlegroups.com
> <https://groups.google.com/d/msgid/hugin-ptx/b9dc107f-ff87-4186-9d32-a0ce1f4fe918%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptYDntBEBEcb3-zOiTgB9Z0v59J%2BC-8ixOBRQ%2B5j2gW3g%40mail.gmail.com.

Re: [hugin-ptx] Re: Hugin 2019.2.0 rc1 released

[Harry van der Wolf]

The "/usr/bin/env" command is used for many programs, not only python.

The "env" command checks the linux configuration where the default program
has been installed in case of multiple versions like python2 or python3,
but also java-8, java-10, java-11 and other multi-version installs.
If there are multiple installs of for example python3 and the OS "knows"
about it, it can be overridden by "sudo update-alternatives --config
python3" to point to /usr/bin, /usr/local/bin or wherever you have
installed (your own) version of python.
It means that by using the "/usr/bin/env python3" (or /usr/bin/env javac")
to use an "outside PATH" installation.

So in the case of "/usr/local/bin/python3", the command "/usr/bin/env
python3" can point, and therefore use, the /usr/local/bin/python3.

Harry

Op vr 29 nov. 2019 om 16:19 schreef T. Modes :

> Hi Bruno,
>
> Am Freitag, 29. November 2019 08:24:58 UTC+1 schrieb Bruno Postle:
>>
>>
>> Yes the fedora policy on this is much more pedantic. The /usr/bin/env
>> stuff has use-cases for people who need to use weird computer systems, but
>> it can only cause problems for people who get Hugin from a Linux
>> distribution.
>>
>
> I didn't know this. So I let the /usr/bin/env approach.
> A short search revealed that BSD like distros are using
> /usr/local/bin/python3.
> So we have
> /usr/bin/python3
> /usr/bin/env python3
> /usr/local/bin/python3
>
> All 3 one are used by different distros, but not a single common usage...
>
> Thomas
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/ca481fcd-99b1-4267-a8db-5a8307a7fd5c%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPputw1iusSrLXx6WpuWMwLmx7HSe4V8nu4egqPEC8TBq5g%40mail.gmail.com.

Re: [hugin-ptx] Re: Hugin 2019.2.0 rc1 released

[Harry van der Wolf]

Hi,

Op vr 29 nov. 2019 om 00:18 schreef David W. Jones :

> On November 28, 2019 12:11:47 PM HST, Bruno Postle 
> wrote:
> >Fedora packages of Hugin 2019.2 rc1 are here:
> >https://copr.fedorainfracloud.org/coprs/bpostle/panorama/
> >
> >(Note that I'm still changing #!/usr/bin/env python3 to
> >#!/usr/bin/python3 to get the build through the fedora tests)
>
> Hmm, would that work on Debian? Since the only option that seems available
> is flatpack or something like it that I've never gotten to successfully
> work at all.
>
>
 I do not understand your question with regard to Debian. I have a Debian 8
(just switched on again), Debian 9 and Raspbian 10 system, and an Ubuntu
Bionic system, all having python3 in /usr/bin. I do agree that the
"/usr/bin/env python3" is highly preferable, but I do not see why it would
not work on Debian.
Your answer about flatpack (should be flatpak I suppose) is a "general
purpose" question over all distributions, not specifically for Debian where
it should work (I think).

Can you elaborate on this? I think your mail is a little too short.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsGhY%2BHu0kGJYt%3Dkx_j9i1%3D0mUqdNb8Osow%3DuRjSBJu8A%40mail.gmail.com.

Re: [hugin-ptx] Python help needed

[Harry van der Wolf]

Op za 20 jul. 2019 om 19:10 schreef 'kfj' via hugin and other free
panoramic software :

>
>
> On Saturday, July 20, 2019 at 1:13:09 AM UTC+2, Tduell wrote:
>>
>> On Fri, 19 Jul 2019 18:40:22 +1000, 'kfj' via hugin and other free
>>
> I think forcing the linking-in of a python3 interpreter should be handled
> by cmake. On my system, for example (I mistyped, I'm on ubuntu 18.04 LTS),
> when I build hugin as per instructions in the wiki, it comes out a python2
> interpreter. There's docu I found here
>
> https://cmake.org/cmake/help/git-stage/module/FindPython3.html
>
> Does that help?
>
> Kay
>
>
>

I think we can simply say that python 3 should be mandatory. python 3.0 was
released in December 2008. And python 3.0 is long out of support.
Any OS of around that date is already out of support: patches, virus, etc.
Even the long LTS Ubuntu versions and relatively long supported Debian
versions are out of support.

Windows 7 was released in 2009 and is out of service January 2020. Windows
8 out of support. Windows 8.1 still quite some years to go.
Python.org really promotes to use 3.x. Why would any "new" user try to
download 2.7? Most Windows users want to have the "latest and greatest"
anyway (sorry, my prejudice).

MacOS updates are only bound by older hardware, otherwise upgrades are free
and easy to install. MacOS is always running (way) behind with python but
that can easily be upgraded.

If you want an old (unsupported) OS with python 2.7, you can simply take an
older Hugin version. All Hugin versions since 2009~2011 function very nice.
Use a "classic" Hugin on a "classic" OS.

But that's my personal view on supporting "old stuff".

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpvOxMOYSXf01%3D4tqj6SMh67wD82_Cheo-Gb7tb5_8bN7A%40mail.gmail.com.

Re: [hugin-ptx] Linux distro of choice?

[Harry van der Wolf]

Op di 16 jul. 2019 om 10:59 schreef David W. Jones :

>
> > But I was
> >thinking of file system snapshots, available on UFS and ZFS.  They do
> >pretty much the same thing.  I don't know which Linux file systems
> >support them.
>
> Ah. I don't either. A quick duckduckgo search found BTRFS supports
> snapshots. Apparently you can also create snapshots if you use what one
> site called the "Linux native" file system lvm.
>
>
All Linux distro's support UFS, ZFS and BTRFS.
I had one 7x24 Debian RPi running using BTRFS, indeed to be able to make
snapshots.
I did use ZFS on an Ubuntu system for another reason, but that worked
straight-forward as well.
Simply add from apt/apt-get and then it is good to go. Standard /etc/fstab
entry

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpt228mZMYJbvduQ5ZvdrbMzmYWpjAwFFXQ0PhXAgakjhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Python help needed

[Harry van der Wolf]

Hi,

Op vr 17 mei 2019 om 17:27 schreef Dr Rainer Woitok :

>
> If I didn't completely missunderstand the problem, this seems easy: just
> use
>
>#! /usr/bin/env/python2
>

If using this work-around, the shebang actually should not be "#!
/usr/bin/env/python2".
It should be "#!/usr/bin/env python2". No space between "#! /" and a space
between the env command and python2.

And it will not work if hugin and the hsi is compiled against python 3
(like compiled from  /usr/include/python3.5)

But I agree with Bruno: Some volunteer should fix it, or it should be
removed.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpuLUG1TUdVZxe4e%2BNzq_yLpLC-Y9yHfhno8e7C4X608mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Piranesi's perspective trick

[Harry van der Wolf]

Thanks a lot Bruno.

Great article!

Harry

Op wo 1 mei 2019 om 10:57 schreef Paul Womack :

> Yes - this is a perfectly usual way to specify a morph.
>
> e.g. Imagemagick's -distort Polynomial option
>
> http://www.imagemagick.org/script/command-line-options.php#distort
>
>   BugBear
>
> On Wed, 1 May 2019 at 08:10, David W. Jones  wrote:
>
>>
>> Thanks. Haven't read it yet, but it seems to me that control points
>> could be used to do arbitrary image warping. Like we used to do in high
>> school art by overlaying a square grid over an image, then drawing a
>> distorted grid over another sheet and copying the points over (along
>> with whatever line/shading/distortions were needed due to the distorted
>> grid).
>> 
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/CAD1remafDzZGdLVT9JHkL5rPAS3%3DerrJiELxixUbXSH80Vdsrg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpududCv_xSyGpXzZZr%2B2_OGwm1PM7PMgCi8a0otUKt0Zw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2018.0 beta1

[Harry van der Wolf]

Ok,

I didn't know that about the fuzzy translations. I simply thought that
every translated string would be picked up.
I will alter the two fuzzy strings with the ampersand and look for an
available shortcut-character.
To be honest: I didn't touch Hugin for quite some time now. It's more that
I still feel "loyal" to the project.

Harry

2017-12-12 17:21 GMT+01:00 T. Modes <thomas.mo...@gmx.de>:

> Hi Harry,
>
> Am Dienstag, 12. Dezember 2017 08:57:58 UTC+1 schrieb Harry van der Wolf:
>>
>> I'm sorry. Those were correctly translated but poedit still thinks they
>> are fuzzy. For two of them it is because the original has a key-shortcut,
>> like "", which is "Fotos" in Dutch, so no Ctrl-Key combinations
>> possible with a "P". These kind of translations I always leave as fuzzy.
>>
> Just as comment: fuzzy strings won't be translated in the GUI. So on place
> of the fuzzy strings there appears the English text.
> With the ampersand I think you mix things up: The shortcuts (combination
> with the Ctrl/command key) are not translated and are not included in the
> po file. The ampersand in the text is used as menu mnemonic - so you can
> open fast a menu item when pressing the underlined character (=the
> character after the ampersand). (Or with Alt+character open the top menu).
> So you can use another characters for the mnemonic in your translation. You
> have only to check that in each sub-menu each character is only used once.
> (Otherwise you iterate through all menu items with the same character and
> need to press return explicit.)
> For instance the English text "" is in German "".
>
> Thomas
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/hugin-ptx/ac8c0698-f273-470f-90c4-258c0d24e1e0%40googlegroups.com
> <https://groups.google.com/d/msgid/hugin-ptx/ac8c0698-f273-470f-90c4-258c0d24e1e0%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpurf0RzWHURKPD0tR4_%3D893q0LCt-o-ODcVS3eBW71woQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2016.2 released

[Harry van der Wolf]

Hi Thomas,

Thanks for all the work and time you spend to Hugin providing new
functionality, bugfixes and an ever improving new version of Hugin.

Kind regards,
Harry


2016-09-18 10:02 GMT+02:00 T. Modes :

> Hi all,
>
> today we are releasing the final version of Hugin 2016.2.
>
> Source tarball can be downloaded
> at sourceforge: https://sourceforge.net/projects/hugin/files/hugin/hugin-
> 2016.2/hugin-2016.2.0.tar.bz2/download
> or at launchpad: https://launchpad.net/hugin/20
> 16.2/2016.2.0/+download/hugin-2016.2.0.tar.bz2
>
> Verify its checksums:
> md5: bfc28b0774e5147207e8b4b54875c33d  hugin-2016.2.0.tar.bz2
> sha1: 9d28609d973fa72b95b1e2506cf1de7d24578e67  hugin-2016.2.0.tar.bz2
> This is a source code release.
> Users communities produce executables for their respective platforms.
> Please announce further here.
>
> Users have already provided executables for Windows and Mac OS X:
> Windows 32 bit: https://sourceforge.net/projects/hugin/files/hugin/hugin-
> 2016.2/Hugin-2016.2.0-win32.msi/download (MD5:74ef9eb8639b99d46e69ec770
> 4b1ca73)
>
> Windows 64 bit: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2016.2/Hugin-2016.2.0-win64.msi/download
>  (MD5: fa9d36e9de2043ee5fc1949000861cc4)
> Mac OS X: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2016.2/Hugin-2016.2.0.dmg/download
>  (MD5: 02abec952fe0b27ff23c1a1f75af1c93)
>
> (The release corresponds to changeset be8da0221960 in our repository,
> which is also tagged as 2016.2.0. The final version is identical to release
> candidate 2.)
>
> Attention:
> There is a known issue on Linux: When starting Hugin the Photos tab is not
> correctly drawn. This happens only with GTK+3.20 and with some window
> managers (not all).
> This is a bug in wxWidgets and/or GTK+3.x and needs to be fixed upstream.
> A workaround is to resize the Hugin window after start up, then the Photos
> tab is correctly draw.
> For builders: We recommend therefore to compile Hugin with an older
> versions of GTK+2.x or GTK+3 <3.20.
>
> Changes since 2016.0.0
>
> * Allow reading of image positions from Papywizard XML files: First add
> the image to a new project and then select File, Import settings from
> Papywizard XML file... This will read the lens settings, the image
> positions and also, if applicable, the bracket settings. After this, the
> usual workflow is to run cpfind with --prealigned switch and then geocpset
> to connect orphanded images.
> * The internal blender and verdandi got the possibility to blend seams as
> alternative to current hard seam: For each seam the color of second image
> is adapted to the match the color of the first seam. For this blender, the
> blender order changes according to the overlap. The blending starts with
> the exposure anchor and blends then all overlapping images. This blending
> mode is not suited if there are bigger misalignments or bigger parallax
> errors.
> * The display of the control point error (after optimizing and in fast
> preview window) and the control point list window can now limited to take
> only control points in active images into account (menu Edit, Optimize only
> active images, connected with the setting on the optimizer tab).
> * Improvements to mask tab in Hugin (edit crop of all images of the same
> lens at once) and find panorama dialog in PTBatcherGUI (remove images from
> found panoramas, split found panorama into two).
> * Several improvements for Mac OS.
> * Fixes several issues with fast preview window which could result in
> random crashes (uninitialized variables, memory leaks).
>
> Upgrading from previous versions of Hugin should be seamless. If you do
> have problems with old settings, these can be reset in the Preferences
> window by clicking 'Load defaults'.
>
>
> The release notes can be found at http://hugin.sourceforge.net/r
> eleases/2016.2.0/en.shtml
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/hugin-ptx/ebf756cf-8bd0-48be-bcef-9cf37b90951b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [hugin-ptx] new image stitching software

[Harry van der Wolf]

As such I don't care that someone ceates another tool to do these kind of
things.

What bothers me more is this:
http://molanisvr.com/78-molanis-vr/76-360-vr-image-stitching-software

To me his now promoted software looks exactly like hugin. I assume (?) that
mr. Valdes will act according all license obligations he has to prevent
legal issues. The problem is that I can't find any reference to it.
Based on that screenshot(s) his software must contains parts of hugins code
base.


Harry

2016-07-28 10:20 GMT+02:00 bugbear :

> Forex Valdes wrote:
>
>> Hi all
>>
>> I am launching a new image stitching software. You can get it here
>> http://molanisvr.com/78-molanis-vr/85-360-vr-image-stitching-download
>> This version does not have any watermarks. It is fully functional.
>>
>
> What problem, that Hugin does *not* solve, does your software solve?
>
>   BugBear
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/5799C042.5010206%40papermule.co.uk
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptybeysQGvzHLg47%2BJC0xXZG8PXkRheQBLkBHCqS1ozMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Call for translators

[Harry van der Wolf]

2016-06-22 11:11 GMT+02:00 Carl von Einem :

> Isn't that covered in
> ?
>

Yest it is :)
And sometimes you (I) do it wrong.

Harry

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptmDwB7krYdwvK9-9--kwp%3DJBsOOOFo%2BdS5rYeMvCaecQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Call for translators

[Harry van der Wolf]

Hi,

I thought I had set my mercurial to the 2016.2 branch but I accidently
pushed to the default tree.
I assume my knowledge is by now too rusty.
I also checked and improved some older translations.
By now that becomes a big job with 9682 lines in total with 7733 text
containing lines (1949 blank lines).

hoi,
Harry


2016-06-19 19:51 GMT+02:00 Frederic Da Vitoria :

> Hello GS,
>
> 2016-06-17 16:44 GMT+02:00 Carl von Einem :
>
>> Hi GS,
>>
>> try Poedit, you'll find the link and more information here:
>> 
>>
>> Cheers,
>> Carl
>>
>>
>> Click From Mars - wrote on 17.06.16 12:29:
>>
>>> Hello,
>>>
>>> I just contacted Mr Coulon, whose name is at the top of the french
>>> translation PO file, about it.
>>> I have no clue about using PO files for translation, but if one can show
>>> me an easy tool to use to get it done, I wouldn't mind giving a hand :)
>>>
>>> GS
>>>
>>>
> I also found http://docs.translatehouse.org/projects/virtaal/en/latest/#
> It seems to have some nice features, like automatically checking tags and
> placeholder consistency. One not so nice, though: it crashed once. But if
> you save your work frequently, I guess you are safe.
>
> BTW, did you start translating, or do you wish me to work with you ?
>
> --
> Frederic Da Vitoria
> (davitof)
>
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/CANe_y9T%2BirAOJS-Zd%2BURoPE9jSNgObtogveL2j-fSR37Bz9ANA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpsGGr4rAzbMDFLcWTdPUmUVg%3DvHrWLtZvz0fyp4gBBf0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Call for translators

[Harry van der Wolf]

Working on the Dutch one.

Harry

2016-06-17 16:44 GMT+02:00 Carl von Einem :

> Hi GS,
>
> try Poedit, you'll find the link and more information here:
> 
>
> Cheers,
> Carl
>
>
> Click From Mars - wrote on 17.06.16 12:29:
>
>> Hello,
>>
>> I just contacted Mr Coulon, whose name is at the top of the french
>> translation PO file, about it.
>> I have no clue about using PO files for translation, but if one can show
>> me an easy tool to use to get it done, I wouldn't mind giving a hand :)
>>
>> GS
>>
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/56b96fef-38dc-cb8a-fb6e-6c099ff1735d%40einem.net
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptQcajrD13cJWFpLExraug4eHfti%2BDHc8M%2BTu7r9yecdA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Mac Build

[Harry van der Wolf]

The problem in this case is that macos is not the working directory, but
the directory one higher.
The directory that contains pkginfo and Info.plist is the working folder.
I'm not sure (as I can not test myself) that a path like ./MacOS/enblend
might work

Harry

2016-04-19 14:13 GMT+02:00 Niklas Mischkulnig <nik...@mischkulnig.de>:

> Exiftool and enblend/enfuse are in there: (both PTBatcherGUI.app and
> Hugin.app), see the attachments
>
> when enblend is called, it is exspected to be somewhere in PATH, i.e. 
> /usr/local/bin;
> ./enblend , however,  searches in the current dir, next to Hugin
> You can try that out in bash.  That is why I set enblend and enfuse to
> alternative paths, since I couldn't find a path to enblend and enfuse in
> the src. Or could Hugin change PATH ?
>
>
> Am Dienstag, 19. April 2016 09:41:10 UTC+2 schrieb Harry van der Wolf:
>>
>> With regard to the exiftool error: In the previous builds exiftool was
>> also incorporated in the bundles. I assume that was forgotten for this
>> bundle.
>>
>> W.r.t. enblend and enfuse: Please check whether they are inside the
>> bundles. If not: then it is the same error as above. If the enblend
>> --version command works it means that enblend is available.
>>
>> If you have an external enfuse and enblend you can point hugin towards
>> these versions.
>>
>> Harry
>>
>> 2016-04-19 7:05 GMT+02:00 Niklas Mischkulnig <nik...@mischkulnig.de>:
>>
>>> *I had to go into the Hugin.app settings, under programs and set
>>> alternative enblend/enfuse **executables** to **./**enblend** and **./*
>>> *enfuse** to make **PTBatcherGui** work. *
>>> Am 19.04.2016 00:53 schrieb "Donald Johnston" <dgjoh...@accesscomm.ca>:
>>>
>>>> To add to this error information I did two additional tests with these
>>>> images.
>>>> 1. the first three images so it was an exposure stack. All fine until
>>>> “Create panorama…”; same failure.
>>>> Blender: Unknown blender (enblend —version failed)
>>>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>>>> ExifTool: FAILED
>>>>
>>>> 2. images 1, 4, and 7; so no exposure stack just a three image pano …
>>>> same failure (except no enfuse failed).
>>>> Blender: Unknown blender (enblend —version failed)
>>>> ExifTool: FAILED
>>>>
>>>>
>>>>
>>>> On Apr 18, 2016, at 4:32 PM, Donald Johnston <dgjoh...@accesscomm.ca>
>>>> wrote:
>>>>
>>>> Another error. I loaded an old project with 18 images that requires
>>>> exposure fusion and stitching. The project loaded fine, the preview window
>>>> show the aligned preview as it should be.  When I ran the stitcher it goes
>>>> for a while and then fails with the following Status Report. I then
>>>> reloaded the original images as a new project, aligned the images, and got
>>>> the same failure.
>>>>
>>>>
>>>>
>>>> 
>>>> Stitching panorama…
>>>> 
>>>>
>>>> Platform: Mac OS X (Darwin 15.4.0 x86_64)
>>>> Version: 2016.1.0 built by Niklas Mischkulnig
>>>> Working directory:
>>>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
>>>> Output prefix: IMG_0809 - IMG_0826Test2016
>>>>
>>>> Blender: Unknown blender (enblend —version failed)
>>>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>>>> ExifTool: FAILED
>>>>
>>>> Number of active images: 18
>>>> Output exposure value: 15.9
>>>> Canvas size: 7298x2179
>>>> ROI: (108, 190) - (7237, 1174)
>>>> FOV: 144x43
>>>> Projection: Equirectangular(2)
>>>> Using GPU for remapping: false
>>>>
>>>> Panorama Outputs:
>>>> * Exposure fused from stacks
>>>>
>>>> First input image
>>>> Number: 0
>>>> Filename:
>>>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
>>>> Size: 2592x1728
>>>> Projection: Normal (rectilinear)
>>>> Response type: custom (EMoR)
>>>> HFOV: 34
>>>> Exposure value: 16.0
>>>>
>>>>
>>>> Remapping LDR images without exposure correction…
>>>> Multiple images output
>>>> loading IMG_0809.J

Re: [hugin-ptx] Mac Build

[Harry van der Wolf]

With regard to the exiftool error: In the previous builds exiftool was also
incorporated in the bundles. I assume that was forgotten for this bundle.

W.r.t. enblend and enfuse: Please check whether they are inside the
bundles. If not: then it is the same error as above. If the enblend
--version command works it means that enblend is available.

If you have an external enfuse and enblend you can point hugin towards
these versions.

Harry

2016-04-19 7:05 GMT+02:00 Niklas Mischkulnig :

> *I had to go into the Hugin.app settings, under programs and set
> alternative enblend/enfuse **executables** to **./**enblend** and **./*
> *enfuse** to make **PTBatcherGui** work. *
> Am 19.04.2016 00:53 schrieb "Donald Johnston" :
>
>> To add to this error information I did two additional tests with these
>> images.
>> 1. the first three images so it was an exposure stack. All fine until
>> “Create panorama…”; same failure.
>> Blender: Unknown blender (enblend —version failed)
>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>> ExifTool: FAILED
>>
>> 2. images 1, 4, and 7; so no exposure stack just a three image pano …
>> same failure (except no enfuse failed).
>> Blender: Unknown blender (enblend —version failed)
>> ExifTool: FAILED
>>
>>
>>
>> On Apr 18, 2016, at 4:32 PM, Donald Johnston 
>> wrote:
>>
>> Another error. I loaded an old project with 18 images that requires
>> exposure fusion and stitching. The project loaded fine, the preview window
>> show the aligned preview as it should be.  When I ran the stitcher it goes
>> for a while and then fails with the following Status Report. I then
>> reloaded the original images as a new project, aligned the images, and got
>> the same failure.
>>
>>
>>
>> 
>> Stitching panorama…
>> 
>>
>> Platform: Mac OS X (Darwin 15.4.0 x86_64)
>> Version: 2016.1.0 built by Niklas Mischkulnig
>> Working directory:
>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
>> Output prefix: IMG_0809 - IMG_0826Test2016
>>
>> Blender: Unknown blender (enblend —version failed)
>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>> ExifTool: FAILED
>>
>> Number of active images: 18
>> Output exposure value: 15.9
>> Canvas size: 7298x2179
>> ROI: (108, 190) - (7237, 1174)
>> FOV: 144x43
>> Projection: Equirectangular(2)
>> Using GPU for remapping: false
>>
>> Panorama Outputs:
>> * Exposure fused from stacks
>>
>> First input image
>> Number: 0
>> Filename:
>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
>> Size: 2592x1728
>> Projection: Normal (rectilinear)
>> Response type: custom (EMoR)
>> HFOV: 34
>> Exposure value: 16.0
>>
>>
>> Remapping LDR images without exposure correction…
>> Multiple images output
>> loading IMG_0809.JPG
>> remapping IMG_0809.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_.tif
>> loading IMG_0810.JPG
>> remapping IMG_0810.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0001.tif
>> loading IMG_0811.JPG
>> remapping IMG_0811.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0002.tif
>> loading IMG_0812.JPG
>> remapping IMG_0812.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0003.tif
>> loading IMG_0813.JPG
>> remapping IMG_0813.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0004.tif
>> loading IMG_0814.JPG
>> remapping IMG_0814.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0005.tif
>> loading IMG_0815.JPG
>> remapping IMG_0815.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0006.tif
>> loading IMG_0816.JPG
>> remapping IMG_0816.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0007.tif
>> loading IMG_0817.JPG
>> remapping IMG_0817.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0008.tif
>> loading IMG_0818.JPG
>> remapping IMG_0818.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0009.tif
>> loading IMG_0819.JPG
>> remapping IMG_0819.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0010.tif
>> loading IMG_0820.JPG
>> remapping IMG_0820.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0011.tif
>> loading IMG_0821.JPG
>> remapping IMG_0821.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0012.tif
>> loading IMG_0822.JPG
>> remapping IMG_0822.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0013.tif
>> loading IMG_0823.JPG
>> remapping IMG_0823.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0014.tif
>> loading IMG_0824.JPG
>> remapping IMG_0824.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0015.tif
>> loading IMG_0825.JPG
>> remapping IMG_0825.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0016.tif
>> loading IMG_0826.JPG
>> remapping IMG_0826.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0017.tif
>>
>>
>>
>>
>> On Apr 18, 2016, at 11:26 AM, Niklas Mischkulnig 

Re: [hugin-ptx] Mac Build

[Harry van der Wolf]

In the time that I built the bundles I once build the Hugin.app as a full
bundle and made symlinks to all redundant libraries in both other apps.
That decreased the size of the apps indeed but it required all thee apps to
be in the same folder (which as such is quite logical).
However, this build scenario made the compilation even harder and even
though the 3 apps are a big chunk of data: What is 180 MB even on a (small)
128 GB solid state disk. Leave alone on a 750+ GB disk.

At that time I simply wanted to try, but it wasn't worth all the hassle.
Besides: If a user wants it differently then he/she can buid it
himself/herself.

Note that I have left OSX about 2½ years ago.

I think you did an awesome job in building the new 2016 version for Mac. If
enough users have tested the builds I would suggest to upload them to
sourceforge where the other older bundles reside as well.
If you get too many downloads on your dropbox account it will be completely
blocked for others to download. Only you yourself can use it then.
I experienced that myself with another build (not for mac). I used dropbox
mainly to share things with my family. Even that was no longer possible.
With 180 MB bundles this might go faster then you expect.

Harry

2016-04-18 18:29 GMT+02:00 Niklas Mischkulnig <nik...@mischkulnig.de>:

> The main duplicate and large part are the dylibs under
> Hugin.app/Libraries/. These could be in a folder alongside Hugin.app,
> PTBatchGui.app and calibratelensgui.app, reducing the total filesize from
> 231 mb to 231-(2*35)=180mb. Putting the Resources/xrc folder there as well
> would shave off another 15 mb (resulting in 165mb).
> Is it worth the effort?
>
> Niklas
>
> Am Montag, 18. April 2016 18:05:10 UTC+2 schrieb Harry van der Wolf:
>>
>> The fact the mac bundles are that big is due to the "bundle all
>> dependencies" inside the app. That gives a lot of redundancy in the apps.
>> That is already for years and years a fact and as long as Apple doesn't
>> change their policy it will stay that way.
>> When compiling with XCode this strip functionality is automatically
>> executed but results in about 10% size reduction. But my information is
>> going years back.
>>
>> Harry
>>
>> 2016-04-18 17:07 GMT+02:00 Jan Dubiec <j...@onet.pl>:
>>
>>> On 2016-04-18 14:40, Niklas Mischkulnig wrote:
>>> [...]
>>> > Maybe there is someone who can tell me exactly what program needs which
>>> > libraries (especially which boost library) and binaries(like cpfind,
>>> > celeste, ...)  to shrink down the application sizes (currently 2* ~80mb
>>> > and 1* ~50mb) ?
>>> I don't know Macs but I'm quite sure that there is strip utility
>>> (https://en.wikipedia.org/wiki/Strip_%28Unix%29) for Macs.
>>>
>>> If you want to know about dependencies, read about CMake's --graphviz
>>> option. It allows you to generate graphs like this:
>>> * for the whole project –
>>> https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
>>> * for the whole project with external dependencies –
>>> https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
>>> * for a module (hugin in this case) –
>>> https://www.dropbox.com/s/bfsz6byb86o2l89/HuginHg.hugin.pdf?dl=0
>>> * for a module with external dependencies –
>>> https://www.dropbox.com/s/7h1yauyooqo0ggj/HuginHg.hugin-ext.pdf?dl=0.
>>>
>>> /J.D.
>>>
>>> --
>>> 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/5714F841.2020009%40onet.pl.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/a7cc3b06-7e9c-4ecd-8d65-866a67480afe%40googlegroups.com
> <https://groups.google.com/d/msgid/hugin-ptx/a7cc3b06-7e9c-4ecd-8d65-866a67480afe%40go

Re: [hugin-ptx] Mac Build

[Harry van der Wolf]

The fact the mac bundles are that big is due to the "bundle all
dependencies" inside the app. That gives a lot of redundancy in the apps.
That is already for years and years a fact and as long as Apple doesn't
change their policy it will stay that way.
When compiling with XCode this strip functionality is automatically
executed but results in about 10% size reduction. But my information is
going years back.

Harry

2016-04-18 17:07 GMT+02:00 Jan Dubiec :

> On 2016-04-18 14:40, Niklas Mischkulnig wrote:
> [...]
> > Maybe there is someone who can tell me exactly what program needs which
> > libraries (especially which boost library) and binaries(like cpfind,
> > celeste, ...)  to shrink down the application sizes (currently 2* ~80mb
> > and 1* ~50mb) ?
> I don't know Macs but I'm quite sure that there is strip utility
> (https://en.wikipedia.org/wiki/Strip_%28Unix%29) for Macs.
>
> If you want to know about dependencies, read about CMake's --graphviz
> option. It allows you to generate graphs like this:
> * for the whole project –
> https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
> * for the whole project with external dependencies –
> https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
> * for a module (hugin in this case) –
> https://www.dropbox.com/s/bfsz6byb86o2l89/HuginHg.hugin.pdf?dl=0
> * for a module with external dependencies –
> https://www.dropbox.com/s/7h1yauyooqo0ggj/HuginHg.hugin-ext.pdf?dl=0.
>
> /J.D.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/5714F841.2020009%40onet.pl.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPpucCCj3AuQ3ikSK4GwRNy_h604yub%3D5X_8BrXt9M2A4tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Hugin 2016.0 beta 1 released

[Harry van der Wolf]

I will try to build a win-64 version this weekend. At the moment I'm quite
busy with other things and my windows laptop "is lying in a corner" as I'm
back on ubuntu again.

Harry

2016-02-02 3:01 GMT+01:00 Terry Duell :

> Hello Martin,
>
> On Tue, 02 Feb 2016 09:04:28 +1100, Martin Pecka  wrote:
>
> Hello devs. Can we expect a Windows build of the beta to appear? I'd like
>> to test the (supposed-to-be-fixed) support for GPU remapping on
>> integrated Intel GPUs. Thanks for answering (and for your great work!).
>>
>>
> The beta release is a source code release, and the project relies on
> volunteers to build the binaries.
> I'm not sure if we have a Windows builder at the moment...hopefully
> someone can provide a more definitive answer.
>
> Cheers,
> --
> Regards,
> Terry Duell
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/op.yb6nxel8rs0ygh%40localhost.
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptkxkdC6tSgQjM3hQBDsbt1Yz8hEpd5WYOjDEhiM93iyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.