Re: [hugin-ptx] Hugin startet nicht

[Greg 'groggy' Lehey]

On Friday, 23 December 2011 at 15:10:40 -0800, R.Lehmeier wrote:
> Hallo!
> Ich habe die Version 2011.4.0 installiert. Als ich auf den Startbutton
> drückte kem nur die Fehlermeldung : Hugi hat ein Problem festgestellt
> und muß beendet werden.
>
> Woran liegt es und welche Maßnahmen muß ich treffen damit es wieder
> läuft?

Well, first you should describe the problem in English, the languge of
this forum.  Writing in German will seriously limit the number of
responses you get.  Wenn du wirklich kein Englisch kannst, antworte
privat.  Ich kann aber nicht versprechen, dass ich helfen kann.

Next, you should describe your installation.  What operating system,
what version of Hugin.

Then: has it ever worked for you, or is this a fresh installation?

That's just for starters.

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


pgphBRBXonsHP.pgp
Description: PGP signature

Re: [hugin-ptx] Re: FORK HUGIN

[Greg 'groggy' Lehey]

On Sunday, 27 November 2011 at 22:30:01 -1000, Gnome Nomad wrote:
> Bob Campbell wrote:
>>
>> On Nov 25, 6:30 pm, Gnome Nomad  wrote:
>>> I only have normal lenses: 28-75mm F2.8, 80-300mm zoom, 500mm telephoto.
>>
>> Er, technically a camera is only going to have a small range for
>> "normal" lenses, depending on the film/sensor area (particularly the
>> diagonal).  Which is why a normal lens for a 35mm is 50mm but for a
>> 4x5 camera the normal lens is 150mm.
>>
>> http://en.wikipedia.org/wiki/Normal_lens
>
> "Normal" in this context meaning "not wide-angle or fisheye".

I haven't been following this thread much, beyond noting that the real
problem appears to be lack of understanding of Hugin (which may
indicate weaknesses in the documentation), but my understanding of
"normal" was "not fish-eye", or "rectilinear".  See
http://en.wikipedia.org/wiki/Rectilinear_lens

And I thought it most specifically *does* include wide-angle lenses:

On Monday, 21 November 2011 at  9:39:08 -0800, mark skama wrote:
> for normal lenses i mean not fisheye type and start from 20mm in the
> 35mm format sensor

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


pgpjoML8T0VfZ.pgp
Description: PGP signature

Re: [hugin-ptx] keep one image above others?

[Greg 'groggy' Lehey]

On Friday,  4 November 2011 at  6:39:59 -0200, Carlos Eduardo G. Carvalho 
(Cartola) wrote:
> Em sexta-feira, 4 de novembro de 2011, TinCanFury 
> escreveu:
>> I have a series of photos I'm trying to merge, two of them contain an
>> object in the overlapping area where I would like to have one image be
>> used for that space and not the other image that also contains that
>> space, but I can't for the life of me figure out how to do that.
>> Everything I've tried still has the image I don't want to be used for
>> that space being used.
>
> Have you tried hugin masks?

As I was going to say.  But in my experience, only exclude masks
work.  Has anybody got include masks to work as well?

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


pgpvEBvIyUOzy.pgp
Description: PGP signature

Re: [hugin-ptx] Image alignment help

[Greg 'groggy' Lehey]

On Tuesday, 25 October 2011 at  9:57:55 +0200, Luk?? Jirkovsk wrote:
> On 25 October 2011 03:17, Jason Dunham  wrote:
>
>> I have a pair of images which I want to align. They are not a
>> panorama, but rather they are images of the same object, one in
>> natural light, one in fluorescent light.  They were taken with a
>> point-and-shoot camera with a cheap tripod and some changeover
>> setup required, so they are not perfectly aligned.
>
> I think align_image_stack is the tool you are looking for.

align_image_stack requires the images to be very close to each other.
It goes completely off the rails if they're not.

I've been trying to do this too--see my prior message at
http://groups.google.com/group/hugin-ptx/browse_thread/thread/dd769b183a9bced4/c46771e3091e279c?lnk=gst&q=overlapped+image#c46771e3091e279c

I still don't have a solution for that.  If you find one, I'll be very
interested.

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


pgpo5PtAcm7AT.pgp
Description: PGP signature

Re: [hugin-ptx] 360 of the church

[Greg 'groggy' Lehey]

