Re: [hugin-ptx] Problems stitching with newer versions of Hugin

[Greg 'groggy' Lehey]

On Saturday, 22 June 2024 at 20:02:27 +, wirz wrote:
>
> I've looked at the example case for a while, trying to answer three
> questions: a) What about those dark (nb, not black!) corners?  b) Where do
> the large slightly too bright areas come from?  c) What is different from
> version 4.1.4?
>
> a) This is simple, they are parts of the tripod, but you know that of
> course.  While they are not desirable, I wouldn't call it a bug if some
> corners of an actual image end up in the blended result.  Using masks is the
> only way to be sure.

Another way is to use enblend 4.1.4.  Yes, masking them out would
work, but it's a lot of work.  I've never had issues with enblend
4.1.4.

> b) ... Enblend has two algorithms for generating primary seamlines:
> nearest-feature-transform and graph-cut.  While graph-cut is more
> sophisticated and produces better details, it can sometimes be
> completely wrong (such as unnecessary loops around half the image,
> something that looks like self intersections, and seamlines that get
> shifted to the boundary of the overlap areas).  My general advice
> would be to use graphcut, and if weird things happen, use NFT.
> Indeed I get perfect results if I use NFT for your test case, while
> there are some truly insane seamlines produced by GC.

I went looking for the enblend man page, but drew a blank.  All I have
is the --help.  You're talking about one of these, right?

  --primary-seam-generator=graph-cut
  --primary-seam-generator=nearest-feature-transform

I may try this.  Is it possible to have a less verbose variant?

> c) Version 4.1.4 was released ~9 years ago and I don't manage to
> compile it without installing old versions of boost and old
> compilers. So I didn't.

Yes, I had difficulty there too.  But it looks as if it might be worth
it.  None of these issues has shown up with 4.1.4.  What was wrong
in that version that required changes in the algorithm?

Greg
--
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Strange Hugin failure

[Greg 'groggy' Lehey]

On Friday, 14 June 2024 at 15:56:48 -1000, David W. Jones wrote:
> On 6/14/24 15:49, David W. Jones wrote:
>> Here's what I got after running the tapiola images through Hugin
>> Pre-Release 2023.0.0.548f2a905b6a using the Assistant. It looks like
>> there might be unnecessary images, maybe somewhere around 11, 12, 13,
>> 14. There were a lot of bad control points in that area. But I don't
>> think the final blend shows any big exposure changes.
>
> Well, got a message from Google Groups saying it has permanently
> removed my "illegal content," so I guess I won't bother. The
> generated image is 1.6MB, the PTO much smaller, let me know if
> you're interested.

Thanks.  It got through to me fine.  I'm still scratching my head
about what happened, but I'll get back to you and Thomas.

> Stupid Google.

It's not picking on you.  My first attempt at my message was also
rejected:
http://www.lemis.com/grog/diary-jun2024.php?subtitle=Google:%20You%20have%20violated%20our%20policy=D-20240613-021154#D-20240613-021154
I was particularly annoyed because they give me no choice of getting a
Real Human to look at the issue.  My guess is that they didn't like
the URLs I included in the first message.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

[hugin-ptx] Strange Hugin failure

[Greg 'groggy' Lehey]

A friend of mine recently published a panorama that he had stitched
from first principles with Mathematica.  It didn't look bad:

https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240608/small/tapiola-kirma.jpeg

Before you go looking at these individual links, I have a summary at
the bottom of this message.

But I thought it could be done better with Hugin.  I was wrong.

First, I ran it through my scripts, which effectively run pto_gen,
cpfind, celeste_standalone, cpclean and autooptimiser.  The result was
very uneven:

https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240608/small/tapiola-optimized.jpeg

OK, I thought that maybe I had something in my scripts that wasn't
doing the right thing, so I tried running it in a vanilla version of
Hugin without any ~/.hugin file.  Things were *much* worse.  Hugin
couldn't align the images at all.  It seems that it couldn't
understand the exposure info, and it made the component images
progressively darker:

https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240610/small/Tapiola-Hugin.png

It also came with a popup "The project covers a big brightness
range,".  But that's not what the images show.  They cover a range 9.8
to 11.4 EV, and that matches the lighting.  About the only thing
that's unusual is that the photos, taken with a Google Pixel 8 Pro,
were taken at a sensitivity of only 15 ISO.  But that shouldn't make
any difference.

I've tried this with the latest version of Hugin and also with a 5
year old one, and the results are the same.  You can see the summary,
with all the images above and more, at
http://www.lemis.com/grog/diary-jun2024.php?topics=p=Hugin%20fail=D-20240611-005714#D-20240611-005714
, and the images themselves are available at
http://www.lemis.com/grog/Day/20240610/tapiola-panorama-photos.zip
(about 400 MB).

Any ideas?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Problems stitching with newer versions of Hugin

[Greg 'groggy' Lehey]

On Tuesday,  7 May 2024 at 16:19:55 +, wirz wrote:
> On 07/05/2024 10:19, Greg 'groggy' Lehey wrote:
>> On Monday,  6 May 2024 at 15:58:31 +, wirz wrote:
>>> While I don't know what differs between the versions of hugin /
>>> enblend that are packaged in freeBSD, your images very much look
>>> like the old enblend bug that was fixed recently (earlier this
>>> year).  If your enblend is older than mid February 2024 / changeset
>>> 1556, I'd recommend to try a newer version.
>>
>> Yes, that sounds like a good idea.  Only: where do I find this
>> version?  Am I wrong in looking at http://enblend.sourceforge.net/?
>
> That's the right place, can get the current source here:
> https://sourceforge.net/p/enblend/code/ci/default/tree/

OK, done that.  It would be good if the README file included more
detailed build instructions.  It starts by running ./configure, which
is built in the first stages of install, and it took me a while to
find out how to build things.  I can't use the FreeBSD framework
because it would require significant changes.

I could suggest changes, but I don't know how they would affect
Microsoft and Apple.

So: I've tried things out, specifically enblend 4.3-e87da60fab22.
It's better, but not good.  I've put comparison images at

  
http://www.lemis.com/grog/photos/Photos.php?dirdate=20240511=011100

Click to enlarge.  They show the output from enblend 4.1.4, 4.2 and
4.3 respectively.  As you can see, 4.3 is better than 4.2, but not as
good as 4.1.4.  I've also put the build logs at

  http://www.lemis.com/grog/Day/20240511/Log-enblend-4.1.4
  http://www.lemis.com/grog/Day/20240511/Log-enblend-4.2
  http://www.lemis.com/grog/Day/20240511/Log-enblend-4.3

Let me know if you want the source images (a total of 683 MB).  For
some reason this particular view frequently suffers from this problem.
At one point I thought that this was masking, but there are no masks
today.  And the images were taken starting roughly in the middle of
the view.

Greg
--
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Problems stitching with newer versions of Hugin

[Greg 'groggy' Lehey]

On Monday,  6 May 2024 at 15:58:31 +, wirz wrote:
> On 06/05/2024 06:05, Greg 'groggy' Lehey wrote:
>> I've been making documentary panoramas of my house every week for the
>> past 10 years, and for a long time I was using version 2018.0.0 of
>> hugin on an old machine that I didn't plan to upgrade, running FreeBSD
>> 10.2.  I now have a new machine running FreeBSD 13.2 and Hugin version
>> 2023.0.0.d88dc56ded0e, but I'm having problems stitching panoramas
>
> What version of enblend are you using?

The version currently available at http://enblend.sourceforge.net/,
which identifies itself as 4.2.  But all the files are much older than
this year.

> While I don't know what differs between the versions of hugin /
> enblend that are packaged in freeBSD, your images very much look
> like the old enblend bug that was fixed recently (earlier this
> year).  If your enblend is older than mid February 2024 / changeset
> 1556, I'd recommend to try a newer version.

Yes, that sounds like a good idea.  Only: where do I find this
version?  Am I wrong in looking at http://enblend.sourceforge.net/?

Greg
--
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

[hugin-ptx] Purpose of this list (was: align_image_stack parameters)

[Greg 'groggy' Lehey]

On Wednesday, 17 April 2024 at 23:39:07 -0700, Chris wrote:
> T.Modes, Wie du sicher weißt, bedeutet das deutsche Wort "Gift" etwas ganz
> anderes als das englische Wort "gift" :).
> Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie
> haben etwas unterschiedliche Bedeutungen.
>
> (As I am sure you are aware, the German word "Gift" means something quite
> different to the English word "gift" :).
> Perhaps the words "impliziert" and "implies" are false friends - they have
> rather different meanings.)
> On Wednesday, April 17, 2024 at 7:33:51 AM UTC+1 Chris wrote:

Chris, I've seen a lot of messages from you.  This one seems to be the
second one with identical content.  And most of them seem to have
nothing to do with the software.

If you feel that you have to attack T.Modes, please do it privately.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Disappearing posts

[Greg 'groggy' Lehey]

On Monday,  8 April 2024 at 10:13:09 -0700, Chris wrote:
> This is my third post. The previous two attempts have both disappeared.
> There was no suggestion that they might have been awaiting moderation. What
> is going on?

I don't know, but I'd guess that it's at your end.  It's not
moderation: I got both copies within 2 minutes.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

[Greg 'groggy' Lehey]

On Thursday, 28 March 2024 at 18:09:38 -0700, Venkat wrote:
> Your example showed the file names in alphabetical order. My
> understanding was that this isn't what you wanted.

> We were providing alphabetical order so that even when we pass
> --sort we would end getting the right order (assuming sort does
> ascending). But you are right if the user knows the order then no
> need for "--sort" or having sorted order file names.

Somewhere round here I'm getting the feeling that we're
misunderstanding each other.  Anyway:

> That would be my guess. If you're running under Linux, why not
>   use the Linux version of Hugin? I'm sure it gets much more
>   developer attention. And then I guess you wouldn't need to do
>   anything special to get your images processed in a timely
>   fashion.
>
> Yeah, having a dedicated linux box would be ideal. Since we had a
> windows laptop we just enabled the linux subsytem on windows and
> tried the linux modules to see as a prototype.

Clearly this is another misunderstanding.  I thought you were running
Microsoft on top of Linux, in other words the other way round.

Still, you can get Hugin for Microsoft.  Why not install that and see
how it works?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

[Greg 'groggy' Lehey]

On Wednesday, 27 March 2024 at 13:44:34 -0700, Venkat wrote:
> Thanks for taking a stab at this.
>
>> You don't say how you "provide the individual images". If you
>> specify the names in the order you want, you're half way there. But
>> you're using the undocumented --sort option, which imposes the same
>> sort order. What happens if you do something like this?
>>
>> pto_gen -o output.pto 4.jpg 6.jpg 8.jpg 1.jpg 2.jpg 3.jpg 7.jpg 9.jpg 5.jpg
>> 10.jpg 11.jpg
>
> The above option ( ex - pto_gen -o output.pto 1.jpg 2.jpg 3.jpg
> 4.jpg 5.jpg ) still resulted in multiple combinations to find best
> matching pair.

Yes, but there's a subtle difference: as I said,

>> That's an example of out-of-order processing; substitute your own.
>> And note the lack of the --sort option.

Your example showed the file names in alphabetical order.  My
understanding was that this isn't what you wanted.  And you missed
this important part:

>> If your images are all in the same plane, --linearmatch is probably
>> what you're looking for.

Without --linearmatch, the sequence isn't important.  Still, all of
this may be overkill:

>> I'd be interested, though, in why your processing takes so long. Is
>> this a very slow machine, or are the images very large?
>
> Average size of image - 1.56 mb, resolution - 4000 x 1600 RAM - 20
> GB.

Nothing unusual in that.  I regularly stitch much larger images.

> It was running on Windows Subsytem For Linux ( Ubuntu 22.04 ). May
> be WSL is causing slowness.

That would be my guess.  If you're running under Linux, why not use
the Linux version of Hugin?  I'm sure it gets much more developer
attention.  And then I guess you wouldn't need to do anything special
to get your images processed in a timely fashion.

If you do this, it would be good to hear from you whether it improves
performance.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

[Greg 'groggy' Lehey]

[Rearranged for clarity]

Original post:

On Monday, 25 March 2024 at  8:55:19 -0700, Venkat wrote:
>
> We are trying to use the hugin assistant in code to stitch a panoramic
> image. We were wondering is there command line parameter to force the order
> of images. Currently the assistant figures out  by trying different
> combination in some cases its taking around a minute or two for a set of 11
> or 12 images. Since we know the order to be stitched wonder is there a way
> to force the assistant to use the designated order as opposed to trying all
> the permutations.  Any pointers would be really appreciated.

Current messages:

On Monday, 25 March 2024 at 23:48:02 -0700, Venkatramani Sankarlingam wrote:
> On Mon, Mar 25, 2024 at 4:09 PM Greg 'groggy' Lehey 
> wrote:
>
>> On Monday, 25 March 2024 at 11:19:52 -0700, Venkat wrote:
>>>
>>> Cool thanks for the note. I will see if we could tweak the
>>> assistant to handle cpfind --prealigned. If you have the
>>> information handy, it would be helpful as well.
>>
>> Again, I may be misunderstanding, but I'm not sure that --prealigned
>> would help here.  From the --help (for some reason this isn't
>> mentioned in the man page):
>>
>>   --prealignedMatch only overlapping images,
>>   requires a rough aligned panorama
>>
>> I haven't used it, but it seems that this is a second step, and I
>> think you're looking for the first.
>
> Thanks for the additional clarification. We are doing the following steps
> 1. pto_gen -o output.pto *.jpg --sort

OK, this is clearly not what you want.  You're selecting your files
sorted by name (*.jpg), when in fact you want to specify your own
order.

>  2. hugin_executor --assistant output.pto
>  3. hugin_executor --stitching --prefix=prefix output.pto
>
> And the images are numerically numbered starting from 0. And #2 and #3 can
> be potentially combined into one step. The above approach ends up trying
> all permutations.We also tried to provide the individual images during #1
> and ended up with the same result.

You don't say how you "provide the individual images".  If you specify
the names in the order you want, you're half way there.  But you're
using the undocumented --sort option, which imposes the same sort
order.  What happens if you do something like this?

pto_gen -o output.pto 4.jpg 6.jpg 8.jpg 1.jpg 2.jpg 3.jpg 7.jpg 9.jpg 5.jpg 
10.jpg 11.jpg

That's an example of out-of-order processing; substitute your own.
And note the lack of the --sort option.

I'd be interested, though, in why your processing takes so long.  Is
this a very slow machine, or are the images very large?

On Tuesday, 26 March 2024 at  9:30:13 -0700, Thomas Modes wrote:
>
> When the assistant checks all image pairs there is a wrong setting
> in the preferences.  Goto the menu File>Preferences, on tab control
> points detectors select reset to default.

