Re: [hugin-ptx] Re: OpenMP CMakeLists.txt patch

[Gunter Königsmann]

Disabling openMP seems like something that is useful when during debugging one 
wants to know if some malfunction is a threading race condition. But for 
compiling the application for the end-user disabling openMP sounds strange to 
me...

-- 
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/4CA76323-8507-44D6-A70E-73487788F5BD%40gmail.com.

Re: [hugin-ptx] Mac builds of Hugin

[Gunter Königsmann]

Sounds like you tried to start a ARM app on an Intel Mac or vice versa...

Kind regards,

  Gunter.

-- 
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/5B3231F9-1B2D-4400-844F-404B392D42E7%40gmail.com.

Re: [hugin-ptx] Combining small X-rays of circuit boards to make one complete image

[Gunter Königsmann]

I already used Hugo for stitching >200 screenshots from the microscope to a big 
picture one can do deeper analysis on. The only place hugin needed help was 
when it placed a few control points into the wrong repetition of a repetitive 
structure.

-- 
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/5F52358C-5B44-4EBB-9E31-9EFA9708A765%40gmail.com.

Re: [hugin-ptx] Stitching existing files together via Hugin

[Gunter Königsmann]

We should update that tutorial or somehow make that functionality easier to see 
as a big percentage of the questions is caused by having no obvious way to 
stitch flat images.

-- 
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/AE139135-A7DF-44BB-B8CB-F4376CC51291%40gmail.com.

Re: [hugin-ptx] Re: Simple UI improvement suggestion (correct exposures and colors)

[Gunter Königsmann]

For my microscope a few months back I bought a (cheap) astronomical camera that 
uses a Bayer array: the microscope produces an intermediate image with parallel 
rays that then is viewed using a telescope and since light constantly rips 
electrons from chemical bonds and therefore much light eventually kills what 
you are looking at one needs a camera that is able to deal with dim light. I 
guess astronomical devices should not spontaneously change the spectrum of 
their colour filters between two measurements, though.

But last night I remembered something different: 
I once had a camera that had not a bad pixel, but a bad spot that wasn't big - 
but caused the photometric optimization to go wild: In one picture there was a 
gray spot where in the next picture was red, green, blue or something else.

Kind regards,

  Gunter.

-- 
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/BE652A1C-2AE5-45B0-BC0B-A69EE50FF268%40gmail.com.

Re: [hugin-ptx] Re: Simple UI improvement suggestion (correct exposures and colors)

[Gunter Königsmann]

My cameras all seem to have a Bayer Colour Filter Array with 1 Red Filter, 1 
Blue Filter and 2 Types of green Filters that each filter different parts of 
the light spectrum.If one photo uses one of these green filters and for the 
next one the camera decides to use the other photometric optimization cannot 
help too much: For some pigments and dyes both filter will result in exactly 
the same colour, while for others the coklors thw camera sees will differ 
greatly.

Might this be the underlying problem?

-- 
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/6A9FC6B7-A2C9-42B8-BC21-4C469E4C40D3%40gmail.com.

Re: [hugin-ptx] Stitch Panorama Without Blending Exposure?

[Gunter Königsmann]

Can you use multiblend instead of enblend? It's faster and has no intelligent 
seams.

Kind regards,
   Gunter.

-- 
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/8BBE958C-61A7-45E7-81CC-C052AE13760D%40gmail.com.

Re: [hugin-ptx] Stitch Panorama Without Blending Exposure?

[Gunter Königsmann]

If you use the advanced UI you can leave out the "photometric optimization" 
step. Does that do what you want?

-- 
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/D3ECA977-20B7-435A-8988-4874DB270255%40gmail.com.

Re: [hugin-ptx] Re: Model Railroad backdrops from Streetview

[Gunter Königsmann]

Another problem will be: if the street view camera crosses a street one picture 
will look into the crossing street from the left. The next will look at it from 
the front and the following picture looks at it from the right. You have one 
picture of a balcony from the left and one from the right, but for stitching 
you would need it from the front... ...no matter where you stitch together 
these pictures these items won't fit: when stitching things recorded from 
several perspectives nothing should be oriented in Z direction.

Kind regards,

Gunter

-- 
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/6E4ACAC4-E545-4631-AFC8-AA5A796DB7A0%40gmail.com.

Re: [hugin-ptx] Basic newbie question

[Gunter Königsmann]

To me it looks like the camera hasn't only changed the angle it shot the images 
from, but also was moved horizontally, which means that one cannot warp the 
images in a way that they fit together in all places at once. Often Hugin 
Manages to move these discontinuities to places where they are hard to see.  
But that often requires the images to overlap strongly in order to give hugin 
more possibilities to place the seams.

One important thing I had to learn was not to tilt the camera around its 
center, but around the center of the lens.

Kind regards, Gunter 

-- 
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/9E86506A-0619-438F-8510-8209421A8093%40gmail.com.

Re: [hugin-ptx] Mac builds of Hugin

[Gunter Königsmann]

Not initializing glut before using it sounds scary...

-- 
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/C3928A88-B542-420C-A0F2-504621F08417%40gmail.com.

[hugin-ptx] Re: Wondering what I'm doing wrong

[Gunter Königsmann]

To me the first set of images looks like just not being indefinitely sharp 
- which is typical for real-live images: The optics in front of the camera 
sensor isn't perfect, even if you pay thousands of Dollars/Euros for it. 
The autofocus of your camera is optimized on something between speed and 
accuracy. And even if it happens to tell the optics to keep exactly this 
point in focus . the rest of the scene, being 3D, won''t be. Then the image 
is compressed so many of them fill on real-live disks - and only every 
roughly every fourth pixel gives you a measurement for the "red" value, 
every fourth pixel one for the blue one and every fourth for the green one 
- even without the pixels on the sensor being so small that it is virtually 
impossible for a photon to make sure to in the end always hitting the 
correct one That phenomenon is then counter-acted by the software that 
interprets data from the sensor.

The result is: You get pictures that are sharp enough for most real-world 
applications. But if you zoom in and look at the details you see that no 
mechanism human beings create is perfect.

The last image you sent looks like you moved the camera while it was shot. 
The darker it is (and thus: the longer the camera has to collect light in 
order to get enough photons per camera pixel that it can offer a good 
signal-to-noise ratio) and the more your optical zoom zooms enlarges the 
picture (and this reduces the area to collect light from whilst enlarging 
any effect from moving the camera) the harder it is to get a steady image.
sussys0s-oper...@protonmail.com schrieb am Donnerstag, 18. Mai 2023 um 
04:27:03 UTC+2:

> Can anyone please help?
>
> On Wednesday, March 1, 2023 at 3:45:23 PM UTC-5 Sussy OS wrote:
>
>> Here is another example on a bigger scale: 
>> https://drive.google.com/file/d/1_ADF6kgp1aP_2Yn0tOSTGaFkCjeVr9kL/view?usp=sharing
>>
>> On Wednesday, March 1, 2023 at 3:23:04 PM UTC-5 Sussy OS wrote:
>>
>>> Hello, I just downloaded Hugin recently, and it worked fine for 
>>> stitching two images side by side, but if I try to do images where I zoom 
>>> into the details (see examples below) it tuns out all blurry. Can anybody 
>>> help me to use Hugin correctly? I'm using the Sony Cyber-shot DSC-W220 
>>> Optical SteadyShot 12.1 MP camera for my images. EXAMPLE: 
>>> https://imgur.com/a/kh6duzM
>>
>>

-- 
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/128ca03b-bb0b-41f8-9a12-65d4e8bfb55an%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[Gunter Königsmann]

I still get a "repository not found" error.

-- 
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/A91864FB-A2C5-44ED-8C96-2BF2D791F885%40gmail.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[Gunter Königsmann]

One message of this thread mentioned C++ complains about using a private method 
of wxString. That error message normally means that a function expects totally 
different types of arguments than it gets from the current code.

If you allow the system to automatically convert everything to wxString and 
wxString to everything else without that causing an error you can call all 
versions of all functions with all types of arguments in any order without 
causing any error any more. But calling that function with those arguments 
still won't make any sense.p

-- 
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/FA4DF325-D249-481E-9A14-3954F735C257%40gmail.com.

Re: [hugin-ptx] Can't add any RAW converter in preferences (linux)

[Gunter Königsmann]

My guess is that a flatpak comes with its own /usr directory and doesn't see 
the one the system provides.

Am 17. April 2023 07:40:45 MESZ schrieb "David W. Jones" :
>My opinion? Don't use flathub and such things. I've never been able to make 
>them work here on my Debian 11 system.
>
>I have Hugin compiled locally and have no such problems.
>
>On 4/16/23 13:36, Piotr Szczuka wrote:
>> Hello everyone I am a hugin user for a while on linux mint system. My 
>> problem is that After new installation/ upgrade to mint 21,1 and installing 
>> hugin as flathub i can't import RAW images to it. When I am tryng add path 
>> to Darktable or to RAWtherapee I cant. Executable files are indeed in to 
>> /usr/bin directory but some how hugin do not see them in file-> preferences 
>> ->general -> RAW converter ->choose. I also tried just to put directoies 
>> manually without any resoults. I also tried to chenge flatseel configuration 
>> without any luck. Any sugestions for making hugin work with darktable as a 
>> converter? --
>> 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/c26e2a69-6199-460d-90cd-73685c3d6f7fn%40googlegroups.com
>>  
>> .
>
>
>-- 
>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/5e1d3a3f-524c-9128-4637-5ee403d2a65e%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/E4F38D8A-2C6E-48C3-93D1-440A6BC47DA9%40gmail.com.

Re: [hugin-ptx] Re: Insta360 One R dual lens image stitching

[Gunter Königsmann]

Normally both pictures of such a camera have a black border around it. If you 
don't use a mask to tell hugin that this border isn't part of the real picture 
hugin will try to match the black borders to each other, not the picture 
contents. For the rest of you give hugin a rough guess of the parameters and a 
few control points in which the pictures match hugin os good in optimizing the 
lens parameters until they match the lens.