On Wednesday, 12 October 2011 at 16:37:05 -0700, mcncyo wrote:
> I am trying to do a 360 of a church,  We have the alter (table)  just
> in front of the camera which is just a large rectangle.   When I
> created the image the alter(table) is always curve.  I have put some
> more control points on the table itself but it's not helping.  Does
> anyone have any suggestions?

Nothing you'd like, I fear.  That's part of the perspective.  If you
go further away from the altar, the curvature will be less pronounced,
but the fact remains that the edges are further away than the middle.

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


pgpeZKPFZFweu.pgp
Description: PGP signature

[hugin-ptx] Strange control point detection problem

[Greg 'groggy' Lehey]

A couple of days ago I took some photos in the Ballarat Botanical
Gardens and stitched them together.  Most worked well, but in one case
it went completely off the rails.  I wasn't able to align the images
even with a manual choice of control points.

There was nothing obvious wrong with the images themselves, and I was
later able to create a good panorama by starting with only two images
and adding them one at a time.  I get the feeling that this is some
kind of bug in hugin, but I'd appreciate other opinions.  There's a
writeup, including full description and images, at
http://www.lemis.com/grog/diary-aug2011.php#stitch-failure

Details:
  Hugin Pre-relase 2011.3.0
  Panomatic
  FreeBSD 8.2

I'll try some other combinations (in particular the control point
detector), and if I have any enlightenment I'll report back.

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


pgpIqjBLuyCVe.pgp
Description: PGP signature

Re: [hugin-ptx] Re: autopano-sift-c working better than cpfind on small rectilinear images

[Greg 'groggy' Lehey]

On Sunday, 14 August 2011 at 15:11:17 -0400, Yuval Levy wrote:

Sorry, just got round to reading this thread.

> On August 14, 2011 05:47:43 am kfj wrote:
>
>> If, of course, we'd find that in certain use scenarios one definitely
>> outshines the other, this would be helpful. Not that I expect this to
>> happen
>
> I also do not expect this to happen, but if we don't collect
> information we won't find out.  And it is often such borderline
> cases that help the next iteration of development that eventually
> brings about a third generation tool that is superior to both the
> first and second generation.

FWIW, I have a scenario where I find that the control point generators
generate very different control points from the ones I choose myself
when I'm doing it manually.  Every week I make a number of panoramas,
the most complicated of which is at http://tinyurl.com/3mcw2bb

This is a two-row 360° panorama made out of 24 images, each
tone-mapped from three images.  The subject has both straight lines
and corners (timber) and soft transitions (leaves and other
vegetation).  The leaves can move both between individual tone-mapped
images and also between the background images for each tone-mapped
images.  The timber stays where it is.

But all the CP generators I have tried go for the leaves.  That's a
particular problem when it's windy.  When I do it manually, I choose a
spot or a corner on the timber, and things work much better.

Clearly there's a reason why the CP generators make this kind of
choice, but I don't understand it.  Are there some technical reasons
why it's done this way?  Or are there generators that do choose hard
surfaces?

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


pgpPojzvrlToX.pgp
Description: PGP signature

Re: [hugin-ptx] Mercurial browse disappeared from sourceforge site

[Greg 'groggy' Lehey]

On Friday, 19 August 2011 at  8:44:25 +0200, Felix Hagemann wrote:
> On 19 August 2011 07:58, Terry Duell wrote:
>>
>> Can someone please try  and
>> report if you get the normal page showing who committed what to which
>> branch?
>
> Same problem here, no matter which browser I use.

"Me too".

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


pgp9m5b7wNH0p.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Thursday,  4 August 2011 at 22:33:19 +0200, Harry van der Wolf wrote:
> It's a bit of a shame that this discussion is now more or less split
> over 2 threads.

Somehow this reminds me of the problem itself.

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


pgpLesEjZbd4x.pgp
Description: PGP signature

Re: [hugin-ptx] Test images available

[Greg 'groggy' Lehey]

On Wednesday,  3 August 2011 at 21:54:17 -0500, AKS-Gmail-IMAP wrote:
> Pardon the off topic comment, but would someone please explain how one
> can expect trees to grow in the street within the curb line?

It's an Australian thing.  In this part of the world, the two main
causes of car accidents are:

1.  Speeds in excess of what a bureaucrat thinks is enough.
2.  People driving into trees.

This panorama is an example of an attempt to give cause 2 a fair
chance.

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


pgpRQLjhTbqca.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Tuesday,  2 August 2011 at 21:50:39 -1000, Gnome Nomad wrote:
>
> If it's a race condition in the preview, that could possibly be
> spotted by code inspection.