Wouldn't it be a good idea to check what the current setting is first?
But I can't find how to do that in the GUI, and I can't find a "reset
to default" button, just "Load Defaults".  This is Hugin
2023.0.0.d88dc56ded0e.  But the information is all in the ~/.hugin
file.  Here an example entry that probably matches what Thomas is
saying:

  Description=Hugin's CPFind
  Program=cpfind
  Arguments=--multirow -o %o %s
  ProgramMatcher=
  ArgumentsMatcher=
  Option=1

POLA warning: this has changed at some point relatively recently.  In
my ~/.hugin I have:

  Description=Hugin's CPFind
  Program=cpfind
  Arguments=-o %o %s
  ProgramMatcher=
  ArgumentsMatcher=
  Option=1
  [AutoPano/AutoPano_1]
  Type=1
  Description=Cpfind (multirow/stacked)
  Program=cpfind
  Arguments=-o %o --multirow %s
  ProgramMatcher=
  ArgumentsMatcher=
  ProgramStack=align_image_stack
  ArgumentsStack=-f %v -v -p %o %i

That corresponds to two entries on the GUI preferences screen, Hugin's
CPFind and Cpfind (multirow/stacked).  So the old Hugin's CPFind no
longer exists, and has been replaced by the contents of Cpfind
(multirow/stacked).  Others might also be interested in this change.

It's not clear, though, that this is what you want.  --multirow only
makes sense when you have, well, multiple rows.  If your images are
all in the same plane, --linearmatch is probably what you're looking
for.  I don't know how to set it from the GUI, but you can edit the
.cpfind file.  Be sure to keep a backup in case something goes wrong.

> Then check the default control point setting, it should be cpfind
> and it should contain the --multirow switch in the settings.

Thomas: OK, where do I check this?  How do I change it?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microso

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

[Greg 'groggy' Lehey]

On Monday, 25 March 2024 at 11:19:52 -0700, Venkat wrote:
>
> Cool thanks for the note. I will see if we could tweak the assistant to
> handle cpfind --prealigned. If you have the information handy, it would be
> helpful as well.

Again, I may be misunderstanding, but I'm not sure that --prealigned
would help here.  From the --help (for some reason this isn't
mentioned in the man page):

  --prealignedMatch only overlapping images,
  requires a rough aligned panorama

I haven't used it, but it seems that this is a second step, and I
think you're looking for the first.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Providing order of images in Hugin assistant

[Greg 'groggy' Lehey]

On Monday, 25 March 2024 at  8:55:19 -0700, Venkat wrote:
>
> We are trying to use the hugin assistant in code to stitch a
> panoramic image. We were wondering is there command line parameter
> to force the order of images.

I don't understand the question.  If you're using the "command line",
simply name the images in the order that you want.  To make any sense,
you'd need the --linearmatch option.  Or am I missing something?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin making spiral panorama

[Greg 'groggy' Lehey]

[Rearranged for clarity]

On Tuesday, 20 February 2024 at  7:55:43 -0800, Graham Jantz wrote:
> On Monday, February 19, 2024 at 6:06:07 PM UTC-7 Groogle wrote:
>> My workaround, which works in 99% of the cases: start with a very few
>> images and align them in the fast panorama preview window. If the
>> partial result is good, save the .pto file. Add another couple of
>> images, align again. Save. Continue until all images have been
>> aligned.
>>
>> This is possibly not perfect. I've recently become aware of the
>> --linearmatch option to cpfind. The man page is vague, but my
>> understanding is that this causes cpfind to search for control points
>> only in adjacent images. That might solve the problem, but it won't
>> work for multi-row panoramas.
>
> Thanks for the tips. I was able to make some progress but it's not
> yet where I want it to be. I find it's trying to make control points
> between images that are far away from one another and I think that's
> what caused the spiral.

Yes, this is what I expected.  That's why I suggested just a few
points to start with.  Is that what you did?

> Here's what I've got so far but there's still another layer at
> the top that I haven't been able to get to line up. Also there's still lots
> of misaligned images.[image: DSC_0070 - DSC_0131_resize.png]

This suggests that you at least just did one row.  Without knowing
what the original looks like, it's not clear how good this pano is.

What you could do, which would also solve the --linearmatch issue, is
to create single row panos and then stitch them together.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin making spiral panorama

[Greg 'groggy' Lehey]

On Monday, 19 February 2024 at 14:08:36 -0800, Graham Jantz wrote:
> Hi all, looking for some advice on running Hugin. I have a panorama of 83
> photos that I'm trying to stitch together but the resulting image it's
> giving me is a weird spiral shape. I used the assistant and went through
> adding control points to images the did not have them and this still came
> out.

Occasionally I get something like this, for reasons that I can't
understand.

My workaround, which works in 99% of the cases:  start with a very few
images and align them in the fast panorama preview window.  If the
partial result is good, save the .pto file.  Add another couple of
images, align again.  Save.  Continue until all images have been
aligned.

This is possibly not perfect.  I've recently become aware of the
--linearmatch option to cpfind.  The man page is vague, but my
understanding is that this causes cpfind to search for control points
only in adjacent images.  That might solve the problem, but it won't
work for multi-row panoramas.

> Also don't love that it tried to color correct some of the images.

This problem might go away by itself once the images are correctly
aligned.  But you can tell Hugin not to change the colours.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2022.0 Black blotches on final stitches

[Greg 'groggy' Lehey]

On Saturday, 11 November 2023 at 22:08:34 -0800, Robert Mahar wrote:
> ( OK, well 2022.0.0.a0962865f932 )
>
> I often get black regions in final stitches.   For smaller projects, not
> often.

"Me too".  This seems to be happening more frequently.  Until recently
I was using the 2018 version, then 2022, and with 2022 things became
worse.

I'm still investigating, and so far I don't have any further
information, but at least I wanted to say that you're not alone.
Hopefully I'll come up with more information.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2023.0.0 released

[Greg 'groggy' Lehey]

On Saturday, 11 November 2023 at  0:58:54 -0800, T. Modes wrote:
>  Hi all,
>
> today we are releasing Hugin 2023.0.0

The FreeBSD port has been updated to this version.  Update your source
tree and build /usr/ports/graphics/hugin.  It will take a little
longer for the package to become available.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panoramas

[Greg 'groggy' Lehey]

On Tuesday, 22 August 2023 at 20:54:51 -0400, Hugin developers list wrote:
> The pop-up did occur and I chose do not link. The resulting image was very 
> wide and narrow.

Both wide and narrow?

I have difficulty believing this.  I've tried all three answers and
find that if I select "Link position", I get a panorama that is half
the expected width, and also ridiculous error values (667 average,
1297 maximum).  My guess is that this is what you selected.

The other two both generate what appear to be similar images.  Would
you please check again?  Specifically, you want the selection on the
left "Don't link position".

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panoramas

[Greg 'groggy' Lehey]

On Tuesday, 22 August 2023 at  8:24:24 -0400, Stanley Green wrote:
> Thank you Greg, I really appreciate all the work you guys are putting into 
> solving my problem
>
>> On Aug 22, 2023, at 7:48 AM, Greg 'groggy' Lehey  wrote:
>>
>> On Tuesday, 22 August 2023 at  6:57:45 -0400, Stanley Green wrote:
>>> The stitching problems only occur when using all three rows.
>>
>> And what were they?
>

> When I tried to stitch all three rows, Hugin thought that they were
> a stack and produced a stitch that bore no resemblance to the scene.

You did read this, right?

On Tuesday, 22 August 2023 at 10:27:39 +1000, Greg 'groggy' Lehey wrote:
>
> 1. Loading the files produced the popup
>
>  Hugin has image stacks detected in the added images and will
>  assign corresponding stack numbers to the images.  Should the
>  position of images in each stack be linked?
>
>That's incorrect.  There are no image stacks here, so you should
>answer No.  I've almost never seen this message, and I suspect it
>comes here because of the overlap between images.  30% should be
>enough.  This will give you fewer images and will greatly reduce
>the stitching time.

You can see an image of this popup at
http://www.lemis.com/grog/photos/Onephoto.php?dirdate=20230817=/grog/Photos/20230817/Hugin-fail-2.png

Did you not see it?  I've gone to the trouble to set the simple
interface, but the message still appears.  You should have selected
the first option ("Don't link position").  Did you do this?  Or did
the popup not appear?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panoramas

[Greg 'groggy' Lehey]

On Tuesday, 22 August 2023 at  6:57:45 -0400, Stanley Green wrote:
> I tried stitching different pair combinations.

A lot of detail missing here.

> Row 1 & 3: No problem
> Row 1 & 2: No problem
> Row 2 & 3: No problem

Except that the second and third variants only give you part of the
pano.

> The stitching problems only occur when using all three rows.

And what were they?

We've gone to a lot of trouble to investigate your problems.  One of
them seems to be lack of adequate problem reporting.  You don't even
say which method(s) you tried.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

On Monday, 21 August 2023 at 20:36:26 -0600, dgjohnston wrote:

> Greg, thanks for the additional information. The images in this set
> are well suited to the quick run though using the Fast Pano Preview
> because of the randomness of the rocks, trees, and water. It’s hard
> to detect any minor discrepancies like one would with images of
> manmade structures. With those the iterative process that David
> covered works well to get the best alignment.

... except that it didn't at first.  And I found it surprisingly
complicated.

> I don’t know why David’s version of Hugin wasn’t able to find
> connections between so many images. He used 2022.0 and I’m using
> 2022.1 (listed as pre-release).

FWIW, mine is ancient: 2018.0.0.  It's been some time since we've had
issues in this area.

> 1. Another reason that Hugin might be coming up with the “image
>stacks” is the difference in shutter speed of the images … they
>run from 1/125 s to 1/500 s (but I don’t know what Hugin is
>basing its decision on).

I'm not sure either, but I tried a second panorama with only the top
and bottom rows (leaving out the middle row).  I no longer got the
"has image stacks detected" message, and it stitched perfectly.  The
error was down to 1.9 average and 14.7 max.  See the second image at
http://www.lemis.com/grog/photos/Photos.php?dirdate=20230817
So my guess is that the overlap with the middle row confused it.

> Stanley … I’ve seen many suggestions that pano images be taken in
> manual mode with the settings base on the brightest part of the
> image.

Yes, that's the recommendation IIRC.  I used to set aperture priority
mode with my older panos (10 years or so ago), but then I started
using HDR images and moved to manual mode with 3 bracketed images:
+1.7 EV, +4.7 EV and -1.3 EV.

> Also, keeping the white balance fixed might help the colour
> tinting that shows up.

We only have TIFF images here, but my guess is that Stanley is using
raw images, so the colour balance doesn't really count.  But it would
be interesting to see what Hugin thinks.

> 2. After Align, I get a mean error of 5.5 pix with max 38.6.

That's strange.  But I've seen this before, years ago (round 26
December 2012 if you want to go searching).  You might also like to
look at
http://www.lemis.com/grog/diary-dec2012.php?subtitle=Control%20point%20detector%20or%20random%20number%20generator?=D-20121226-230249#D-20121226-230249

> I received the same colour tint issues that showed in David’s
> stitched image. The top-right corner has a green tinge.

Can you confirm that that's not the case with my images?  I
deliberately didn't try any tuning.
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] What do I wrong?

[Greg 'groggy' Lehey]

On Monday, 21 August 2023 at  3:42:13 -0700, Martin wrote:
>
> I just started to test Hugin, and prepared four well matching  levelled
> images . I got this bent panorama:

Without seeing the input files, it's hard to know if anything went
wrong.  But you can fix this from the Move/Drag tab in the Fast
Panorama Preview: there's a “Straighten” option that lets you bend the
pano to match reality.

If you need more help, please don't send images to this list.  If you
have difficulty finding somewhere to put them, we should discuss.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

On Sunday, 20 August 2023 at  6:34:23 -0400, Stanley Green wrote:
> If the link is still active, you can try to get the images directly:
>
> https://wetransfer.com/downloads/c5b1b40878f4f80c5b68af6a6767392b20230817102250/51d164ee951b6c084af7ed1d0d27730e20230817102250/2ee2fd

Thanks for that.

I'm confused.  A week ago I wrote:

On Tuesday, 15 August 2023 at 11:02:08 +1000, Greg 'groggy' Lehey wrote:
>
> My suggestion: use the Align tab on the Fast Panorama Preview.

Specifically,

1. Load the files from the "Load Images" tab in the Fast Panorama
   Preview.
2. Select "Align" from the Fast Panorama Preview.
3. Select "Create Panorama" from the Fast Panorama Preview.

And that's all.

In a little more detail for this specific panorama:

1. Loading the files produced the popup

 Hugin has image stacks detected in the added images and will
 assign corresponding stack numbers to the images.  Should the
 position of images in each stack be linked?

   That's incorrect.  There are no image stacks here, so you should
   answer No.  I've almost never seen this message, and I suspect it
   comes here because of the overlap between images.  30% should be
   enough.  This will give you fewer images and will greatly reduce
   the stitching time.

2. Aligning the images gave me an image with mean error 3.8 pixels,
   maximum 28.4.  Potentially you could improve on this with more
   attention to the position of the entrance pupil, but part of it
   will be due to the water, which doesn't stay the same from one
   image to the next.  You could tune the control points, but in this
   case I don't think you need to: I don't see any inconsistencies in
   the finished panorama.

3. "Create Panorama" offers you a choice of stitching options,
   defaulting to "exposure corrected, low dynamic range".  That's the
   one.

But that's all.  In particular, I don't understand the problems that
David W. Jones had, but then I don't understand the complexity either.
I also didn't see the colour discrepancies that he mentions.

So: the final image is at
http://www.lemis.com/grog/photos/Photos.php?dirdate=20230817
I have also put the .pto file at
http://www.lemis.com/grog/Day/20230817/GF_6-panels_-3-Rows-0-GF_6-panels_-3-Rows-17.pto
This will not be directly applicable, because I have removed the
spaces from the file names you provided.

Click on the image up to three times to increase the size up to the
original (about 113 MP).  Also let me know if you want this image
removed after we're done.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

On Thursday, 17 August 2023 at  6:12:55 -0400, Hugin developers list wrote:
> David,
> We transfer is not cooperating. I tried sending it several time to
> the email address shown on your responses to me.

I'm almost happy.  I set up an account, but it didn't make it clear
how it worked.

If you have an ftp client, you may be able to put the files on my
server.  Change to a directory that contains all the files that you
want to copy, and only those files.  Do something like this:

  $ ftp  www.lemis.com
  Connected to www.lemis.com.
  220 lax.lemis.com FTP server (Version 6.00LS) ready.