Am 23. März 2023 17:32:09 MEZ schrieb "T. Modes" :
>robert...@gmail.com schrieb am Donnerstag, 23. März 2023 um 13:02:24 UTC+1:
>
>I don't have much experience with dual lens cameras and need some 
>guidance regarding the Hugin workflow. 
>What are the lens parameters? It's over 180 FOV, but I can find the 
>exact numbers. 
>
>I'm also a bit stumped regarding crop/mask settings. 
>
>
>A profile would be perfect! 
>
>
>An example image would be nice (preferred is a link, this is a mailing 
>list, don't attach big images to a mail) . 
>Otherwise it's only guessing.
>
>Hugin ships with the dual lens assistant. But not sure if the assistant 
>matches to your camera.
>There is also some discussion on the list, e.g. 
>https://groups.google.com/g/hugin-ptx/c/vYeBUu7_7Ic/m/hDy5vzKWBgAJ
>
>-- 
>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/7b2076da-37a3-4553-a5f9-8f39959cd7afn%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/EFFE4171-0CCC-4A99-BE42-78D64ED49BC7%40gmail.com.

Re: [hugin-ptx] Re-arrange image order to fix "blackout" sections

[Gunter Königsmann]

Multiblend should also 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/CA65C1B5-CDF3-4C54-95CD-B3B34F8E2BCC%40gmail.com.

Re: [hugin-ptx] Trying to compile Hugin: what is this MSGFMT error?

[Gunter Königsmann]

Either you haven't gettext installed or your cake is too old to know about 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/0F4C9B07-0F37-48EC-B076-2A2AC5523E68%40gmail.com.

Re: [hugin-ptx] Problem: Only 1/4 of Fast Panorama Visible

[Gunter Königsmann]

If it is on the Mac: with the open source program I maintain I have learnt that 
on hi-dpi ma s you can create low-dpi bitmaps (that are blurry) or bitmaps with 
n times the resolution. Which means that a "640x480" bitmap with 3-fold 
resolution claims to be 640x480, but needs to be filled with 3*640x3*480 
pixels...

-- 
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/F4DA51DC-E572-4125-9EEA-6F807C8E13A5%40gmail.com.

Re: [hugin-ptx] Trapezoidal distorsion when stitching scanned images

[Gunter Königsmann]

The head of my scanner isn't really horizontal bit slanted to one side by a few 
degrees. Maybe that is part of the problem for you, too?

Am 5. August 2022 19:31:47 MESZ schrieb Pierre Pierre 
:
>Hi all,
>
>First, some background, I'm currently trying to digitize all my father's 
>paintings and drawings; For artworks somewhat larger than my scanner I 
>needed stitching, and have been using hugin for that purpose for a few 
>months now.
>Using a script heavily inspired by the one referenced in the "stiching 
>scanned image" tutorial, or the script from Matthew Petroff 
>(https://github.com/mpetroff/stitch-scanned-images) usually gives good 
>results.
>The main issue I'm often facing is that the output image has some kind of 
>trapezoidal distortion, from mild to pronounced: usually the left end is 
>taller than the right end.
>I don't know why this happens, images overlap correctly and I can stitch 
>the same images manually without too much effort (it's just a lot slower).
>My current hypothesis is that output uses a rectilinear projection, but I'd 
>need a projection that's both rectilinear and conformal. I there a way to 
>request such optimization, or to postprocess control points mapping to 
>convert it to a conformal mapping?
>Thank you for your attention,
>Pierre
>
>-- 
>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/94e339d6-b128-42ca-9232-3adf7f957f7fn%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/07D0E588-6DA4-4147-A07A-003631E7E7A2%40gmail.com.

Re: [hugin-ptx] Hugin and Nvidia LHR

[Gunter Königsmann]

They obviously cannot publish what triggers their "someone is mining crypto" 
detection so I cannot tell. But I guess hugin does stuff that is 
graphics-centered and should be detected as graphics stuff that can be run at 
full power.

Am 5. Juli 2022 09:30:06 MESZ schrieb Mihai Dobrescu :
>Hello,
>
>I've noticed Hugin detecting my video card and using it to process.
>Is this impacted by LHR?
>
>Best regards,
>Mihai Sorin Dobrescu
>
>-- 
>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/CALJK-Qjg2iLCcuk5T5SKC_GzdnbutAy5mJCJurj3XLauaMe%3DEA%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/96272E80-2AB1-4AD8-AF19-CF16A0125958%40gmail.com.

Re: [hugin-ptx] PyImageFuser 0.5.0 released

[Gunter Königsmann]

I believe that error message to mean that the app wasn't signed with one of 
that keys apple sells for $100 per year. I believe in the app's right-click 
menu you can tell your computer you still want to execute it even if no-one 
payed apple for telling "that guy has a lot of money. He cannot possibly do any 
wrong to a computer"

-- 
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/B82A8232-F910-4CB9-B5E4-B1087CE155DB%40gmail.com.

Re: [hugin-ptx] hugin++, creating package

[Gunter Königsmann]

Afaik the file should not be part of the package, neither.

-- 
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/5DE028ED-A5C6-4979-B0DD-DDE2E15B7B6E%40gmail.com.

Re: [hugin-ptx] Precise meaning of control point coordinates?

[Gunter Königsmann]

If control points would link a pixel in one image to a pixel in another they 
could have integer coordinates.
But if they link a 4.5 pixel wide and 2.5 pixel high leave of a tree to the 
same leaf in a different photo the leaf might be 300.45 pixels more to the left 
and 2.4 pixels higher in one picture than in the other.

If you drop the digits after the comma the world might get a playstation-1-look.

-- 
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/09B75E23-D6FF-4B9A-8280-E09637BED9D7%40gmail.com.

Re: [hugin-ptx] Re: Control Point Bias

[Gunter Königsmann]

Two possible reasons I can think of: If you place 100 control points very near 
to each other they will count more than a few control points at the edges 
caused by their sheer number.

...and if the lens distortion isn't modeled accurately for your lens there is a 
high probability that the middle of the lens can be matched better than the 
edges of the viewport.

-- 
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/50E08DE0-8413-4181-B03F-5AEB58E3C75C%40gmail.com.

Re: [hugin-ptx] Determining lens distortion parameters from multiple panoramas

[Gunter Königsmann]

My first smartphone (a htc wildfire) had a slightly different scale at the top 
left edge of the image than on the bottom right one. ...and lens parameters 
determined with landscape photos didn't work with ones that were made in the 
other orientation.
Perhaps this discussion has now explained a reason why that might have been

-- 
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/C86502B4-2F56-4A25-AA4E-FE1E1983D161%40gmail.com.

Re: [hugin-ptx] Stop enblend from removing result

[Gunter Königsmann]

You can remove exzessive overlap by adding a mask that removes part of an image.
But I wonder if too much overlap should be a warning, not a "error out and 
delete all the evidence" 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/019E1259-E459-4E27-8427-C91A516130C7%40gmail.com.

Re: [hugin-ptx] where make install puts things

[Gunter Königsmann]

That should be the right way to do it. Except that editing Cmakelists.txt can 
be avoided if during configuration cmake is called with the 
-DCMAKE_INSTALL_PREFIX=path switch...

-- 
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/C104F747-AA01-48BE-A504-A7C61631B156%40gmail.com.

Re: [hugin-ptx] Re: Common base class for CPImageCtrl and MaskImageCtrl

[Gunter Königsmann]

If two classes have nothing in common from the implementation side deriving 
them from the same base class still might have a big advantage: You can make a 
pointer to an object of that base class and access all the common members 
without casting them and without writing code that is specific for dealing with 
one of these classes. Sometimes that allows to de-duplicate much of the code 
that uses the two classes...

-- 
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/F18C4563-2E1B-4627-B04C-3EB31359A71E%40gmail.com.

Re: [hugin-ptx] Memory saving and performance issues in control point editor

[Gunter Königsmann]

Scrolling tends to be a place where wxWidgets might issue a excess number of 
redraw steps. 
In all other cases if the intervals at which onDraw is called are strange I 
would wonder where Hugin triggers that.

The wxWidgets application I maintain (wxMaxima) draws the whole worksheet as a 
bitmap and displays it and I cannot complain about wxWidgets's speed even if my 
computer is only slightly better than an Intel Atom. But as I said I trigger 
redraws only from the OnIdle() function and only work on the part of the Big 
Bitmap I currently need...

-- 
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/D11721F1-71B8-4EB9-9AA6-4A40AB1F744F%40gmail.com.

Re: [hugin-ptx] Memory saving and performance issues in control point editor

[Gunter Königsmann]

The same "speedup" method is used by the real time Linux kernel: The 
default kernel acts on every interrupt as fast as possible and by doing 
that saves every CPU cycle it can. But on slow computers that feels 
sluggish.
The real time kernel patch makes every interrupt set a flag that tells the 
system that if it has time it has some work to do here. If it has time it 
looks at the flags and priotizes the work. Both wastes additional CPU time. 
But the "choosing the right priority" part means there the system reacts 
instantaneously when you want it ti. Even if it makes your all- 
night-rendering-job run 20 minutes longer.
Gunter Königsmann schrieb am Donnerstag, 17. Februar 2022 um 19:23:54 UTC+1:

> I don't know if that is the case here. But if the GUI feels sluggish one 
> typical reason is that you try to update the display for every single mouse 
> event you get sent (which means that if you draw slightly slower than your 
> 19200dpi-7ms-latency-mouse sends data you start to fall behind with work 
> and soon start lagging by a noticable amount). The way to counteract it is 
> to update the display only when you get sent an "idle" event: this means 
> that while and directly after the mouse moves you'll redraw the display as 
> soon as the GUI thread manages to keep up with the work, but only if 
> something has happened since the last redraw (which might be a timer or a 
> mouse event or a key press). This might mean that you don't redraw after 
> every single mouse event. But your monitor refresh rate might be slower 
> than your mouse, anyway... ...and even if it isn't: Updating the zoom 
> window only 40 times a second instead of at every screen refresh isn't bad. 
> But lagging behind the user actions is.
>
> Kind regards,
>
> Gunter. 
>

-- 
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/d6932b7c-48ac-47c5-8f25-14a4409fe8d7n%40googlegroups.com.

Re: [hugin-ptx] Memory saving and performance issues in control point editor

[Gunter Königsmann]

I don't know if that is the case here. But if the GUI feels sluggish one 
typical reason is that you try to update the display for every single mouse 
event you get sent (which means that if you draw slightly slower than your 
19200dpi-7ms-latency-mouse sends data you start to fall behind with work and 
soon start lagging by a noticable amount). The way to counteract it is to 
update the display only when you get sent an "idle" event: this means that 
while and directly after the mouse moves you'll redraw the display as soon as 
the GUI thread manages to keep up with the work, but only if something has 
happened since the last redraw (which might be a timer or a mouse event or a 
key press). This might mean that you don't redraw after every single mouse 
event. But your monitor refresh rate might be slower than your mouse, anyway... 
...and even if it isn't: Updating the zoom window only 40 times a second 
instead of at every screen refresh isn't bad. But lagging behind the user 
actions is.

Kind regards,

   Gunter. 

-- 
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/563CBE31-1388-49AE-A87C-445765B67796%40gmail.com.

Re: [hugin-ptx] HEADS UP: Don't use gmail! (was: Control Point dialog features)

[Gunter Königsmann]

It is an endless battle: The ones that write spam try to evade the spam 
filters. The ones that write spam filters adapt their filters for that which 
causes the ones that write spam to adapt their spam to the filters...
...And there are many things that look like spam and aren't: Mailing lists, for 
example, send the same mail to many users. These mails might be sent from the 
same server as real spam (a spam Sender might want this to happen). They might 
send mails to mail accounts that no longer exist (which is another red flag for 
spam) and they might occasionally mention things like blue, pills and money. 

In the end the best a mail provider can do is to try to find a spot in which 
the spam filter Filters out about as many legit mails as it lets through spam 
ones. Or to not Filter anything out that might be even remotely legit.

-- 
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/DF09CF82-4BA6-457B-829A-65DE3D2731BC%40gmail.com.

Re: [hugin-ptx] CP Editor tab 400% and 800% zoom choices

[Gunter Königsmann]

Could wxImage::GetSubImage and then scaling the resulting portion of the 
original image in CpImgCtl::OnDraw do the trick?

Am 5. Februar 2022 13:04:25 MEZ schrieb "johnfi...@gmail.com" 
:
>On the branch with my previous CP Editor change, I pushed code to provide 
>400% and 800% zoom choices.
>
>*slow and ugly:*
>Currently, 400% and 800% are slow and ugly.  I have plans for changing both 
>those things.
>
>But I have been using them this way for a while, and for my use having 
>those choices has been much better than not having them.
>
>For my own current use, I later switched from wxIMAGE_QUALITY_NORMAL to 
>wxIMAGE_QUALITY_BILINEAR, which makes it even slower and no longer ugly.  
>That change did not seem appropriate to include in this commit. 
>
>*scale and rotate on demand:*
>Currently, the entire image gets scaled.  If the image is portrait mode, it 
>gets rotated.  Then since my display on Fedora is also portrait mode, the 
>lower level code needs to rotate it back.
>
>The scaling code in wxImage is not terrible efficient for what it does and 
>is not multi-threaded (which would help a lot for big images).
>It does not take performance advantages from scale factors being easy 
>rational numbers (N/2**M for tiny N and M).  It shouldn't take such 
>advantage (doesn't apply to enough of its uses) but conceivably hugin 
>should, since our scale comes from a small list of choices.
>I don't actually think any of this is the right answer to scaling being 
>slow, but felt the possibilities worth mentioning.
>
>Getting rid of the hugin rotation of an image intended mostly for handing 
>off to a wxDC seems to be practical, so the rotation might not actually be 
>needed and if needed will be done by faster code.  I need to learn a bit 
>more about wxDC to nail down the details.
>
>Usefully delaying the scaling until CPImageCtrl::OnDraw and then not 
>scaling large undisplayed areas, is certainly practical.  But the tools 
>inside wxImage aren't properly exposed to enable that.  So it would involve 
>some reinventing of existing wheels, so I'd rather look for alternatives 
>first.  But ultimately it isn't very much code and could be done better 
>than wxImage did it.
>
>On a related subject, wxImage uses *unsigned long *for things where *uint64_t 
>*would be the more obvious choice (a much better choice than  *unsigned 
>long* on Windows and an equal choice on Linux).  wxImage runs on platforms 
>where  *uint64_t* would be a very bad choice (for an efficient data type), 
>but I expect hugin never will.  Does anyone reading this know of a platform 
>hugin gets built for on which *uint64_t* is not a good data type?  At the 
>moment, it seems to be used only in hugin/src/foreign/flann
>
>-- 
>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/39f8664e-2f4f-48b8-af06-ae2e7ae84a9an%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/9D307265-C7D0-44ED-AC5D-08CC768A4012%40gmail.com.

Re: [hugin-ptx] Removing magnifier hiding timer etc. from CPImageCtrl.cpp

[Gunter Königsmann]

That might be a point: If you want to hit exactly the right pixel on a retina 
display you'll have to resort to a powerful magnifier. If you find the right 
part of a scene on my 1280x800 screen a 8xmagnifier might instead be a way to 
get completely lost while a 1x magnifier will introduce helpful contrast.

-- 
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/E9220ECC-06B6-4396-893F-260A7F588CC6%40gmail.com.

Re: [hugin-ptx] Control Point dialog features

[Gunter Königsmann]

Do we really have to magnify all of the image if afterwards only a small 
portion of the magnified image fits on the screen? For me that feels like an 
use of something similar to wxScrolled: wxScrolled tells you what part of the 
image to render, you render that part and the rest happens by some magic the 
operating system offers.

Unfortunately wxScroleld itself chokes on too big virtual areas to scroll in as 
GTK3 does do so when volunteering the magic that on scrolling moves all parts 
of the displayed area that can be re-used after scrolling, then requests the 
areas that aren't cached, currently (only the pixels that are visible on the 
screen are cached). Afterwards that magic copies the resulting bitmap to the 
screen; if the wxScrolled is only updated when wxWidgets issues an idle event 
that feels both speedy and allows real work to be done in the background.

Am 23. Januar 2022 13:51:05 MEZ schrieb "johnfi...@gmail.com" 
:
>I had misunderstood some memory use info, to conclude the images there were 
>using 16 bytes per pixel.  Actually it is only 3 bytes.
>The actual measure of the limit past which it fails is 2**27 pixels in the 
>magnified image.  I was incorrect thinking that was 2GB.
>So it makes even less sense than when I first looked for it.  I can't see 
>anything either in hugin or in wxImage that should be bothered by having 
>over 2**27 pixels.  But as soon as the magnified image is larger than that, 
>it doesn't get displayed at all (wxImage correctly creates the large image 
>in memory, but it doesn't display).
>
>-- 
>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/4c71e3c2-4ea4-4d6b-8b8e-e6d61bc159a9n%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/BADF64A5-A45A-41D0-8EA6-08BA08A79F70%40gmail.com.

Re: [hugin-ptx] Control Point dialog features

[Gunter Königsmann]

On MS Windows cmake only detects wxWidgets if wxWidgets *wasn't* built using 
cmake. The rest should work fine there, too, minus Windows having no standard 
paths to store all the libraries in and therefore needing to be told where to 
find them all.

Am 22. Januar 2022 10:51:23 MEZ schrieb Bruno Postle :
>On Sat, 22 Jan 2022 at 01:17, johnfine wrote:
>> On Friday, January 21, 2022 at 7:20:51 PM UTC-5 bruno...@gmail.com wrote:
>>
>> Without a clear statement of the original intent, there is no way I would 
>> try to fix the code for removing the magnifier to behave as intended and 
>> predictably.
>
>I'm not sure anyone can remember what the original intent of the
>magnifier was, all I know is that it disappears just when I want it.
>
>> I didn't take notes as I kludged past issues.  I'd rather be in Fedora than 
>> in Ubuntu for this anyway.  So I think my best path on that is to do it over 
>> from scratch on Fedora and capture details each time I need to kludge 
>> something.  Then I'll put all that in a new thread here.
>
>Hugin builds out of the box on all versions of fedora. First fetch the
>build dependencies:
>
>sudo dnf install gcc-c++ libpano13-devel zlib-devel libtiff-devel
>libjpeg-devel libpng-devel gettext-devel wxGTK3-devel boost-devel
>freeglut-devel cmake desktop-file-utils OpenEXR-devel exiv2-devel
>glew-devel python3-devel swig flann-devel perl-Image-ExifTool
>mesa-libGLU-devel libXmu-devel sqlite-devel vigra-devel perl-podlators
>fftw-devel lcms2-devel
>
>..then in the Hugin source:
>
>mkdir BUILD
>cd BUILD
>cmake ..
>make
>sudo make install
>
>This will install it into /usr/local, so (on fedora) you will need to
>set LD_LIBRARY_PATH before you run Hugin:
>
>   LD_LIBRARY_PATH=/usr/local/lib64 hugin
>
>-- 
>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/CAJV99ZgPLzW95a6%2BkMJRUudFyWdvtN2VCJnnYWoLvHJ02qFnvg%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/A61D786B-71B5-4CE0-8EEC-C6F7B64EA95C%40gmail.com.

Re: [hugin-ptx] Control Point dialog features

[Gunter Königsmann]

I'm just an user. But I seem to have the same problems with Control Points as 
you.

Am 21. Januar 2022 19:34:06 MEZ schrieb "johnfi...@gmail.com" 
:
>I want to make a bunch of changes to the control point dialog.
>Maybe this is just for my own use.  But if those in control of the project 
>think any of these are good ideas, I'd be happy to go to the extra effort 
>to do these changes in a way that can go into the official version (I'll 
>need a bit of guidance on that).
>
>For any of these, I'm asking first for what I misunderstood about the 
>existing UI that makes the change unnecessary (how could I otherwise have 
>avoided the problems I want to fix), and second for suggestions on 
>how/where to make the change, and third for suggestions of a different 
>feature I might add that would solve the same problem in a way other users 
>would prefer:
>
>1) Max resolution.  200% really isn't enough for me to place control points 
>easily.  I don't know what puts me or my photos or my large high res 
>displays outside the usual range, but adding 400% and 800% choices is a 
>trivial code change that will make the program easier for me to use.
>2) Losing the magnifier.  It always goes away at 200%, even though it 
>magnifies enough to be helpful at 200% and can be made to usefully magnify 
>even more.  I found/understand the code that removes it for 200%.  It also 
>sometimes gets a timer and goes away by timer.  I found but don't 
>understand that code.  I don't understand the intent of it going away by 
>timer, nor the actual behavior (as a user, I can't predict which actions do 
>or don't make the magnifier go away on a timer).  I'm slow.  I never want a 
>timer taking the magnifier away.  I do want to be able to actively get rid 
>of the magnifier, see item 3.
>3) More keyboard control.  I don't have the dexterity to do as much with 
>the mouse in that dialog as I assume others do.  I have a lot of accidents, 
>such as create a point when I intended to move one, then try to delete the 
>new one, randomly deleting a distant one instead, then they renumber (see 
>item 5) and I'm totally lost.  Using the keyboard to move a point, I can 
>never predict nor control which of the two will move (see item 4).  I want 
>keys to control which side is selected.  Code exists that given a user 
>provided position for one side of a control point will try to find the 
>other side.  I don't yet know where that code is, but I want to define a 
>key to activate it (user places or moves a point then presses the key to 
>switch sides, then the key to auto place the corresponding point).
>4) Visible indicator of which side is selected.  No clue what it should 
>look like nor how to code it.  Suggestions appreciated, but I'll figure it 
>out myself if necessary.
>5) Global stable numbering of points (as an option if this gets shared with 
>others).  I'm sick of losing track as points renumber.  I want a gap left 
>when I delete a point, that may be reused for a new point but won't be 
>reassigned to a different point.  I want the ability to place a control 
>point on more than two images in multi-way overlap.  So I should be able to 
>switch the active list of points for a pair of images from their 
>intersection to their union (and have some visible indicator of left vs. 
>right vs. both) then select a point that is in just one of the two sides 
>and right click selection and/or key to have the software guess where it 
>goes in the other side.  (I have enhancement ideas elsewhere that depend on 
>points identified this way, but even without those enhancements, this would 
>be a convenience feature for me).  Advanced version of this would have the 
>option to use the most recent optimize results to exclude point that are 
>outside the geometry of the other side.
>
>I don't yet have a correct build of hugin either on Windows (mingw64)  or 
>on Linux.  I struggled with both and never got cmake to believe the given 
>location of dependencies either for hugin itself or for dependencies of 
>dependencies when building those.  I got past that in Linux with modest 
>kludging and in Windows with massive kludging.  I'll start a different 
>thread on any of that if help is available.  Current state on both 
>systems:  Most of hugin works including the whole control point dialog and 
>the ability to save the project.  But no way to make it stitch.  On both 
>systems I also have a binary install of hugin in a different place that can 
>stitch (from the project saved from the version I built).  So I can 
>test/use control point changes without correcting build issues.  But I'd 
>like to fix the build issues.
>
>
>-- 
>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] calculation if images overlap