If you're *very* lucky.  Ultimately all problems are solved by code
inspection, of course, but there's lots of code to inspect.  It would
be nice to catch the thing in action and point a debugger at it.  That
would at least narrow things down.

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


pgpaMK4kKNQ9w.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Tuesday,  2 August 2011 at 19:55:05 -1000, Gnome Nomad wrote:
> Terry Duell wrote:
>> Hullo Greg,
>>
>> On Wed, 03 Aug 2011 09:12:42 +1000, Greg 'groggy' Lehey
>>  wrote:
>>
>> [snip]
>>
>>> And FWIW, I can't reproduce this with FreeBSD and the proprietary
>>> nVidia driver.
>>
>> OK. Does this indicate that it might be affected by different versions
>> of some libs, or somesuch?
>
> Might be effected by Xorg versions, too?

Quite possibly.  Until we have a better feeling for what the problem
is, we can't exclude anything, though my bet is that it's not
dependent on the phase of the moon.

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


pgpQslYHhNtol.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Tuesday,  2 August 2011 at 19:50:18 -1000, Gnome Nomad wrote:
>
> If Hugin only works properly with NV and has problems with Nouveau,
> Hugin needs to fix them.

... assuming the problem is with Hugin.  So far we can't be sure,
though the appearance of the problem with Microsoft as well suggests
that it *is* a Hugin problem.

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


pgpeQR4nqgvRn.pgp
Description: PGP signature

[hugin-ptx] Test images available (was: CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview)

[Greg 'groggy' Lehey]

On Wednesday,  3 August 2011 at 10:08:43 +1000, Greg 'groggy' Lehey wrote:
> On Wednesday,  3 August 2011 at  9:22:40 +1000, Terry Duell wrote:
>> On the first front, I do have a set of images that I have been using as my
>> test set, and I was able to easily provoke the failure on my system when
>> testing versions since the merge of the overview code, but unable to get a
>> failure on versions prior to that.
>> The set consists of 5 images each approx 2 MB. I will see if I can get the
>> problem to show itself with reduced size version of those images, which
>> might make it easier to make them available.
>> How to I make them available? I don't have a site where I can put them.
>
> I can give you a place to put them.  I'll reply in private mail.

OK, Terry has now uploaded a set of images at
ftp://w3.lemis.com/pub/hugin/P1040510.JPG to
ftp://w3.lemis.com/pub/hugin/P1040514.JPG .  I've tried them with my
version of Hugin, and they stitch well with no problems.  YMMV.

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


pgpvyl830jzVT.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Wednesday,  3 August 2011 at  9:22:40 +1000, Terry Duell wrote:
> Hullo Greg,
>
> On Wed, 03 Aug 2011 09:12:42 +1000, Greg 'groggy' Lehey
>  wrote:
>
> [snip]
>
>> And FWIW, I can't reproduce this with FreeBSD and the proprietary
>> nVidia driver.
>
> OK. Does this indicate that it might be affected by different
> versions of some libs, or somesuch?

I'd say it's a data point, no more.  It just shows that the
proprietary nVidia driver doesn't necessarily cause the FPW to hang.

>> I don't think this is a traditional coding error.
>
> OK. I don't have enough of the right experience to know one way or
> another on that.

I should have included the "else" clause: my guess is that this is a
race condition, where two threads trip over each other.  Thus my
second suggestion below.

>> I made two suggestions that don't seem to have been followed up on:
>>
>> - Find a set of photos which provoke the problem.
>
> On the first front, I do have a set of images that I have been using as my
> test set, and I was able to easily provoke the failure on my system when
> testing versions since the merge of the overview code, but unable to get a
> failure on versions prior to that.
> The set consists of 5 images each approx 2 MB. I will see if I can get the
> problem to show itself with reduced size version of those images, which
> might make it easier to make them available.
> How to I make them available? I don't have a site where I can put them.

I can give you a place to put them.  I'll reply in private mail.

>> - Try limiting the number of concurrent threads.
>
> On the threads question, I could test limiting the number of
> concurrent threads, if I knew how to do that. Anyone who can help
> with that?

My assumption (looks at Yuval) is that this will require code.
Considering that you may not necessarily want to tie up all resources
on your 16 processor system, it might also be useful beyond looking
for bugs, so it could be added to the configuration.  But I don't know
(enough of) the code base to say how to do that.

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