Here you will get a prompt for a user name.  Use ftp.

  331 Guest login ok, send your email address as password.

And here your real email address.

  230 Guest login ok, access restrictions apply.
  Remote system type is UNIX.
  Using binary mode to transfer files.

Note this previous line.  If you don't get it, enter the following
line:

  ftp> bin
  Using binary mode to transfer files.
  ftp> cd incoming
  250 CWD command successful.
  ftp> mput *

This tells ftp to copy all files in the directory

  mput e-from-house-0+0EV.tiff [anpqy?]? a
  Prompting off for duration of mput.
  229 Entering Extended Passive Mode (|||56930|)
  150 Opening BINARY mode data connection for 'e-from-house-0+0EV.tiff'.
   10% | | 12570 KiB  523.69 KiB/s  
  03:22 ETA
  ...

Let me know if you have any difficulties.  After we've taken a look at
the images, I'll remove them from the server.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

On Wednesday, 16 August 2023 at 13:35:48 -0400, Hugin developers list wrote:
> Beautiful day, less than beautiful results
>
> I shot a set of 18 images( 3 rows / 6 panels). I imported the raw
> images into Capture One and then exported the images as Tiffs. I
> tried to stitch the 18 images into a merged image using Hugin. Hugin
> was a disaster, I cannot begin to describe the mess.

That's a pity.  Without some description, there's little we can do,
though you should follow my previous suggestion, repeated by David,
and put the images somewhere where we can play with them.  The .pto
file that you generated would also be instructive.

> I am obviously doing something wrong.

My guess is that at the very least you didn't read the messages that
Hugin produced.  You did align the images, right?  Did you get the
message "2 unconnected image groups found: [0-4] [5-17]" or similar?

In any case, let's see the images and we can explain.  If C1 is too
polite to include the original Exif data, it would be good to know the
camera and lens(es).

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

On Monday, 14 August 2023 at 15:12:37 -0400, Stanley Green wrote:
> Is anybody familiar with this video tutorial? 
> https://www.youtube.com/watch?v=OaLNFKh82Dg
> "Producing multi-row image panoramas with Hugin"

No, I haven't watched it.  I'll try to find time to do so later.

> In this tutorial, the author created his control points using,
> “Feature Matching/Settings”. He chose an option called: “Cpfind
> (multirow/stacked)”.

Yes, I recall that.  I'm not sure that we need it any more.

> I am using Hugin version: 2019.2.0 (Mac), and when I go settings,
> I’m unable to find the Cpfind (multirow/stacked) option in the
> list. Is this a Mac issue or is he using a different version of
> Hugin?

It's still there in the version I use (probably not the newest), under
Feature Matching.  Your list looks like the one from Feature Matching,
so maybe it has gone away since then; somebody else could answer.

> On Mac v 2019.2, I see 6 choices:
>   1. cpfind

Until proof of the contrary, use this, but see below.

>   2. Cpfind + celeste (slower, but no cps on clouds)

I've found celeste to be singularly useless.

>   3. Align_image_stack

I've used this before.  In some cases, it might produce better results
than cpfind.  cpfind is newer, and initially there were some issues.

>   4. Align_image_stack Full Frame Fisheye

Unless you have a fisheye lens, this is clearly not needed.  I do most
of my panos with a full frame fisheye, and the standard cpfind does
just fine.

>   5. Vertical lines

Useful in some situations, but I've seldom found it useful.  In
particular, it may recognize things like trees as being vertical when
in fact they're leaning slightly.

>   6. Hugin’s CPFind (prealigned)

And I have no idea what this is.

My suggestion: use the Align tab on the Fast Panorama Preview.  If
that doesn't give you joy, try cpfind and possibly align_image_stack.
If you still can't get anything useful, there's more help on this
list.  Don't attach images: put them somewhere on the net and point to
them.

Good luck
Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panoramas

[Greg 'groggy' Lehey]

On Friday, 11 August 2023 at 17:57:46 -0400, Stanley Green wrote:
> I am trying to learn how to try to stitch a multi-row pano using Hugin (Mac).
>
> Tomorrow I plan to take 6 shots (2 rows, 3 shots per row) and see
> how it goes. Any tips for making work?

I used to make a lot of multirow panoramas, but I haven't done so for
a while.  But my recollection is that it Just Works.  Take your shots,
put them through the control point detector, and you should get what
you want.  My panos were 360�x180�, and I don't recall any particular
issues beyond finding a way to fake the nadir.  Try it and report.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: automatically solving vignetting at sunrise and down in a series of panoramas

[Greg 'groggy' Lehey]

On Wednesday,  5 July 2023 at 22:47:00 +0100, Bruno Postle wrote:
> Yes, something like this (all on one line, Google will mangle this email):
>
>   enblend -o project.tif -l 27 project.tif project0001.tif

Is this documented anywhere?  I see a brief mention of the syntax on
the man page, but not what it really does.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Vuze Camera 3D 360° VR. Parameters for import and stitching photo

[Greg 'groggy' Lehey]

On Wednesday,  1 March 2023 at 10:33:44 -0800, Francesco Sorrentino wrote:
>
> Il giorno mercoled� 1 marzo 2023 alle 17:47:25 UTC+1 T. Modes ha scritto:
>
>> Could you provide a sample set of images so we can have a look?
>
> Of course! Due to group size restrictions, I send four photos at a time
> (eight in total)

OK, I've taken a look at the images.  They don't overlap, which is
strange given the nature of the device, so Hugin can't find control
points.  What happens if you take another 8 images with the camera
offset by 45�?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] is "downscale final pano = 70% of max width" overriden by "calculate optimal size"?

[Greg 'groggy' Lehey]

On Sunday, 22 January 2023 at 10:38:34 -0800, T. Modes wrote:
> bruno...gmail.com schrieb am Sonntag, 22. Januar 2023 um 12:25:21 UTC+1:
>> This 'calculate optimal size' function uses the 70% default.
>
> The calculate optimal size button is using by default no additional scaling
> factor.  (So it ignores this setting. Except you hold the control button.)
> The downscale factor of 70 % is on the assistant tab in the preferences.
> This indicates that this setting is only used by the assistant.

The missing quote (now added) confused me.  I think you're saying what
I have observed: by default the pano is scaled to 70%, but "calculate
optimal size" sets it to 100%.  Right?

Thanks for the hint about the preferences.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

I've been chasing up a mail configuration problem delivering mail to
Gmail (hint: make sure you have an SPF record or similar), and in the
process came across this message and about 30 more that were filed as
spam:

On Friday, 21 January 2022 at 10:34:06 -0800, johnfi...@gmail.com wrote:
> I want to make a bunch of changes to the control point dialog.

(end quote)

I don't understand why; there's nothing obviously wrong with the
message, and unlike the problems that Gmail caused for my third-party
domain, both sender and mailing list are under the control of Google.
There were two other threads, also sent by people with Gmail accounts,
so maybe this is part of the problem.

It seems that Google is going over the top in trying to control spam,
and in the process it is rejecting valid mail.  I'm seriously
considering giving up my Gmail account.  If you have a Gmail account,
you should at least check the spam folder daily to see what surprises
Gmail has in store for you.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: How to export panos to Google Maps?

[Greg 'groggy' Lehey]

On Tuesday,  4 January 2022 at  4:03:54 -0800, Carlo wrote:
> Can anyone see this one?
> https://goo.gl/maps/xJxgPLeSrAdgLmQHA

Yes, looks fine; not too far from where I used to live.

> I just published it with iPhone and the Street View app.

And that's my problem.  WHY does Google insist on a mobile phone to
upload panoramas?  I can't get my head around it.  My original
question was

>> Groogle schrieb am Dienstag, 4. Januar 2022 um 00:10:48 UTC+1:
>>
>>> Only I can't find how to upload it. The only instructions still on
>>> the web require a MOBILE PHONE! Nothing about uploading from a
>>> computer.
>>>
>>> Can anybody help?

I'm sure that it was once possible.  And I'm sure that Google don't
use mobile phones to store their own images.  Why are they doing this?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

[hugin-ptx] How to export panos to Google Maps?

[Greg 'groggy' Lehey]

I have a relatively standard 180°x360° panorama of a street crossing
that I wanted to put on Google Maps.  I had investigated this some
time in the past and discovered that I needed various metadata if the
vertical angle wasn't 180°, and put it in the "too hard" basket.  But
this pano is complete.  Only I can't find how to upload it.  The only
instructions still on the web require a MOBILE PHONE!  Nothing about
uploading from a computer.

Can anybody help?

Greg
-- 
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] HDR Tutorial

[Greg 'groggy' Lehey]

On Saturday, 13 November 2021 at 16:32:12 -0500, Stanley Green wrote:
>
> I have one problem remaining with the finished panorama, if you look
> at the rocks on the left side of the image, you will see a
> ghost. Between images one and two the guy sat down.
>
> I was able to clone stamp it out in Affinity, but I???d like to know
> how to get rid of it before stitching.

If it's only in one of the images, mask it out.  Mask tab in the main
display.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin is driving me bonkers

[Greg 'groggy' Lehey]

On Wednesday, 14 July 2021 at 16:35:03 -0400, Hugin developers list wrote:
> Thank you. Yes, Affinity uses control points very similar to Hugin.
> I did not bother to insert CPs because I was only trying to point out that 
> Hugin was having trouble finding the cPs, but Affinity had no such problem.
> Being able to use Hugin is still my choice (when it works) because it has 
> fewer artifacts.

As Klaus Foehl says, you might like to read the instructions.  If you
don't bother to use the product the way it is intended, you can't
complain about it not doing what you want.  My guess is that Affinity
automatically does what it thinks you want, while Hugin gives you a
choice.  It even tells you what to do in the first of your images.  If
you don't make the choice, it won't do what you hope.

Please try to use it as intended and report your results.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

On Wednesday, 28 April 2021 at  4:31:07 -0700, Brian Charles wrote:
> 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?

Hugin doesn't see (disk) drives.  If anything, it sees mounted file
systems, but I don't understand what you mean by "see".  Can you
explain what you're trying to do?  Did it work before?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] [Request]: Resolve confusion between "Distance" and "Correlation"

[Greg 'groggy' Lehey]

On Monday,  8 February 2021 at 21:28:45 -0600, dgjohnston wrote:
> Before I use hugin I usually use DxO PhotoLab to correct for lens
> and camera body distortion.

Yes, I do that too.

> Does anyone know if DxO uses the Brown-Conrady lens model for their
> routines or anything similar?

The DxO developers will know.  Why don't you ask a question of
support?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] [Feature request]: Circle brush eraser for control points

[Greg 'groggy' Lehey]

On Monday,  1 February 2021 at  0:25:51 +, Hugin developers list wrote:
> I take many nature landscape panoramas in which most features are
> not straight like buildings. So when I want to remove CPs, the
> rectangle selection (Ctrl + right click) is unhandy, as I have to
> draw many rectangles to erase points on, say, a single tree.
>
> If there was a circular brush tool to erase control points, removing
> them would be much easier.
>
> Does this seem useful to users other than me?

Yes, this seems an excellent idea.

As people have told me on other projects when I come up with an idea
like this: "Send code".  I don't know how difficult it is, but my
guess is that nobody else will implement it.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2020.0 beta 1 release

[Greg 'groggy' Lehey]

[sequence recovered]

On Sunday,  3 January 2021 at 10:57:52 -0800, Abrimaal wrote:
> On Sunday, November 1, 2020 at 3:04:43 AM UTC+1 Groogle wrote:
>> On Sunday, 25 October 2020 at 1:58:55 -0700, T. Modes wrote:
>>> today we are releasing beta 1 of Hugin 2020.0.0
>>
>> A FreeBSD package is available at
>> http://www.lemis.com/pkg/hugin-2020.0.txz . I won't be committing the
>> port to the repository, because it will go away "soon".
>
> No changes since 2017. I am so sorry. I see it will be easier for me to buy
> 5 new hard drives, convert about a million photos to .png and continue the
> work.
> What does the sequence -ca-pah-2s_fd-cp-ph2c_bf-h-mk-b mean?
> This is the order of edits of a single photo. The photo has been processed
> in various software, Hugin, android apps, PC apps.
> If a photo is bad, no color space can help. Who cares of color space?

Sorry, I don't understand.  Do you want a copy of this package?  On
the face of it your content is unrelated to the message to which
you're replying.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: Man page problems (was: [hugin-ptx] Hugin 2020.0.0 released)

[Greg 'groggy' Lehey]

On Sunday, 13 December 2020 at  9:18:08 +, Bruno Postle wrote:
> On Sun 13-Dec-2020 at 11:43 +1100, Greg 'groggy' Lehey wrote:
>> On Saturday, 12 December 2020 at  5:40:30 -0800, T. Modes wrote:
>>>  Hi all,
>>>
>>> after a long beta 1 phase without bugs reported we are releasing today
>>> Hugin 2020.0.0
>>
>> It builds out of the box.  But where are the man pages?  They were
>> there in the beta.
>
> The man pages are ok here.  They are not normally shipped in the
> tar.bz2 source release, as they are created during the build by the
> pod2man tool.

Yes, that's what seems to have happened so far.  But since 2020.0.0
the build doesn't build the man page any more.  I didn't want to debug
the build process.  In each case I did a 'make all'.  The beta version
built the man pages (it seems), while the release version didn't.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Stitching vertical panoramas (was: Greetings and hello!)

[Greg 'groggy' Lehey]

You will probably get more responses with a descriptive Subject: line.

On Thursday, 12 November 2020 at 11:48:56 -0800, EM Matthews wrote:
> Is there a way to stitch together vertical panoramas using hugin?

The same way you stitch any panorama.  Hugin detects the control
points and arranges the images correctly.  I've done it in the past,
but haven't found it very useful.  The main issue I had was deciding
on a projection.

> I've checked out other applications that can do so, Lightroom, etc.,
> but can't seem to find any helpful information regarding hugin.

Do they need something special?

> Also, I'm using Darktable 3.0.

That shouldn't make any difference.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Some typo

[Greg 'groggy' Lehey]

On Sunday,  1 November 2020 at  9:11:01 -0800, Cristian Marchi wrote:
>
> Hi, while translating new strings I've found some typo:
>
> PanoOperation.cpp row 603 e 1277
> "...have to have to same size" I think it should be "...need to have the
> same size"

"Have to have" is perfectly correct grammar, though maybe it's a
little clumsy.  Without looking at the complete sentence, "should
have" seems a better candidate.

> Preview_frame.xrc row 1193
> "You have selected a fisheye as lens projection. It may necessary to mask
> out unused black space in the input image. Should the mask/crop tab now
> opened, where you can do this?"
>
> I think it should be something like:
> "You selected fisheye as lens projection. It may be necessary to mask out
> unused black area in the input image. Should the mask/crop tab be opened
> now to do this?