[Gunter Königsmann]

Can there be a need to rotate them in order to make them overlap? If no you 
might want to look into fast convolution algorithms.

Am 20. Januar 2022 15:37:49 MEZ schrieb chaosjug :
>Hi,
>
>does someone have the formulas or a code example how to calculate if images
>overlap? So starting with y,p,r,hfov and aspect ratio.  I only need an
>estimate, so I hope I can neglect the lens type.
>
>Regards
>Stephan
>
>
>-- 
>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/4434312.LvFx2qVVIh%40chaos-home.

-- 
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/093E6A2D-712C-4F42-9F26-1EF729A54B9C%40gmail.com.

Re: [hugin-ptx] Re: libpano13 PTtiff2psd testsuite error on multiple archs

[Gunter Königsmann]

https://cmake.org/cmake/help/v3.5/module/TestBigEndian.html

-- 
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/1F05354D-FD18-4400-AE3E-8BCCE0CA3DEE%40gmail.com.

Re: [hugin-ptx] How to level a sea horizon?

[Gunter Königsmann]

Adding horizontal lines to at least a few images should do most of the trick 
(just add a control point pair with both control points at the sea level in the 
same image). Hugin now knows what is horizontal.

...and then you need to choose a projection that makes horizontal lines end up 
horizontal. Cylindrical should be fine. Alternatively in the panorama viewer 
you can drag the image to the point that makes this specifoc horizontal line to 
be projected as a straight line.

Kind regards,

Gunter.