pgpGaFgpNKk5a.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Wednesday,  3 August 2011 at  8:51:37 +1000, Terry Duell wrote:
>
> If I understand this correctly, hugin worked OK for you with the NV
> driver but failed when you used the proprietary nvidia driver.  My
> experience with Fedora 15 is that I have had the same FPW failures
> with the proprietary nvidia driver and the with the open source
> nouveau driver.

And FWIW, I can't reproduce this with FreeBSD and the proprietary
nVidia driver.

> On the wider question, can anyone who knows more about this business
> than I, say if we are getting closer to homing in on this bug?

I was wondering that too.

> I would like to help more, if I can, but that stops well short of
> looking for a coding error.

I don't think this is a traditional coding error.

I made two suggestions that don't seem to have been followed up on:

- Find a set of photos which provoke the problem.
- Try limiting the number of concurrent threads.

One thing that I undertook to do was to try my photos out on
Microsoft.  That didn't get off the ground.  My old Microsoft laptop
overheated and shut down, and running it in a VM didn't work because I
didn't have the right support software installed, and my Microsoft-fu
isn't up to installing it.  I also suspect that it would have run out
of memory (I can't give a VM more than about 800 MB memory).

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


pgpXVTkLA8pSK.pgp
Description: PGP signature

[hugin-ptx] Overview mode (was: CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview)

[Greg 'groggy' Lehey]

On Tuesday, 26 July 2011 at 17:11:57 -0400, Yuval Levy wrote:
> On July 26, 2011 03:16:43 AM Greg 'groggy' Lehey wrote:
>> I don't like the overview mode (maybe because I don't understand
>> its purpose)
>
> the relationship between the preview and the overview is like that between a
> map of the earth and a globe.  The overview shows the globe itself, and you
> can turn it around in "3D", while the preview is a flat projection.
>
> The overview is helpful when making full spherical panoramas.  You can look at
> the poles (zenith and nadir) without distortion, while they are too distorted
> in the preview.

Indeed.  I've played with it now, and it's quite nice.  But I don't
really need it for the work I do, so it's good to be able to turn it
off.

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


pgpVlvWOzpq7u.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Tuesday, 26 July 2011 at  9:40:50 -0400, Yuval Levy wrote:
> On July 24, 2011 11:52:53 PM Greg 'groggy' Lehey wrote:
>
>> I wasn't able to provoke this bug.
>>
>> Anything else I should try?
>
> I am no expert.  You probably know better than me, and indeed you
> seem to be on the right track with the threading thing.  What would
> you suggest we try next?

Difficult to say.  Everybody has his own procedures, and mine would
have been with gdb if I had been able to reproduce the bug.  What I'm
going to do now is to try it out with Apple and Microsoft and see if I
can reproduce it on those platforms with the same data.  But if I do,
I don't know what I can do about it, at least on Microsoft, where I
don't have any development tools.

Which version should I be trying?  hugin-2011.2_beta?

> I just tried to apply a strategy that I know from solving finance
> problems to solve this code problem, helping those who can provoke
> the bug zero-in on the changeset that introduced it; and trying to
> find correlations between their specific situations and the buggy
> behavior while not being able to reproduce it myself.

Certainly getting a collection of data on where it happens and where
it doesn't might be useful.  It seems we need at least:

  OS, including specific release
  Way the executable was built (libraries, etc)
  Number of processors

It would also be good to find a standard set of images with which the
bug shows itself.

Another thing that might be of interest would be to set the
preferences to use only one CPU and see if the problem still occurs.
It might also be nice to add an option to limit the number of threads,
but I suspect that's non-trivial.

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


pgp1DnA2JiyNQ.pgp
Description: PGP signature

Re: [hugin-ptx] Re: CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Wednesday, 27 July 2011 at 13:29:52 +1000, Terry Duell wrote:
> Hullo All,
>
> On Wed, 27 Jul 2011 13:22:00 +1000, Tduell  wrote:
>
>
>> Hugin bundles zthread 2.3.1 which was released 08-2003.
>> The current release of zthread is 2.3.2 (03-2005).
>
> I may have been a bit premature.
> I assumed that the zthread bundled with hugin was 2.3.1 as that is what it
> says in the Readme file, but it also says that in the 2.3.2 tarball readme!
> The licence file in the version bundled with hugin says 2005, so there is
> a good chance that hugin already uses 2.3.2.
> Can anyone confirm?

