Pablo d'Angelo | 1 Jan 12:00 2007
Picon

Re: 0.7beta1 and a few late Christmas wishes


Hi J. Schneider schrieb:
> 
> Hi all,
> 
> I just played a little with a few panoramic snapshots from christmas eve 
> and found some strange behaviour:
> 
> stitcher tab:
> setting pixel hight sets new vfov - is this intended?

Something has to changed if the height changes. Candidates are: width, HFOV 
or VFOV. I think vfov is a good choice, since it is intuitively linked to 
the height of the image.

> While usability has improved greatly recently, there are still some 
> smaller and some bigger things I would wish - unfortunately Christmas is 
> over already.

Luckily, some of the things you mentioned have been handled already. 
However, I won't have that much time for hugin in the new year :-(
to fulfill the other wishes quickly.

> It would be nice if ...
> 
> - the assistant tab showed not only the average error but also the 
> maximum - which is a good hint sometimes if I can improve the fit with a 
> simple operation
> 
> - the straighten horizon feature didn't choose a random image center 
(Continue reading)

stryker | 1 Jan 13:19 2007
Picon

Re: help: hugin 0.7 beta 1 hangs at alignment step...


stryker wrote:

> At the alignment stage (either after manual keypoint or auto-pano's
> completion) hugin.exe consumes 50% CPU and an unchanging memory count
> (and shows as Not Responding in Windows Task Manager) and goes to the
> hourglass cursor.  I've left it overnight now at this stage 3 times
> after setting it up in autopano with fewer keypoints each time - and
> there's no change after 14 hours.  Meanwhile the PC itself continues
> fine - it's not hung overall.
>

More info on this.  I can consistantly reproduce this issue with more
than one panorama set by selecting the "Automatic pre-aligning of
image" option in autopano-sift.  Not using that avoids the hang and the
preview displays within seconds of closing autopano (where previously
hugin would eat CPU cycles and stop responding).

Any thoughts?
Geoff

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

(Continue reading)

Pablo d'Angelo | 1 Jan 13:34 2007
Picon

Re: help: hugin 0.7 beta 1 hangs at alignment step...


stryker wrote:
> 
> 
> stryker wrote:
> 
>> At the alignment stage (either after manual keypoint or auto-pano's
>> completion) hugin.exe consumes 50% CPU and an unchanging memory count
>> (and shows as Not Responding in Windows Task Manager) and goes to the
>> hourglass cursor.  I've left it overnight now at this stage 3 times
>> after setting it up in autopano with fewer keypoints each time - and
>> there's no change after 14 hours.  Meanwhile the PC itself continues
>> fine - it's not hung overall.
>>
> 
> More info on this.  I can consistantly reproduce this issue with more
> than one panorama set by selecting the "Automatic pre-aligning of
> image" option in autopano-sift.  Not using that avoids the hang and the
> preview displays within seconds of closing autopano (where previously
> hugin would eat CPU cycles and stop responding).

Thanks for the report. Did you use autopano-SIFT from within hugin, or did 
you start it externally and then loaded the resulting project file into hugin?

ciao
   Pablo

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic
software" group.
(Continue reading)

