Kornel Benko | 1 May 2011 10:49
Picon
Favicon

hugin trunk not compilable

Hi, trying to compile hugin, I get this:

...

/usr/include/c++/4.4/backward/backward_warning.h:28: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated.

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp: In constructor ‘LensCalFrame::LensCalFrame(wxWindow*)’:

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:152: error: ‘class wxConfigBase’ has no member named ‘ReadBool’

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:154: error: ‘class wxConfigBase’ has no member named ‘ReadBool’

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:156: error: ‘class wxConfigBase’ has no member named ‘ReadBool’

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:158: error: ‘class wxConfigBase’ has no member named ‘ReadBool’

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp: In destructor ‘virtual LensCalFrame::~LensCalFrame()’:

...

On my system there is similar function, but with prefix "do".

...

// do read/write the values of different types

virtual bool DoReadString(const wxString& key, wxString *pStr) const = 0;

virtual bool DoReadLong(const wxString& key, long *pl) const = 0;

virtual bool DoReadInt(const wxString& key, int *pi) const;

virtual bool DoReadDouble(const wxString& key, double* val) const;

virtual bool DoReadBool(const wxString& key, bool* val) const;

virtual bool DoWriteString(const wxString& key, const wxString& value) = 0;

...

And this here are the remaining problems

...

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:209: error: call of overloaded ‘Write(const wchar_t [30], unsigned int&)’ is ambiguous

/usr/include/wx-2.8/wx/confbase.h:189: note: candidates are: bool wxConfigBase::Write(const wxString&, const wxString&)

/usr/include/wx-2.8/wx/confbase.h:192: note: bool wxConfigBase::Write(const wxString&, long int)

/usr/include/wx-2.8/wx/confbase.h:195: note: bool wxConfigBase::Write(const wxString&, int)

/usr/include/wx-2.8/wx/confbase.h:198: note: bool wxConfigBase::Write(const wxString&, double)

/usr/include/wx-2.8/wx/confbase.h:201: note: bool wxConfigBase::Write(const wxString&, bool)

/usr/include/wx-2.8/wx/confbase.h:206: note: bool wxConfigBase::Write(const wxString&, const wxChar*) <near match>

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp: In member function ‘void LensCalFrame::OnFindLines(wxCommandEvent&)’:

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:576: error: conversion from ‘const wxCharBuffer’ to non-scalar type ‘std::string’ requested

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalFrame.cpp:582: error: no matching function for call to ‘ImageLineList::SetLines(HuginLines::Lines)’

/usr/src/hugin/hugin_hg/src/hugin1/calibrate_lens/LensCalTypes.h:56: note: candidates are: void ImageLineList::SetLines(HuginLines::Lines&)

make[2]: *** [src/hugin1/calibrate_lens/CMakeFiles/calibrate_lens_gui.dir/LensCalFrame.cpp.o] Fehler 1

...

Kornel

Terry Duell | 1 May 2011 12:37
Picon
Picon

Re: hugin trunk not compilable

Hullo Kornel,

On Sun, 01 May 2011 18:49:25 +1000, Kornel Benko <Kornel.Benko <at> berlin.de>  
wrote:

> Hi, trying to compile hugin, I get this:
> ...
[snip]
I also get error messages trying to build an rpm package on Fedora 14.
I have filed a bug report.

Cheers,
-- 
Regards,
Terry Duell

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

gilgab | 1 May 2011 08:39
Picon

french traduction : multi-row tutorial