Yes, but the passive is to be avoided :-) And "open" is an overloaded
term.

"Do you want to select the mask/crop tab now to perform this operation?"?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2020.0 beta 1 release

[Greg 'groggy' Lehey]

On Sunday, 25 October 2020 at  1:58:55 -0700, T. Modes wrote:
> Hi all,
>
> today we are releasing beta 1 of Hugin 2020.0.0
>
> Source tarball can be downloaded
> at sourceforge:
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2020.0/hugin-2020.0_beta1.tar.bz2/download
> or at launchpad:
> https://launchpad.net/hugin/2020.0/2020.0beta1/+download/hugin-2020.0_beta1.tar.bz2

A FreeBSD package is available at
http://www.lemis.com/pkg/hugin-2020.0.txz .  I won't be committing the
port to the repository, because it will go away "soon".

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: No succes stitch spherical pano from Meike 6.5 mm circular fisheye.

[Greg 'groggy' Lehey]

On Monday,  5 October 2020 at 14:21:34 -0700, Henk Tijdink wrote:
> Hello Thomas
>
> Removing the control points in the Nadir did the job.

Did you read my reply?  For me it worked out of the box, and produced
better results than you attach.  See
http://www.lemis.com/grog/photos/Photos.php?dirdate=20201002

> But when I see the result in the preview screen you think it goes wrong.
> You see a lot of sawteeth in the preview.

Yes, as I said.  It's an issue with the *fast* preview screen.  The
normal preview works.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] No succes stitch spherical pano from Meike 6.5 mm circular fisheye.

[Greg 'groggy' Lehey]

On Friday,  2 October 2020 at  6:50:35 -0700, Henk Tijdink wrote:
> I have send the pictures with Wetransfer.

OK, I have good news and not-so-good news.

First the good news: the panos stitched out of the box with no
problems.  First I had to tell Hugin about the lens: circular fisheye,
190° FoV.  You can see the results at
http://www.lemis.com/grog/photos/Photos.php?dirdate=20201002.

The not-so-good news: the fast panorama preview makes a mess of the
display, and may be the reason that you thought it didn't work.  But
the normal preview (the one nobody uses) shows the display correctly.
This is probably a bug that needs to be corrected.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Auto calculation of Yaw, pitch and roll failed in some computers

[Greg 'groggy' Lehey]

On Thursday,  1 October 2020 at 21:46:17 -0700, Parasar Ghimire wrote:
> Hi Thomas,
> Thanks for replying. Please find the attached images. This set of pictures
> works on my computer when I align them but doesn't work on other computers.
> Please advise me if I am missing something.
> My general approach is:
> 1. import images into HUGIN
> 2. Set Lens type as Circular fisheye and focal length as 3.154
> 3. Click Align to auto-detect control points.
>
> The results are fine on my computers but fail in others as it isn't able to
> calculate yaw, pitch, and roll values. This is why I cannot recommend and
> standardize the process.
>
> https://drive.google.com/file/d/1AlkHTbkZIKkAhTS1QxT4Uh5SQLl6KV12/view?usp=sharing

OK, I've taken a look at the images.  I'm amazed that you can get them
to align at all.  There's barely any overlap.  And most certainly the
images as shown were not taken with a circular fisheye.  I selected
full frame fisheye (which is probably also stretching the case) and
got the first five without trouble.  I needed to add the sixth
manually.  And that's as far as I got.  I couldn't recognize any
connection between the last two and the rest.  I think it speaks
highly for Hugin that any version works.

Why don't you try again with more images?  Consider that the control
point detector needs to find at least 6 control points between images.
Think what points might be of use and ensure that they appear in at
least two images.  If all else fails (like the ground in your images)
you could consider putting something like a lens cap on the ground and
taking it in different images, then removing the cap and taking more
images, finally omitting the images with the lens cap from the final
panorama.

And why does this work on some computers and not others?  I've seen
similar issues in the past, but first you should check if you have the
same control point detectors on all the computers.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] No succes stitch spherical pano from Meike 6.5 mm circular fisheye.

[Greg 'groggy' Lehey]

On Thursday,  1 October 2020 at  7:33:02 -0700, Henk Tijdink wrote:
> Dear readers,
> I've bought a Meike circular fisheyelens 6.5 mm f2 for a MFT camera. and
> want to use it for making full spherical panorama's.
> You get than partly a circle  On the long side of the sensor it is shaved
> off. FOV there ca 120 degrees.
> Making 4 pictures at 90 degrees turn and in the demo of PTGUI it stitches
> perfectly.
> In Hugin however I can't get it all right.
> It finds control points between the images. I did the circular crop in the
> mask tab, but optimizing gives a very bad result.

I do this kind of panorama all the time using an Olympus 8 mm f/1.8
fisheye, also with 4 images, and it works fine.  If you can make the
images available online (NOT on this list!), I'll take a look at them,
at least in part because I was rather interested in this lens.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] enfuse is not compiled with GPU support even when enblend is....

[Greg 'groggy' Lehey]

On Thursday,  3 September 2020 at 15:12:19 -0700, Elias Tsolis wrote:
> Compiling enblend do not result support for GPU for enfuse. I followed
> these information for compiling hugin / enblend (included enfuse).
>
> ...
> Then, to get information on the extra features enabled in enblend i run:
> enblend --version --verbose
>
> it printed:
> enblend 4.1.5 Extra feature: dmalloc support: no Extra feature: image

Why are you installing this version?  The current version is 4.2,
released on 29 March 2016.  You might run into the same problem with
the current version, but you don't want to have to do it twice.

FWIW, I read the much less verbose output:

  Extra feature: image cache: no
  Extra feature: OpenMP: no
  Extra feature: OpenCL: no

That shouldn't happen, so I'll have to do some head-scratching.  I'll
report here if anything interesting crops up.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2019.2.0 released

[Greg 'groggy' Lehey]

On Monday, 30 December 2019 at  1:31:31 -0800, T. Modes wrote:
> Hi all,
>
> today we are releasing Hugin 2019.2.0
>
> Source tarball can be downloaded
> at sourceforge:
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2019.2/hugin-2019.2.0.tar.bz2/download
> or at launchpad:
> https://launchpad.net/hugin/2019.2/2019.2.0/+download/hugin-2019.2.0.tar.bz2

The FreeBSD port has now been updated.  The package will follow
shortly.

> Verify its checksums:
> md5:
> 3409c3a84e1881145b5b556df63de73c  hugin-2019.2.0.tar.bz2
> sha1:
> e91bfbb286d0d5f40cd93ecb961eb55a37f3f5bb  hugin-2019.2.0.tar.bz2

For those of us using SHA256, the details are:

  SHA256 (hugin-2019.2.0.tar.bz2) = 
8ba6bdfea246313f142f17f42e066c6888f51b72e4f8814b5e1c84ff56a95a3e
  SIZE (hugin-2019.2.0.tar.bz2) = 10335030

You don't need to worry about this, since the port automatically
checks.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Request : forum migration

[Greg 'groggy' Lehey]

On Friday, 22 November 2019 at 14:13:25 +, ChameleonScales' wrote:
> So I finally deleted my Google account completely and I'm sending
> this email as a test to see if copying the subject line from the
> topic's web page (in this case Re: [hugin-ptx] Re: Request : forum
> migration) puts it as a response in the right thread by using
> protonmail.

That's not sufficient.  To add a message to a thread, you need an
In-Reply-To: header.  For example, this message contains:

  In-Reply-To: 
<_d1TXT9v2l1Ldfp7tD9KZbNIfVeUzou3lO9WfEpAX59LPWdGYIsm3Fo-pRs4VBGLmDXRgH9SUWkQ5BSN5HCSCP_VSxCzLD2hQjJ9U1bJHLk=@protonmail.com>

You'll recognize your domain name there.  The rest was generated by
your mail system.  Without that, you will create a new thread.  To
avoid that problem, simply sign up for the group with your email
address and, as I said before, reply to the message that you're
referring to.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] How to email in existing topic

[Greg 'groggy' Lehey]

On Thursday, 21 November 2019 at 14:42:25 +, Hugin developers list wrote:
> Hi, sorry to ask but I didn't find an answer in the FAQ or
> elsewhere.  I just subscribed to the mailing list using my email
> (not a Google account) and I would like to add a post to an existing
> topic.

Adding a post to an existing topic is a reply.  Just reply to the
message to which you want to refer.  The polite thing is to remove all
irrelevant content and reply to the individual points.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] OpenGL preview button greyed out

[Greg 'groggy' Lehey]

On Tuesday,  1 October 2019 at 16:07:13 +0100, Bruno Postle wrote:
> I'm no expert, but this looks fine.
>
> I suggest deleting/renaming your ~/.hugin file to reset your preferences.

That's a bit drastic.  You can also just rename it:

 bash$ mv ~/.hugin ~/.hugout

That way you replace it if that wasn't the issue.  If it does work,
you can run diff against the two to see what has changed, and maybe
pinpoint what caused the problem.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Request : forum migration

[Greg 'groggy' Lehey]

On Tuesday, 23 July 2019 at  9:41:36 +0800, RizThon wrote:
>
> The discourse interface is from my point of view way better than
> google groups, but migrating to discourse will probably be quite
> some work and a change for all people used to the mailing list

Yes, I was thinking something like this.  My feeling is "if it ain't
broke, don't fix it".  I've seen lots of suggestions of how to
migrate, and clearly they will all involve effort.  I haven't seen
what's so wrong with Google.  Yes, they're not my favourites either,
but they're not that bad.  And I've seen at least one forum die after
migrating to a new platform.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Request : forum migration

[Greg 'groggy' Lehey]

On Sunday, 21 July 2019 at  7:09:18 -1000, David W. Jones wrote:
> On July 21, 2019 5:12:13 AM HST, "J. Schneider*"  wrote:
>> Hi,
>> I have a question about how Disourse or an alternative would be used.
>> My
>> short seach and wikipedia reading on Discourse didn't answer this.
>> What would a user have to do to read this forum and write to it? Would
>> it be manifest as a web page? Would a user have to be a member?
>> Seemingly there is also an app for mobile devices, but what does it
>> work
>> like for a Windows computer user?
>> (At the moment I use simply my e-mail client (Thunderbird) to read the
>> hugin mailing list and to me this is convenient as it is integrated
>> into
>> software I use anyway and messages are available without any
>> interaction
>> from my side.)
>
> Yes, that is why I hate web forums. I have to go there, login. With
> email, I just get my email as usual and posts are there.

+1

On Sunday, 21 July 2019 at 14:13:16 -0700, somebody masquerading as Hugin 
developers list wrote:
> Wait, I don't understand. You just confirmed that you need a google
> account, so this means you can't post without logging into
> Google. How does that require less steps than logging into any other
> service?

I can't speak for David, but I have my Google mail forwarded to a sane
email system, and that's where I read it, just like any other mail.
And that's how I answer, like now.  If I want to send a new message, I
send it to hugin-ptx@googlegroups.com.

We saw a couple of days ago the pain of using the Google web
interface, when somebody sent four messages without knowing it.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

On Monday, 15 July 2019 at 20:39:54 -1000, David W. Jones wrote:
> On 7/13/19 8:38 PM, Greg 'groggy' Lehey wrote:
>> I've tried all three of these distros.  I decided against Fedora, but
>> that was well over 10 years ago, so it's not relevant to modern
>> releases.  I think that if I were to start using Linux again, I'd go
>> for Debian, but for casual use Ubuntu is close enough.
>
> Ubuntu's easiest to install, I think.

Yes, that was my consideration.

>>> Ubuntu has a very effective upgrade process, too, but I think it
>>> only applies from LTS version to next LTS.
>>
>> Not really the issue here: I just want to see if the problems I see
>> also occur under Linux.  I'd be happy to reinstall every time.
>
> Try under VirtualBox, maybe?

Hugin doesn't really run well under VirtualBox.  I've tried it, but
it's a pain, and since I have the hardware lying around, there's no
reason not to use it.

>>> In both cases, I'd make a partition image or an fsarchiver copy
>>> before trying it.
>>
>> Not a snapshot?
>
> Not knowing what you mean by a snapshot... partition images.

VirtualBox offers snapshots: you can effectively freeze the contents
of the disk and return to older versions if you want.  But I was
thinking of file system snapshots, available on UFS and ZFS.  They do
pretty much the same thing.  I don't know which Linux file systems
support them.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

On Saturday, 13 July 2019 at 20:34:05 -1000, David W. Jones wrote:
> On July 13, 2019 5:51:33 PM HST, Terry Duell  wrote:
>> Hello Greg,
>>
>> On Sun, 14 Jul 2019 12:20:10 +1000, Greg 'groggy' Lehey
>>  wrote:
>>
>>> I'm seeing a few issues with Hugin running on FreeBSD.  While I don't
>>> think it has anything to do with FreeBSD, it would be nice to compare
>>> its behaviour with what happens under Linux.  What distro should I
>>> choose?
>>
>> I've been a Fedora user for almost as long as I remember, and regularly
>>
>> test build hugin, enblend and darktable. All work with minimal problems.
>> One of the nice things about Fedora (these days) is the very nice
>> upgrade process they have for the new release every 6 or so months...
>> a great improvement over the old days. Other distros may be be as good
>> in this respect, but I only have experience with Fedora.

I've tried all three of these distros.  I decided against Fedora, but
that was well over 10 years ago, so it's not relevant to modern
releases.  I think that if I were to start using Linux again, I'd go
for Debian, but for casual use Ubuntu is close enough.

> Ubuntu has a very effective upgrade process, too, but I think it
> only applies from LTS version to next LTS.

Not really the issue here: I just want to see if the problems I see
also occur under Linux.  I'd be happy to reinstall every time.

> Debian - I run Debian Testing, so it's sort of like a rolling distro
> to me. I think Debian Stable changes are possible now: a recent
> Debian apt update displayed a message asking for permission to change
> distro pointers to the new Testing. That *could* mean that a similar
> pointer change with a clean/update/dist-upgrade might migrate an
> installed Debian Stable to the new Stable.
>
> In both cases, I'd make a partition image or an fsarchiver copy
> before trying it.

Not a snapshot?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Linux distro of choice?

[Greg 'groggy' Lehey]

I'm seeing a few issues with Hugin running on FreeBSD.  While I don't
think it has anything to do with FreeBSD, it would be nice to compare
its behaviour with what happens under Linux.  What distro should I
choose?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Removing control point detectors (was: autopano-sift-c failed with error code: 2)

[Greg 'groggy' Lehey]