Jean-Luc Coulon (f5ibh | 1 Jan 15:29 2007
X-Face
Picon

Fwd: CVS: compilation failed [jean-luc.coulon <at> wanadoo.fr]

With the right identity ;-/

Le 01.01.2007 14:48:43, Jean-Luc Coulon (f5ibh) a écrit :
Hi,

Latest CVS failed to build.

if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H "-I." -I../../src/include  
-I../../src/foreign -I../../src/include -I..  
-I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6  
-DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES  
-D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA   -DPNG_NO_MMX_CODE -pthread  
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include  
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0  
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  
-I/usr/include/freetype2 -I/usr/include/libpng12 -DHasPANO13 -pthread  
-I/usr/include -DINSTALL_XRC_DIR=\"/usr/share/hugin/xrc\"  
-DINSTALL_LOCALE_DIR=\"/usr/share/locale\" -g -O2 -MT wxPanoCommand.o  
-MD -MP -MF ".deps/wxPanoCommand.Tpo" -c -o wxPanoCommand.o  
wxPanoCommand.cpp; \
         then mv -f ".deps/wxPanoCommand.Tpo" ".deps/wxPanoCommand.Po";  
else rm -f ".deps/wxPanoCommand.Tpo"; exit 1; fi
if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H "-I." -I../../src/include  
-I../../src/foreign -I../../src/include -I..  
-I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6  
-DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES  
-D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA   -DPNG_NO_MMX_CODE -pthread  
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include  
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0  
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  
(Continue reading)

Pablo d'Angelo | 1 Jan 20:28 2007
Picon

Re: hugin 0.7 beta 2 released


Hi Joachim,

I released beta 2 in a hurry, not a good idea...

> In the preferences (fine tune tab), there is no value in the "patch
> width" box. As a consequence, finetuning doesn't work. When I set it, it
> works again. After restarting hugin it shows that the entry of "10" has
> not been saved.

Fixed in beta3

> When using the "load defaults" button and then canceled the dialogue,
> the defaults where applied in spite of canceling.

Known bug...

> I wanted to try the brightness adjustment of PTStitcher and specified
> PTMender as alternative. When stitching I got the error message:
> Execution of command "start" "<output file path>" failed (error 2:
> System can't find specified file.)

I have added an option to open the stitched pano with another program after
completion. It was enabled accidentally. Sorry there is no Tab in the
Preferences for it yet, so it is disabled in beta3.

>> 1. The buggy crop dialog has been replaced by a crop tab.
> I haven't yet found out how to use it; it seems not to do what it should
> do.

(Continue reading)

J. Schneider | 1 Jan 20:42 2007
Picon
Picon

Re: 0.7beta1 and a few late Christmas wishes


Pablo d'Angelo schrieb:
> Hi J. Schneider schrieb:
>> ... stitcher tab:
>> setting pixel hight sets new vfov - is this intended?
> 
> Something has to changed if the height changes. Candidates are: width, 
> HFOV or VFOV. I think vfov is a good choice, since it is intuitively 
> linked to the height of the image.
What about hight?
Change width -> hight is adjusted; change hight -> width is adjusted.
This would be intuitive for me.

>> It would be nice if ...
> Luckily, some of the things you mentioned have been handled already. 
> However, I won't have that much time for hugin in the new year :-(
> to fulfill the other wishes quickly.
Hope it is due to pleasant work you get payed better.

>> - the straighten horizon feature didn't choose a random image center 
>> (but it's a great feature - I just tried the first time and it is 
>> really magic!)
> 
>  From hugin 0.7 beta2 onwards, the view is centered after the horizon 
> straighten.
This is good. But what is centered in a 360° pano? It is always centered 
on image 0, no matter where the anchor is set. (To be exact: in my test 
case image 0 out of 25 is set to 7° yaw, being nearest to 0°. Anchor is 
no. 11.)

(Continue reading)

Pablo d'Angelo | 1 Jan 23:56 2007
Picon

Re: 0.7beta1 and a few late Christmas wishes


J. Schneider schrieb:

> Pablo d'Angelo schrieb:
 >
>> Something has to changed if the height changes. Candidates are: width, 
>> HFOV or VFOV. I think vfov is a good choice, since it is intuitively 
>> linked to the height of the image.
> What about hight?
> Change width -> hight is adjusted; change hight -> width is adjusted.
> This would be intuitive for me.

There is also a technical reason... HFOV, width and height are the values 
used by panotools. Using VFOV requires calculations that depend on the 
projection, and hugin currently doesn't support setting vfov for some of the 
new projections, therefore the height is currently the only way to set the 
image size for them.

>>  From hugin 0.7 beta2 onwards, the view is centered after the horizon 
>> straighten.
> This is good. But what is centered in a 360° pano? It is always centered 
> on image 0, no matter where the anchor is set. (To be exact: in my test 
> case image 0 out of 25 is set to 7° yaw, being nearest to 0°. Anchor is 
> no. 11.)

I have fixed that in beta3 (currently uploading to sourceforge...) Now the 
view is only centered for partial panoramas.

ciao
   Pablo
(Continue reading)

Pablo d'Angelo | 2 Jan 00:02 2007
Picon

Hugin 0.7 beta3


Hi all,

Hugin 0.7 beta 3 is available for testing. Changes from beta 2 include:

- fixed various major bugs in crop tab
- possibility to automatically open final panorama with an image editor
- straighten does not recenter 360 degree panos
- display output of all command line utilities in own window instead of the 
terminal (linux)
- warn user that PTmender does only support TIFF_m
- include autooptimiser in the window binary package

Source code and windows binaries are available at:
http://hugin.sourceforge.net/download/

ciao
   Pablo

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

stryker | 2 Jan 02:34 2007
Picon

Re: help: hugin 0.7 beta 1 hangs at alignment step...


> Thanks for the report. Did you use autopano-SIFT from within hugin, or did
> you start it externally and then loaded the resulting project file into hugin?
>
> ciao
>    Pablo

Hi Pablo,

Autopano-SIFT was launched by hugin so I'm doing all this using the
assistant tab.  The only wrinkle is that the EXIF data doesn't survive
the conversion to TIF so I've had to manually enter the focal length
and perspective-crop multiplier.  Then I hit Align and it launches
Autopano-SIFT which completes successfully - I close that and the
hourglass starts.

Last night I've created two more panoramas in Hugin without the
automatic alignment ticked in Autopano-SIFT. I really thought I had
that set in the first few I did (but my recollection may be flawed on
that).

Thanks for your help...I can put some representative images up on an
FTP for you if you can't recreate this at your end.

Cheers!
Geoff

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic
software" group.
(Continue reading)

Ippei UKAI | 2 Jan 02:47 2007
Picon

hugin 0.7 beta gui


Happy New Year,

I've finally had a time to try the 0.7 beta.

Not sure how other people are feeling about it, but I found the new  
Assistant tab odd. All other tabs are for editing one aspect each of  
the opened project, but the Assistant tab is out of place. Maybe it  
should be implemented as a separate window, say like a Wizard-type  
assistant many other applications have?

Meanwhile, I have to apologise that I still have not enough time, but  
as discussed before just after the 0.6 release, the overall review of  
all the menu/button labels and keyboard shortcuts should take a  
place. Could anyone take a look at it? The task is only to rename  
buttons, menu items etc. and assign new shortcuts to them so that all  
Win, Mac, Gnome and KDE people would feel fairly natural and  
comfortable to use. Considering how badly "Redo" shortcut varies  
among Mac apps (supposed to be Cmd-Shift-Z), I think it's good to  
have platform specific shortcuts. Maybe all shortcuts should be  
specified in a resource file, which we can have platform defaults, as  
well as user specific customized one.

By the way, could the preferences panel easily be converted into the  
more common style like VLC and Audacity's?

Sorry having not so much time. I hope I'll have some time after I get  
back to the UK. I hope to at least do the Japanese localization on  
time for 0.7.

(Continue reading)


Gmane