<h1>Tutoriel Hugin - Assemblage Multi-rangées de photos</h1>
<br />(http://hugin.sourceforge.net/tutorials/multi-row/en.shtml)
<p><strong>Ce tutoriel couvre une utilisation plus complexe de Hugin,
en prenant deux séries de photographies pour les assembler pour former
une seule image, en utilisant <em>l'assistant</em> automatisé. Le même
procédé peut être appliqué à plus de deux rangées.</strong></p>
<p><strong>Vous aurez besoin d'un générateur de point de contrôle tels
que autopano-sift-C installé pour faire cette génération panoramique
entièrement automatisé.</strong></p>
<p><em><span style="font-weight: bold;">Note : </span>Ce tutoriel est
basé sur la version 0.7.0 de Hugin. Même si votre version diffère, le
principe sous-jacent reste le même.</em></p>
<p>Ci-dessous, le groupe de photographies qui ont été prises de la
Bibliothèque d'État de Victoria, Swanston Street à Melbourne.</p>
<p>Vous pouvez télécharger ces images (<a href="http://
hugin.sourceforge.net/tutorials/multi-row/p986.jpg">p986.jpg</a> <a
href="http://hugin.sourceforge.net/tutorials/multi-row/
p987.jpg">p987.jpg</a> <a href="p988.jpg">p988.jpg</a> <a href="http://
hugin.sourceforge.net/tutorials/multi-row/p989.jpg">p989.jpg</a> <a
href="p990.jpg">p990.jpg</a> <a href="http://hugin.sourceforge.net/
tutorials/multi-row/p991.jpg">p991.jpg</a> <a href="http://
hugin.sourceforge.net/tutorials/multi-row/p992.jpg">p992.jpg</a>, et
<a href="http://hugin.sourceforge.net/tutorials/multi-row/
p993.jpg">p993.jpg</a>) et essayer par vous-même.</p>
<p><img src="http://hugin.sourceforge.net/tutorials/multi-row/all-
pics.jpg" alt="Toutes les images" /></p>
<p>Cette série de photos est un bon exemple sur la façon dont Hugin
peut assembler et mélanger plusieurs rangées de photos en un panorama,
avec des complications inhabituelles :</p>
<ul>
<li>Le nombre de photos est différent dans chaque ligne.</li>
<li>L'appareil a été laissé sur "exposition automatique" ce qui
signifie que la luminosité des photos varie de deux diaphragmes entre
les plans les plus sombres et les plus clairs.</li>
<li>L'appareil a été tenus à la main, ce qui signifie que les photos
sont décalées vers le haut ou vers le bas dans chaque ligne.</li>
<li>Il ya une erreur de parallaxe causée par le déplacement physique
de l'appareil photo créant une petite distance entre certains plans.</
li>
</ul>
<p>Commencez par lancer Hugin, et en utilisant l'onglet
<big><strong>Assistant</strong></big> et sélectionnez le bouton :
<big><strong>[ 1. Charger des images... ]</strong></big> pour
sélectionner toutes les images du projet.</p>
<p><em><span style="font-weight: bold;">Astuce :</span> vous pouvez
sélectionner plusieurs images dans la boîte de dialogue de fichier ou
de glisser des fichiers à partir d'un navigateur de fichier
approprié.</em></p>
<p>Sélectionnez le bouton : <big><strong>[ 2. Aligner ]</strong></big>
et le programme autopano commencera à trouver des points communs
(points de contrôle) dans toutes les zones de chevauchement des
images.</p>
<p>Lorsque le programme autopano a terminé la mise en correspondance
des points de contrôle, Hugin alignera les images en ajustant les
positions et la correction d'exposition, alors la fenêtre de
prévisualisation s'ouvrira.</p>
<p><img src="http://hugin.sourceforge.net/tutorials/multi-row/
preview.jpg" alt="prévisualisation" /></p>
<p>Hugin peut avoir réglé la projection sur <big><span style="font-
weight: bold;">Panorama (cylindrique)</span></big>, mais pour un
projet de cette nature, il est préférable de définir la projection
<big><span style="font-weight: bold;">rectiligne</span></big>. Vous
pouvez essayer différentes projections pour voir l'effet.</p>
<p>Vous pouvez maintenant fermer la fenêtre d'aperçu et sélectionnez
le bouton <big><strong>[ 3. Créer le panorama ]</strong></big> une
fois terminé, on vous demandera où vous voulez enregistrer vos
fichiers de projet et d'un nom pour l'image finale assemblée, qui est
représenté ici.</p>
<p><img src="http://hugin.sourceforge.net/tutorials/multi-row/auto-
stich-1.jpg" alt="final" /></p>
<p>Hugin a fait du bon travail d'assemblage et de mélange des images,
en fait, il a fait beaucoup mieux que je n'aurais été en mesure de le
faire en sélectionnant manuellement les points de contrôle. Hugin est
plus rigoureux que la plupart d'entre nous et est susceptible de
sélectionner beaucoup plus de points de contrôle, garantissant ainsi
un bon résultat. Le résultat final serait améliorée si les «trous» à
droite en haut et à l'avant avaient été couverts, mais l'image peut
encore être améliorée tout en conservant le bâtiment de la
bibliothèque et la plupart des marches de l'entrée.</p>
<p>Lorsque vous tentez un panorama multi-lignes, il peut aider à
contrôler la façon dont les images se chevauchent, et, si possible,
trouver la meilleure longueur focale pour assurer une bonne couverture
de la scène et le chevauchement des images avant de tenter de prendre
les photos. Contribuant également à mettre en place un plan visuel
dans votre esprit pour la couverture du sujet.</p>
<p>Pour un sujet où le nombre de lignes est supérieur à deux, il
pourrait devenir difficile de garder trace de vos localisation d'image
et il peut être utile de faire un croquis de la mise en page des
photos que vous pouvez utiliser pour voir où chaque cliché doit être
pris afin d'assurer de ne pas vous retrouver avec des trous dans votre
panorama.</p>
<p>Si vous étiez tenté de le faire manuellement, lors de l'ajout des
points de contrôle que vous faites pour tous les chevauchements des
photos côte-à-côte et dessus-dessous, suivez les principes des deux
tutoriaux photos, comme le montre ce schéma.</p>
<p><img src="http://hugin.sourceforge.net/tutorials/multi-row/multi-
row.jpg" alt="overlap-diagram" /></p>
<p>Le panorama qui en résulterait pourrait avoir une perspective
corrigée, en utilisant les méthodes décrites dans le tutoriel sur la
<a href="http://hugin.sourceforge.net/tutorials/
perspective">perspective.</a></p>
<p>Ce tutoriel et les photos sont de Terry Duell avril 2008 (traduit
par R2G le 20110430)</p>

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

spsilk | 1 May 2011 17:39
Picon

Hugin Khan Deghosting Algorithm having no effect

Hi All,

I was trying use the Khan algorithm implemented in Hugin as a
deghosting method for a pure HDR application. At just one iteration,
it gives better results than the basic average, but increasing the
number of iterations beyond 1 doesn't seem to have any effect, i.e.
the ghosts do not "fade away" as described in Kahn et al.'s paper. Can
anyone tell me if there's some trick to this?

What I've done is just taken in my exposure-bracketed images, manually
entered exposure info for them in the Camera and Lens tab (they were
shot at 1/3 EV spacing so I entered zero EV for first, then decreased
by .33EV for each successive shot), and put it on linear response
because I shot RAW then used a linear demosaicing process. In the
Stitcher tab, I check HDR for Panorama outputs, and under HDR merger,
choose Deghosting -> Khan.

I've uploaded my images and Hugin project file below if anyone has a
moment to look at it and see if I'm missing some setting. Thanks.

Test set: http://www.site.uottawa.ca/~ssilk083/hugin_test.rar

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

sebastien delcoigne | 1 May 2011 19:08
Picon
Gravatar

Re: Re: masks

Thanks kay

On Sat, Apr 30, 2011 at 3:53 PM, kfj <_kfj <at> yahoo.com> wrote:


On 29 Apr., 16:14, sebastien delcoigne <sebastien.delcoi... <at> gmail.com>
wrote:
>
> That's already what I do. But most of my panos have more than 15 photos and
> a lot of them have over 20. I guess I'll take a look at the project files,
> see if I can figure out what lines correspond to the mask.

Sensible step. The relevant lines in the pto (at least in a hugin-
generated one) look like this:

# masks
k i0 t0 p"2334 4319 1704 3106 1531 3161 1286 3437 908 4343"
k i1 t0 p"2334 4319 1704 3106 1531 3161 1286 3437 908 4343"
...

the '#masks' is just a comment, after that you get a set of 'k-lines'.
Their first field (after the k, which is the line type specifier), so
in this case 'i0' says which image the mask is used for (image 0 in
this case), 't0' indicates an exclude mask, and the string after the p
has a set of pairs of coordinates. If you want to reuse a mask for
another image, you can simply copy the k-line and change the i-field,
which is what I have done to get the second k-line in the example. You
can do this in an editor or do a bit of script-writing to automate the
task.

Kay

--
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx



--
Sébastien

--
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
Bruno Postle | 2 May 2011 01:40
X-Face

Re: x-y-ratio in mosaic-mode

On Fri 29-Apr-2011 at 16:34 +0200, Wirz wrote:
>
>I take photos of graffities a lot: [1]
>
>Is there any way to make sure the x-y-ratio of the object and the photo
>are the same?  I have the impression that it differs a little although
>my photos match perfectly.  If I understand the mosaic mode correctly
>this is to be expected -- the single photos do still match if they are
>all compressed or stretched by the same amount.  The only way to get the
>correct result would be to take one photo in a direction rectangular to
>wall and set {X, Y, Z}=0 for this photo.  Do I understand this correctly?

My experience is that it doesn't matter, Hugin reprojects the photos 
onto an imaginary plane and the proportions of this plane are 
'correct'.  i.e. Both of these were taken with the camera pointing 
at an angle to the surface for every shot, but they look right to me: 
http://www.flickr.com/photos/36383814 <at> N00/5454266721
http://www.flickr.com/photos/36383814 <at> N00/5666484281

-- 
Bruno

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Kornel Benko | 2 May 2011 07:37
Picon
Favicon

Re: hugin trunk not compilable

Am Sonntag, 1. Mai 2011 schrieb Terry Duell:

> Hullo Kornel,

>

> On Sun, 01 May 2011 18:49:25 +1000, Kornel Benko <Kornel.Benko <at> berlin.de>

>

> wrote:

> > Hi, trying to compile hugin, I get this:

> > ...

>

> [snip]

> I also get error messages trying to build an rpm package on Fedora 14.

> I have filed a bug report.

>

> Cheers,

Thaks Terry. Sorry for being so lazy.

Kornel

Terry Duell | 2 May 2011 08:12
Picon
Picon

Re: hugin trunk not compilable

Hullo Kornel,

On Mon, 02 May 2011 15:37:14 +1000, Kornel Benko <Kornel.Benko <at> berlin.de>  
wrote:

>> [snip]
>> I also get error messages trying to build an rpm package on Fedora 14.
>> I have filed a bug report.
>>
>> Cheers,
>
> Thaks Terry. Sorry for being so lazy.

It is now fixed. Builds OK.

Cheers,
-- 
Regards,
Terry Duell

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Oskar Sander | 2 May 2011 12:11
Picon

Re: x-y-ratio in mosaic-mode

But is it right to say that you still do need to indicate to Hugin how you would like to projet the images, i.e. what view you want.  In a case where all the immages have been at an angle,   I've done this by in one image indcate a straight vertical and horizontal line for hugin to include in optimization.

Cheers
/O


2011/5/2 Bruno Postle <bruno <at> postle.net>
On Fri 29-Apr-2011 at 16:34 +0200, Wirz wrote:

I take photos of graffities a lot: [1]

Is there any way to make sure the x-y-ratio of the object and the photo
are the same?  I have the impression that it differs a little although
my photos match perfectly.  If I understand the mosaic mode correctly
this is to be expected -- the single photos do still match if they are
all compressed or stretched by the same amount.  The only way to get the
correct result would be to take one photo in a direction rectangular to
wall and set {X, Y, Z}=0 for this photo.  Do I understand this correctly?

My experience is that it doesn't matter, Hugin reprojects the photos onto an imaginary plane and the proportions of this plane are 'correct'.  i.e. Both of these were taken with the camera pointing at an angle to the surface for every shot, but they look right to me: http://www.flickr.com/photos/36383814 <at> N00/5454266721
http://www.flickr.com/photos/36383814 <at> N00/5666484281

--
Bruno


--
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx



--
/O

--
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
gridrix | 2 May 2011 17:17

hugin slow with many images

Hello everybody,

first I want to say thank you to all the people working on hugin, it's
a great program that I use a lot.
The problem is that I recently built a panorama-roboter with
fischertechnik, and after a test run I tried to build the panorama
with hugin. I used cpfind in multirow mode to create the control
points.
Opening the panorama, showing the preview is of course slower, but
reasonably so.
However if I try to disable or enable single images in the preview
window, or when I try to disable parameters in the optimizer tab hugin
hangs busy for tens of second for every single action I do. I did a
debug build of hugin and started to do some profiling with oprofile,
and it seems to spend 99% of its time in
HuginBase::ImageVariable<hugin_utils::TDiff2D<double>
>::searchForwards(HuginBase::ImageVariable<hugin_utils::TDiff2D<double>
> const*) const
in the api documentation there is a comment about the ImageVariable
stuff being slow, so is there a chance of speeding this up?

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Gmane