On Thursday, 20 June 2019 at 10:34:39 +0200, Jens Scheidtmann wrote:
> Hi Greg,
>
> Am Do., 20. Juni 2019 um 04:05 Uhr schrieb Greg 'groggy' Lehey
> :
>>
>> On Tuesday, 18 June 2019 at  9:46:32 -0700, T. Modes wrote:
>>> Am Dienstag, 18. Juni 2019 02:25:15 UTC+2 schrieb Groogle:
>>>>
>>>> Please don't remove panomatic until cpfind functions reliably under
>>>> all circumstances.
>>>>
>>> I'm not aware of problems with cpfind. There are no reports in the bug
>>> tracker or recently here on the list.
>>
>> I wasn't aware of a bug tracker, and I can't find any reference on
>> http://hugin.sourceforge.net/.  Where is it?  It would be a good idea
>> to add a link on the home page.
>
> The "Tech" page links to "Launchpad", there's a bug tracker:
>
> https://bugs.launchpad.net/hugin

Thanks.  It's well hidden.  I'll use it when I have something to
report.

On Thursday, 20 June 2019 at  9:15:20 -0700, T. Modes wrote:
> Am Donnerstag, 20. Juni 2019 04:05:38 UTC+2 schrieb Groogle:
>>
>> I wasn't aware of a bug tracker, and I can't find any reference on
>> http://hugin.sourceforge.net/.  Where is it?  It would be a good idea
>> to add a link on the home page.
>>
> There is a link on the homepage in the main menu.

I assume you're talking about the "Launchpad" link.  I wouldn't have
recognized it if I hadn't read Jens' mail first, and I might have
missed the submenu "bugs".

> (Maybe the label could be better, but then the whole menu would
> increase).

What's wrong with that?  A link that nobody understands is of little
use.  I still don't understand the text "Launchpad".  It certainly
doesn't sound like anything to do with bug reports.

> Also the main help page of Hugin contains a link to it.
> Furthermore the bug tracker was mentioned (with link) for each release of
> betas/rcs in the last years.

Certainly not a disadvantage, but by no means a substitute for clear
web page navigation.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Removing control point detectors (was: autopano-sift-c failed with error code: 2)

[Greg 'groggy' Lehey]

On Tuesday, 18 June 2019 at  9:46:32 -0700, T. Modes wrote:
> Am Dienstag, 18. Juni 2019 02:25:15 UTC+2 schrieb Groogle:
>>
>> Please don't remove panomatic until cpfind functions reliably under
>> all circumstances.
>>
> I'm not aware of problems with cpfind. There are no reports in the bug
> tracker or recently here on the list.

I wasn't aware of a bug tracker, and I can't find any reference on
http://hugin.sourceforge.net/.  Where is it?  It would be a good idea
to add a link on the home page.

I've reported these bugs in the past, and discussed them with you.
I'll do so again.  I haven't put them in the bug tracker because I'm
trying to find a cause.  I do a weekly series of panoramas round my
house, and almost every time I run into problems.  Now that I go back
to try to reproduce them, of course, I can't find them, but next time
it happens (probably on Saturday), I'll report here, and to the bug
tracker if I have found it by then.

> No program will work under *all* circumstances.
> (panomatic is unmaintained also since 10 years and it has also problems
> with fisheye lens.)

My problems were with fisheye lenses, and in some cases panomatic did
better than cpfind.

> Also only the default setting will be removed. An user who needs it can add
> it every time.

Good to hear.  But how does the user know what to add?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Removing control point detectors (was: autopano-sift-c failed with error code: 2)

[Greg 'groggy' Lehey]

On Monday, 17 June 2019 at  8:27:35 -0700, T. Modes wrote:
> Am Montag, 17. Juni 2019 11:52:21 UTC+2 schrieb Henk Tijdink:
>>
>> When you take Autopano Sift-C from the default settings, then yoy can take
>> away Autopano (A. Jenny) from the default settings too.
>>
> I will remove all other cp generator settings (except cpfind and
> align_image_stack).

Please don't remove panomatic until cpfind functions reliably under
all circumstances.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] stitching 4 pictures with meike 6.5mm f2.0

[Greg 'groggy' Lehey]

On Friday,  3 May 2019 at 11:27:38 -0700, giuseppe.porci...@gmail.com wrote:
> Hi,
>
> I have problems in stitching 4 pictures from a sony a5000 (aps-c) and meike
> 6.5 f/2.0 manual lens.
> I choosed "fisheye circular lens" and I inserted a 190 degree HFOV value
> (as for meike specs) and also 185 degree HFOV, maybe more accurate.
> I also cropped the circular fisheye images in Hugin crop tab as suggested
> in the forum but I obtained strange stitched image.
> The pictures may be downloaded here:
>
> http://www.visteappiedi.it/meike4/DSC00602.JPG
> http://www.visteappiedi.it/meike4/DSC00603.JPG
> http://www.visteappiedi.it/meike4/DSC00604.JPG
> http://www.visteappiedi.it/meike4/DSC00605.JPG
>
> If anyone could give a try in stitching the images and give any
> suggestions it would be a great help for me.

OK, I've taken a look at this.  By accident I used the panomatic
control point detector instead of cpfind, and it only found relations
between some of the images, not unusual for panomatic.  But with
cpfind it went completely crazy until I cropped the images.  And then
it still didn't find any control points between some of the images.

I've found in the past that an attempt to add control points manually
is doomed to failure, so I added some first and then ran “Align†.
Yes, it closed the panorama, but badly, and I discovered that it did
not add any additional points at all.

Why?  Clearly a limitation in cpfind; I have them as well, and I'm
still trying to understand them.  But one thing struck me: the images
are not overly sharp.  Looking at the 1/4000 s shutter speed and the
ISO 100, I would assume that you took these images at maximum f/2
aperture.  You might make life easier for the control point detectors
if you stop down to, say, f/4 or f/5.6.

I'm attaching the project file that I generated with the manual
control points.  You might like to play around with it.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20190505034453.GA67928%40eureka.lemis.com.
For more options, visit https://groups.google.com/d/optout.
# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360  E15.5805 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin  autoCenterCrop=1 cropFactor=1.6
i w5456 h3632 f2 v198.421018983846 Ra0 Rb0 Rc0 Rd0 Re0 Eev15.580494060253 Er1 
Eb1 r0 p-44.9946191425074 y-89.9892382850148 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a0 b0 
c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  S871,4585,0,3632 Vm5 n"DSC00602.JPG"
#-hugin  autoCenterCrop=1 cropFactor=1.6
i w5456 h3632 f2 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev15.580494060253 Er1 Eb1 r0 
p-44.9946191425074 y0 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 
Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  S871,4585,0,3632 Vm5 n"DSC00603.JPG"
#-hugin  autoCenterCrop=1 cropFactor=1.6
i w5456 h3632 f2 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev15.580494060253 Er1 Eb1 r0 
p-44.9946191425074 y89.9892382850148 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a=0 b=0 c=0 
d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  S871,4585,0,3632 Vm5 
n"DSC00604.JPG"
#-hugin  autoCenterCrop=1 cropFactor=1.6
i w5456 h3632 f2 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev15.580494060253 Er1 Eb1 r0 
p44.9946191425074 y-89.9892382850148 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a=0 b=0 c=0 
d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  S871,4585,0,3632 Vm5 
n"DSC00605.JPG"


# specify variables that should be optimized
v Ra0
v Rb0
v Rc0
v Rd0
v Re0
v Vb0
v Vc0
v Vd0
v Eev1
v r1
v p1
v y1
v Eev2
v r2
v p2
v y2
v Eev3
v r3
v p3
v y3
v


# control points
c n0 N1 x3950.25104898375 y670.749615780793 X1954.0766034 Y705.1189921 
t0
c n0 N1 x3792.0558678 y3078.1321817 X2003.65615133985 Y2920.93220760406 
t0
c n0 N1 x3532.39724017721 y2786.5860541577 X1454.00531826086 Y2772.99104590537 
t0
c n0 N1 x3615.1286934 y892.0915373 X1399.36994575833 Y851.956625120782 
t0
c n1 N2 x4065.63126381838 y2522.36231974598 X2093.26064224115 Y2465.75720758945 
t0
c n1 N2 x4244.0781819 y2347.1294458 X2252.87110364994 Y2273.5925553044 
t0
c n1 N2 x3508.64844341689 y2819.54822403447 X1742.4161072503 Y2844.77857409062 
t0
c n1 N2 x3858.0934511 y2043.1129059 X1599.19914917959 Y2037.56402857473 
t0
c n2 N3 x2766.47960350229 y2501.49826972342 X1281.49520591271 Y2554.28434493281 
t0
c n2 N3 x3894.0934617 y2036.1135698 X2106.88594446722 Y2007.8723838625 
t0
c n2 N3 x3780.0725167 

Re: [hugin-ptx] Re: Hugin 2019 crash at startup

[Greg 'groggy' Lehey]