Am 16. August 2021 01:35:17 MESZ schrieb "David W. Jones" 
:
>I have a sea horizon I shot from shore, handheld. No matter what I do, 
>the horizons on different images tilt different ways. I've tried using 
>the Assistant (it fails to find control points on one of the images, but 
>when I add control points, there's no improvement). I've tried using 
>horizontal lines on the horizons for each image, things still end up all 
>over the place. Using the Straighten button makes part of it a curve, 
>then it turns into tilted horizons again.
>
>I've tried adding vertical lines on each image at right angles to the 
>sea surface. That just started throwing images around in weird vertical 
>places.
>
>It's situations like this that really makes me wish Hugin had a "Find 
>horizontal lines" function...
>
>Using Hugin 2020.0.0.2f576e5d5b4a on Debian Linux.
>
>Ideas?
>
>-- 
>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/c682baa2-8d26-de7b-b419-028b9b8c0794%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/FCFE0E87-DDA9-4C60-B01D-59E00C31A5D0%40gmail.com.

Re: [hugin-ptx] Hugin++ : fast geometrical optimization and other features

[Gunter Königsmann]

On Ms windows there normally is no good way of telling where libraries are 
installed.

Am 14. August 2021 18:41:13 MESZ schrieb "Florian Königstein" 
:
>I have build Hugin and Hugin++ on Windows also with vcpkg. There I have the 
>vcpkg directory in the root-directory
>of Hugin++.
>I use the CMake Gui instead of the command line version. As far as I 
>remember WxWidgets was also not found although it
>was installed via vcpkg. I entered the paths to WxWidgets manually in CMake 
>Gui, and so it worked. It was necessary
>to enter the paths of other libraries manually, too. Maybe I made something 
>"sub-optimal" so that the libraries could
>not be found automatically.
>
>Florian
>
>kornel schrieb am Samstag, 14. August 2021 um 18:10:01 UTC+2:
>
>> Am Sat, 14 Aug 2021 15:24:29 +
>> schrieb "'ChameleonScales' via hugin and other free panoramic software"
>> :
>>
>> > line 112 in ./CMakeLists.txt (the one at the root), freshly downloaded 
>> from
>> > https://sourceforge.net/projects/huginplusplus/ :
>> > 
>> > > include( vcpkg/scripts/buildsystems/vcpkg.cmake ) 
>> > 
>> > We're talking about vcpkg, right?
>> > 
>>
>> Probably my fail. I am using hugin, not huginplusplus.
>>
>> 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/49690851-ccb7-430e-85de-6e5d24486017n%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/01B750ED-8A76-494F-88F4-DF16B52D2473%40gmail.com.

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

[Gunter Königsmann]

That means a library is missing. What kind of Linux system do you use?

Am 8. August 2021 02:01:58 MESZ schrieb 'ChameleonScales' via hugin and other 
free panoramic software :
>Hi everyone,
>I'd like to give multiblend 2.0 rc3 a try but the given build command for 
>Linux gives this error :
>multiblend.cpp:31:10: fatal error: tiffio.h: No such file or directory
>and indeed there is no such file.
>What now ?
>
>-- 
>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/OajTX3jnuUKqTxcYXbJC-AH0gW8AUue3Tamyc9QZPZeQhgiWd_ZvShh4h67t6qBs_lXcYoCNAavpry3h038F8sd1S55aSLgw9BhF7aRuLTs%3D%40protonmail.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/A73C61C0-B086-422A-8ED4-84774B47079B%40gmail.com.

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

[Gunter Königsmann]

AFAIK if you pass the parameter @filename to a program on ms windows the 
contents of the file "filename" is used as command-line parameters. Thw last 
time I tried if the parameters are read from a file the maximum length was 
higher than the 256 bytes the limit was at back then.

Am 1. Juli 2021 07:04:12 MESZ schrieb "Florian Königstein" 
:
>I tried to stitch a panorama with 1350 images with multiblend. It didn't 
>work in Windows because the command line where all the image filenames are 
>listed was longer than 32768 characters. At least in Windows the limit is 
>32768 (or maybe one less).
>
>I suggest adding the possibility to read the command line arguments from a 
>file.
>I changed multiblend.cpp so that you can add a command line option  
>--argfile filename  or  --argfile=filename . After this no further 
>arguments may follow in the command line, but each line in the file 
>"filename" counts as another argument, e.g. call
>multiblend.exe" --argfile=test.txt
>with test.txt containing e.g.
>--compression=LZW
>-o
>test110.tif
>--
>test110.tif
>test111.tif
>...
>
>In the attachment I have the modified version of multiblend.cpp.
>
>Maybe Hugin and HuginExecutor could be changed so that the arguments are 
>written in a file if they are many.
>
>Florian
>
>klaus...@gmail.com schrieb am Sonntag, 13. Juni 2021 um 11:55:00 UTC+2:
>
>> Hello,
>>
>> as there is actual coding of new software going on, maybe one can iron out 
>> a deficiency in the Hugin lens model. At least lay the groundwork for it.
>>
>> The Brown-Conrady model parameters are sound, but the intersection with 
>> the abc-Hugin parameter set contains only one (1) non-trivial distortion 
>> parameter.
>>
>> I suggest to add further Brown-Conrady parameters to the software code you 
>> are currently writing. Now.
>>
>> Best regards
>>
>> Klaus
>> On 11.06.21 18:20, Florian Königstein wrote:
>>
>> Monkey, I much appreciate your software.
>> I like it because I like big panoramas ... and the speedup is welcome.
>>
>> For big panoramas there's another issue: Geometrical optimization is slow.
>> I developed a fork for the libpano library that I called fastPTOptimizer.
>> For large panoramas the speedup factor for optimization can be 100 or more.
>>
>> I integrated both your multiblend and my fastPTOptimizer into a 
>> "development version" of Hugin.
>> Multiblend is now the default enblend-like program (in the GUI is still 
>> written "enblend"
>> but you can see that multiblend is used by choosing Preferences / 
>> Programs).
>> Only the CMakeLists.txt files are not updated so that Multiblend is 
>> automatically integrated
>> because I'm not yet so familiar with creating files for CMake.
>>
>> My version of Hugin is here:
>> https://sourceforge.net/projects/huginplusplus/files/development/
>>
>>
>> Monkey schrieb am Samstag, 10. April 2021 um 22:00:35 UTC+2:
>>
>>> Has anyone out there tried either the x64 or x86 versions of Multiblend 
>>> 2.0 on Windows XP or Windows Vista? Someone's reporting vcredist problems 
>>> and I'm not sure if it's because I built using the latest platform toolset.
>>>
>>>
>>> On Sunday, 4 April 2021 at 17:11:16 UTC+1 lownsl...@gmail.com wrote:
>>>
 I'll give it a shot. last time I used it it for a aerial 360 it removed 
 cars and other ground objects.

 On Friday, March 5, 2021 at 3:57:30 PM UTC-8 Monkey wrote:

> *(* for a Gigapixel mosaic, anyway; it's complicated, see below)*
>
> http://horman.net/multiblend/
>
> It seems Groups won't let me post the quasi-essay I had written, 
> complete with images, so the link above will have to suffice.
>
> Here's Multiblend 2.0, faster, better, more... blendy. I'm calling it a 
> Release Candidate because there's only so much testing I can stand to do, 
> and I've hit a dead-end with features, so I thought I'd put it out there 
> for people to try. I expect some bugs to be found pretty quickly, which 
> I'll hopefully fix pretty quickly.
>
> It's released under GPLv3.
>
 -- 
>>
>> 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/2699006b-895d-42f4-bd19-6ed0d3f3863bn%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 

Re: [hugin-ptx] Is there any way to keep pixels unchangeable with Hugin?

[Gunter Königsmann]

Are you sure that working on a gray scale representation of the thernographys 
looses information? Normally a thermocam has an 8-bit ADC, and allows to save 
pictures in 256 different gray levels or alternatively using a palette that 
provides 256 colors that are easier to distinguish visually. It also most 
certainly comes with software that losslessly converts images from one of these 
formats to the other. Ergo the correct workflow would be: Losslessly convert 
the pictures to gray scale, then stitch them and then convert them to the fancy 
colorful palette.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/D5F75D3F-73B6-4384-95F5-120AD016EA0F%40gmail.com.

Re: [hugin-ptx] Re: Hugin++ : fast geometrical optimization and other features

[Gunter Königsmann]

If weighing control points by cpfind's confidence that this is a valid control 
point makes sense? If there are repeating structures like window fronts   
sometimes control points look excellent even at the second glance, though...
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/FECFD97A-86ED-45E2-AFF4-33070751CD86%40gmail.com.

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

[Gunter Königsmann]

Why dangerous?

Kind regards,

   Gunter.

Am 5. Juni 2021 11:43:15 MESZ schrieb Kornel Benko :
>Am Sat, 5 Jun 2021 10:36:55 +0200
>schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
>:
>...
>> @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?
>
>Too dangerous, even if that were possible.
>But I can provide a debian package (based on ubuntu 19) if needed.
> $ dpkg -s lux
>Package: lux
>Status: install ok installed
>Priority: optional
>Section: universe/graphics
>Installed-Size: 12741
>Maintainer: Kay F. Jahnke 
>Architecture: amd64
>Version: 1.0.9-0git
>Depends: libc6 (>= 2.15), libgcc1 (>= 1:3.0), libsfml-graphics2.4, 
>libsfml-system2.4 (>=
>2.4.2+dfsg-4~), libsfml-window2.4 (>= 2.4.1~), libstdc++6 (>= 6)
>Description: lux - a free open source image and panorama viewer
> .
> lux can show -normal- images, panoramas in various formats
> and PTO files made with software like hugin. It can also do
> simple stitching and blending jobs. You can find documentation
> at the bitbucket site: https://bitbucket.org/kfj/pv
>
>
> $ ldd `which lux` | egrep 'libexiv|libgcc|libstdc|libvigra'
>   libvigraimpex.so.11 => /usr/local/lib/libvigraimpex.so.11 
> (0x7ff05ae5d000)
>   libexiv2.so.27 => /usr/lib/libexiv2.so.27 (0x7ff05a21)
>   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
> (0x7ff059c68000)
>   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
> (0x7ff0596b2000)
>
>I suppose that libvigraimpex.so.11 may make problems though.
>
>   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/20210605114315.061ff6ba%40admin1-desktop.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/31998D25-BBAD-408A-ACF3-18D647E5832E%40gmail.com.

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

[Gunter Königsmann]

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//
>>
>> 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
>> 
>> .
>>
>
>-- 
>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/CAGu%2BGga7aZam_UA2TyJt%2BEwdZ%2BJTEgtBmCfFK12Xzxh7tFtuRg%40mail.gmail.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/7ADB701F-C8B2-413A-A7D8-FA63CC1A8C10%40gmail.com.

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

[Gunter Königsmann]

Well... ...that's the problem, and has always been: The commercial systems rule 
the world, because your computer comes prepackaged with them. But they lack 
apt-get and there is no good way of replacing it. Some programs come with their 
private copies of the sources of all libraries, just in case the system doesn't 
offer them. But that tends to create even more problems.

Am 24. April 2021 08:47:47 MESZ schrieb "'Kay F. Jahnke' via hugin and other 
free panoramic software" :
>Am 23.04.21 um 16:29 schrieb 'Kay F. Jahnke' via hugin and other free 
>panoramic software:
>
> >> @Kornel: Can't we include find_package statements ...
> >> to make cmake find the required libraries automatically?
>
>Now the penny drops. It's not that find_package actually *fetches* the 
>libraries, it only figures out where they have been put on the system. 
>As a debian user, where getting a bunch of libraries is as simple as 
>apt-get ..., I had asumed that CMake would do that for me. So what I had 
>in mind was something like FetchContent, but that doesn't seem to be 
>good for loading libraries. Any ideas?
>
>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/8bc013c1-526a-e0c3-079a-d0f0371b9322%40yahoo.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/53C8DDA9-310B-48D6-A223-CFB86AAC13FE%40gmail.com.

Re: [hugin-ptx] skip "align" button in assistant?

[Gunter Königsmann]

A good strategy might be first adding a few (4 per image pair) control points 
that tell hugin which window is which, then aligning preliminarily and telling 
hugin only then to add its 20 additional control points. One or two of then 
will be in the wrong place, again. But there is the "clean up control points" 
option for that.

Kind regards,

Gunter.


Am 5. April 2021 16:47:48 MESZ schrieb "Luís Henrique Camargo Quiroz" 
:
>Hi Csaba!
>
>   Just an idea:  maybe you are using the "simple" interface, and this
>creates or tries to create new CP pairs before new alignment of (new)
>images? I am not sure, because I don't use this interface; I think it is
>intended for beginners and aiming to create a panorama "at once" from a
>given set of photos. And of course in your case you are feeding and growing
>an initial set of photos  (your # 3) , and starting a recipe meant to be
>run just once when you press align (#1) and this starts with "create CPs".
>
>I advise you to try at least the advanced interface.  In this case you
>will "align" only when you *optimize* the panorama parameters, and this
>process does *not* create new CPs. You will have to create the CPs
>beforehand, and you can improve or create yourself new CPs when desidered
>-- and they will take effect after a subsequent optimization.  A rule of
>thumb is optimization of 'positions only', and when the result seemed OK
>(or almost), then you could include 'positions and visualization', etc.
>For a correct 'visualization' optimization the panorama must be a complete
>turn around, and this is the case with your cylindricals.
>
>   As for the stacks, I think some photos could have an excessive
>superposition and/or the same kind of image content and this could fool
>Hugin.
>
>  Try please the advanced interface and tell us your progress.  Goof luck!
>
>  regards,
>
>  Luis Henrique
>
>Em seg., 5 de abr. de 2021 às 06:04, Csaba Tóth 
>escreveu:
>
>> Hello!
>> My problems are:
>> I have a large (100+) photo set for cylindrical projection. (for the whole
>> rendering take 12+ hour)
>>
>>1. If I use the align button, it will always create new contol points.
>>An because the image contains many block house always create point between
>>wrong pairs. If I fix this, I cant preview it, because it say "need to
>>align again". If I do, it will mess up again (and I need to check every
>>100+ image to searching the wrong pairs, It will be better to display a
>>matrix, every cell how many cp for that pair)
>>2. there are "stacks" in the result: many images in the same place,
>>same orientation, and I dont know why, and how handle it.
>>3. If I start with few images and add more, (and "align" it to see the
>>result) I get error: there are two not linked group [0],[1-9] If i fix it,
>>add new one, get more not linked groups: [0],[1],[2-10], and begin mess up
>>(start rotate the first image)
>>
>> How can I "align" the images to see the result without the "align" button,
>> or without the messing up?
>>
>> what I want to do:
>>
>>1. load every image, "align" it to see where need to fix.
>>2. fix an error (add/remove cp-s, try to rotate, add horizontal lines
>>etc)
>>3. preview the result, if there is error: -> 2
>>4. straigthen
>>5. define the crop
>>6. create the panorama
>>
>> Thanx
>> Csaba[image: stacks.png]
>> (there is two stacks each with 10+ image, the same place, same orientation)
>>
>> --
>> 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/c4cb55f9-c593-4582-b39b-134f10fb3f7an%40googlegroups.com
>> 
>> .
>>
>
>
>-- 
>-- 
>Luis Henrique Camargo Quiroz
>http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
>http://panoramaslh.net/
>
>-- 
>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/CAEKSoZbq6nRq8L1K7-m0W%3DYBEk9UaVhhTjtGM1OqDfm%2BXZ49pA%40mail.gmail.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this 

Re: [hugin-ptx] Using Hugin to stitch microfilm scans

[Gunter Königsmann]

Basically for stitching flat items you must 

- tell hugin that every scan was made with a different lense (which allows that 
lense to start at a different position)
- make sure that you exclude eventual black bars at the end of the scanned area 
using masks
- and then tell hugin to optimize only the parameters that actually make sense.

Am 1. April 2021 15:30:32 MESZ schrieb Benjamin Kalish 
:
>I'm brand new to Hugin and am trying to use it to stitch microfilm scans
>together. I feel certain the result could be better—what can I do to get
>better output?
>
>I've attached my pto file and the output from my most recent attempt.
>
>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/CAGi3ZJxsAQ-XYqryuGKcOvZG1QiKozZR1Xa2SpsTKMB2AAQmjA%40mail.gmail.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/157AF222-39B2-4F1E-B6B6-B26289D30B7D%40gmail.com.

Re: [hugin-ptx] image comparison with hugin

[Gunter Königsmann]

Don't know how hugin finds similar images. But often this is done using fast 
folding...

Am 27. März 2021 15:11:04 MEZ schrieb "Pilar C. Ocaña" :
>Hello and thank you for getting interested in this topic. First of all, i'd 
>like to say sorry if the question is unappropriate, but i'm pretty new to 
>this software, and do not know to which extent does it work (and also i'm 
>not what you would call 'a genus of IT').
>My question is as follows: In my university there's a project in which the 
>ones involved are using hugin. From that, i got interested and i've seen 
>what Hugin is capable to do: to compare several images in order to stitch 
>them. From that, i thought that it would be great if it could be used for 
>comparing images and indicating the most similar one to it from a set of 
>pictures, i thought about a database of other pictures or something like 
>that. I investigated and the only ways i've seen which appear to do as i 
>say are algorithms programmed in python and such, but nothing using this 
>software. is possible to do something like what i've thought with Hugin, or 
>i've just mixed unrelated concepts? 
>thank you so much for your time, i hope this is not absolutely ridiculous, 
>and i hope you have a good day!
>
>-- 
>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/5886ad86-02c3-49bc-9d08-70860ef25128n%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/0BAD2D6B-CA64-4A8F-A702-47EF357A3D09%40gmail.com.

Re: [hugin-ptx] Hugin freezing during blending

[Gunter Königsmann]

Hmmm... One partially related question: Would it make sense to make multiblend 
the default for new hugin installs?

Am 20. März 2021 15:48:25 MEZ schrieb Monkey :
>Enblend is very slow. Multiblend is much, *much *quicker:
>
>http://horman.net/multiblend/
>
>You change the Hugin settings under the Programstab (Use alternative 
>Enblend program) and point it to multiblend.exe instead.
>
>On Friday, 19 March 2021 at 19:24:00 UTC MikaylaL wrote:
>
>> Hi Bruno,
>>
>> Thanks so much! 
>> Yes, it's the google earth logo. I left it because I figured the photos 
>> overlapped enough it wouldn't be a problem. 
>> I considered it may have just been taking a long time to process, but I 
>> think what would happen is that it would eventually time-out on my computer 
>> and end up failing. I will try again! Hopefully I can get it to work.
>> Thanks again!
>>
>> Best,
>> Mikayla
>>
>> On Friday, March 19, 2021 at 2:17:37 PM UTC-5 bruno...@gmail.com wrote:
>>
>>> Hi Mikayla, I can get it to stitch here, the enblend warning is just 
>>> because the output panorama is very small (4096x2048), but this is 
>>> ok. It takes a few minutes for enblend to blend everything 
>>> together, maybe it was just taking a very long time.
>>>
>>> The images are all very precisely arranged in the panorama, but the 
>>> control points make no sense - are these the correct positions for 
>>> the photos? or do they need aligning?
>>>
>>> The control points are all clustered in a small rectangle at the 
>>> bottom left of each image, is there a logo or something in every 
>>> picture? If you want to generate control points you will first need 
>>> to mask out this area using the Masks tab in the Panorama Editor.
>>>
>>> -- 
>>> Bruno
>>>
>>> On Fri 19-Mar-2021 at 09:38 -0700, MikaylaL wrote:
>>> >Sure!
>>> >Thanks for taking a look!
>>> >
>>> >It occurred to me today that there is the possibility that it's a 
>>> hardware
>>> >issue, so I will be trying it on a different computer in the next few 
>>> days.
>>>
>>> >On Friday, March 19, 2021 at 8:34:34 AM UTC-5 bruno wrote:
>>> >
>>> >> Hi Mikayla, this doesn't sound like a familiar problem, so we can't say
>>> >> for sure. Please can you post a PTO project file so we can have a look 
>>> (no
>>> >> need to post the images).
>>> >>
>>> >> On 18 March 2021 15:35:22 GMT, Mikayla wrote:
>>> >> >Hello!
>>> >> >I'm very new to Hugin, so I apologize if this is a rudimentary 
>>> question.
>>> >> I
>>> >> >am trying to stitch images taken from Google earth to create an
>>> >> >equirectangular panorama shot. When I go to stitch the images, the
>>> >> >commands freeze when it gets to:
>>> >> >"Blending images...
>>> >> >enblend: warning: input images too small for coarse mask
>>> >> >enblend: note: switching to fine mask"
>>> >> >I don't know what's happening or why It refuses to continue 
>>> processing.
>>> >> >
>>> >> >Any help would be greatly appreciated!
>>> >> >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/beb088fc-a774-4dff-bf53-10143b1332bcn%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/36DF2DD4-1D7E-4304-9F2D-BC7F2E4A133F%40gmail.com.

Re: [hugin-ptx] Project files

[Gunter Königsmann]

I personality don't own a windows PC it iwith orher programs I know similar 
behavior can be provoked by using a non-ascii username => does your username 
contain non-ascii characters?

Kind regards,

   Gunter.

Am 17. März 2021 17:55:54 MEZ schrieb Viktor Balogh 
:
> 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).
>
>Steps to reproduce:
>
>   1. A fresh installation of Hugin (I think is it optional)
>   2. Move the attached images (img1/2.tif) to 
>   C:\Users\\AppData\Local\Temp
>   3. Open Hugin
>   4. Open the images
>   5. Save project as... with filename: pano*1*
>   6. Click on align
>   7. Save project as... with filename: pano*2*
>   8. Open pano*1*.pto in any text editor and observe the filename at end 
>   of line 8: you got n"img1.tif"
>   9. Open pano*2*.pto in any text editor and observe the filename at end 
>   of line 8: you got n"\Users\\AppData\Local\Temp\img1.tif" 
>
>Some info:
>OS: Windows 10 (build 19042) 64-bit
>Hugin version: 2020.0.0.2f576e5d5b4a built by Thomas
>
>Thanks in advance!
>
>Viktor
>
>Attachments:
>Images 
>
>
>-- 
>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/612299bc-0a31-48fc-93ce-44a5ee0d9eefn%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/CF98061E-85D6-46C1-A7F7-5D9ABEC7DAF4%40gmail.com.

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

[Gunter Königsmann]

As a user the only thing I wonder about is if multiblend2 will be the new 
default instead of enblend. And we could try harder to explain the projection 
types to the users. And we could add a mosaic wizard. Besides that I cannot 
complain.

Kind regards,

   Gunter.

Am 7. März 2021 14:16:12 MEZ schrieb yuv :
>On Sun, 2021-03-07 at 09:22 +, Bruno Postle wrote:
>> currently there is a single person doing code maintenance, 
>> collecting translations, _and_ doing the releases - these could 
>> easily be different roles.
>
>This!  What made Hugin great and successful in years past was the co-
>operation and co-ordination of the different teams / authors to the
>point of trusting and sharing full access to their respective code
>repositories; being able to inter-changeably assume the different roles
>for the different packages; reaching mutual agreement on repositories
>and other tools to use to simplify interchangeability of roles; co-
>ordinate releases, bug fixes, etc.
>
>That co-ordination seems to have gone missing, and re-building it will
>require sacrifices and compromises on all ends.
>
>I have just taken a half-hour stroll down memory lane.  The main
>comment I have:  Why have no admins been added to Hugin / Panotools /
>Enblend in ages?  My memory fades, but all the names I see are people
>that were either there before me, or were added on my initiative.  Who
>has taken care of the team after I moved on because life?
>
>* have any new contributors been invited?
>* if yes, why have they not accepted the invitation?
>* if no, why?
>* how many other contributors has the ecosystem missed? not just admins
>(the highest level of access/trust).
>
>Below follow a longish (and incomplete) list of signs of what is in my
>view organizational rot.  Those signs point to extra work.  I am not
>asking the exisisting and dwindling team to take on that extra work.  I
>am saying that the organizational rot is the consequences of the
>failure to welcome and embrace new contributors.  Who wants to join a
>dwindling team who does not welcome change?
>
>adding team members requires two thrusts:
>(a) individuals inspired to become team members, to bring new energy,
>new ideas, new code, and eventually change to the projects;
>(b) an existing team that is welcoming new contributors and accepts the
>change that they bring.
>
>where are those thrusts?
>
>And now for the longish list.
>
>* why are the projects still using Mercurial?  IIRC back when the
>switch to a unified VCS was made, Mercurial won because it was the one
>with most even support amongst operating system (Windows!).  Meanwhile,
>the landscape has shifted, git is the tool.  That would require some
>flexibility from all individuals, including Kay (bitbucket? exotic! I
>would not adopt it at this time).
>
>* why are the projects still on Sourceforge?  History is past, and they
>may have corrected they blunders.  But there is no going back and today
>Gitlab is the place to be (which would also replace Launchpad, that I
>introduced ages ago).
>
>* it pains me to see F*book promoted on the Hugin's website.  Really? 
>it surely explain less traffic to this mailing list, which means less
>potential contributors coming its way.  Don't expect an
>influencing/advertising tool that has an interest to isolate users into
>echo chambers to be a positive to this community.  if I was around the
>time that decision came up for discussion, I would have vehemently
>opposed it.
>
>* the Enblend/Enfuse website is still... mine!  What is the new
>generation of contributors waiting to leave their mark?  Last news from
>five years ago?  OK, the tool has matured and no need for new releases,
>but someone with a little bit of marketing flair could point out to the
>continued flow of Hugin releases, and now to Multiblend, a very
>interesting development?
>
>* the Panorama Tools website list the last new to almost eight years
>ago!  the latest release tarball is two years ago.
>
>I could probably find a bunch more, but the point is: encourage new
>contributors to take over and replace the current generation and take
>this community to its future with as little interference as possible
>from us oldies.  Else, the community will die when we inevitably do. 
>So please, please, please, make this a more welcoming place to new
>contributions.  Kay and Harrie are no newbies, so imagine how difficult
>this is for someone who has not been around for that long.  The
>alternative is to fade into irrelevance, which is why I asked the
>thought-provoking question of whether pv is already a replacement to
>Hugin.
>
>--
>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 

Re: [hugin-ptx] Re: Build fails - missing MSGFMTConfig.cmake

[Gunter Königsmann]

If cmake fails often the only problem is too old an cmake. Which cmake version 
do you use?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/E6F46A9A-004B-4D9E-8763-A23142C6DBF7%40gmail.com.

Re: [hugin-ptx] Re: Build fails - missing MSGFMTConfig.cmake

[Gunter Königsmann]

You can pass variable values to cmake via -D switches...

Am 27. Februar 2021 14:17:26 MEZ schrieb "T. Modes" :
>
>
>Zupino schrieb am Samstag, 27. Februar 2021 um 09:35:50 UTC+1:
>
>> What I noticed is that I do not have CMAKE_MODULE_PATH set, so I set it 
>> with export CMAKE_MODULE_PATH='/home/' and 
>> run again cmake, but still same error.
>
>CMAKE_MODULE_PATH is a variable inside the CMake build system, not an 
>environment variable. It is (probably) correctly set, otherwise CMake 
>should have complained earlier about other missing search module (e.g. 
>libpano)
>  
>
>> I also noticed that FindMSGFMT.cmake contains a check on the 
>> MSGFMT_EXECUTABLE var, which was also not set. I set to the value 
>> returned by `/usr/bin/msgfmt`, which is installed in my system.
>>
>Here the same. These are internal CMake variables which are picked up when 
>running. The problem the log mentions is that CMake does not found the file 
>- it does not even started to look after it. So you don't need to set an 
>environment variable with that name.
>
>Is CMake having any sort of cache I should clean before running it again 
>> with the environment variable set?
>>
>The cache is stored in the build directory. Simply clean up the build 
>directory and retry. But I fear it won't change much - because the 
>mentioned enviroment variables are not used by CMake.
>
>-- 
>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/2ca1d05a-e792-4ab2-abaf-03989f660e6an%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/FBDA5463-10FA-47D3-96BC-B6842F2AB659%40gmail.com.

[hugin-ptx] Re: Preview work space does not show complete picture

[Gunter Königsmann]

One big difference between Mac Is and the other platforms is that on high 
DPI screens Mac Os supports bitmaps with the size n x m and o times the 
low-dpi screen resolution.
If the preview doesn't know that this makes the bitmaps the size o*n x o*m?

Daniel Pittoors schrieb am Freitag, 19. Februar 2021 um 08:49:08 UTC+1:

> Preview space only shows fraction of loaded picture overview on Mac - did 
> not have this issue on Windows?
>

-- 
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/5e2203ae-de7c-49d0-8924-dacaf9b13587n%40googlegroups.com.

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

[Gunter Königsmann]

gimp-like memory management that allows to handle target images that are
bigger than the RAM. don't know if it is already implemented. 

The gimp splits big images into tiles that small enough so a few of them
fit into the RAM and then tries to work on these tiles one at a time. 

On 11.02.21 18:33, Monkey wrote:
> It's been several years but I'm working on a new version of Multiblend
> that's a bit faster, produces much nicer results, and will blend much
> bigger mosaics.
>
> Does anyone have any feature requests for a blender that I could
> consider incorporating?
>
> Along the same lines, does anyone use Enblend's colour space features?
> Do they produce notably more "correct" results, or just different
> ones? I've added an approximately linear RGB mode to Multiblend, but
> it doesn't seem to produce great results so I'll only be leaving it
> there as a curiosity.
> -- 
> 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/c0e1493b-014c-43b1-b897-39c1d7ac9d41n%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/9362b041-074b-0c59-7f5c-9f411600e287%40gmail.com.

Re: [hugin-ptx] Bad results with cpfind

[Gunter Königsmann]

One thing that can go with auto-detecting control points on stars  is:
Stars look all alike, from a distance. cpfind is good. But from time to
time it might happen that cpfind will interpret one tiny speck of ligkt
as a completely different one. In that case you can sometimes get
surprising results involving a warped sky.

Kind regards,

  Gunter

On 17.12.20 17:32, T. Modes wrote:
> aks schrieb am Mittwoch, 16. Dezember 2020 um 18:35:45 UTC+1:
>
> 1. “Fine-tune all Points” after running the “Create control
> points” process. This command is found in the Edit pulldown menu.
> The control point distances get normalized in a way to make it
> easier to notice the outliers. The fine-tune process also reports
> how many control points fall below the “Correlation Threshold” set
> in the Control Points Editor preference.
>
>
> Cpfind search control points at different scales and does also some
> other kind of fine-tuning (different algorithm). Using fine-tune from
> the menu is only looking at the 1:1 scale on a small patch. So if you
> manually fine-tune the cp after cpfind you are destroy some information.
> So after running cpfind there should be no need to additional run
> fine-tune from the menu. Please stay away from this or post a bug
> report if you think there is a bug in the algorithm.
>
> 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/bc761c57-46a9-4c9d-a672-cbbc5f8195a2n%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/4f9c2599-161b-ab14-52bf-67c9fc183a6c%40gmail.com.

Re: [hugin-ptx] Re: New to Huglin looking for some help.

[Gunter Königsmann]

There are several tutorials for stitching murals or scanned images. I guess 
these should be near to your use case. Basically the first step is telling 
hugin that the camera has a very small field of view and that each image was 
made using a different lense (which tells the program it might have been made 
from a different location, too).  Then you allow hugin to optimize the 
distortion to zero and the x and y positions the photos were shot from, but 
*not* the other parameters (scale of the images,...).

...but a specific mural/scanned image mode would be nice, admittedly...

Am 14. Dezember 2020 16:05:01 MEZ schrieb nor s :
>Hi Daniel,
> I've been trying to use HUGIN to stitch mosaics of the Rosette nebula 
>and ended up with  a distorted image. Part of the nebula was missing and 
>kind of squeezed together new the middle. The preview image showed that  
>some of the segments were turned slightly.   I have come to the conclusion 
>that my problem is the fact that HUGIN corrects for all kind of effects 
>such as curvature or perspective, etc which are common in terrestrial 
>imaging using different lenses. However images shot with a telescope of 
>objects in the night sky are for all practical purpose FLAT. 
>
>It sure seem like HUGIN is a very powerful program, but does it have a 
>simple flat stitch function that  will allow the stitching of images 
>without turning or skewing the segments? I see that  there are all kinds of 
>different options to use for stitching unfortunately I not familiar with 
>any of them.
>
>Your suggestion would be greatly appreciated.
>
>Thanks
> Nor  
>On Thursday, December 3, 2020 at 7:26:27 AM UTC-5 nor s wrote:
>
>> Hi Daniel,
>>Wow you sure have that  process down pat. I will have a closer look at 
>> your steps and see how they will work on my stuff.
>>
>> Cheers
>>  Nor
>>
>>
>> On 12/3/2020 6:56 AM, 'dkloi' via hugin and other free panoramic software 
>> wrote:
>>
>> Stitch looks good. You can see in the stitch tab that the FOV is now a 
>> more reasonable 4 deg x 5 deg. The optimisation process seems to have come 
>> up with a more proper value for the lens HFOV. 
>>
>> I have made available example Hugin pano projects at:
>> http://www.dkloi.co.uk/?p=1490
>> http://www.dkloi.co.uk/?p=1501
>> http://www.dkloi.co.uk/?p=1518
>> They are for complete panospheres but many of the the basic concepts are 
>> unchanged for a partial pano and may be useful for gaining familiarity with 
>> Hugin.
>>
>> On Wednesday, 2 December 2020 at 18:16:46 UTC njsg...@gmail.com wrote:
>>
>>> HI 
>>>I've been playing around with Hugin 2019.2 and finally got it to work 
>>> today. Yes the finished size is rather large since each segment is 
>>> 3020x1985 which roughly translates to 6040x7940 as the completed 2x4 
>>> mosaic.  I've attached a finished mosaic and the screen capture of the 
>>> stitcher tab that  I finally used.
>>>
>>> Not really being familiar with this program I was just poking and hoping 
>>> that  something would work. ONce I have it all figured out I'll put 
>>> together a work flow.
>>>
>>> Thanks for the reply.
>>> Cheers
>>> Nor
>>>
>>>
>>>
>>>
>>> On 12/2/2020 10:24 AM, 'dkloi' via hugin and other free panoramic 
>>> software wrote:
>>>
>>> Welcome to the group. It would help if you could provide the images. You 
>>> should be able to stitch astronomical images together. I note on the log 
>>> file: 
>>> Number of active images: 3
>>> Output exposure value: 0.0
>>> Canvas size: 6040x7940
>>> ROI: (0, 0) - (6040, 7940)
>>> FOV: 360x473
>>> Projection: Equirectangular(2)  
>>>
>>> The FOV is a bit big (473 deg vertically), this is probably causing the 
>>> problem. The FOV of you images are probably too large, this can be manually 
>>> set (by specifying the focal length and crop factor) but this may have been 
>>> optimised to the wrong values, leading to the problem.
>>>
>>> Once we can see the photos and your Hugin project file, we can tell you 
>>> more.
>>> On Wednesday, 2 December 2020 at 06:13:03 UTC njsg...@gmail.com wrote:
>>>
 Hi,
   A little about me. I've been doing astrophotography for many years and 
 occasionally want to image an object that  is larger than the field of 
 view 
 of my equipment. The obvious way of doing that  is to image the object in 
 sections and then stitch them together to form one complete image. In the 
 past I have been using  photoshop to manually match the segments and back 
 grounds. A difficult problem at times. An acquaintance put me on to Hugin 
 so I loaded up version 2012 and gave it a try on the, Pleiades. To my 
 pleasant surprise it did a very good job of combining the 2x3 image grid 
 into a single picture.

 Later When I tried to open Hugin again, it requested the lens info twice 
 and then quit. I tried it several more time even after rebooting the PC 
 but 
 still no luck. I decided to un install2012 and get the  latest from the 
 

Re: [hugin-ptx] Unsupported file format | Could not decode image

[Gunter Königsmann]

If you are using windows you might be in that weird situation that you don't 
see non-ascii characters in the path to your files: "Documents" for example is  
shorthand for "C:\users\(your username)\(the translation of " documents" into 
your system language).
Also the temp directory temporary files are stored in might be in a similar 
path - even if that pathname is never shown.

Might that be the case, this time?

Kind regards,

   Gunter.

On November 28, 2020 1:03:49 PM GMT+01:00, Anoop Bhaskar 
 wrote:
>Greetings all,
>
>I am really new with Hugin.
>
>I want to stitch 26 images to form a 360 panorama or an equirectangular 
>image, but i am not able to load the images as it is not able to decode.
>
>When googled it said that it might be because of non latin characters, but 
>all the files are in latin script. 
>
>The images are from DJI, i have edited them on lightroom and converted them 
>to jpg.
>
>Has anyone faced a similar issue?
>
>Thank you,
>Anoop
>
>-- 
>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/5804fb8b-67e3-4df3-8fdd-f88af85688c0n%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/67842618-6297-448A-8290-6A06E0EAAD16%40gmail.com.

[hugin-ptx] Re: nona causes server reboot

[Gunter Königsmann]

Or a faulty RAM: libraries can crash. But they should not be able to reboot 
the server even it they actively tried to.

Erik Krause schrieb am Donnerstag, 22. Oktober 2020 um 18:28:41 UTC+2:

> Am 21.10.2020 um 18:59 schrieb Bruno Postle:
>
> > So I would recommend filtering these files through a tool that has had
> > lots of attack exposure, like ImageMagick
>
> Tried to convert one of the questionable images to PNG on the server.
> ImageMagick caused a server reboot as well. Does this indicate it's one
> of the libraries?
>
> --
> Erik Krause
> http://www.erik-krause.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/e66bd524-358d-4e69-86e6-57e954eb3c23n%40googlegroups.com.

[hugin-ptx] Re: nona causes server reboot

[Gunter Königsmann]

Only very few things should be able to cause a reboot:

 - a kernel bug  
 - an out of memory killing sysvinit/upstart/systemd 
 - root killing sysvinit/upstart/systemd  
 - root calling the appropriate system command  
 - or an eventual watchdog.

Nona can only do the second of these things => I would guess it is the 
kernel (hopefully fixed by an update) or the watchdog. 

Erik Krause schrieb am Mittwoch, 21. Oktober 2020 um 20:11:20 UTC+2:

> Am 21.10.2020 um 18:59 schrieb Bruno Postle:
>
> > So I would recommend filtering these files through a tool that has had
> > lots of attack exposure, like ImageMagick. If you use ImageMagick to
> > convert all your incoming JPEG files to PNG and then use this
> > temporary PNG file as input to nona, this will likely solve your
> > server reboot problem, while making the software more robust overall.
>
> That's an exceptionally good idea. We have ImageMagick on the server,
> and it will of course add a bit to the processing time, but I think
> that's worth it...
>
> --
> Erik Krause
> http://www.erik-krause.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/860f6576-d7e1-4df5-8f77-5f37143d90a9n%40googlegroups.com.

Re: [hugin-ptx] Re: nona causes server reboot

[Gunter Königsmann]

To me "server reboot" and "unfinished file" both look like the server ran 
out-of-RAM, somehow which caused its kernel to kill a vital process.

bruno...@gmail.com schrieb am Dienstag, 20. Oktober 2020 um 23:53:16 UTC+2:

>
>
> On 20 October 2020 21:23:10 BST, Erik Krause  >
> >The complete output of ldd -v for both nona instances can be found on
> >https://we.tl/t-Jsw6BqEckG (4kB)
> >
> >The libraries I copied to the server (all in the same directory as nona)
> >are binary identical to the local installation.
> >
> >I'd be grateful if anyone could have a look...
>
> Maybe somebody else can see something I can't, this looks fine to me.
>
> You have copied over a lot of libraries, but you are using the libtiff and 
> libjpeg that are already on the server - this really should not be a 
> problem - as a test you could try uploading these too, then the set of 
> libraries would be basically the same on both machines.
>
> -- 
> 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/692682c4-12df-4570-9bb2-501499009e63n%40googlegroups.com.

Re: [hugin-ptx] PPA trouble?

[Gunter Königsmann]

That is simple: your lubuntu is based on a ubuntu version the ppa contains no 
build for. 
The error message is nearly impossible to understand right, though...

Kind regards,

  Gunter.

On October 8, 2020 4:47:56 PM GMT+02:00, Paul Womack  
wrote:
>I have just done an install of Lubuntu 20, and was following the
>instructions from the launchpad PPA site:
>
>https://launchpad.net/~hugin/+archive/ubuntu/hugin-builds
>
>I did this:
>
>sudo add-apt-repository ppa:hugin/hugin-builds
>
>but got the error/warning message:
>
>Reading package lists... Done
>E: The repository 'http://ppa.launchpad.net/hugin/hugin-builds/ubuntu
>focal Release' does not have a Release file.
>N: Updating from such a repository can't be done securely, and is
>therefore disabled by default.
>N: See apt-secure(8) manpage for repository creation and user
>configuration details.
>
>Can anyone advise how I persuade my system to use this PPA?
>
>  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/CAD1remb6Gi%3DacUZfwNWJtgZ9HM4X9_i0Og4ta9wauFKKfrjwJA%40mail.gmail.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/D1D72FB7-D6B3-40DB-9293-8511CF406ED8%40gmail.com.

Re: [hugin-ptx] The math is perfect ...

[Gunter Königsmann]

Math is never perfect if floating-point numbers are involved and one of the 
cool things about reality is that it always provides surprises, especially if 
you want to apply perfect math to it.

Having said that: Could you describe what you see and what isn't expected?

On October 4, 2020 4:25:03 PM GMT+02:00, Abrimaal  wrote:
>Dev1: The math is perfect, we may release it. 
>Dev2:  Was it tested by users?
>Dev1:  They are just users.
>
>Usr1: Hugin, can you help me find the matching point?
>
>All: What is wrong in this picture?
>
>[image: help me find matching point - why white background.jpg]
>
>-- 
>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/220d95f1-443a-40f6-94e1-33fb3e8ce196n%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/A5FB3511-A80C-4727-92F4-D38F482656E9%40gmail.com.

Re: [hugin-ptx] Stitching four 180 x 180 degree fish eye image

[Gunter Königsmann]

Or you might need a mask that excludes the black areas. Not that hugin tries to 
align the images in a way that makes the black areas match, instead of matching 
the image contents.

On September 11, 2020 11:55:28 PM GMT+02:00, DerekS 
 wrote:
>Can anyone shed some light on how to stitch four 180 x 180 degree fish eye 
>images into a 360 x 180 degree  equirectangular image?  
>
>The images are fine, as I've been able to stitch them on a trial version of 
>PTGui, but in Hugin 2019 the images when aligned are stacked upon each 
>other as shown below.
>
>[image: Hugin_Screen_Shot.jpg]
>
>Any idea where I'm going wrong?
>
>Thanks
>
>
>Derek
>
>Images attached have been shrunk by 50% to reduce file size.  
>
>-- 
>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/009c13de-8cdb-47c6-8dc7-a6dab83c953dn%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/1F2C1DAF-533C-41E1-95C1-06C2B0136F39%40gmail.com.

Re: [hugin-ptx] Stitching four 180 x 180 degree fish eye image

[Gunter Königsmann]

That looks a bit like you have loaded the images but not yet have searched for 
control points or like you didn't optimize the right variables, afterwards 
which causes hugin to move the images to the right places. But I am not 
entirely sure...
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/2B209A73-1CAA-4E28-942D-5D5A96769C6D%40gmail.com.

Re: [hugin-ptx] Fails on Catalina

[Gunter Königsmann]

To me the "project file not found" slightly rings a bell. There was a thread 
about a similar error quite a while ago. I seem to remenber it contained a 
solution.

Where do you tell the computer to save the .pto files before rendering. Not 
that we have a "unicode-in-username-and-therefore-in-homedir-name" type of 
problem or similar.

On August 12, 2020 10:27:58 PM GMT+02:00, "David W. Jones" 
 wrote:
>Hmm, yet the software works in Catalina 10.15.6 according to others on the 
>list.
>
>Since your Mac is brand new, why is it running an older 10.15.5 Catalina? 
>Maybe an update is in order? Could be the fault is in the older Catalina.
>
>On August 12, 2020 8:48:46 AM HST, Bill Meador  wrote:
>>Nope, even added everything in the Hugin folder to Full Disk Access,
>>the
>>program will not run on my brand new iMac Catalina 10.15.5. Crashes
>>every
>>single time with the same error message:
>>
>>“Could not open project
>>file:/Users/briar/Desktop/1BM_4873-1BM_4880.pto.”
>>
>>That is the file name suggested by the program, and whether or not I
>>change
>>it to something else does not matter, it still fails.
>>
>>The software has major faults!
>>
>>Bill
>>
>>On August 12, 2020 at 12:11:28 PM, 'Stanley Green' via hugin and other
>>free
>>panoramic software (hugin-ptx@googlegroups.com) wrote:
>>
>>Specifically for me, allowing the “Full Disk Access” Privacy setting
>>for
>>Hugin results in Hugin showing up as allowed in the “Files and Folders”
>>Privacy list. Hugin was not previously in the “Files and Folders”
>>Privacy
>>list and the +/- controls for that list remained dimmed regardless of
>>the
>>administrator’s padlock status. PTBatcherGUI was already in the Files
>>and
>>Folders” Privacy list with checked options for "Removable Volumes" and
>>"Desktop Folder”. Adding Hugin eliminated the hang. I could reinstate
>>the
>>hang by unchecking Hugin in the “Full Disk Access” Privacy setting.
>>
>>On Aug 12, 2020, at 12:05 PM, Bill Meador  wrote:
>>
>>Beg to differ with you, but it does not work with Catalina…….I do have
>>Full
>>Disc Access enabled, I do have Allow Internet applications to run, but
>>it
>>fails and crashes every time with “could not open project file” error
>>message (screen shot attached).
>>
>>Bill
>>
>>On August 11, 2020 at 5:13:58 PM, AKS-Gmail-IMAP (aksei...@gmail.com)
>>wrote:
>>
>>Hugin does work on Mac Catalina. You need to manually grant Hugin “Full
>>Disk Access” in the Privacy tab of the OS X System Preferences,
>>Security &
>>Privacy. Apple made a security change that the Hugin OS X build has yet
>>to
>>figure out and catch up with in regard to making the OS X build install
>>with that setting.
>>
>>On Aug 11, 2020, at 3:18 PM, Bill Meador  wrote:
>>
>>Cannot get this software to work in any form on Mac Catalina 10.15.5 or
>>later.  Always crashes saying it cannot find "the working directory".
>>Wanted to put it to use and if good upgrade to the paid version they
>>say
>>they offer...no such luck.
>>
>>I would suggest removing from Mac downloads!
>
>
>
>-- 
>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/5EBEF95C-B59B-463F-B416-483EEE21701B%40gmail.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/4CD6BA84-5AC9-41E5-AE99-90EFFA08F68F%40gmail.com.

Re: [hugin-ptx] Re: red artifacts after stitching

[Gunter Königsmann]

That looks like the pixel data is still there but the color profile of
the original image were discarded. But it is only a rough guess: I can
completely wrong...

Kind regards,

    Gunter.

-- 
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/35be49c6-ae86-e1b9-8108-dab27343c3c6%40gmail.com.

Re: [hugin-ptx] Control Point search fails on fairly simple images

[Gunter Königsmann]

Grouped CPs often indicate that the lense parameters are widely incorrect.

On July 9, 2020 8:29:15 AM GMT+02:00, Frederic Da Vitoria  
wrote:
>Hello,
>
>I don't have an explanation, but I notice that Shaunak De's control points 
>are grouped instead of being spread on the common parts of the images. More 
>than the number of CPs, my guess is that the position of those CPs and the 
>fact none of them is far from the others is the cause of the problem. 
>
>I suggest manually adding CPs as widely spaced as possible. I guess there 
>are too many comfusing things in those images. For example, if Hugin marks 
>a "e" on one picture, finding the matching "e" on the other could be 
>tricky, because there are a lot of exactly identical letters. So I'd put a 
>few carefully chosen CPs. For example, I'd put at least 2 CPs in the title 
>(one at each end of the common part) and one at the bottom of the column 
>which is barely visible at the bottom-left of the second image. I'd add a 
>few CPs as widespread as possible, which means probably a few close to the 
>center. Then I'd remove all the CPs which were automatically created, reset 
>all optiizations made in previous runs, and run optimization again. 
>
>But this is a way to get around the issue, it does not explain why it 
>happened in the first place.
>
>Le jeudi 9 juillet 2020 02:19:25 UTC+2, Tduell a écrit :
>>
>> Hello Shaunak De, 
>>
>> On Wed, 2020-07-08 at 16:41 -0700, Shaunak De wrote: 
>> > On further examination of your project file, I notice you have a lot 
>> more 
>> > control points than me. I can't seem to figure out why that would be. I 
>> am 
>> > using Hugin's default settings! 
>> > 
>>
>> At the moment I can't think why that would be the case, maybe someone else 
>> will 
>> chime in with a possible explanation. 
>> I had a try with your full sized images, and that too worked OK. 
>> I didn't follow the tutorial explicitly, I used the following steps... 
>>
>> 1. load images and apply 10 deg field of view to each, hugin automatically 
>> set a 
>> new lens for each. 
>> 2. run cpfind, which found 24 control points. A quick check of those 
>> looked OK. 
>> 3. Optimize in steps, to everything without translation. 
>> 4. check the result and adjust crop boundaries. 
>> 5. stitch. 
>>
>> Attached is the pto file for this project. 
>> Hope that helps. 
>>
>> Cheers, 
>> -- 
>> 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/e00e42ba-d541-4305-bc96-9f364e33f71do%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/34A1030E-9AC6-44B9-A40C-BDB833E210F4%40gmail.com.

Re: [hugin-ptx] Re: Using hugin for grid'd macro pictures from USB microscope

[Gunter Königsmann]

That application would be the "stitching murals" case, see the tutorials 
section: in order to tell hugin that each image was made from a different 
position one needs to tell hugin it was made from a different, but identical 
lense.

See also https://github.com/mpetroff/stitch-scanned-images for automating that.

Kind regards,

   Gunter.

On July 8, 2020 12:00:34 AM GMT+02:00, Shaunak De  wrote:
>This is an exciting application! Thanks for posting!
>
>On Thursday, March 12, 2020 at 11:13:30 PM UTC-7, Ahron wrote:
>>
>> Hi,
>>
>> I have a macro scanner made out of basically smooshing a USB microscope 
>> into the extruder hole of a 3D printer. Said USB microscope captures 
>> 480x720 images in a regular grid of equal overlaps of ~20-50%. The 
>> mechanical repeatability of the system is good to better than or no more 
>> than a few pixels, depending on magnification. Is there a set of settings 
>> for this scenario with Hugin? I feel like it should be almost "easy mode", 
>> but in my current state of things (mostly running the auto and fumbling 
>> with controls) I can't seem to get a good picture with anything! 
>>
>> I currently use microsoft ICE since it usually does a fantastic job with 
>> no muss or fuss, but have recently been looking for an alternative for 
>> reasons involving lack of API and formation of artifacts. I am sure you 
>> have heard this story somewhere before, but right now to do batching we 
>> have an open loop VBS script that runs through the menus with physical 
>> keypresses!
>>
>> Beyond the actual stitching them together, I am sure there is plenty to 
>> deal with blending, dealing with exposure changes, etc... my hope is that 
>> by controlling many variables though I will be able to automate the process 
>> to minimal human input most of the time. Does anyone in the community have 
>> faith that this is possible? it would mean a great deal to me, as my 
>> project means a great deal to me.
>>
>> Thank you so much for any possible assistance!
>>
>
>-- 
>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/9f718616-04a0-49d9-ae78-763a5356964do%40googlegroups.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/962C7F9A-BE31-45AD-869F-1EBBA35B5F60%40gmail.com.

Re: [hugin-ptx] Re: can't get fulla (or Hugin) to work for vignetting (and chromatic aber cor)

[Gunter Königsmann]

The numbers look a bit like you could approximate a n from lensfun by an 
n:0:0:1-n in fulla...

Kind regards,
   Gunter.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/BF8897C7-5378-48F2-8FD7-534E7C6130FC%40gmail.com.

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

[Gunter Königsmann]

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.

-- 
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/23c9ce97-51c4-bd81-8c3f-857f6818a0a3%40gmail.com.

Re: [hugin-ptx] Discard JPG color profiles - interpret them as simple RGB

[Gunter Königsmann]

Are wie sure that the color profiles are never an important part of the jpeg 
that will make them more producible if it is missing? If not removing them 
might be no option, bit applying them on uncompressing the image will. I 
believe no camera will use something like the profiles found in 
http://www.color.org/version4html.xalter that excjange redwith green or similaf 
but one never knows.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/A02C35B3-B973-45F8-9EC9-33920832C842%40gmail.com.

Re: [hugin-ptx] Select all vertical lines and change to horizontal at once - it this possible?

[Gunter Königsmann]

Feels like an interesting feature-request (don't know if it is a low-hanging 
fruit or something the devs would struggle with for months) and a description 
of the pros and cons of any heuristics: it constantly fails for some users.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/0D803671-33EC-4D9F-9084-DEFFC3ACF7D0%40gmail.com.

Re: [hugin-ptx] Select all vertical lines and change to horizontal at once - it this possible?

[Gunter Königsmann]

In most cases seemingly horizontal lines in real live often aren't while 
vertical ones often are vertical.

On March 20, 2020 4:47:00 PM GMT+01:00, "David W. Jones"  
wrote:
>On March 20, 2020 12:25:26 AM HST, Bruno Postle  wrote:
>>The vast majority of panoramas don't have sea horizons, detecting
>>horizontal lines would mess things up for everybody else. The code is
>>capable of detecting horizontal lines, but the functionality is
>>disabled.
>>
>>-- 
>>Bruno
>>
>>
>>On 20 March 2020 07:58:57 GMT, "David W. Jones" wrote:
>>>My use case for this is to use horizontal lines for leveling handheld 
>>>strip panoramas that include sea horizons. The horizon itself never 
>>>seems to be detected as a horizontal line. Yet if I rotate the image, 
>>>the find vertical lines function finds the horizon as a vertical line.
>>>
>>>Maybe the question is why doesn't the point finding function find 
>>>horizontal lines in the first place? What makes them different from 
>>>vertical lines that they can't be found?
>>
>>-- 
>>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/33E5-53F2-46B3-9224-9567A02A77CD%40postle.net.
>
>Why is the functionality disabled?
>
>-- 
>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/65695B91-1F5B-4698-B94E-2529879B894B%40gmail.com.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/854A3A8D-8A72-4139-8AA3-8F2B4121745C%40gmail.com.

Re: [hugin-ptx] Re: Stitching two (or multiple) images with different resolutions together with Hugin

[Gunter Königsmann]

Hugin can adjust the fov if it is told that the image with the different fov 
has been made using a different lens.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/3CDA8952-75C8-4F84-983D-BD5BFC51A0B5%40gmail.com.

Re: [hugin-ptx] Can you calculate position and FOV of cameras using Hugin for 3dsmax?

[Gunter Königsmann]

Am AFK right now. But most of your task is like the "stitch murals" one (which 
there is a tutorial for): Advanced mode, tell hugin each different location to 
ba a different "lens", let hugin search for control points in the area both 
images have in common (possibly using masks), and let it optimize the 
parameters whose value you want to know.

Kind regards,

   Gunter.

On 6 January 2020 17:06:11 CET, Richard Birket  wrote:
>I'm interested to know if I were to take a series of photos of a 
>building/object from different locations (even different FOVs), would Hugin 
>be able to calculate (after manually picking common points) exactly where 
>each photo was taken from (rotation/FOV etc) so that I can 'import' this 
>info into a 3D software package like 3dsmax? I am pretty sure it is 
>possible, but haven't found a tutorial/guide to get me started.
>
>Anyone know of anything?
>
>Cheers
>
>-- 
>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/be94a049-e4ad-46db-988d-a6151635d166%40googlegroups.com.

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

-- 
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/2ABC9D99-2838-4191-A10F-127288731ECE%40gmail.com.

Re: [hugin-ptx] automated stitching

[Gunter Königsmann]

...and there was an emblend option to prefer the sharpest image parts for the 
final image. I don't remember how it was named, though. 
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

-- 
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/6A462968-EDA4-4910-8A66-BB0821FE4AEB%40gmail.com.

Re: [hugin-ptx] automated stitching

[Gunter Königsmann]

As the images are taken at different points in time and from a different 
perspective I would guess that the shadow from a cloud that makes one part of 
the border of one image dark, but doesn't do the same to the same region in 
another image will cause photometrics to go wild occasionally if it tries to 
make the two brigjtnesses match. Also basically what you do is what the 
"stitching murals" tutorial does do => any checkpoint on nearby features will 
show a different parallax error than a point in the horizon.

As the question was if the images can be made sharper: does making more 
pictures and trying to make an HDR image help? This might average out some 
noise, but overlaying more images might produce ghost images of everything with 
an parallax error.

On 2 January 2020 18:35:32 CET, Daniel Baertschi  
wrote:
>
>
>We are about to create a solution to continuously stitch images 7x24. The 
>solution setup looks as follow:
>
>
>Camera/lens: Nikon Z-series with Nikkor 14-30/4S, typically focal length 
>around 20mm
>
>Camera mounted vertical, rotated around nodal point. Horizonal 
>repositioning 0.01 degree absolute.
>
>Number of images typically between 8 to 10
>
>Aperture, ISO and shutter speed gets automatically adjusted by own 
>algorithm over the course of the day
>
>Images are taken in manual mode. Image luminosity and color temperature is 
>fixed for all images per panorama
>
>Stitching with Hugin 2019.1 7x24 every 10 to 20 minutes based on a 
>predefined project
>
>Live example: https://feed.yellow.webcam/feed/44M64QO4X 
>
>
>
>We experience little issues except visible blending issues and are 
>searching for advice. We usually adjust aperture first and keep shutter 
>speed fast and ISO at fair level to avoid motion blur and get good image 
>quality. Typical camera locations are on cable car poles and roof tops. 
>Every test location shows little motion, either due to sunshine or wind 
>speed sometimes exceeding 200 km/h. We understand the negative impact of 
>larger aperture but cannot avoid it to get sharper images especially on 
>windy days and at nighttime.
>
> 
>
>What can you recommend to lower blending issue? What parameter shall we 
>tackle to get maximum benefit?
>
>
>   - Correction of vignetting before stitching
>   - Calculating lens distortion
>   - Lens calibration
>   - Optimize blending
>
>Anyone experience with automated stitching 7x24?
>
>Thanks
>Daniel
>
>-- 
>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/1160ecb1-0173-4713-92a0-b8de6d9c7e46%40googlegroups.com.

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

-- 
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/A47A367C-E5C3-44E5-A8CB-E100AFC7535D%40gmail.com.

Re: [hugin-ptx] Aligning images of different dimensions

[Gunter Königsmann]

What happens if you tell hugin each of the images has been made by a different 
lense?

On 10 December 2019 17:03:26 CET, Judson Fisher  wrote:
>Hello,
>I am trying to align a stack of historical aerial photos using their 
>fiducial marks.  The images are photos of photos and were taken such that 
>the images sizes are inconsistent, varying by up  to 40 pixels.  I've made 
>control points between a base image and the rest but when I attempt to 
>stitch them the batch processor returns an error regarding the inconsistent 
>image size.  Do i need to use other software to make my image size 
>consistent, or can Hugin help me with this?
>thanks,
>/Jud
>
>-- 
>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/8fb321e6-37e7-478c-aad1-f46141240353%40googlegroups.com.

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

-- 
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/7BA24CF0-9577-42D2-86A9-0685C1AEDEFA%40gmail.com.

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

[Gunter Königsmann]

If fedora does one thing in a completely different way from Debian, BSD, 
Ubuntu, ArchLinux and MacOs and wants all software projects to decide if to 
decide for fedora or for the rest... ...why on earth do they do such a thing?

On 29 November 2019 19:47:43 CET, Harry van der Wolf  wrote:
>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
>> 
>> .
>>
>
>-- 
>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.

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

-- 
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/56D5B5AE-01DE-4CB9-9FA3-F39923962E83%40gmail.com.

Re: [hugin-ptx] Compiling enblend with gnu g++

[Gunter Königsmann]

I believe if you add -std=c++1z  to the compiler flags it works.

Kind regards,

Gunter.

Am 22. November 2019 00:57:58 MEZ schrieb Kornel Benko :
>Hi,
>the recent version of enblend sources (from repo) is
>not compilable with the gnu compiler.
>
>Using it I get
>In file included from /usr/src/enblend/enblend-code/src/enblend.cc:85:
>/usr/src/enblend/enblend-code/src/optional_transitional.hpp:40:51:
>error: 'experimental'
>in namespace 'std' does not name a type 40 | template 
>using optional
>= ::std::experimental::optional; |
>^~~~
>/usr/src/enblend/enblend-code/src/optional_transitional.hpp:41:11:
>error:
>'experimental' has not been declared 41 | using
>experimental::nullopt;
>  |   ^~~~
>/usr/src/enblend/enblend-code/src/enblend.cc:118:6: error: 'optional'
>in namespace 'std'
>does not name a template type 118 | std::optional
>OutputMaskFileName;
>  |  ^~~~
>/usr/src/enblend/enblend-code/src/enblend.cc:118:1: note:
>'std::optional' is only
>available from C++17 onwards
>...
>
>Patching the CMakeLists.txt to use the required --std=c++17, the error
>compiling src/enblend.cc is:
>In file included from /usr/include/vigra/stdconvolution.hxx:43,
> from /usr/include/vigra/convolution.hxx:41,
>  from /usr/src/enblend/enblend-code/src/openmp_vigra.h:32,
> from /usr/src/enblend/enblend-code/src/enblend.h:41,
> from /usr/src/enblend/enblend-code/src/enblend.cc:197:
>/usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17
>does not allow
>dynamic exception specifications 1413 |
>throw(PreconditionViolation)
>  | ^
>.
>
>This is the same with the recent g++9.2 compiler.
>
>   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/20191122005758.60f2c8a6%40admin1-desktop.

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

-- 
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/F52CF71F-6D47-4A2C-AEAC-6CFA8D616468%40gmail.com.

Re: [hugin-ptx] PTmender, PTuncrop without root access?

[Gunter Königsmann]

On Linux traditionally many program share the same shared libraries -
which can decrease the size of a linux installation to 10% and less.
...and it is deemed to be a potential security problem if one picks up
.dll files that are just lying around somewhere (search for dll
injection for details).

But there is a variable named|LD_LIBRARY_PATH| that tells the dynamic
library loader where to search for libraries. See
https://stackoverflow.com/questions/13428910/how-to-set-the-environmental-variable-ld-library-path-in-linux
for details.

Kind regards,

   Gunter


On 17.11.19 18:44, Erik Krause wrote:
> Hello,
>
> I'd like to run PTmender and PTuncrop on a server (ubuntu 14 x86_64)
> where I don't have root access for installation. I copied PTmender and
> PTuncrop from a deb package and it starts but complains about libpano13
> shared library not found (even though it's in the same directory, which
> is also on PATH). Is there a way around this problem? F.e. a stand alone
> version?
>
> -- 
> Erik Krause
> http://www.erik-krause.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/a2a47d3e-1818-8ce9-c0ea-afeac32b3d18%40gmail.com.

Re: [hugin-ptx] Re: enblend / black corners and fringes

[Gunter Königsmann]

A possibility that often is overlooked is the reason for many glitches in 
modern computer games: What if all algorithms work out as expected - but even 
the small numeric error double floats make add up to one pixel? Wilkinson's 
polynomial shows us that truly  catastrophic add-up can occur in simple 
mathematical problems of the like hugin solves even without trigonometric 
functions that can convert small errors on the input to large errors on the 
output => leaving one pixel of error margin might do wonders even where the 
equation is flawless math. If Wilkinson's polynomial isn't impressive enough 
feel free to search for Siegfried Rump's polynomials. Both have been indicated 
to me by Richard Fateman from the maxima Project that is about an open-source 
program that is willing willing to do nearly all maths (including playing with 
equations) you'll ever need.

Kind regards,

   Gunter.

Am 4. November 2019 20:02:45 MEZ schrieb Wirz :
>Hi Thomas and Chris,
>
>Thank you for your suggestions!  I'm not sure when I'll have time for
>that, but starting with improved error detection should certainly be
>doable for some time soon.
>
>It's not important but I actually have an example where NFT+coarse+nopt
>leads to small but well visible black triangles next to the entry
>points
>of the seam.  Even with NFT+fine+nopt I can spot a single black pixel.
>
>cheers, lukas
>
>
>
>On 30/10/2019 19:09, T. Modes wrote:
>> Hi Lukas,
>> 
>> I got an answer from Chris Spiel, the main enblend developer, to your
>
>> questions.
>> I hope this helps you further.
>> 
>> Am Mittwoch, 25. September 2019 23:14:41 UTC+2 schrieb lukas:
>> 
>> In all examples that I know of, the problem is that the seamline(s)
>> run(s) slightly outside of the overlap area.
>> 
>> Furthermore, there are problems if the Simulated-Annealing
>> seamline optimizer plaits loops or sometimes even only cusps.
>> 
>> 
>>  As a result, pixels are
>> included from one image which lie outside the image's area, or in a
>> transparent area (which apparently is not invalid but black).  This
>> problem can occur for NFT and GC, becomes less frequent with fine
>and/or
>> optimise but can occur with any combination.
>> 
>> I'd be surprised if **pure** NFT generates a seamline outside
>> the overlap area.  BTW, you can compare the Vigra implementation
>> (default; on host CPU) with the OpenCL implementation of the NFT
>> running on a GPGPU (only Manhattan and Euclidean metrics here).  Use
>> parameter "gpu-kernel-dt" to reroute the program flow.
>> 
>> Rosomack is the expert for GC; it's his code.
>> 
>> 
>> 
>> --- snip ---
>> If I understand the relevant algorithms correctly, this problem could
>> be/should be caught in three different places:
>> 1) Neither GC nor NFT should return a seamline outside the overlap
>> 
>> Correct.
>> 
>> 
>> 
>> 2) the seamline optimisation should return only seams inside the
>> overlapping region
>> 
>> Also correct.
>> 
>> 
>> 
>> 3) the blending should not assume out-of-bound or transparent pixels
>to
>> be black but either transparent or take a pixel from the other
>picture.
>> 
>> Indeed we ought to file this item under "never reached".  But
>> obviously these conditions **are** met and black or just weird areas
>can
>> show up in the blended image if the seamline took a detour to la-la
>> land.
>> 
>> 
>> 
>> Which brings me to my question:  Do you have any opinion on where
>this
>> problem should be fixed?  I would assume fixing 3) is the easiest and
>> safest.  On the other hand, seamlines outside the overlap area,
>produced
>> by 1) or 2) entirely refute the point of finding a good seamline to
>> begin with (leading to poor quality).  So maybe one should treat this
>> problem in all three places (four actually, because GC, NFT, opt,
>blending)?
>> 
>> After more than a decade of maintaining Enblend/Enfuse I can
>> tell you that the difficulties really start when you dive into the
>> code.
>> 
>> The first step I'd take is to add a set of precise diagnostics that
>> help spotting the problem.  For example:
>>   * issue a warning for any deviant seamline in the terminal window,
>>   * improve the output of `--visualize',
>>   * paint incorrect black areas with #ff00ff, or enclose them with
>> #00-colored diamonds (at a minimum size to emphasize
>> single-pixel errors)
>> There is no reason to restrict these diagnostics to the final image
>as
>> any stage could be buggy and equally deserves a check.  For
>> flexibility and reducing the number of recompilations `--parameter'
>> always comes in handy; see file "parameter.h".
>> 
>> IMO, the second step could be to work through the image-processing
>> pipeline front-to-back, i.e. start with the NFT, make it rock solid.
>> Then proceed to GC, harden it, and so on.
>> 
>> 
>> HTH,
>> cls
>> 
>
>
>-- 
>A list of frequently asked questions is available at:

Re: [hugin-ptx] Request : forum migration

[Gunter Königsmann]

There are many solutions to the problem how or where to host a forum. Every
of these solutions has drawbacks.
If you use Google they will most probably know where you are and that you
are a reader of hugin-ptx. But I guess they will know that, anyway, as many
websites are hosted by Google or have Google analytics or are transferred
over a Google fiber.
If you just want to have an account less a mailman account would be an
account, too...

>
>

David W. Jones  schrieb am Di., 23. Juli 2019, 20:13:

> On July 23, 2019 5:12:18 AM HST, "'Caetano Veyssières' via hugin and other
> free panoramic software"  wrote:
> >David W. Jones
> >>> It is frequently described in derogatory terms. Just like Gooole, it
> >
> >also tracks users throughout the web, wherever a Discourse forum is
> >used.
> >
> >Again, I'm not seeing any proof. Could you provide a link or 2 to
> >confirm
> >that? Personally all I find is that Discourse doesn't track any data
> ><
> https://meta.discourse.org/t/question-about-the-extent-of-data-tracking-pseudo-ai/105740/2
> >
> >
> >of external forums except for the forum's url and the Discourse version
> >
> >used. Data is tracked only internally for the admins to manage trust
> >levels
> >and other admin features.
>
> Ok. I still see no need or benefit to switching to a web forum of any
> sort. They (including Discourse) are clunky, inconvenient and completely
> unnecessary.
>
>
>
> --
> 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/6A2FEF11-6199-46F7-9B80-4BEB9F292679%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/CAMcFxV13fL4YsTk7TGptVy3D1z6ZP5aTD3-Y9doWfOOL3b8ZnQ%40mail.gmail.com.