Yes, it seems so.  I've just run diff on the two trees.  There are a
couple of minor differences in MutexImpl.h:

--- ./MutexImpl.h   2005-03-13 14:59:15.0 +1100
+++ 
/usr/ports/graphics/hugin/work/hugin-2010.4.0/src/foreign/zthread/src/MutexImpl.h
   2010-12-28 23:57:50.0 +1
100
@@ -153,7 +153,7 @@

   _owner = self;

-  ownerAcquired(self);
+ Behavior::ownerAcquired(self);

 }

Makefile.am also differs.  But all the platform-specific directories
have identical contents.

Pity
Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpvjvoKTtQRm.pgp
Description: PGP signature

Re: [hugin-ptx] Re: CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Tuesday, 26 July 2011 at 20:22:00 -0700, Tduell wrote:
> On Jul 27, 7:51 am, Yuval Levy  wrote:
>
> [snip]
>
>> The current hypothesis is that this is a threading issue, and a different
>> threading library means a potentially different behavior / effect.  So we 
>> have
>> to watch for different CPUs (i.e. number of cores / threads) different O/S
>> Versions (i.e. how those threads are managed) and different threading
>> libraries used (i.e. those present in the system which can be very different
>> across same systems; and/or those present in the SDK used to build the
>> binaries).
>
> Hugin bundles zthread 2.3.1 which was released 08-2003.
> The current release of zthread is 2.3.2 (03-2005). The last entries in
> the zthread changelog are ...
> ...
>
>   Bug in non-vanilla AtomicCount implementations corrected.
>   (Caused hanging in some cases and general trouble with CountedPtr)
> ...
> 
> Is it worth trying to build a test version using zthread 2.3.2?

Given the fact that it's been out for 6 years, I'd think it's a good
idea anyway.  But maybe it would make more sense to make it an
external dependency rather than part of the distribution.  Do you see
a problem with that?

> I have had a quick look at the zthread src in hugin and at the content
> of the 2.3.2 tarball, and on the surface it looks like 2.3.2 could be
> dropped in to replace 2.3.1 with a few changes ie. remove some of the
> stuff used to build from the tarball and keep the Cmakefiles dir,
> CmakeLists.txt etc, assuming that those don't need tweeking.
> Given that my system seems to be pretty sensitive to this bug, I think
> it might be useful for me to do a test build,

Indeed.

> but I am groping about here and would really appreciate advice from
> some who know a bit more about this.

That's not me, but it does sound like a good idea.

> I don't really know what I don't know, the dreaded unknown unknowns
> :-)

There's one way to find out :-)

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpYW7JdZEIbZ.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Tuesday, 26 July 2011 at 16:24:32 +1000, Terry Duell wrote:
> Hullo Greg,
>
> On Mon, 25 Jul 2011 13:52:53 +1000, Greg 'groggy' Lehey
>  wrote:
>
> [snip]
>
>> Anything else I should try?  Until I can reproduce it with tip, there
>> doesn't seem to be much point to try a binary search.
>
> I have found slightly different behaviour with the latter versions, where
> they are often OK if the FPW opens with the overview mode hidden.

Ah!  I don't like the overview mode (maybe because I don't understand
its purpose), but I didn't know I could turn it off.  Instead I
detached it and pushed it off the edge of the screen.  But now I

> If Hugin has been quit with the FPW showing the overview mode, when
> hugin is next started, and when the FPW is opened it will be showing
> the overview mode, and THAT is when it gives trouble.

Well, all that applies, but it doesn't give me any trouble.  I thought
that maybe that's because I detached the overview window, but I've
tried again with the window attached, and it still works fine.

> If you haven't already done so, try your version after quitting with
> overview mode shown in FPW. It will be interesting to see if you can
> find a fault.

That's what I've been doing all the time.  No problems.

> I wonder if the varying behaviour of different systems is being
> influenced by the varying versions of dependent libraries that
> different systems have installed, each reacting a bit differently to
> some bit of code in the overview mode. Just my 2 bobs worth.

Quite possibly.  Did you see the bug report I put in today?  It seems
that some component crashed on exiting because of a consistency check.
Since it was exiting anyway, it seems to be harmless, but it's clearly
related to specific threading libraries.

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpoaUZGTfACt.pgp
Description: PGP signature

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

[Greg 'groggy' Lehey]