On Friday,  3 May 2019 at 20:11:23 +0200, giuseppe porciani wrote:
> 2019-05-03 8:52 GMT+02:00, T. Modes :
>> Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle:
>>>   (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time()
>>>   should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the 
>>> timestamp
>>>   should instead be gathered at the time the user initiated the request for 
>>> the
>>>   window to be shown
>>>   zsh: segmentation fault (core dumped)  hugin
>>
>> This warning is strange. Neither hugin nor wxWidgets are using this
>> function.
>>
>> If the settings and a corrupted installation are excluded, I would try to
>> test if OpenGL works. Try starting another program which uses OpenGL, e.g.
>> glxgears
>
> Thank you very much!

Are you experiencing this problem too?  If so, could you please give
more details, in particular software versions.  So far I'm completely
puzzled.

[HTML code omitted]

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Hugin 2019 crash at startup

[Greg 'groggy' Lehey]

On Thursday,  2 May 2019 at 23:52:24 -0700, T. Modes wrote:
> Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle:
>>
>>   (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time()
>>   should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the 
>> timestamp
>>   should instead be gathered at the time the user initiated the request for 
>> the
>>   window to be shown
>>   zsh: segmentation fault (core dumped)  hugin
>
> This warning is strange. Neither hugin nor wxWidgets are using this
> function.

Possibly an internal call?

> If the settings and a corrupted installation are excluded, I would
> try to test if OpenGL works. Try starting another program which uses
> OpenGL, e.g.  glxgears

Thanks for the suggestion.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

On Monday, 29 April 2019 at 19:04:23 -0700, James Proctor wrote:
> On Monday, April 29, 2019 at 6:26:49 PM UTC-7, Groogle wrote:
>>
>> On Monday, 29 April 2019 at 18:19:23 -0700, James Proctor wrote:
>>> If you have ideas re. my bigger problem of creating a true 360° pano
>>> from the original fourteen images, I'd appreciate! See earlier posts
>>> in thread for clarification.
>>
>> As I suggested, put the images somewhere where somebody can take a
>> look at them.
>
> Um, I did!...see my reply from earlier today (PanoImages.zip).

Oh.  I wasn't expecting them as an attachment.  That's generally
frowned upon because of the size, though in this case it's not too
bad.

These images stitch out of the box for me.  Take a look at
https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20001224/small/Pano-orig.jpeg
and
https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20001224/small/Pano.jpeg.
The former is literally without any tweaks, the latter has been
automatically optimized for colour.  The project file is at
http://www.lemis.com/grog/Photos/20001224/DSC1-DSC00014.pto

So what went wrong with your stitching?  I really don't know.  I
checked my suspicion that it might be the vertical control points, but
even with them it worked perfectly.  I did this a couple of times,
once with a focal length multiplier of 8, the other with 10, and they
both worked fine.  The best you could do would be to compare the
project file with the one I refer to above.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

On Monday, 29 April 2019 at 18:19:23 -0700, James Proctor wrote:
> If you have ideas re. my bigger problem of creating a true 360° pano
> from the original fourteen images, I'd appreciate! See earlier posts
> in thread for clarification.

As I suggested, put the images somewhere where somebody can take a
look at them.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

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

[Greg 'groggy' Lehey]

On Sunday, 28 April 2019 at 16:34:44 -0700, 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.

My first thought looking at that pano is that the horizon looks as if
it has been bent.  Is the ground really like that?  In particular, the
trees at the left are leaning to the left, but they're coming out of
the ground at 90°.

Do you have vertical control points?  I've found them to be more of a
problem in this kind of pano.  Check in the Assistant tab: uncheck
"Detect vertical lines".

Otherwise if you can put the source images somewhere, we can take a
look at them.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Hugin 2019 crash at startup

[Greg 'groggy' Lehey]

I've received a bug report against Hugin 2019.0 running on FreeBSD:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237585

Summary: after "normal" error messages on startup, it receives:

  (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time()
  should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the timestamp
  should instead be gathered at the time the user initiated the request for the
  window to be shown
  zsh: segmentation fault (core dumped)  hugin

It's not clear whether the error message and the SIGSEGV are related.
I also don't believe that this is directly related to FreeBSD or
version 2019 ("It works for me").  Does anybody have any suggestions
about what I should look for?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Is there a tutorial for stitching dual lens photos?

[Greg 'groggy' Lehey]

On Tuesday,  9 April 2019 at 18:05:44 -0700, CarbonMan wrote:
> I have a Samsung Gear 360. I would like to convert an image into a skybox.
> How do I go about doing that? I have only used Hugin for stitching when
> there were multiple images that needed to be stitched together. In this
> case there are 2 images within the 1 picture.

I don't think that Hugin caters for that.  But the solution is simple:
crop the image twice to extract the individual images, then stitch
them.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2019.0.0 released

[Greg 'groggy' Lehey]

On Friday,  5 April 2019 at 23:39:27 -0700, T. Modes wrote:
> Hi all,
>
> today we are releasing Hugin 2019.0.

The FreeBSD port has been updated.  You can build from source now, and
in a few days the package will be available.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] stitching two circular fisheye images

[Greg 'groggy' Lehey]

On Friday,  5 April 2019 at  7:14:20 -0700, giuseppe.porci...@gmail.com wrote:
> Hi,
> I would like to use hugin to stitch 2 circular fisheye image.
> I have a sony a5000 aps-c camera and I would like to buy a meike 6.5mm
> circular fisheye lens for sony aps-c sensor.
> The image will fit into the sensor as a circle image, FOV is 190 degrees as
> stated in lens specs.

I don't have anything to add on the procedure, but maybe a thing to
think about: what do you have from a circular fisheye lens?  It may
have other purposes, but for Hugin you will probably find it easier
with a full frame (field of view, not sensor size) fisheye.  I do that
on a regular basis, and I don't have to do anything specific (once I
have initially told Hugin that it's a fisheye lens, so that it can
note it in its database).

> Should I only insert the lens specs or I need some other specific
> settings (or procedure) in order for Hugin to stitch properly two
> images in one equirectangular 360x180 image?

Even with the Meike, you won't get that from two images.  Assuming
that you really get your 190°, that's only horizontally.  My program
tells me that you won't get that vertically, and you need some
overlap:

  Focal length: 6.50 mm
  Horizontal FOV: 208.03°
  Diagonal FOV:   249.86°
  Vertical FOV:   138.39°
  Panorama steps (30% overlap):
  Horizontal: 146°
  Vertical:97°

The angles beyond 190° are theoretical; that's the part that's blacked
out.  And the sample images I've seen, such as at
https://www.dpreview.com/forums/thread/4121672 , confirm this.  It
suggests that you'll need at least 6 images to get a full 360x180
panorama.

--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Hugin 2019.0.0 rc1 released

[Greg 'groggy' Lehey]

On Saturday, 23 March 2019 at  2:05:42 -0700, T. Modes wrote:
> Hi all,
>
> today we are releasing release candidate 1 of Hugin 2019.0.

If anybody wants a FreeBSD port, please contact me.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: nona, verdandi and --wrap parameter

[Greg 'groggy' Lehey]

On Tuesday,  1 January 2019 at 23:48:44 -0800, T. Modes wrote:
> Am Dienstag, 1. Januar 2019 09:45:40 UTC+1 schrieb stephan...@wanadoo.fr:
>>
>> I'm trying to use Hugin to batch stitch many partial equirectangular
>> panorama made with my custom rig (Xiaomi Yi 2k x4)
>> 
>>
> For partial equirectangular panos the wrap switch is not needed.
>
> #hugin_verdandiOptions --wrap --seam=blend
>
>> The script stopped with this error :
>>
>>> /usr/bin/nona: invalid option -- 'w'
>>
>> Is that a bug ?
>
> The wrap parameter is automatically handled by
> nona/hugin_stitch_project/PTBatcherGUI depending on the output
> settings in the pto file. There is no need to fiddle with that
> parameter by hand.

Do I understand this exchange correctly?  I had thought that it
implied that the --wrap option in hugin_verdantiOptions was causing
the invalid flag -w to be passed to nona.  If that's the case, I would
have thought that this is a bug.

Greg
--
Sent from my desktop computer.
Finger g...@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Aligning multiple image stacks in the same pano - any way to do this automatically?

[Greg 'groggy' Lehey]

On Friday, 19 October 2018 at 19:42:34 -0700, Geoffrey Liu wrote:
> I have a panorama, 42 images in total, 14 frames of 3 exposure stacks each.
> As part of my workflow, I align the 3 images in each stack.
>
> So far the only way I've found to do this is to:
>
> ...

I do something very similar.  I used to merge the exposure stacks with
align_image_stack and enfuse.  This has the advantage that it can be
embedded in a Makefile and made completely automatic.  The script is
at http://www.lemis.com/grog/src/HDR , but it's rather tied to my way
of processing things.  If you try it, feel free to ask me private
questions.

I no longer use this method.  It doesn't handle ghosting At All, and
I've finally given in and used a Microsoft-space program, Photomatix
(http://www.hdrsoft.com/), which seems to do a good job with batching.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] libpano gcc 8 warnings

[Greg 'groggy' Lehey]

On Sunday, 23 September 2018 at 23:43:38 +0100, Bruno Postle wrote:
>
>
> On 23 September 2018 13:48:10 BST, Andreas Metzler wrote:
>>
>> building libpano with gcc 8 (instead of 7) triggers a couple of new
>> warnings that might be interesting:
>>
>> parser.c: In function 'ReadImageDescription':
>> parser.c:1854:38: warning: '%s' directive writing up to 65535 bytes
>> into a region of size 256 [-Wformat-overflow=]
>> sprintf( sBuf.destName, "%s", buf );
>>  ^~   ~~~
>
> It looks harmless to me, but my C isn't good enough to say for sure.

I think what it's trying to say is "consider using snprintf ()".

> Along with the earlier typos I'm inclined to release the release
> candidate, since it has been waiting so long, then fixes for these
> can go into the next release.

Sounds reasonable to me.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Offensive behaviour (was: Wrong assumptions)

[Greg 'groggy' Lehey]

On Wednesday, 19 September 2018 at  8:22:08 -0700, T. Modes wrote:
> Am Mittwoch, 19. September 2018 06:00:08 UTC+2 schrieb Groogle:

Nein, er schrieb das am Mittwoch, 19. September 2018 14:00:03 +1000.
Er hat mit UTC+2 nichts am Hut.  Wo die 5 Sekunden Versatz entstanden
sind, ist mir ein Rätsel.

>> Sorry, but is wrong.  I spent quite a bit of time going through this
>> page a while back, and it contains numerous issues.  Apart from
>> autopano-sift-c, in the main text there are also references to
>> autopano-sift, match-n-shift, ptoinfo, ptscluster, ptoclean,
>> ptovariable and panostart, as well as to the pano.mk file that no
>> longer exists.
>
> Next time, before answering, check your facts.

I checked my facts.

> Have you checked your facts?

Yes.

> Match-n-shift, ptoinfo, ptoclean, ptovariable and panostart are part
> of the Panotools::Scripts. There are still available, are up to date
> and work with the current Hugin version. They are not obsolete like
> you claim.From the linked wiki page:

I stand corrected.  The document is not only out of date, it's also
incomplete.  The location of those programs is not described in this
document, and that's what we're talking about.

> 
> Panotools::Script for manipulating project files
>  Many of the command-line tools described in this document are
> written with this library.
> 

Which?  This is incomplete.  It's also in the wrong place.  Let's take
an example:

Is:
 match-n-shift - All in one wrapper around align_image_stack and autopano-sift-c
Should be:
 match-n-shift - All in one wrapper around align_image_stack and
  autopano-sift-c, part of Panotools::Script

This section also needs sorting.  align_image_stack is a forward
reference.

> Remaining autopano-sift-c, autopano-sift and ptscluster,

Wouldn't that have been enough?

>> From the wiki page:
>
> 
> Hint: Other control points generator, such as autopano-sift,
> autopano-sift-c, panomatic and match-n-shift 
> 

Yes, I saw that.  Your point?  It's a reference to a programs that are
no longer in Hugin and commands that are part of an unmentioned script
library.  For me, that's an indication that the document is
incomplete.

> 
> Other control point cleaners are ptscluster and ptoclean. cpclean has
> largely replaced ptoclean
> 

Again, I don't see what point you're trying to make here.

> These are mentioned in a hint/footnote.

The only other reference to ptoclean is in the list of commands.  The
link takes you to a page https://wiki.panotools.org/Ptoclean, which
doesn't exist.  Your point?

> So when there are some smaller references to older programs in
> footnotes, you declare the whole page "very out of date."

No, "horribly out of date".  To that I add "incomplete and
misleading".

> So it seems I have another definition of "up to date" than you???

Yes, so it seems!!!  Your definition seems to be "defendable" rather
than usable.  I don't accept it.  You have found what you consider to
be a sufficient excuse.  It may be sufficient to you, but it isn't to
me, and I assert that it isn't to a beginner.  The document is broken.

Your continuous obnoxious behaviour shows that you don't understand,
or that you don't want to.  And I note that you avoided answering any
of my comments on the effect on the project of this attitude.  As a
result, I plan to look for alternatives to Hugin.  This wouldn't have
happened if the project team were interesting in improving the
current situation.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Offensive behaviour (was: BigTIFF)

[Greg 'groggy' Lehey]

This is mainly addressed to Thomas Modes, but since it's not the first
time I've seen him behave like this, I think it's time to come out in
the open.

On Tuesday, 18 September 2018 at 10:00:34 -0700, T. Modes wrote:
> Am Dienstag, 18. September 2018 05:46:34 UTC+2 schrieb Groogle:
>>
>> There is one at
>> https://wiki.panotools.org/Panorama_scripting_in_a_nutshell, but it's
>> horribly out of date.  I've been meaning to update it, but I've always
>> found something more rewarding to do.  In particular, it makes
>> reference to obsolete programs.
>
> Sorry, but is wrong. The main part with the description is up to
> date.  The only one obsolete program in the main part is
> autopano-sift-c - but this is only shown as alternative; the
> mentioned main program cpfind is still part of Hugin.

Sorry, but is wrong.  I spent quite a bit of time going through this
page a while back, and it contains numerous issues.  Apart from
autopano-sift-c, in the main text there are also references to
autopano-sift, match-n-shift, ptoinfo, ptscluster, ptoclean,
ptovariable and panostart, as well as to the pano.mk file that no
longer exists.

In the "Full list of command-line [sic] tools", only 5 of the first 10
tools still exist.  I also seem to recall that some of the options are
also no longer relevant, though I could be wrong here.

This list also contains the line:

autopano - Keypoint matcher, part of autopano-sift-c and not to be confused 
with autopano

Well, I'm confused.  Beginners certainly will be.

Maybe you have a different definition, but for me this is very out of
date.

I had intended to bring this page up to date.  Based on this attack,
you will understand that I am now disinclined to do so.  It will
remain out of date until somebody else who recognizes the problem also
finds time and inclination to do something about it.

> The next time be more precises what you are referring instead of
> make such general and diffuse statements.

Next time, before answering, check your facts.  You come across as
offensive and inaccurate, not for the first time.  This attitude also
greatly reduces people's willingness to cooperate in the project.  A
few years back a whole lot of people were involved in the project.
Now you seem to be the only one.  It would be easy to get the
impression that your attitude has something to do with this.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: BigTIFF

[Greg 'groggy' Lehey]

On Monday, 17 September 2018 at 16:30:17 -0700, Battle wrote:
> HI Thomas,
> I hate to be a kludge, ...

My guess is that you were looking for a different word.  To quote OED,
a kludge is "a hastily improvised and poorly thought-out solution to a
fault or ‘bug’."

> I see that in regular Hugin Stitcher tab I can add command line options for
> enabled, but I don't see a way to do that for nona.  So that means using
> terminal I suppose.  Is there a tutorial on command line?

There is one at
https://wiki.panotools.org/Panorama_scripting_in_a_nutshell, but it's
horribly out of date.  I've been meaning to update it, but I've always
found something more rewarding to do.  In particular, it makes
reference to obsolete programs.

--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Help!!! Hugin not stitching correctly with fisheye lens

[Greg 'groggy' Lehey]

On Thursday,  6 September 2018 at  8:58:30 -0700, T. Modes wrote:
> Hi Greg,
> Am Donnerstag, 6. September 2018 07:12:04 UTC+2 schrieb Groogle:
>>
>> TO HUGIN DEVELOPERS: It seems to me that there are bugs involved here,
>> possibly relating to circular fisheye lenses.  I take photos with full
>> frame fisheyes on a regular basis, and though I have issues that may
>> be related (and which I will report when I have investigated
>> sufficiently), I have never seen anything like this.  In particular
>> the lack of recognition of the field of view and the the initial
>> panorama previews look like bugs to me.
>
> The first one is due to the check of plausibility of the EXIF data. This
> was too hard. I relaxed the check.

What was the issue?  The Exif data looked fine to me.

> The second one is no bug. If you don't crop the black border, this is was
> you get - GIGO.

This has nothing to do with the border.  Did you check the images to
which I referred?  They're completely wrong, nothing like the stitched
result.

> (Using the crop has the advantage that the crop is remembered when
> you stitch a project and then loaded automatically when you load
> images from the same lens the next time.)

There seems to be a discontinuity here.  I crop completed panos, not
individual images.  Are you talking about the latter?

Greg

--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Help!!! Hugin not stitching correctly with fisheye lens

[Greg 'groggy' Lehey]

On Wednesday,  5 September 2018 at 12:43:40 -0700, jiangjia...@gmail.com wrote:
On Wednesday,  5 September 2018 at 12:55:36 -0700, jiangjia...@gmail.com wrote:

Once is enough,especially since you included relatively large images
(for email).  It would have been better to put all the images on your
Google Drive page.

> I have 4 pictures taken using canon 5d mark ii and 8mm fisyeye lens. files
> can be found
> here, 
> https://drive.google.com/drive/folders/1HpG0k7f9Zg8L-W3fuVrItYqtvZpLNRgY?usp=sharing
>
> I followed the simple steps on hugin, but the final output looks awful.
>
> [image: IMG_0429 - IMG_0432.jpg] 

Indeed, this is not good.  I've put a copy at
http://www.lemis.com/grog/Photos/20180906/small/IMG_0429---IMG_0432.jpeg
for anybody who is interested in checking.

> In contrast, ptgui has no major issues at all.
> [image: IMG_0429 Panorama.jpg] 

This is better, but still not good.  Copy at
http://www.lemis.com/grog/Photos/20180906/small/IMG_0429-Panorama.jpeg.
There are clear discontinuities round the frame of the “Chicago"
poster on the left.

> Can anyone help and tell me what I was doing wrong? and how can I
> improve the quality?

This is really very puzzling.  I downloaded the images and stitched
them.  I expected problems, and I got them.  But they were in no way
related to your problems.  Some look like Hugin bugs:

1.  The Exif data clearly show:

File IMG_0429.JPG
Date taken: Friday, 24 August 2018, 21:12:58
Exposure:   1/4 sec, f/4.0 (EV 6.0), 29/640 ISO
Camera: Canon Canon EOS 5D Mark II
Lens:   Canon EF 8-15mm f/4L Fisheye USM
Focal length:   8.0 mm (full frame equivalent: 8 mm)

But Hugin still asks for a crop factor.  That shouldn't be
necessary.  I put in 1, of course.  Did you?  That might be part
of the problem.

2.  I set "circular fisheye" in the Assistant, and it located control
points relatively well, a maximum error of 4.6.  But the fast
panorama preview looked terrible, full of black:
http://www.lemis.com/grog/Photos/20180906/Hugin-1.png.  I tried a
normal panorama preview and got the same thing.

3.  I stitched the panorama anyway, and got a panorama still with
black areas, but not nearly as much:
http://www.lemis.com/grog/Photos/20180906/small/IMG_0429-IMG_0432-2.jpeg

4.  The disturbance was clearly related to the panorama head reaching
into the image, so I masked that off.  And then, without any
further problems, I was able to stitch a reasonable panorama:
http://www.lemis.com/grog/Photos/20180906/small/IMG_0429-IMG_0432.jpeg.
Clearly it needs cropping, but I deliberately didn't do so.

All of these images are available at
http://www.lemis.com/grog/photos/Photos.php?dirdate=20180906

I can't see any discontinuities in the final panorama, and I did
absolutely nothing to avoid them.  So I'm really puzzled how you ended
up with such poor results.  The project file is at
http://www.lemis.com/grog/Photos/20180906/IMG_0429-IMG_0432.pto.  Try
it and see what you get.

TO HUGIN DEVELOPERS: It seems to me that there are bugs involved here,
possibly relating to circular fisheye lenses.  I take photos with full
frame fisheyes on a regular basis, and though I have issues that may
be related (and which I will report when I have investigated
sufficiently), I have never seen anything like this.  In particular
the lack of recognition of the field of view and the the initial
panorama previews look like bugs to me.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Stitching errors despite numerous and precise manual control points

[Greg 'groggy' Lehey]

On Monday, 27 August 2018 at 12:11:41 -0700, Hugin developers list wrote:
> @ Greg, Panostar:thanks for the detailed responses.
>
> Concerning the zenith/nadir: the two pictures in question are "horizon"
> ones (shot horizontally).
>
> Concerning entrance pupil/parallax errors, the area that poses
> stitching problems spans from 1 to 3 meters approximately from the
> camera, and there is no closer object in-between.

Yes, this is typical of parallax issues.  They become more severe the
closer you are to the camera.

> And it is a flat surface. Can even this condition pose parallax
> errors ?

Absolutely.  Each of these pavers appear in a slightly different
perspective in each image.

> May the parallax errors come from further objects in the scene ?

The parallax errors come from the position of the entrance pupil.
They affect the entire image, but they're less of an issue with
distant objects.

> Concerning the exactitude of the control points, these were
> meticulously placed and verified : a few to begin with, then more
> and more numbered, and then organized following a kind of a
> grid. I've arrived at this level of density (more than the pictures
> I posted previously), and the algorithm simply overrides the control
> points, making seams.

You don't need many control points.  10 are probably enough if they're
well positioned.

> [image: Nbr_1.JPG] 
> [image: Nbr_2.JPG] 

I tried to align these, but the control point detectors weren't very
happy with them.  This may be due to the reduced images, which
sometimes cause problems.  You say that you used an 8mm lens, but you
don't say what sensor format, and the images you supplied don't
include Exif data.  This information is important.  Looking at the
images, they're clearly full-frame fisheye, which suggests a Four
Thirds or possibly APS sensor.  I've tried aligning them, but the
control point detectors don't like them much.  Can you post all the
original files (raw if possible, but definitely with Exif data)
somewhere?  Also your project file (the one with a name ending in
.pto) would be interesting.

> ... but maybe he has trouble with 8mm lens extreme distortions), to
> no avail.