Re: [hugin-ptx] Re: Hugin Windows installer tries to modify system files?

[Gunter Königsmann]

Plus -static-libgcc and -static-libstdc++

There is one thing one has to keep in mind when using software that isn't
installed in the standard locations: a virus that wants to modify it has
all the rights necessary for that. But that is arguably not a problem the
developer of the software has to care about.

Andrey Beresnyak  schrieb am Mi., 5. Juni 2019,
21:17:

> Ever thought of "-static"?
>
> On Wednesday, June 5, 2019 at 6:34:22 AM UTC-4, Gunter Königsmann wrote:
>>
>> Additionally afaik eventual security updates for vc redist only apply to
>> the vc redist that is installed in the default location. We cannot
>> possibly want to turn them ineffective.
>>
>> Kind regards,
>>
>>  Gunter.
>>
>> --
> 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/79bbc62e-8686-48e6-a2e3-c58eaa80a3a7%40googlegroups.com
> <https://groups.google.com/d/msgid/hugin-ptx/79bbc62e-8686-48e6-a2e3-c58eaa80a3a7%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/CAMcFxV176DzkROMu1m1TV8eVvzjmgoWXt8PKE0WAOyETc0h29Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Hugin Windows installer tries to modify system files?

[Gunter Königsmann]

Additionally afaik eventual security updates for vc redist only apply to
the vc redist that is installed in the default location. We cannot
possibly want to turn them ineffective.