On Sunday, 24 July 2011 at  9:47:14 -0400, Yuval Levy wrote:
>
> We know that the current Hugin is plagued with a pesky spurious bug that is
> difficult to reproduce.  It is causing grievance to a lot of users as seen on
> the ML and on the main tracker ticket where the bug is discussed  [0].
>
> This is most likely caused by a memory leak.  The most difficult part of
> fixing a memory leak is to identify where it happens.  Would you like to help
> nuke this bug?

I've just cloned the hg repository and built the latest version
(5345).  I had some difficulties building, which I'll mention in a
separate message, but I wasn't able to provoke this bug.  From reading
the bug report, it seems possible that it's hardware or software
dependent.  My system:

  OS: FreeBSD 8.2-STABLE, i386, 3 GB memory
  X:  X.Org X Server 1.7.7
  Display card:   NVIDIA GPU GeForce 9500 GT (G96) (2, FWIW)
  Display driver: nVidia nvidia-driver-256.53_1

This was with my own images, a collection of 25.  I tried playing
around with the buttons in the fast preview window and kept an eye on
the process memory image with ps, but there's no evidence of any
memory leak.

Anything else I should try?  Until I can reproduce it with tip, there
doesn't seem to be much point to try a binary search.

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpzxzGIDyhMj.pgp
Description: PGP signature

Re: [hugin-ptx] Re: Hugin 2011.2.0 release notes - fixed background image

[Greg 'groggy' Lehey]

On Sunday, 24 July 2011 at  9:40:32 +1000, Terry Duell wrote:
> Hullo Yuv,
> On Sun, 24 Jul 2011 04:21:10 +1000, Yuval Levy  wrote:
>> On July 23, 2011 05:15:42 am cri wrote:
>>> [1] http://hugin.sourceforge.net/releases/2011.2.0/it.shtml
>
>> I have only tested with Firefox, Chrome, and Konqueror.  The versions are
>> those that come with Lucid.  Need more testing, especially Internet
>> Explorer
>> and Safari.
>>
>> Yuv
>>
>> [0] http://hugin.sourceforge.net/releases/2011.2.0/en.shtml
>
> I have looked at [0] and [1] with Opera 11.5, and both have problems.
> screenshot hugin-1.jpg shows how Opera renders [1]
> screenshot hugin-2.jpg shows [0] page scrolled to top
> screenshot hugin-3.jpg shows [0] page scrolled down

I get similar problems with firefox 5 on FreeBSD.  They're close
enough to the problems with Opera that it doesn't seem worth attaching
screen shots, but I'll do so if anybody wants them.

Note that both pages fail validation at http://validator.w3.org/ ,
though it's not clear the rendering problems are related to that.

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpu0kmsjI88N.pgp
Description: PGP signature

Re: [hugin-ptx] Re: Hugin 2011.2.0 release notes

[Greg 'groggy' Lehey]

On Friday, 22 July 2011 at 21:54:51 +0100, Bruno Postle wrote:
> On Fri 22-Jul-2011 at 13:09 -0700, Carl von Einem wrote:
>> What's the "official" name for it?
>
> Also it's called "Hugin Calibrate Lens" in the linux desktop menu,
> and "Hugin Lens calibration GUI" in the application itself.
>
> I think "GUI" doesn't mean anything to most people so we should
> avoid it, I'd go for "Hugin Lens Calibration Tool"

Given that this is part of Hugin, the repeated word "Hugin" seems
redundant.  Why not just "Lens Calibration Tool"?

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpdWb9K2OZZI.pgp
Description: PGP signature

Re: [hugin-ptx] Another overlapped image issue

[Greg 'groggy' Lehey]

On Monday, 11 July 2011 at 23:55:25 +0100, Bruno Postle wrote:
> On Sun 10-Jul-2011 at 17:19 +1000, Greg 'groggy' Lehey wrote:
>>> On Sun, 10 Jul 2011 10:22:58 +1000, Groogle  wrote:
>>>
>>>> There's more description, including the images, at
>>>> http://www.lemis.com/grog/diary-mar2011.php#time-lapse
>>>> The resultant images are shown in the diary entry mentioned above.
>>>> The original ones are at:
>>>>
>>>> http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-before.jpeg
>>>> http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-during.jpeg
>>>> http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-after.jpeg
>
>> I'll address the rest in answer to your other message.

Sorry for the slow response here.  My original mail messages came
through with more than 48 hours delay.  From the headers, it seems
that it was from somewhere within Google.  Hopefully this reply will
come through faster.