I don't see any issue with distortion in your photos, though there's a
bit of CA.  Fisheye lenses don't distort, they just have a different
projection, and Hugin handles that well.  I do most of my panos with
an 8 mm fisheye lens, and though I have issues with the control point
detectors, I'm sure that they're not related to the lens, and they're
also not like the problems you're reporting.

It would be interesting to hear how you determined the position of the
entrance pupil for your lens.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Stitching errors despite numerous and precise manual control points

[Greg 'groggy' Lehey]

On Friday, 24 August 2018 at 17:26:06 -0700, Hugin developers list wrote:
> Dear All,
>
> I'm working on a relatively high precision 360x180 panorama, and have an
> issue with the stitching.

> 1) In the ground tiling, the stitching makes irregular cracks, even tough
> the control points that I added manually are relatively dense, and
> organized - following a grid :
>
> [image: 1.1-control points.jpg] 
> [image: 1.2-cracks-2.jpg] 
>
> Is there a way to improve this ?

In my experience, this is one of the most difficult things to stitch.
I'd suggest removing all the control points with an error larger than,
say, 4, and see what things look like.  Then place control points
round the areas where the discontinuities occur.  You might also have
success with masking.  And of course meticulous attention to the
entrance pupil position will make life easier.

> 2) The previous is the output when I used "horizon" pictures
> only. When I added the "up" picture, the same cracks, strangely,
> changed (for the worse). IS this normal ? Is there a way to avoid
> this ?

Did you align before or after adding the additional images?  I
wouldn't expect them to make any difference, but possibly masking
could help again.  Run the cursor over the fast panorama preview while
holding down the control key (this works for me on X; not sure if it's
different on your platform), and it will show you the extent of each
image, and then you can get an idea of how to mask things.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: What causes highlight clipping to gray in hdr mode?

[Greg 'groggy' Lehey]

On Tuesday, 21 August 2018 at 13:39:18 -0700, Matija Kogoj wrote:
> I believe to have figured this out -* colour space*.
>
> Working on other scenes in the meantime I found that jpgs from my camera
> were written in AdobeRGB97, which is proprietary. Using 16bit TIFF files,
> exported from RAW, resulted in the same issue but once those were written
> in sRGB colour space solved the whole thing.

Interesting.  Of course, if you had used raw images, this wouldn't
have happened.

> It would be best if someone could confirm this.

I do this kind of thing all the time, and I have no issues.  As I
mentioned earlier, I do three shots at 3 EV intervals: +4.7 EV, +1.7
EV and -1.3 EV.  I take a separate shot with the sun blanked out and
then merge them, using only the area round the sun for the shot that
includes the sun.  This is not for exposure purposes, but it gets rid
of flare in the shadows.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] strange issues with 360 pano?

[Greg 'groggy' Lehey]

On Monday, 13 August 2018 at 22:04:50 -0700, clepsydrae wrote:
>
> Here's what I've gotten to
>  now that I'm not
> optimizing translation. Very happy with the results. Just need to
> understand why translation optimization confused it so much... maybe the CP
> detection on dark images, as you suggested?

Certainly doing just the dark images doesn't help.  But I'm probably
out of my depth here.  Maybe others can venture an opinion at to what
optimization parameters make sense.

I do my panos a bit differently:

1.  Take 3 images bracketed 3 EV apart, skewed about 1.3 EV towards
overexposure (+4.3 EV, +1.3 EV, -1.7 EV).  I think this would work
well for your scene as well.

2.  Convert images to HDR externally to Hugin (specifically,
Photomatix on a Microsoft box).  Hugin doesn't handle ghosting.

3.  Run the resultant images through Hugin.  Until proof of the
contrary, use the Align function of the Assistant.  This is what I
did with your images.

Recently I've been playing with scripting the conversions, so in
fact what I do is:

pto_gen -o my-1 $FILES
cpfind -o my-2 my-1
celeste_standalone -i my-2 -o my-3
cpclean -o my-4 my-3
autooptimiser  -a -l -s -o my-5 my-4
pano_modify -o $PTO --center --straighten --canvas=AUTO --crop=AUTO my-5

The my-? are intermediate steps in the project file so that I can
see what has changed; the documentation is minimal and out of
date.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: strange issues with 360 pano?

[Greg 'groggy' Lehey]

On Monday, 13 August 2018 at 21:50:18 -0700, clepsydrae wrote:
> Aha -- it seems to be related to optimization of translation... I inspected
> the .pto and saw some extreme-seeming values for TrX, TrY, and TrZ. I
> started over and did not optimize translation and the issue doesn't happen.

Possibly.  I'd attend to the other issues first.  I'm surprised that
the control point detectors found anything on the original images.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] strange issues with 360 pano?

[Greg 'groggy' Lehey]

On Monday, 13 August 2018 at 17:50:53 -0700, clepsydrae wrote:
> I have uploaded all the test images and the demo .pto here
>  -- but be warned
> that it is a 2GB file. It is uploading now and should be done at the latest
> in ~45 minutes (18:30 PDT/UTC-7, 01:30 UTC).

OK, in the end it was only 1 GB.

On Monday, 13 August 2018 at 17:53:17 -0700, clepsydrae wrote:
> On Monday, August 13, 2018 at 4:58:30 PM UTC-7, Groogle wrote:
>>
>>> Smaller images are fine as long as they show the problem.
>
> ...if the 2GB file is ridiculous I can try to make a small version of the
> issue... let me know, thanks!

That was the background for my suggestion.  But I've looked at the
original, and I think I have answers for you.

What I see is that the problems are with the source images, not Hugin:

1.  The images are underexposed by about 5 EV.  The control point
detectors just can't cope.

2.  The images show extreme vignetting in the corners.  This may be
the background for the clipping.  I processed the images with DxO
Optics Pro, bringing out results that were acceptable, if not
good.  DxO knows the lens/camera combination and corrected for the
vignetting in the lens, but not completely.  That suggests that
there may be something wrong with your lens (or, of course, with
DxO's correction profiles).  You may find things clear up with a
marginally longer focal length setting.

3.  There was dirt at the top of the images, slightly to left of
centre.  It wasn't visible until the images were lightened.

Take a look at
http://www.lemis.com/grog/photos/Onephoto.php?image=/grog/Photos/20180804/cedarpano.jpeg=3
for the results.  That image is by no means perfect, but it's exactly
what Hugin did with the standard Align function.  There's a
discontinuity on the board at bottom mid-left, but that could be dealt
with with a mask.

In passing, you probably don't need that many images for a circular
panorama (not 360°; that includes a complete sphere).  My program
tells me steps of 50° for this lens, sensor and orientation, so 8
images (45° steps) should do it.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] strange issues with 360 pano?

[Greg 'groggy' Lehey]

On Monday, 13 August 2018 at 15:31:59 -0700, clepsydrae wrote:
> Howdy -- I'm attempting a pano made of 14 images (~10mm on a 1.62x APS-C).
> CPFind doesn't find CPs well unless I drag the images to a rough correct
> overlap, so I do that first.
>
> Then CPFind finds the CPs, I remove some CPs from the clouds, and
> optimization (Pos/Trans/View/Barrel) does a good job. (~average error of 10
> pixels.)
>
> Now the panosphere looks perfect, but the preview pane exhibits some kind
> of odd clipping. ...

I've frequently seen that the preview shows problems that don't exist
in the final stitched image.  Have you tried stitching?  Unfortunately
I find the panosphere pretty useless, and the views you show are hard
to interpret.

If the image doesn't stitch well, can you put the source images and
project file somewhere where people can look at them?  Smaller images
are fine as long as they show the problem.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Crop to maximal area issue

[Greg 'groggy' Lehey]

On Sunday,  5 August 2018 at  3:00:37 -0700, Capri Flyhennessy wrote:
> Hi Greg,
>
> Here are the jpg's I am using:
> https://drive.google.com/open?id=1tQ78OvePAh1hb9B_g3XIWhZY48_0L4id
>
> And the script:
> pto_gen -o project.pto *.jpg
> cpfind -o project.pto --multirow --celeste project.pto
> cpclean -o project.pto project.pto
> #linefind -o project.pto project.pto
> autooptimiser -a -m -l -s -o project.pto project.pto
> pano_modify -s -c --fov=AUTO --output-type=N --ldr-file=TIF 
> --ldr-compression=LZW --canvas=AUTO --output=project.pto project.pto
> hugin_executor --stitching --prefix=pano project.pto
>
> I checked and when the remapping happens, when I check the intermediary
> tiffs it creates I can already see the top cropping happening.

OK, I've taken a look at this, and "it works for me".  Comparing our
workflows, it seems that you have omitted "--crop-AUTO" from the call
to pano_modify, so there is no crop mask.

> Ideally for me it would be cool not to enter the GUI at all, as that would
> be a way to quickly batch process all of my panorama's (that's why I
> started creating a bash script for creating the panorama's).

That should be possible.  I ran your scipt as shown, with the addition
of the --crop=AUTO, and it generated a properly cropped result.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Crop to maximal area issue

[Greg 'groggy' Lehey]

[reformatted]

On Saturday,  4 August 2018 at  2:42:31 -0700, Capri Flyhennessy wrote:
> On Saturday, August 4, 2018 at 2:52:15 AM UTC+2, Groogle wrote:
>> On Friday,  3 August 2018 at 11:08:00 -0700, Capri Flyhennessy wrote:
>>>
>>> I am quite new to Hugin but I am writing a bash script to
>>> automatically run through all of my panoramas and I have bumped
>>> into an irritating issue that I do not really know how to fix.
>>> The whole process works but I would like it to crop the stitched
>>> image to the largest possible area where my pictures are and not
>>> for it to always crop the top part (sometimes it crops the sides
>>> as well).
>>>
>>> Is there something I am missing to automatically fix this, it
>>> doesn't seem such a far fetched thing.
>>
>> Clearly the "autocrop??? feature in the GUI works, so it should be
>> possible.  Can you post your bash script?  I'm doing something
>> similar, but I haven't looked at cropping yet.
>
> Well in the GUI it also has issues like the top part not being in
> the canvas and I have to manually remove all of the empty space at
> the bottom.

This is beginning to look like an issue with your images.

> This is the part of my bashscript that deals with the creation of the
> panorama:
>
> pto_gen -o project.pto *.jpg
> cpfind -o project.pto --multirow --celeste project.pto
> cpclean -o project.pto project.pto
> linefind -o project.pto project.pto

I've found that linefind pessimizes my images, which contain a number
of trees that are not all vertical.  But it doesn't look like this is
your issue.

> autooptimiser -a -m -l -s -o project.pto project.pto
> pano_modify -s -c --fov=AUTO --output-type=N --ldr-file=TIF 
> --ldr-compression=LZW --canvas=AUTO --output=project.pto project.pto
> hugin_executor --stitching --prefix="$PANONAME" project.pto

Apart from that, that's pretty much what I do (I've now looked at
cropping), and "it works for me".

On Saturday,  4 August 2018 at  2:46:36 -0700, Capri Flyhennessy wrote:
> On Saturday, August 4, 2018 at 7:51:47 AM UTC+2, Marius Loots wrote:
>>
>> Hi,
>>
>> Friday, August 3, 2018, 8:08:00 PM, you wrote:
>>> The whole process works but I would like it to crop the stitched
>>> image to the largest possible area where my pictures are and not for
>>> it to always crop the top part (sometimes it crops the sides as well).
>>
>>> Is there something I am missing to automatically fix this, it
>>> doesn't seem such a far fetched thing.
>>
>> Cropping as it currently works will select an area so that there are
>> no empty spaces. There isn't an option - that I am aware of - to crop
>> to maximal area. I do that by hand in each case.
>
> Could you explain the "no empty spaces" a bit more because isn't the bottom
> part empty space? Is there some data there? Why is it even so big?

I'd use the term "hole" rather than "empty space".  If there's an
undefined area in the middle of the image, cropping will avoid it.
But this doesn't seem to be your issue.

On Saturday,  4 August 2018 at  7:10:09 -0700, Capri Flyhennessy wrote:
> Hi,
>
> I also wanted to add that I am not sure why this is happening but when
> stitching panorama's. Sometimes the stitch outright fails.

What's the error message?

> I have added an example of this. The only way to fix it, that I have
> found, is to rerun the stitching part of Hugin. I there a way I can
> avoid this?

Are you saying that you run your script, and the hugin_executor fails,
that you re-run just that part, and it works?  If so, you really need
to look at those error messages.

> 