Kind regards,

 Gunter.

-- 
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/d9dcd6e1-e8ce-84a2-fd57-ba3b71580287%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Photometric alignment changes the reported control point distances

[Gunter Königsmann]

Then it looks like hugin for measuring errors uses "pixels in the output
image" as unit. Which might be as good as any other potential unit as all
images are distorted during stitching and the definition of "pixels" in the
input images therefore might change depending which part of the image is
meant.

Luís Henrique Camargo Quiroz  schrieb am Sa., 25. Mai
2019, 14:07:

>
>Hi,
>
>   I think one important thing to observe is the size of the output. By
> default Hugin starts with a 3000x1500 equirectangular, and I place CPs and
> do many optimizations with this output size. Lter, when I start to generate
> bigger "previews", or the biggest, final result, the errors apparently
> increase, which is (should be, I never checked) proportional to the size
> increase.  Is this effect the culprit in this case?
>
>regards,
>
>Luís Henrique
>
> Em sáb, 25 de mai de 2019 às 03:55, T. Modes 
> escreveu:
>
>>
>>
>> Am Donnerstag, 23. Mai 2019 18:27:01 UTC+2 schrieb Dr. Kurt:
>>>
>>> After more experimentation with just a pair of images (separated in yaw
>>> by about 7º), I find that the reported distances are dependent on the size
>>> of the active area in the quick preview window and the image position
>>> within this window!  If I optimize geometry and then exposures before
>>> opening the quick preview to center the panorama, then the distances stay
>>> at their (presumably correct) small values; if I optimize geometry but then
>>> recenter before the exposure optimization then the distances all increase.
>>>
>>> You can take a look at my test images and pto files along with some
>>> screen shots at:
>>>
>> I can't reproduce the issue with your project (or other projects).
>> Can you describe *one* workflow which shows the issue? Please state all
>> steps you done from loading your pto file. Also where do you check the
>> error - in the cp tab or in the cp list window.
>>
>> --
>> 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/39137c60-c5c5-47fc-af06-a341a8a8526d%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> --
> Luis Henrique Camargo Quiroz
> http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
> http://panoramaslh.net/
>
> --
> 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/CAEKSoZZC_GuuN00b_3BWgqwZ9X-%2BFjxrBE%3DMPyC_xCcAfMmFxw%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/CAMcFxV21JfuuD22uGQMtbcsN_wezCkG9OyjfeHobsnjLYNdWzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Compiling Enblend for Windows

[Gunter Königsmann]

The main() function of enblend is in the file enblend.cc. But the functions
defined in this files call functions from other .cc files that don't define
main() functions and that therefore have to be part of the Code::Blocks
project, as well.

Kind regards,

   Gunter.

Matija Kogoj  schrieb am Sa., 11. Mai 2019, 16:06:

> Hello.
>
> I have hit the same problem as before, and I see some other people have as
> well.
> Seems like Enblend is the problem and I want to update it; by following
> the issue tracker links it seems as if the code was updated in 2019, but I
> don't know how to compile the source code into an .exe file for use in
> windows. It is compiling on my linux system (if I find all required
> dependencies) but that computer can't be used for stitching.
>
> I've got codeblocks and gcc, but all tutorials I found told me to find a
> "main.c" ... but there was no "main" and no "c" in the code I downloaded.
>
> Any help appreciated.
>
> --
> 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/9eb631e9-4f64-4cd2-9bb9-d8918a99bdb0%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 
https://groups.google.com/d/msgid/hugin-ptx/CAMcFxV1%2BtDec1HFnmkT2ekXj7y9oY5XvceaNn1xe7bv-ZRLOPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: stitching cylindrical pano from rectilinear images results in vertical mismatch at ends

[Gunter Königsmann]

With cell phone optics sometimes the upper left corner has a slightly
different zoom factor than the lower right. Might it be something like this?

Erik Keever  schrieb am Di., 30. Apr. 2019, 06:42:

> Hi Jim,
>
> What do you mean not using control points? The usual process is
> (1) Load pictures
> (2) Detect control points
> (2b) Prune bad control points
> (3) Have Hugin align images
> (4) Stitch
>
> The stitching process is "just" a bunch of computational geometry that
> projects input images onto the 4 steradians of a sphere using one set
> of transforms & then projects part/all of that sphere back onto an image
> using another.
>
> Which is a long way to say that it doesn't matter at all if your pictures
> are the least bit aligned, stitching will "work."
>
> You don't have an unreasonable (meaning about 75 or more) number of images
> so you should be able to simply select them all and detect CP using cpfind,
> then click 'optimize geometry' and Hugin will be able to line everything up
> with subpixel accuracy.
>
> The key to making a 360* panorama work is to connect the "left" and
> "right" edges with control points and then have Hugin optimize your lens
> field of view. While we say e.g. that my normal lens has a focal length of
> 50mm, in reality it's 50. mm, and the exact number is derived by
> Hugin when we require that a string of images spanning 360* does in fact
> span exactly 360*.
>
> Your 'lens type' means the projection used by the lens taking the image,
> which is almost 100% for sure rectilinear. The thing called 'projection
> type'  is the projection used by the lens of the imaginary camera at the
> center of that sphere I mentioned that determines what gets projected onto
> the output image (You may notice that many of the output projections, like
> equirectangular or cylindrical, do mappings that are nigh impossible for
> any physical lens).
>
> -- Erik
>
> On Mon, Apr 29, 2019, 7:08 AM James Proctor  wrote:
>
>> Thank you, all, for your replies so far!...very helpful. Quick responses:
>>
>>- I haven't been using control points, and assumed the overlap btw
>>first/last image would render stitching possible. By establishing control
>>points btw first/last image, would this in effect tell Hugin that I have a
>>360° set of images? My intuition suggests there would be a simpler way to
>>do this.
>>- The tripod head was set to level when I shot all these images,
>>which are on considerable terrain, hence they may appear to be off
>>vertically but they're not. (And here too, I did not manually input 
>> control
>>points given the pano head I used to establish careful overlap btw 
>> images.)
>>I attach a zipped version of input files to this reply.
>>- Each input image is flat/rectilinear. Collectively, the fourteen
>>images describe a 360° view. I tried (once, maybe incorrectly?) to set the
>>Lens Type from Normal (rectilinear) to Panoramic (cylindrical), but the
>>result was goofy. I have been setting Projection (all this via Simple
>>interface) to Cylindrical prior to stitching; where would the input
>>projection be set, if I understand your recommendation correctly? (Btw, my
>>QTVRs are at less resolution than the originals, so I'd prefer to start
>>with the originals at this point.)
>>
>> I hope the above is helpful. My gut tells me that there is some setting
>> I'm missing that tells Hugin my images comprise a 360° view, thus it would
>> stitch the first and last together as two adjacent images, same as the rest.
>>
>> Sure appreciate any continued ideas,
>>
>> Jim P.
>>
>> On Sunday, April 28, 2019 at 10:40:58 PM UTC-7, James Proctor wrote:
>>>
>>> Greetings -- I'm using Hugin to stitch together some old digital images
>>> taken from a Nikon Coolpix atop a tripod/pano mount (14 total per pano).
>>> There was plenty of overlap btw all images, including the first and last
>>> image. The stitching process seems to work great, but when I export and
>>> view the pano the vertical position of elements at the left and right ends
>>> is off, resulting in a jagged transition...see e.g. attached.
>>>
>>> The settings I used are as follows:
>>>
>>>1. Load Images: Lens type rectilinear, 3.8mm/13.7 multiplier
>>>(automatically detected?)
>>>2. Projection switched from default Rectilinear to Cylindrical
>>>3. I've played a bit with Center/Fit/Straighten buttons, but they
>>>don't seem to do the trick
>>>
>>> There must be an easy explanation as to why the stitching process
>>> doesn't align the two ends of the pano, given the original images overlap
>>> substantially. It just doesn't seem to recognize that these 14 images are
>>> from a quasi-cylindrical (vs. e.g. planar) source.
>>>
>>> If you could please point me to a ready solution I'd sure appreciate!
>>> The app is proving useful for me to re-stitch circa 2000 digital panos
>>> previously saved in now-extinct QTVR format.
>>>
>>> Regards,
>>>