> The control point generators are particularly bad at matching photos
> taken at long time intervals - The changes in quality and direction
> of light are enough to throw off feature matching.  This is probably
> why Terry needed to delete a lot of 'bad' control points.

Agree, but I'm not sure that's the main problem.  I've been playing
around with these results, and I have come to the following
recognitions:

- The way Terry did it, creating the control points from the "Images"
  window, is vastly superior to the way I tried it the first time from
  the "Assistant" window.
- Some of the control points were on plants and leaves which moved
  from one photo to another.

So I thought, it's a simple set of images with some clearly defined
control points.  Let's do it manually with control points on parts of
the house and brickwork.  The result?  Worse than what Terry got!

> If your photos have different focal lengths, then you can 'unlink'
> the 'degrees of view (v)' lens parameter before optimisation.

This is the "link" box in the
 And this, I think, is part of the
question, though I didn't see any difference between linking and not
linking.

But it seems that Hugin is relying on the focal length information
from EXIF, and in the case of my camera, that information is very
inaccurate.  The focal lengths of the two images were given as 21 mm
(44.72°) and 23 mm (41.18°).  The EXIF data will report a maximum of
one focal length value between these two--maybe.  Maybe there's
nothing at all between the two values.

If Hugin is relying on this information, there's a good chance that it
will be wrong.  I suppose I could guess at closer focal length or
field of view values, but there must be a simpler way.

For the fun of it, I tried changing the focal length spec for the
second and third images.  I left the first one at 23 mm, but by
changing the focal length of the other two.  At 22.421 mm, the errors
dropped to an average of 0.3 pixel, with a maximum of 0.92 pixel.
Wonderful!

Unfortunately, the results didn't look at all wonderful.  Now all
three images have a different size.  I'm experimenting further, but
it's beginning to look as if the Hugin or the control point detectors
need to find another way of determining the relationship between the
image sizes than relying on the EXIF data.  Any thoughts?

There's more information, including images and discussion, at
http://www.lemis.com/grog/diary.php#D11-3 , though that doesn't
include the change of focal length.  I'm continuing to experiment.

And since I've messed it up before, you can get bigger and bigger
images of any of these by simply clicking on the image.

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Another overlapped image issue

[Greg 'groggy' Lehey]

On Sunday, 10 July 2011 at 14:01:47 +1000, Terry Duell wrote:
> Hullo Greg,
>
> On Sun, 10 Jul 2011 10:22:58 +1000, Groogle  wrote:
>
>> There's more description, including the images, at
>> http://www.lemis.com/grog/diary-mar2011.php#time-lapse
>> The resultant images are shown in the diary entry mentioned above.
>> The original ones are at:
>>
>> http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-before.jpeg
>> http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-during.jpeg
>> http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-after.jpeg
>>
> This mightn't be a lot of help, but this is what happened when I had a
> look at your pics.
> Firstly, I found the the original images to be quite low resolution,
> 300x225.

This is a feature, not a bug :-) That was just to show what the images
looked like.  Clearly they're not the right thing for processing.

> I was refused connection when attempting to access other links >
> provided.

Sorry about that.  Typo on my part:
http://.lemis.com/grog/Photos/20110330/tiny/Verandah-before.jpeg
instead of
http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-before.jpeg .

I'll address the rest in answer to your other message.

Thanks for the feedback
Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Another overlapped image issue

[Greg 'groggy' Lehey]

I've read the current thread on "registering" images with some
interest but not much understanding.  I think that my issue is
similar, but to avoid muddying the waters, I'm starting a separate
thread.

I'm trying to create time-lapse images according to the instructions
at http://wiki.panotools.org/Align_a_stack_of_photos .  That doesn't
work, possibly because hugin has changed since then: the 'g' command
gives me no control points whatsoever.  So I selected "Create control
points" from the Images window and got a very bad fit.

The three images in question were all taken from a tripod which wasn't
moved during the time between them (about 20 minutes).  The problem
appears to be that I accidentally changed the focal length of the lens
between the first image and the other two.  Clearly I need to scale
the images to the same size.

According to the instructions, this shouldn't be an issue, but I can't
see a way of telling any of the component programs the focal length of
each image.  Is there a way to do so?  Or is there another way?  This
was supposed to be a "simple" test before I attacked something bigger,
so a solution just for this case isn't of much help.

There's more description, including the images, at
http://www.lemis.com/grog/diary-mar2011.php#time-lapse
The resultant images are shown in the diary entry mentioned above.
The original ones are at:

 http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-before.jpeg
 http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-during.jpeg
 http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-after.jpeg