What I see here is that the cropping didn't work at all.  Maybe a
little masking would help.  One difference between my script and yours
is that after creating the project files, control points and cropping,
I start the GUI to play around with the results.  Then I save the
project file and let hugin_executor finish it off.

Maybe it's worth putting your files (source image and project file) up
for us to take a look at.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc

Re: [hugin-ptx] remapping and blending issues

[Greg 'groggy' Lehey]

On Friday,  3 August 2018 at 18:01:53 -0700, Matija Kogoj wrote:
> ...
>
> I don't know what else to do, and have not found anything relating to these
> issues in the documentation.
>
> At the link you will find a zip file with the panorama in question, the
> save file, result...
> https://www.dropbox.com/s/enq5j06uq9vza1y/hugin_20180730_360.zip?dl=0

This doesn't appear to be a ZIP file, despite the URL.  How can I
access the file without having to mess with Dropbox?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Crop to maximal area issue

[Greg 'groggy' Lehey]

On Friday,  3 August 2018 at 11:08:00 -0700, Capri Flyhennessy wrote:
> Hi,
>
> I am quite new to Hugin but I am writing a bash script to automatically run
> through all of my panoramas and I have bumped into an irritating issue that
> I do not really know how to fix.
> The whole process works but I would like it to crop the stitched image to
> the largest possible area where my pictures are and not for it to always
> crop the top part (sometimes it crops the sides as well).
>
> Is there something I am missing to automatically fix this, it doesn't seem
> such a far fetched thing.

Clearly the "autocrop” feature in the GUI works, so it should be
possible.  Can you post your bash script?  I'm doing something
similar, but I haven't looked at cropping yet.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: RAW support with hugin ?

[Greg 'groggy' Lehey]

On Wednesday, 11 July 2018 at  8:29:20 -0400, Robert Krawitz wrote:
> On Wed, 11 Jul 2018 14:15:19 +1000, Greg 'groggy' Lehey wrote:
>> On Tuesday, 10 July 2018 at  8:10:08 -0700, Albert Szostkiewicz wrote:
>>> As much as I wish to stay with Linux (which is my main operating
>>> system) and Hougin Open software, currently I am forced to run PtGui
>>> via wine to do my job as expected.
>>
>> Note that the Unix (and thus Linux) way is to have multiple programs,
>> each able to perform one function and perform it well.  It looks like
>> you're looking for the opposite.
>
> The "UNIX/Linux way" also allows for scripts and other ways to combine
> separate tools into one from the user perspective.

Yes, of course.

> If I have a complex pipeline of operations I want to perform I don't
> have to remember them and run them all by hand; I can use a script
> to do that for me.

Yes, that's exactly what I do.  And also make(1), of course.

>>> It streamlines simple work that has to be done without requirement
>>> of 3rd party software in the process.
>>
>> It still requires mouse pushing.  If you're looking for automatic raw
>> conversions, you can do that too with UFRaw, which has a batch mode.
>> Read in your images, run ufraw-batch on them to produce TIFF output
>> files, and you're ready to go.
>
> One less step, though.

That depends.  We're looking at a single step.  I have a script that
reads in files from the camera, only actually transferring files that
aren't already there.  It would be trivial to augment it to put it
through something like dcraw, if I thought that mindless conversion of
images made sense.

> Other than the work required (which may be non-trivial, balanced
> against the fact that the Hugin developers have other things they
> want to do, not to mention lives outside of Hugin), there's no
> reason Hugin couldn't do the same thing.

In fact, I'm working in exactly the opposite direction, writing
scripts that automate more and more of what Hugin does.  But yes,
possibly the option of starting a raw converter of your choice might
make sense.

>> Just checked https://www.ptgui.com/features.html: yes, PTGui uses
>> dcraw to convert the images.  That's the same program that's behind
>> UFRaw.  The difference with Linux is that you have a choice of raw
>> conversion tools, and that's one of the main reasons for using raw
>> images in the first place.
>
> False dichotomy; there's nothing preventing someone from using a
> separate tool to convert the RAWs into TIFFs or JPEGs and invoking
> PTGui on those.

Of course not, but that misses the point: the original poster wanted
PTGui just for the raw conversion functionality.  If he uses a
standalone program to do the conversion, then he can use Hugin and
doesn't need PTGui.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: RAW support with hugin ?

[Greg 'groggy' Lehey]

On Tuesday, 10 July 2018 at  8:10:08 -0700, Albert Szostkiewicz wrote:
> Personally I am interested in stitching 360 full, true HDR images. I
> am hoping to stitch and get as much of original data as I can. With
> PtGui for eg. I am able to throw my Canon RAWs directly and proper
> exposure merge is being applied.

You can be sure that PTGui is simply converting the raw images to some
RGB format, possibly TIFF.  It sounds like you're not being left much
choice in the matter.

> With Hugin I am forced to use 3rd party apps for conversion into
> TIFF or other format witch adds one more step of possible mistake.

And more control.  Others may correct me, but I'd be surprised if
PTGui is performing the raw conversion itself.  Probably it's invoking
a different program.

> As much as I wish to stay with Linux (which is my main operating
> system) and Hougin Open software, currently I am forced to run PtGui
> via wine to do my job as expected.

Note that the Unix (and thus Linux) way is to have multiple programs,
each able to perform one function and perform it well.  It looks like
you're looking for the opposite.

> It streamlines simple work that has to be done without requirement
> of 3rd party software in the process.

It still requires mouse pushing.  If you're looking for automatic raw
conversions, you can do that too with UFRaw, which has a batch mode.
Read in your images, run ufraw-batch on them to produce TIFF output
files, and you're ready to go.

Just checked https://www.ptgui.com/features.html: yes, PTGui uses
dcraw to convert the images.  That's the same program that's behind
UFRaw.  The difference with Linux is that you have a choice of raw
conversion tools, and that's one of the main reasons for using raw
images in the first place.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Raw image support with hugin (was: RAW support with hugin ?)

[Greg 'groggy' Lehey]

On Thursday,  5 July 2018 at  0:33:45 -1000, David W. Jones wrote:
>
> So when you add a bunch of RAW files to Hugin, it proceeds to popup
> a bunch of windows, one for each frame?

No.  It displays a window "Could not decode (file name).  Abort".

And I think that's correct.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] cpfind function (was: Best Linux distro for Hugin?)

[Greg 'groggy' Lehey]

On Monday,  4 June 2018 at 12:30:17 +1000, Greg 'groggy' Lehey wrote:
> I've been having a strange issue with Hugin for some time now, and
> I've traced it to a difference between the Microsoft and FreeBSD
> versions.  On the FreeBSD version, the control point detectors find no
> control points at all between the first and last images of a circular
> panorama.  There's no obvious reason for this, and it seems that
> "first" and "last" refer to the order in which the images are loaded.

On Monday,  4 June 2018 at 11:18:13 +0100, Bruno Postle wrote:
> The control point detectors are configurable in the Hugin
> preferences. It sounds like you have cpfind --linearmatch set.
>
> Unless you need customised control point detectors, I would reset
> everything using the load defaults button.

I've spent some time investigating this, and discovered:

1.  Yes, --linearmatch only matches the previous and next image in the
stack.
2.  So does --multirow!
3.  This has nothing to do with FreeBSD.  My Microsoft version
(latest, downloaded from the web site) does exactly the same
thing.

I've done a bit of looking through the code, but without internals
documentation it's a bit hard to understand.  I've established that
this behaviour occurs at least as far back as 2013 versions (again,
Microsoft, to avoid any misunderstandings).

So: is this intentional?  In that case, it should be documented.  Or
is it accidental?  In that case it should, of course, be fixed.  And
looking at the documentation, how important is the option any more?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Re: Documentation for project (.pto) files?

[Greg 'groggy' Lehey]

On Sunday, 17 June 2018 at  0:23:16 -0700, T. Modes wrote:
> Am Sonntag, 17. Juni 2018 06:47:41 UTC+2 schrieb Groogle:
>>
>> One thing I haven't found is a description of the project file.  I
>> suppose I could UTSL, but can anybody point me to documentation?
>
> http://hugin.sourceforge.net/docs/nona/nona.txt

Thanks.  This looks the same as what's in the source distribution at
doc/nona.txt.  I came across it while trawling the sources, but it
didn't exactly say what it was.

Does this include everything in the project file?  And is it up to
date?  The modification time stamp is October 2014.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Documentation for project (.pto) files?

[Greg 'groggy' Lehey]

I'm currently going through the documetation on the wiki, which is
sorely in need of it.  I'll submit patches when I'm done, but first I
need to understand it.

One thing I haven't found is a description of the project file.  I
suppose I could UTSL, but can anybody point me to documentation?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Control point finder problems (was: Best Linux distro for Hugin?)

[Greg 'groggy' Lehey]

On Monday,  4 June 2018 at 18:37:36 +0200, Gunter Königsmann wrote:
> Also cpfind will fail if you have once set up the lens parameters wrong by
> a big enough factor once and hugin remembers that lens and your parameters.

Yes, I've run into that, especially as in this case I was using a
fisheye lens.  But it's very much just the overlap at the end.  If I
load the first image a second time at the end, both cpfind and
panomatic find control points with the second copy, but not the first.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Control point finder problems (was: Best Linux distro for Hugin?)

[Greg 'groggy' Lehey]

On Monday,  4 June 2018 at 11:18:13 +0100, Bruno Postle wrote:
> On 4 June 2018 03:30:17 BST, Greg 'groggy' Lehey wrote:
>> I've been having a strange issue with Hugin for some time now, and
>> I've traced it to a difference between the Microsoft and FreeBSD
>> versions.  On the FreeBSD version, the control point detectors find no
>> control points at all between the first and last images of a circular
>> panorama.  There's no obvious reason for this, and it seems that
>> "first" and "last" refer to the order in which the images are loaded.
>
> The control point detectors are configurable in the Hugin
> preferences. It sounds like you have cpfind --linearmatch set.

Possibly, but that wasn't the case.  I did have --multirow, but that's
all.  Also, which I forgot to mention in my initial email, I had moved
~/.hugin out of the way, so hugin created a new, default one.  In each
case, it runs as:

  grog9754  30.0  0.6   350888  216912  -  Rs9:56am  0:02.02 
cpfind --multirow -o /tmp/ap_resopKKTn /tmp/ap_inprojtMDmqp
  grog9753  11.8  0.3   419500   85784  -  Ss9:56am  0:00.25 
/usr/local/bin/icpfind -o /tmp/halB5Z5x /tmp/halB5Z5x

Also I have done this both with panomatic and cpfind, and both show
the same effect.  So whatever it is, it's not that.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

[hugin-ptx] Best Linux distro for Hugin?

[Greg 'groggy' Lehey]

I've been having a strange issue with Hugin for some time now, and
I've traced it to a difference between the Microsoft and FreeBSD
versions.  On the FreeBSD version, the control point detectors find no
control points at all between the first and last images of a circular
panorama.  There's no obvious reason for this, and it seems that
"first" and "last" refer to the order in which the images are loaded.

I'm still trying to understand this, but an obvious thing to do would
be to try it on Linux and see what happens there.  Which distro should
I use?

If anybody wants to play with the images, I have low-quality versions
which show the effect at
http://www.lemis.com/grog/Day/20180602/e-from-house.tar (about 14 MB),
or, if you don't do tar,
http://www.lemis.com/grog/Day/20180602/e-from-house-0.jpeg,
http://www.lemis.com/grog/Day/20180602/e-from-house-2.jpeg,
http://www.lemis.com/grog/Day/20180602/e-from-house-3.jpeg and
http://www.lemis.com/grog/Day/20180602/e-from-house-4.jpeg.  I have
also included my .hugin file at
http://www.lemis.com/grog/Day/20180602/.hugin, and it's in the
tarball.  There's no
http://www.lemis.com/grog/Day/20180602/e-from-house-1.jpeg, which
isn't needed here.  The photos were taken with a full-frame fisheye,
and Exif data is complete.

Apart from this, can anybody think of another reason why this might
happen?  I've checked the .hugin file but found nothing obvious.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Problems with PNG images on 2018.0 on FreeBSD

[Greg 'groggy' Lehey]

On Wednesday, 30 May 2018 at 17:27:22 +1000, Greg 'groggy' Lehey wrote:
> On Wednesday, 30 May 2018 at  6:56:07 +0100, Bruno Postle wrote:
>>
>>
>> On 30 May 2018 04:26:03 BST, Greg 'groggy' Lehey wrote:
>>> I've just received a bug report on Hugin 2018.0.0.5abfb4de7961:
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228547
>>
>>> I suspect that the problem is due to changes in support libraries that
>>> are beyond my immediate control.  Before I go searching blindly, can
>>> anybody suggest where I should be looking?  What library handles PNG
>>> images?
>>
>> Hugin uses the vigra impex library for image file handling, but then
>> vigra uses the standard libpng for PNG. So I would check to see if
>> vigra is linked to libpng.
>
> Thanks.  That's the kind of information I was looking for.

A quick follow-up.  Yes, as Bruno suggested, the bug was in the binary
package for vigra.  I'm still trying to understand why: the Makefile
clearly specifies PNG support, and if you build the port from source,
it works.  So for all of you FreeBSD users out there champing at the
bit to process PNG images, here's what you do:

  # cd /usr/ports/graphics/vigra
  # make deinstall all reinstall

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature

Re: [hugin-ptx] Problems with PNG images on 2018.0 on FreeBSD

[Greg 'groggy' Lehey]

On Wednesday, 30 May 2018 at  6:56:07 +0100, Bruno Postle wrote:
>
>
> On 30 May 2018 04:26:03 BST, Greg 'groggy' Lehey wrote:
>> I've just received a bug report on Hugin 2018.0.0.5abfb4de7961:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228547
>
>> I suspect that the problem is due to changes in support libraries that
>> are beyond my immediate control.  Before I go searching blindly, can
>> anybody suggest where I should be looking?  What library handles PNG
>> images?
>
> Hugin uses the vigra impex library for image file handling, but then
> vigra uses the standard libpng for PNG. So I would check to see if
> vigra is linked to libpng.

Thanks.  That's the kind of information I was looking for.

>> Also, any idea why I can't get the fast panorama preview on the
>> Microsoft version?  The buttons are greyed out, and I can't select
>> them.
>
> Are you running the Windows version on freebsd using Wine? This
> should work, but opengl problems wouldn't be unexpected.

No.  If I wanted to emulate it, I'd use a virtual machine, not Wine.
But I'm running on a real computer.

I am, however, using it over a remote desktop, so that's probably the
problem.  However, starting it on a local monitor still doesn't bring
the functionality back.  Wasn't there some issue with starting with
Ctrl key down or something?

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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


signature.asc
Description: PGP signature