Re: [hugin-ptx] Re: Installed hugin now what?

[Gunter Königsmann]

Am 25.02.19 um 18:13 schrieb Bart van Andel:
> @Abrimaal:
>
> Although the default installation folder in Windows is "C:\Program
> Files", it is not recommended to install any third party software
> on C:, except drivers, codecs, fonts and other shared files.
> Files on C: are often protected by Windows in various ways,
>
That is one of the reasons why most applications default to be installed
in there: In this directory they are at least a bit protected against
being changed by malware.

-- 
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/5c5ccbb5-ff0a-b9b3-f10b-b5e28dbfe528%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Automatic stitch scans of engineering drawings hopeless?

[Gunter Königsmann]

Floating-point numbers often add a small rounding error. Maybe the slightly
negative number isn't a bug but such a thing...

On Sun, 24 Feb 2019, 00:55 AKS-Gmail-IMAP,  wrote:

> I can comment on some of this. I am currently using the "method 3” to
> create “contact sheet” images of 35mm photograph film rolls archived in
> style “35-7BXW” PrintFile archival negatives preservers. These are clear
> plastic negatives preserves holding seven rows of six 35mm image negative
> strips. These scan really well on a desktop flatbed photo scanner in
> transparency mode, but it takes three scans to do one sheet. Therefore the
> scans have to be stitched together. Hugin using method 3 does the job.
> Furthermore, because the negatives might be at radically different
> exposures, Hugin’s stack handling where the stacks are multiple scans at
> different exposures allows exposure fusing all the images in the contact
> sheet to be satisfactory images.
>
> When using this mosaic XYZ mode I always see the “Panorama Tools”
> "Panorama must have positive height” message when the “edit script before
> optimizing” check box is checked where the “Continue with these changes” is
> pressed at the “Edit Panorama Tools Script” form. I would be clueless
> trying to edit the script. I never see any negative numbers in the script.
> Hugin does show “-0” in the Z plane parameters when it calculates the
> parameters. The number is actually a small negative number when viewed in
> the edit box. The "Panorama must have positive height” message will show
> even after reseting all parameters to 0. Perhaps this is a bug. I would not
> know since I am pretty much cook booking my way through this part of Hugin.
>
> By the way, Masks are essential to use in “method 3”.
>
> Regarding engineering drawings, the type and source of which has not been
> described, I do not see how one could automate the task because each image
> requires at least one unique mask and possibly four unique masks and also
> because the image control points are best placed by hand. The time spent
> removing and correcting falsely placed automatic control points is many
> times more the manual effort to create the very few required control
> points. The situation is similar to the fallacy digitizing scanned drawings
> into computer aided drawings.  Incidentally the time spent personally
> observing each image in the manual method pays off with additional
> knowledge about the images. That knowledge might explain causes for
> problems seen in the output.
>
> The type and source of the engineering drawings is not mentioned. I’ve
> worked in that business for many years and I have tried on many occasions
> to reassemble plans using every imaginable technique from “xerox art” to
> Hugin. I cannot recall any time the source images did not have a different
> distortion in both the x and y directions. The results were always
> unsatisfactory to some degree, often terrible. I could see x y scale issues
> with any first generation roll plotter sources and small media copy
> machines. Images created on full sized flat bed equipment were the best but
> what company has one of those these days?
>
> Output from a roll plotting or reproducing device is going to have a
> slight stretch distortion as the media passes over the roll. I would see
> this in recent plots and also back in the day when running vellums or cloth
> through a diazo machine. I would foresee difficulties trying to stitch
> plans back together without being disappointed in the results. Even
> recently the best results with the least amount of effort and frustration
> were always using what we called “xerox art”. This is cut and paste using
> Scotch magic tape with perhaps a bit of pencil or pen touchup followed by a
> run through a large format copier.
>
> Regards, Allan
>
> > On Feb 23, 2019, at 2:40 AM, Bruno Postle  wrote:
> >
> >
> >
> > On 21 February 2019 14:10:41 CET, jim cullen wrote:
> >>
> >> I can't seem to make it fix the roll and pitch at zero successfully
> during
> >> optimization.
> >>
> >> I'm setting the fast preview mode to  Mosaic plane - is that proper?  I
> ask
> >> because the python script
> >> stitch-scanned-images.py which one can find on github constructs a .pto
> >> that seems to use Panosphere.
> >
> > Hugin has so many options that you can do this scanned images thing in
> three completely different ways. I'm wary of prescribing a particular
> method over another, but you can't mix them. They are:
> >
> > 1. Using very narrow field of view, with roll, pitch, yaw optimisation.
> > Imagine that you have taken these images using a very long telescope,
> Hugin will let you stitch them like a 'normal' panorama, as long as you set
> the field of view to a small number (<1°).
> > The result won't be perfectly correct, and there will be odd curvatures,
> but for most purposes you can get away with this.
> >
> > 2. Using the d,e lens shift parameters to move the images around a
> rectilinear 

Re: [hugin-ptx] Automatic stitch scans of engineering drawings hopeless?

[Gunter Königsmann]

g...@github.com:mpetroff/stitch-scanned-images.git

has worked for me in similar cases.


Kind regards,

   Gunter.

-- 
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/ea237d74-fa00-adfb-fb12-74cce3caaa04%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Using hugin on terminal

[Gunter Königsmann]

./hugin_executor

At least I hope this to be the solution: Mac OS doesn't dare to execute an
app from the current folder if not explicitly instructed to do so.

If the doesn't work please send us the output of the command

ls

In this folder. And if you have installed it via homebrew, huginy as an
appbundle or using fink.

Kind regards,
   Gunter.

Am Mo., 7. Jan. 2019, 20:46 hat Christian John 
geschrieben:

> Hey all,
>
> I'm trying to run hugin using terminal on a mid-2012 mac OSX v 10.13.6. I
> downloaded it from sourceforge and am able to open and use the
> point-and-click version of Hugin from Launchpad, but am unable to use the
> command line tools. However, if I try to run `hugin_executor -h` (even
> after navigating to the Hugin app folder) I get the error:
>
> -bash: hugin_executor: command not found
>
>
> Can anyone suggest a course of action from here? I'm guessing I either
> need to somehow load the hugin-tools library (like you would with `import
> np` in python or `library(raster)` in R), or do some additional compilation
> step that I haven't yet figured out...
>
>
> Best,
>
> Christian
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to the Google Groups
> "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/1c53d0f4-9d62-462f-b019-4794a4a03e23%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 
https://groups.google.com/d/msgid/hugin-ptx/CAMcFxV1ANkTdjh1TYacBCGUpYGo7KyDiaq3CSQbkTFoacG_w6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] parallax error in a rig of cameras

[Gunter Königsmann]

If you watch the scene from a different position you see different things.
No algorithm can undo that.

If there is enough overlap between the sensors what you can try is to find
an object in the overlapping section that is sufficiently similar in all
photographs and switch from one sensor to the other there. Which might
break the consistence of the rest of the image: for objects in a different
depth your 360° panorama will have 340 or 380°. Control points don't lie so
they tell inconsistent camera angles and positions and near to the object
you switch cameras things might disappear, get doubled or get way too wide
or too narrow.


My guess the sensor's algorithm will skip trying to use control points in
order to determine the relative position of the cameras: it only needs to
be done once. In hugin you can stitch one image and then just replace the
image files for the next set of images in order to do so.

Switching between images in the Right Place in hugin can be done using
masks. It will automatically fine-tune the border within the remaining
overlapping section between images.


Am Mi., 14. Nov. 2018, 18:22 hat  geschrieben:

> Hi,
>
> I am new to this forum.
> I am planning to set a rig of six small cameras to take panos.
> The distance between the nodal points of each cam is known,
> As far as I know there is no way to solve this parallax error in stitching
> the images in Hugin, except in some particular cases.
> I also read that some manufacterers of 360 degree cameras consisting of a
> number of sensors and lenses claim their included stitching software can,
> partially, deal with the parallax error.
> My question is:
> is there any exhisting algorithms which may (or which is scheduled to) be
> included in Hugin for the above purpose?
>
> Thank you.
>
> Best regards,
>
> Giuseppe
>
> --
> 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/a4bc8d44-30e9-4146-8069-fbcebaf132e0%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 
https://groups.google.com/d/msgid/hugin-ptx/CAMcFxV1MrfCzct%2BKRsO0CuOpiKU2K8zE%3DNXheT2sko_K1KAsyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] I got a 360 image and only want to display a portion of it

[Gunter Königsmann]

Sounds like you are looking for the crop tab of the fast image viewer of
the advanced GUI. Kind regards,

  Gunter.

Am So., 4. Nov. 2018, 01:24 hat Michael  geschrieben:

> you can do it with photoshop (I read). Can I do it with hugin?
>
> --
> 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/9420bd76-b2fe-42eb-9bef-ef1eb1db5688%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 
https://groups.google.com/d/msgid/hugin-ptx/CAMcFxV3u0YqCwqTwXxS0Uc3pW5UJiPKhS7OhLXdve6rrXTU1iQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] libpano gcc 8 warnings

[Gunter Königsmann]

Didn't have the time to patch the whole thing. But a first few lines of
the patch would read as attached to this mail - and obviousy would need
an review as everybody gets this kind of thing wrong.

I'm not sure if all the strings we sprintf'ed into actually had the
right length to accomodate the '\0' that ends the string, though...

Kind regards,

 Gunter.

-- 
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/fe10e8e0-377a-f722-ac04-5a49fc2af315%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
diff libpano13-2.9.19/adjust.c libpano13-2.9.19-snprintf/adjust.c
419c419,420
< newscript = (char*) malloc( strlen(script) + NUMPTS * 60 ); // One line per pair of points
---
> size_t newscriptlen = strlen(script) + NUMPTS * 60;
> newscript = (char*) malloc( newscriptlen + 1 ); // One line per pair of points
421a423
> 	newscript[newscriptlen] = '\0';
426c428
< sprintf( newscript, "%s\n%s", script, cdesc );
---
> snprintf( newscript, newscriptlen, "%s\n%s", script, cdesc );
2173,2174c2175,2176
< 
< sprintf( message,"Strategy %d\nAverage (rms) distance between Controlpoints \nafter %d iteration(s): %25.15g units", getFcnPanoNperCP(), numIt,result);//average);
---
> 		message[255] = '\0';
> snprintf( message, 255, "Strategy %d\nAverage (rms) distance between Controlpoints \nafter %d iteration(s): %25.15g units", getFcnPanoNperCP(), numIt,result);//average);
2935c2937
< 
---
> line[79] = '\0';
2940c2942
< sprintf( line, "c n%d N%d x%lf y%lf X%lf Y%lf\n", cp[i].num[0], cp[i].num[1], 
---
> 	  snprintf( line, 79, "c n%d N%d x%lf y%lf X%lf Y%lf\n", cp[i].num[0], cp[i].num[1], 
diff libpano13-2.9.19/correct.c libpano13-2.9.19-snprintf/correct.c
748,749c748,750
< 			{	
< sprintf( percent, "%d", (int) (xul * 100)/(dx>0?dx:1));
---
> 			{
> 			percent[7] = '\0';
> snprintf( percent, 7, "%d", (int) (xul * 100)/(dx>0?dx:1));
diff libpano13-2.9.19/file.c libpano13-2.9.19-snprintf/file.c
1408c1408,1409
<   sprintf(msg,"width=%d, height=%d, top = %d, bottom = %d, left = %d, right = %d\n",
---
>   msg[999] = '\0';
>   snprintf(msg, 999, "width=%d, height=%d, top = %d, bottom = %d, left = %d, right = %d\n",
1724,1725c1725,1726
< 
< sprintf( &(sLayerName[1]), "%03d", numLayers+1 );
---
> sLayerName[4] = '\n';
> snprintf( &(sLayerName[1]), 4, "%03d", numLayers+1 );
1887c1888,1889
< sprintf(tempString, "%d", 100 / numberImages);
---
> 	tempString[127] = '\0';
> snprintf(tempString, 127, "%d", 100 / numberImages);
2077,2078c2079,2081
< 
< sprintf(&(sLayerName[1]), "%03d", (i+1)%1000 );
---
> 
> 	sLayerName[4] = '\0';
> snprintf(&(sLayerName[1]), 3, "%03d", (i+1)%1000 );
2087c2090
< sprintf(tempString, "%d", i * 100 / numberImages);
---
> 	snprintf(tempString, 127, "%d", i * 100 / numberImages);
2235c2238
< sprintf( &(sLayerName[1]), "%03d", i+1 );
---
> snprintf( &(sLayerName[1]), 3, "%03d", i+1 );
2807c2810
< char fname[40];
---
> char fname[40];fname[39] = '\0';
2820c2823
< sprintf(fname, "_PTStitcher_tmp_%06d", nTry);
---
> snprintf(fname, 39, "_PTStitcher_tmp_%06d", nTry);
2899c2902
< char outputFilename[MAX_PATH_LENGTH];
---
> char outputFilename[MAX_PATH_LENGTH];outputFilename[MAX_PATH_LENGTH-1] = '\0';
2915c2918
< sprintf( outputFilename, outputPrefix, i );
---
> snprintf( outputFilename, MAX_PATH_LENGTH-1, outputPrefix, i );
diff libpano13-2.9.19/filter.c libpano13-2.9.19-snprintf/filter.c
385,386c385,387
< {   
< sprintf( percent, "%d", (int) ((y * 100)/ TrPtr->dest->height));
---
> {
> 			percent[7] = '\0';
> snprintf( percent, 7, "%d", (int) ((y * 100)/ TrPtr->dest->height));
diff libpano13-2.9.19/optimize.c libpano13-2.9.19-snprintf/optimize.c
97c97
< 		char msgx[200];
---
> 	char msgx[200];msgx[199] = '\0';
99c99
< 		sprintf (msgx,"You have too few control points (%d) or too many parameters (%d).  Strange values may result!",o->numData,LM.n);
---
> 		snprintf (msgx,199,"You have too few control points (%d) or too many parameters (%d).  Strange values may result!",o->numData,LM.n);
diff libpano13-2.9.19/ppm.c libpano13-2.9.19-snprintf/ppm.c
198c198
< char header[30];
---
>