Bigger versions are available at
http://.lemis.com/grog/Photos/20110330/small/Verandah-before.jpeg
and
http://.lemis.com/grog/Photos/20110330/big/Verandah-before.jpeg ,
etc.  These images are also shown on the diary page in the preceding
entry (http://www.lemis.com/grog/diary-mar2011.php#D30-1).

This is Hugin 2011.0.0.0f9fdaf56720 running on FreeBSD 8.2-STABLE.

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgp5hh5L9pSHL.pgp
Description: PGP signature

[hugin-ptx] Another overlapped image issue

[Greg 'groggy' Lehey]

Apologies if this is a duplicate, but my earlier message doesn't seem
to have made it after 15 hours.

I've read the current thread on "registering" images with some
interest but not much understanding.  I think that my issue is
similar, but to avoid muddying the waters, I'm starting a separate
thread.

I'm trying to create time-lapse images according to the instructions
at http://wiki.panotools.org/Align_a_stack_of_photos .  That doesn't
work, possibly because hugin has changed since then: the 'g' command
gives me no control points whatsoever.  So I selected "Create control
points" from the Images window and got a very bad fit.

The three images in question were all taken from a tripod which wasn't
moved during the time between them (about 20 minutes).  The problem
appears to be that I accidentally changed the focal length of the lens
between the first image and the other two.  Clearly I need to scale
the images to the same size.

According to the instructions, this shouldn't be an issue, but I can't
see a way of telling any of the component programs the focal length of
each image.  Is there a way to do so?  Or is there another way?  This
was supposed to be a "simple" test before I attacked something bigger,
so a solution just for this case isn't of much help.

There's more description, including the images, at
http://www.lemis.com/grog/diary-mar2011.php#time-lapse
The resultant images are shown in the diary entry mentioned above.
The original ones are at:

 http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-before.jpeg
 http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-during.jpeg
 http://www.lemis.com/grog/Photos/20110330/tiny/Verandah-after.jpeg

Bigger versions are available at
http://.lemis.com/grog/Photos/20110330/small/Verandah-before.jpeg
and
http://.lemis.com/grog/Photos/20110330/big/Verandah-before.jpeg ,
etc.  These images are also shown on the diary page in the preceding
entry (http://www.lemis.com/grog/diary-mar2011.php#D30-1).

This is Hugin 2011.0.0.0f9fdaf56720 running on FreeBSD 8.2-STABLE.

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Hugin 2011.0.0 fast panorama preview hangs (was: subject too long)

[Greg 'groggy' Lehey]

On Friday,  3 June 2011 at 21:30:36 -0700, rocketmonkeys wrote:
> I've used older builds of hugin before, and I like it. I updated to
> the 2011.0.0 release to try it out.  I loaded in just a few (4) small
> (1024x768, I think) images to try it out.  I load the images, align
> them, but when the Fast Panorama Preview window shows it's very short,
> the actual panorama image itself is only about 5 pixels tall, and the
> entire program hangs (ie. windows shows "Not Responding").

FWIW, it works fine on FreeBSD.  Is this problem limited to Microsoft
platforms?

Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgpOHBpe8mook.pgp
Description: PGP signature

[hugin-ptx] Where to submit patches?

[Greg 'groggy' Lehey]

Is this the correct place to submit patches for Hugin?  If not, can
somebody tell me where?

In case it is, here's the (short) patch.  Olympus E series cameras,
including (I think) the Pen, have a different EXIF key for the focal
plane diagonal, with the result that the user has to enter the focal
length for every image when selecting the images.  This patch to
src/hugin_base/panodata/SrcPanoImage.cpp fixes the problem:

--- SrcPanoImage.cpp2010/12/28 12:57:50 1.1
+++ SrcPanoImage.cpp2011/03/19 22:06:50
@@ -545,6 +545,10 @@
 float olyFPD = 0;
 getExiv2Value(exifData,"Exif.Olympus.FocalPlaneDiagonal",olyFPD);

+/* For some reason, Olympus E series cameras have a different key. */
+if (olyFPD == 0.0)
+getExiv2Value(exifData, "Exif.OlympusEq.FocalPlaneDiagonal", 
olyFPD);
+
 if (olyFPD > 0.0) {
 // Windows debug stuff
 // fprintf(stdout,"Oly_FPD:");


Greg
--
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua


pgp23RGxfHMit.pgp
Description: PGP signature