[hugin-ptx] Re: Obsolete programs and outdated translations

[RueiKe]

Hi Thomas,
 
It has been a long time since I have worked on the Chinese Traditional 
translation...  I think I can get back to it and work to improve.  Though 
it may take a while...
 
Rick
 

On Thursday, May 9, 2013 4:09:27 PM UTC+8, T. Modes wrote:

> Hi group, 
>
> the hugin repository contains a lot of programs. Most of them are used 
> by the normal workflow. But there are also some program with are 
> obsolete, duplicates or superseded. 
>
> This affects the following programs: 
> * matchpoint: supersedes by cpfind 
> * PTBatcher: PTBatcherGUI provides the same functionality 
> * nona_gui: Hugin itself is only using nona. Nona_gui provides only a 
> GUI for select the project file to remap. 
> * autopano-noop.sh: wrapper around autopano-sift to show a warning if 
> autopano-sift is not installed. This is obsolete now with cpfind the 
> default control point detector. 
>
> Is there somebody using these programs? 
> If nobody objects these programs will be removed for the next release. 
>
> Second point: translations 
>
> For following translation files cover only 30-40 % and were not 
> updated in the last years. 
> ca_ES.po  (Catalan) 
> 300 translated messages, 576 fuzzy translations, 507 untranslated 
> messages. 
> last updated Nov 2005 
> sl.po (Slovenian) 
> 479 translated messages, 479 fuzzy translations, 425 untranslated 
> messages. 
> last updated Feb 2009 
> uk.po (Ukrainian) 
> 371 translated messages, 574 fuzzy translations, 438 untranslated 
> messages. 
> last updated Aug 2006 
> bg.po (Bulgarian) 
> 509 translated messages, 505 fuzzy translations, 369 untranslated 
> messages. 
> last updated Jul 2008 
> ko.po (Korean) 
> 510 translated messages, 491 fuzzy translations, 382 untranslated 
> messages. 
> last updated Apr 2008 
>
> If there is no update to these language files, they will be removed 
> from the release. 
> (The current status of the file will be preserved - so the already 
> done work is not lost. But they will not be included in the installed 
> version.) 
>
> And a remainder: The following 4 translation are also behind the 
> current state. They cover more strings, but should also be updated. 
> (They will not yet removed, but they are candidates for the next 
> round.) 
> ro.po (Romanian) 
> 674 translated messages, 397 fuzzy translations, 312 untranslated 
> messages. 
> last updated Jan 2011 
> fi.po (Finnish) 
> 811 translated messages, 307 fuzzy translations, 265 untranslated 
> messages. 
> last updated Jun 2010 
> pl.po (Polish) 
> 839 translated messages, 329 fuzzy translations, 215 untranslated 
> messages. 
> last updated Mar 2010 
> zh_TW.po (Chinese) 
> 964 translated messages, 325 fuzzy translations, 94 untranslated 
> messages. 
> last updated Oct 2011 
>
> Thomas 
>

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

--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[hugin-ptx] Re: Declaring 2010.4.0 final and moving on

[RueiKe]

Hi Yuv,

The biggest advantage I see in blending first is just how much use you
can get out of the blended exposure layers.  Since I generate them for
each project, it makes things simpiler to use them in the enfusion.
Some examples:
1) Use layers in gimp to remove movement of faces by overlay faces
from nominal exposure layers like in this example:
http://www.flickr.com/photos/rueike/5306085871/
2) Using the exposure layers for hdr layers to overlay with the
enfusion for better contrast
3) Using various exposure layers overlayed and masked in gimp for
improved dynamic range.  This examples uses both 2 & 3:
http://www.flickr.com/photos/rueike/5046727075/
4) Running enfuse offline, experimenting with exclusion of layers and
adjusting weightings for better results.

I also convinced myself that blended then fused gives better results
than fused then blended in this example: 
http://www.flickr.com/photos/rueike/4321371747/

Regards,
Rick

On Jan 1, 11:33 pm, Yuval Levy  wrote:
> On January 1, 2011 07:03:16 am RueiKe wrote:
>
> > I just wanted to report back with my latest attempt with 2010.4.
>
> Thanks for the report, Rick.
>
> > I have gone through 2 cases making sure I did not optimize translation
> > and everything worked fine!
>
> Sometimes less is more, isn't it?  That's where our interface still sucks at
> guiding users who are between being an occasional user and a power user.
>
> While we muse about how to fix it, the golden rule for wannabe-power-users:  
> more is not always better...
>
> > nicer interface!  Only 2 items that are of some concern.  For some
> > reason whenever nona runs, it pops a command window which becomes the
> > active window, which makes it difficult to work on other items.
>
> Must be a windows build issue.  tifflib if I am not mistaken. �...@matthew?
>
> > I have been using the previously available option for a blended then
> > fused pano and keeping the blended exposure layers.  It doesn't seem
> > to be an option in this release, but it is easy to just enfuse the
> > blended expsosures layers afterward in the command line.
>
> The Stitcher tab was incredibly confusing.  James has cleared some of that
> confusion, and part of it was to remove inefficient options.
>
> What advantage do you see in first blending the exposure layers and then
> enfusing, rather than doing it the other way around (which is computationally
> lighter)?
>
> > I feel bad that I have gotten behind on the Traditional Chinese
> > translation.  I will try to have updated for the next release...
>
> Don't worry.  The project accepts translations on an ongoing basis.  Feel free
> to contribute whenever you have time.
>
> Yuv
>
>  signature.asc
> < 1KViewDownload

-- 
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] Re: Declaring 2010.4.0 final and moving on

[RueiKe]

I just wanted to report back with my latest attempt with 2010.4.  I
have gone through 2 cases making sure I did not optimize translation
and everything worked fine!  Much faster than previous releases and
nicer interface!  Only 2 items that are of some concern.  For some
reason whenever nona runs, it pops a command window which becomes the
active window, which makes it difficult to work on other items.  Also,
I have been using the previously available option for a blended then
fused pano and keeping the blended exposure layers.  It doesn't seem
to be an option in this release, but it is easy to just enfuse the
blended expsosures layers afterward in the command line.

I feel bad that I have gotten behind on the Traditional Chinese
translation.  I will try to have updated for the next release...

Thanks!
Rick

On Dec 27 2010, 8:50 pm, Yuval Levy  wrote:
> Hi Rick,
>
> On December 27, 2010 06:20:34 am RueiKe wrote:
>
> > Thanks Yuv for your very detailed response!
>
> happy to read that it helped.
>
> > I can usually acheive about 0.3 pixel mean error for a 16k wide pano.
>
> beware of this metrics.  It is blind to the quality of the CPs and thus to the
> real quality of the panorama, and I think that if we want to make Hugin more
> user friendy, we should remove the number all together and replace them with
> "likely to be very good / well / poorly / badly aligned" instead.
>
> I've had a long discussion about this metrics with somebody else on this list
> a few months back.
>
> > For this project, the intital alignment looked fine.  It was when I
> > removed the outlier control points and realigned when I ran into
> > problems.
>
> removing the outlier is a blind process as well.  If you have, for example, a
> lot of features in the foreground that "captures" the majority of the CPs, the
> background CPs will be declared outliers, even if it is known that the further
> away from the camera a CP is located, the less sensitive it is to parallax and
> other negative factors.  And if those front features are in movement, the
> statistics are toast.
>
> > Seems like my choice for optimization parameters may have
> > caused the problems.
>
> probably the immediate one, yes.  It seems to me that you have the potential
> to bring your process to the next level and if you want you will find helpful
> feedback here on the list.
>
> > Let me try it again when I finish my current
> > project.  Should be able to report back in a few days.  If I continue
> > to have problems, I will open a bug report.
>
> OK.  Looking forward for your report - preferably a link to your flickr
> gallery ;-)
>
> Yuv
>
>  signature.asc
> < 1KViewDownload

-- 
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] Re: Declaring 2010.4.0 final and moving on

[RueiKe]

Hi Yuv,

Yes, I am glad to be back to this forum after having to step away for
about 6 months.  Had too much going on with a change in my job!  I
have been working through about 3000 photos from a recent trip to
Dresden, so my computer has been non-stop with projects for a while
now.  My photos can be found along with some description of the
process here: http://www.flickr.com/photos/rueike/

Regards,
Rick

On Dec 27, 8:50 pm, Yuval Levy  wrote:
> Hi Rick,
>
> On December 27, 2010 06:20:34 am RueiKe wrote:
>
> > Thanks Yuv for your very detailed response!
>
> happy to read that it helped.
>
> > I can usually acheive about 0.3 pixel mean error for a 16k wide pano.
>
> beware of this metrics.  It is blind to the quality of the CPs and thus to the
> real quality of the panorama, and I think that if we want to make Hugin more
> user friendy, we should remove the number all together and replace them with
> "likely to be very good / well / poorly / badly aligned" instead.
>
> I've had a long discussion about this metrics with somebody else on this list
> a few months back.
>
> > For this project, the intital alignment looked fine.  It was when I
> > removed the outlier control points and realigned when I ran into
> > problems.
>
> removing the outlier is a blind process as well.  If you have, for example, a
> lot of features in the foreground that "captures" the majority of the CPs, the
> background CPs will be declared outliers, even if it is known that the further
> away from the camera a CP is located, the less sensitive it is to parallax and
> other negative factors.  And if those front features are in movement, the
> statistics are toast.
>
> > Seems like my choice for optimization parameters may have
> > caused the problems.
>
> probably the immediate one, yes.  It seems to me that you have the potential
> to bring your process to the next level and if you want you will find helpful
> feedback here on the list.
>
> > Let me try it again when I finish my current
> > project.  Should be able to report back in a few days.  If I continue
> > to have problems, I will open a bug report.
>
> OK.  Looking forward for your report - preferably a link to your flickr
> gallery ;-)
>
> Yuv
>
>  signature.asc
> < 1KViewDownload

-- 
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] Re: Declaring 2010.4.0 final and moving on

[RueiKe]

Hi Kay,

I typically add as many CP as I can and after the first alignment I
will delete those that are definitely bad.  Usually, there will be
many points with errors of several thousand pixels.  You can usually
see a distribution change between normal and outliers.  After this, I
will set the Nadir to a unique lens number and iteratively opimize
everything and remove outliers.  I will inspect a sample of the
outliers to make sure they are really bad each time.  In some
situations, cloud movement will cause good points to have higher
errors, so I am careful not to delete too many good points.  I can
usually get a defect free stitch with a 21mm lens using this
technique, but I agree there are probably simpiler methods.

Regards,
Rick

On Dec 27, 7:48 pm, kfj <_...@yahoo.com> wrote:
> On 27 Dez., 12:20, RueiKe  wrote:
>
>
>
> > The project did use a pano head, so all stacks will be aligned with
> > the exception of the nadir, which may have some slight movement, so I
> > add control points to align the Nadir and specify a different lens
> > after the intial alignment.  I am still using autopano-sift-c.  Yes, I
> > use a lot of control points then delete many during the processes of
> > successive optimizations.  I can usually acheive about 0.3 pixel mean
> > error for a 16k wide pano.
>
> You may loose more than you gain by throwing out a great number of
> CPs. Often the 'best' CPs are clustered in unproblematic areas,
> particularly if you are using a fisheye and/or the lens isn't
> perfectly calibrated. If you just throw out everything above a
> threshold, you may end up with insufficient area coverage. Don't be
> too keen on minimizing the mean error, it's not a measure for the
> quality of your final panorama, just an indicator about the CPs. In my
> experience it is useful to throw out only CPs which are obviously way
> off or wrong (like, the worst 10%, or everything above 10). The
> optimizer is a very clever thing and can well cope with outliers.
>
> 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@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] Re: Declaring 2010.4.0 final and moving on

[RueiKe]

Thanks Yuv for your very detailed response!

The project did use a pano head, so all stacks will be aligned with
the exception of the nadir, which may have some slight movement, so I
add control points to align the Nadir and specify a different lens
after the intial alignment.  I am still using autopano-sift-c.  Yes, I
use a lot of control points then delete many during the processes of
successive optimizations.  I can usually acheive about 0.3 pixel mean
error for a 16k wide pano.

For this project, the intital alignment looked fine.  It was when I
removed the outlier control points and realigned when I ran into
problems.  Seems like my choice for optimization parameters may have
caused the problems.  Let me try it again when I finish my current
project.  Should be able to report back in a few days.  If I continue
to have problems, I will open a bug report.  Thanks again for your
very detailed response!

Regards,
Rick

On Dec 27, 12:39 pm, Yuval Levy  wrote:
> Hi Rick,
>
> On December 26, 2010 09:33:28 pm RueiKe wrote:
>
> > My attempt to use the latest build on a typical complex project
> > indicates significant issues.
>
> I downloaded your PTO file but did not have time to look at it right away and
> now I don't have the "significant issues" you mentioned present.  However I
> played with it and found no "significant issue".
>
> The project loaded well (with placeholder images, that is).  The application
> is responsive.
>
> I see 31 stacks defined.  I see a lot of CPs.  I don't recall how you
> generated them; nor can I visually judge their quality.  I find the quantity
> excessive - personally I would do such a project with less than 200 CPs, while
> you have more than 9000.  Even if this was about stitching 217 individual
> frames (single exposures; or misaligned stacks), 1000-1500 CPs would be more
> than enough.
>
> I assume that the stacks are perfectly aligned (shot on a tripod or so), and
> that you want to tonemap a resulting HDR.  Have you considered merging each of
> the stacks first into an HDR image first using pfstools or LuminanceHDR?  This
> would cut computational work by as much as 80%.
>
> It would be helpful if you could detail the issues in ticket(s) on the bug
> tracker so that when trying to figure them out, developers don't have to
> scramble around for information.
>
> I am working on this in my spare time.  I keep folders on my HDD - one folder
> per issue - and the name of the folder is usually the number of the tracker
> ticket (but in this case it was your pseudonym because there was no tracker
> ticket).  It takes only a few seconds to be back on the right page that way.  
> It takes much longer if there is no ticket.
>
> > I understand that my use case of 217 images is not typical
>
> It may not be typical in the sense that it is not the average project;  and
> that probably there is a more efficient way to deal with the project; but it
> is not unique in terms of size.  There are other users processing that amount
> of images and more.
>
> > , but I think it has always been a critical feature for hugin to be able to
> > handle very large projects.
>
> "critical feature" is a bit of an inflated qualification.  There has never
> been any kind of warranty, implied or explicit, that Hugin is fit for any
> purpose.  It is true that Hugin has been handling successfully projects of
> this size and larger in the past; that we take seriously reports such as yours
> and try to help you get the most out of Hugin.  But a single report from a
> single user is never critical until confirmed.
>
> If the report was in the bug tracker, other users experiencing the same issue
> could confirm; add their own experiences and observations; and we would get a
> better picture of whether this is critical or not and what we are dealing
> with.
>
> The basic assumption for now is that this is a specific issue of your specific
> situation.  And with all due respect, even if you say that this happens to you
> in a number of projects (like Milkman with the Samyiang lens),  the basic
> assumption stays that it is an issue of your setup and not of the Hugin code. 
>  
> To be considered an issue with the Hugin code, it must be confirmed by more
> than one user.  This is what we have triagers working on the bug tracker for.
>
> > I have gone back to 2009.4 with no issues.
>
> That's a long way back.  I would be surprised that an issue is hiding in the
> code for one year with no report.  You will forgive me for thinking that the
> issue is on your end rather in the Hugin code until proven different.
>
> > Let me know if there is any other
> > testing needed for the issue I described the the RC1 thread.
>

[hugin-ptx] Re: Declaring 2010.4.0 final and moving on

[RueiKe]

Hi Yuv,

My attempt to use the latest build on a typical complex project
indicates significant issues.  I understand that my use case of 217
images is not typical, but I think it has always been a critical
feature for hugin to be able to handle very large projects.  I have
gone back to 2009.4 with no issues.  Let me know if there is any other
testing needed for the issue I described the the RC1 thread.

Regards,
Rick

On Dec 27, 7:59 am, Yuval Levy  wrote:
> Hi all,
>
> There are still some issues with 2010.4.0, none of which is particularly
> critical, tragic, or urgent.  Yes, 2010.4.0 is far from perfect and in
> particularly this [0] screenshot is a pain to the eye.
>
> But there is also plenty of stuff waiting to be integrated, and the usual
> suspects have been given a lot in their sprint to fix bugs in the last month.
>
> Should we declare 2010.4.0 final and move on to integrate the panorama
> overview branch?  Or should we wait for some more fixes, apply them to 2010.4
> and issue another release candidate?
>
> Yuv
>
> [0] 
>
>  signature.asc
> < 1KViewDownload

-- 
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] Re: ANN: Hugin-2010.4.0_rc1 released

[RueiKe]

I uploaded the pto file:
http://groups.google.com/group/hugin-ptx/web/DR13_Rev1.pto?hl=en%05eeb80c98d0c9ce2

Regards,
Rick

-- 
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] Re: ANN: Hugin-2010.4.0_rc1 released

[RueiKe]

I have tried this release and the beta 2 version on a current project
and am having some problems.  I originally started the project with
the beta2 build.  The first alignment was fine. I deleted some bad
control points from the control point table.  When I attempted the
alignment again from the optimizer tab, the results in the preview
changed from 360x180 to 180x180.  I reset all parameters for all
images and found that when I try aligning again it stops at iteration
33 and hangs idenfinitely.  I have tried this build, and found the
same issue.

Details of my project and configuration follow:
Project: 217 images in 7 shot 1EV step brackets.  This is typical for
my projects that includes 3 rows of 10 shots each plus the Nadir.  I
added control points between all of the nominal exposures and
specified a different stack number for each exposure bracket. There
are 9323 control points.

System:
Operating System: Windows Vista (build 6002, Service Pack 2)
Architecture: 64 bit
Free memory: 487828 kiB
Active Codepage: 1252 (Western European Windows)

Hugin
Version: 2010.4.0.003a7c16c734 built by Matthew Petroff
Path to ressources: C:\Program Files\Hugin/share/hugin/xrc/
Path to data: C:\Program Files\Hugin/share/hugin/data/

Regards,
Rick

On Dec 24, 5:47 pm, davidefa  wrote:
> On your virtual machine, try selecting a virtual video driver with
> opengl support

-- 
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] Re: Release Candidate #3 of Windows installer for 200.4.0 available for test

[RueiKe]

Hi Dale,

Yes, I used hugin.  It was a very difficult stitch.  The link you
posted was my 7th attempt.  There is a discussion about the technique
at the Hugin Users Group - 
http://www.flickr.com/groups/hugin/discuss/72157623046153395/
where Janne gave his recommendation on the approach.  The key is to
specify the lens you use as a really wide angle circular fish eye,
even when it is not.  Janne suggests that ideally you would specify
the input image lens type as orthographic which is not an option with
Hugin.

Regards,
Rick

On Jan 18, 12:28 pm, Dale Beams  wrote:
> Rick,
>
> I noticed your flicker stream and found this photo.  Did you do this in 
> Hugin?  How?
>
> http://www.flickr.com/photos/rueike/4256191182/in/photostream/
>
> Dale
>
>
>
>
>
> > Date: Sun, 17 Jan 2010 16:19:16 -0800
> > Subject: [hugin-ptx] Re: Release Candidate #3 of Windows installer for 
> > 200.4.0     available for test
> > From: ruei...@yahoo.com
> > To: hugin-ptx@googlegroups.com
>
> > I have installed and ran through a complete project with RC3 of the
> > installer.  I removed a previous version and installed this with no
> > problems.  I saved autopano-sift-c from a previous installation and
> > copied into the bin directory.  Release notes looked fine.
>
> > I also ran through a large project since I did not have a chance to
> > test it earlier.  The project was 175 images in 5 shot 1EV step
> > brackets connected with ~16k alignment points.  After the intial
> > alignment, there were large errors (5-6k pixels) indicated for many
> > points and hugin crashed when i tried to review in the control point
> > table.  I had saved my work before alignment.   When I reopened, hugin
> > indicated 3 of the control points were bad and removed them. After
> > this everything went fine and the initial large errors seen in the
> > control point table were gone.  I ran several iterations of optimize
> > with no problems and then used Align from the assistant tab with no
> > problem.  Finally changing the lens for the Nadir, I optimized
> > everything and iteratively removed outlier control points from the
> > control point table.  Ended with a very good alignment of mean error
> > of <0.5 and max of around 5 pixels.  Stitched an 8k x 4k blended and
> > fused pano with no error but did give me a warning about enfuse
> > options.  We should probably make the differences in the options more
> > available.  I will post on the hugin users group on flickr for the
> > users there.
>
> > Here is the final image:http://www.flickr.com/photos/rueike/4281126265/
>
> > Regards,
> > Rick
>
> > On Jan 10, 4:12 pm, allard  wrote:
> > > Hi all,
>
> > > Thanks to some alert users who were missing things, I searched and
> > > found that there were no less than 4 executables missing from the
> > > previous installers. I corrected this, so in the newest release
> > > candidate you will find
> > > -calibrate_lens.exe
> > > -cpclean.exe
> > > -panoinfo.exe
> > > -tca_correct.exe
>
> > > When you install this version, please take some time to read through
> > > the licence file and the release notes and don't click them away
> > > immediately. If you notice anything you think should be changed, let
> > > me and others know by posting to this list so it can be discussed and/
> > > or changed before a final version is released. For those who would
> > > like to join the discussion but have no Windows I will include the
> > > text of these files at the bottom of my post.
> > > Also test as much as you can find the time for, it is better to catch
> > > problems before releasing everything to the general public. I will
> > > wait at least one week before declaring this final, if issues come up
> > > that are serious or easy to solve it may be longer.
> > > One known 'issue' is that there is no autopano (sift-c or other) or
> > > panomatic included in the bundle. This is a choice, not an omission,
> > > seehttp://groups.google.com/group/hugin-ptx/browse_thread/thread/0defd88...
>
> > > I made a pretty simple job of the release notes for the installer:
> > > "Release notes for the Windows installer of hugin 2009.4.0
>
> > > New in this package with respect to the 2009.02 version:
>
> > > -A brand new version of Hugin, of course. See below for the hugin
> > > release notes.
> > > -No patented control point generators included with this installer.
> > > Unfortunately, there is no control point detector available that is
> >

[hugin-ptx] Re: Release Candidate #3 of Windows installer for 200.4.0 available for test

[RueiKe]

I have installed and ran through a complete project with RC3 of the
installer.  I removed a previous version and installed this with no
problems.  I saved autopano-sift-c from a previous installation and
copied into the bin directory.  Release notes looked fine.

I also ran through a large project since I did not have a chance to
test it earlier.  The project was 175 images in 5 shot 1EV step
brackets connected with ~16k alignment points.  After the intial
alignment, there were large errors (5-6k pixels) indicated for many
points and hugin crashed when i tried to review in the control point
table.  I had saved my work before alignment.   When I reopened, hugin
indicated 3 of the control points were bad and removed them. After
this everything went fine and the initial large errors seen in the
control point table were gone.  I ran several iterations of optimize
with no problems and then used Align from the assistant tab with no
problem.  Finally changing the lens for the Nadir, I optimized
everything and iteratively removed outlier control points from the
control point table.  Ended with a very good alignment of mean error
of <0.5 and max of around 5 pixels.  Stitched an 8k x 4k blended and
fused pano with no error but did give me a warning about enfuse
options.  We should probably make the differences in the options more
available.  I will post on the hugin users group on flickr for the
users there.

Here is the final image: http://www.flickr.com/photos/rueike/4281126265/

Regards,
Rick

On Jan 10, 4:12 pm, allard  wrote:
> Hi all,
>
> Thanks to some alert users who were missing things, I searched and
> found that there were no less than 4 executables missing from the
> previous installers. I corrected this, so in the newest release
> candidate you will find
> -calibrate_lens.exe
> -cpclean.exe
> -panoinfo.exe
> -tca_correct.exe
>
> When you install this version, please take some time to read through
> the licence file and the release notes and don't click them away
> immediately. If you notice anything you think should be changed, let
> me and others know by posting to this list so it can be discussed and/
> or changed before a final version is released. For those who would
> like to join the discussion but have no Windows I will include the
> text of these files at the bottom of my post.
> Also test as much as you can find the time for, it is better to catch
> problems before releasing everything to the general public. I will
> wait at least one week before declaring this final, if issues come up
> that are serious or easy to solve it may be longer.
> One known 'issue' is that there is no autopano (sift-c or other) or
> panomatic included in the bundle. This is a choice, not an omission,
> seehttp://groups.google.com/group/hugin-ptx/browse_thread/thread/0defd88...
>
> I made a pretty simple job of the release notes for the installer:
> "Release notes for the Windows installer of hugin 2009.4.0
>
> New in this package with respect to the 2009.02 version:
>
> -A brand new version of Hugin, of course. See below for the hugin
> release notes.
> -No patented control point generators included with this installer.
> Unfortunately, there is no control point detector available that is
> patent-free worldwide, so there is no automatic control point
> generation in this version. If you are in a position that you can
> legally do so, please download one of the control point generators
> compatible with hugin (e.g. autopano-sift-c, autopano, panomatic) from
> wherever they are available and move it to the hugin/bin directory.
> -A new version of Enblend: 4.0. For information on what's new in
> enblend 4.0 go tohttp://enblend.sourceforge.net/";
>
> Below that the release notes of the hugin 2009.4.0 source are copied.
> The installer licence is adapted from the version in the tarball and
> looks like this:
>
> "Copyright (C) 2006-2010 Pablo d'Angelo.
> Additional Authors see AUTHORS.txt files in the documentation.
> Built and packaged for binary redistribution 2010/01/05 by Allard.
>
> UPGRADES
>
> You can uninstall your previous version of hugin, install multiple
> versions in parallel or install this version over a previous version.
> If you have problems with old settings, these can be reset in the
> Preferences by clicking 'Load defaults'.
>
> DISCLAIMER
>
> The programs in this installer may not work as expected. Use them at
> your own risk.
> This installer is distributed in the hope that it will be useful, but
> WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> LICENSE
> You are free to use, copy, distribute, modify this installer or parts
> thereof, and unless you distribute you should n

[hugin-ptx] Re: 2009.04 windows installer available for test

[RueiKe]

I was able to download and install with no problems.  The file size
was 18.8MB.  I still have not had time to really check it out yet
though.

Regards,
Rick

On Jan 6, 9:05 pm, Henk Tijdink  wrote:
> Hello Allard
>
> It seems tat the setup file is corrupted.
> Download is only 2.779 kB. Normally a lot larger.
>
> Kind regards,
> Henk Tijdink
>
> On 6 jan, 09:08, allard  wrote:
>
>
>
> > OK, that didn't work. Google recognizes urls but doesn't know what to
> > do with them. Here's the link again, see if this works.
>
> >http://www.allardkatan.net/misc/hugin/hugin0904_win32_setup_RC1.exe- Hide 
> >quoted text -
>
> - Show quoted text -
-- 
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] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

I have run this test project with Allard's build of 2009.2 SVN4461 and
had no issues with or without the GPU option.  Both produced identical
450MB tif tiles.  I used "-m 3000" for enblend.

Regards,
Rick

On Nov 3, 6:59 am, RueiKe  wrote:
> Ryan,
>
> Re OoM:  My test run with "-m 1000" did not get the out oe memory
> error, but afterward I tested again with "-m 2000" and got the same
> out of memory error - St9bad_alloc.  I have always used "-m 2000" or "-
> m 3000" in the past with 32bit builds.  I use "-m 8000" for 64bit
> builds.  One other error is after making the final image with "-m
> 1000", it gets an error when deleting the working files.
>
> I will try 2009.2 later tonight for the GPU issue...
>
> Regards,
> Rick
>
> On Nov 2, 11:11 pm, RueiKe  wrote:
>
>
>
> > Hi Ryan,
>
> > Re OoM:  I was not able to get enblend to work, even by setting "-m
> > 2000".  I usually use "-m 3000" for 32bit windows version.  I am
> > trying it again with "-m 1000"... I will report back in the morning.
> > I don't know of a way to change disk cache settings.  I assumed hugin
> > just used as much as it needed.
>
> > Re GPU: SInce enblend did not run on most images, I asumed the problem
> > was with Nona.  If this feature is available in Allard's 2009.2 build,
> > I could give it a try tomorrow.
>
> > Regards,
> > Rick
>
> > On Nov 2, 10:22 pm, Ryan  wrote:
>
> > > Hi Rick,
>
> > > Re: i18n: It sounds like wxWidgets+unicode support was the magic
> > > combination -- I strongly suspect somebody just forgot to i18n-ize
> > > those few spots in the GUI.
>
> > > Re OoM: I couldn't tell from your previous emails: were you able to
> > > work around the error by setting -m smaller and/or increasing the disk
> > > cache size?
>
> > > Re GPU: Yes, the question is whether something is broken about GPU
> > > +enblend+win32. It seems that CPU+enblend+win32 works, and GPU+preview
> > > +win32 works, and GPU+enblend+linux works, which makes me suspect
> > > there's simply a problem with enblend's GPU code under windows. AFAIK
> > > mine is the only enblend+GPU+win32 in the wild. Allard's MSCV 2009.2
> > > build uses the version of enblend that shipped with 0.7, and the
> > > official 3.2 build from Sourceforge doesn't seem to use GPU (links
> > > only to user32.dll and kernel32.dll).
>
> > > If somebody could tell me what it takes to integrate an enblend-4.0
> > > snapshot with hugin I'm game. I just need to know:
> > > 1. How to download an enblend-4.0 snapshot -- the sourceforge site
> > > doesn't make it obvious
> > > 2. What hugin code needs to change to handle the changes to command-
> > > line args in enblend-4.0 vs older releases.
>
> > > Meanwhile, just to be sure, perhaps you could download the official
> > > win32 enblend/enfuse from Sourceforge and see what happens with a GPU
> > > stitch.
>
> > > Regards,
> > > Ryan
>
> > > On Nov 2, 2:37 pm, RueiKe  wrote:
>
> > > > Hi Yuv,
>
> > > > Yes, that is the option I used for the test case that gave the out of
> > > > memory error.  I think Ryan's comment was concerning if the error I
> > > > observed was specific to his build.
>
> > > > Regards,
> > > > Rick
>
> > > > On Nov 2, 9:24 pm, Yuval Levy  wrote:
>
> > > > > Hi Rick,
>
> > > > > RueiKe wrote:
> > > > > > Re GPU:  This is the first time I have tested the GPU option.  If
> > > > > > there is another build to try for comparison, just send me a link 
> > > > > > and
> > > > > > I will give it a try.
>
> > > > > to compare the GPU option with the traditional CPU stitching, just
> > > > > enable/disable GPU stitching in the preferences setting.
>
> > > > > Yuv- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Ryan,

Re OoM:  My test run with "-m 1000" did not get the out oe memory
error, but afterward I tested again with "-m 2000" and got the same
out of memory error - St9bad_alloc.  I have always used "-m 2000" or "-
m 3000" in the past with 32bit builds.  I use "-m 8000" for 64bit
builds.  One other error is after making the final image with "-m
1000", it gets an error when deleting the working files.

I will try 2009.2 later tonight for the GPU issue...

Regards,
Rick



On Nov 2, 11:11 pm, RueiKe  wrote:
> Hi Ryan,
>
> Re OoM:  I was not able to get enblend to work, even by setting "-m
> 2000".  I usually use "-m 3000" for 32bit windows version.  I am
> trying it again with "-m 1000"... I will report back in the morning.
> I don't know of a way to change disk cache settings.  I assumed hugin
> just used as much as it needed.
>
> Re GPU: SInce enblend did not run on most images, I asumed the problem
> was with Nona.  If this feature is available in Allard's 2009.2 build,
> I could give it a try tomorrow.
>
> Regards,
> Rick
>
> On Nov 2, 10:22 pm, Ryan  wrote:
>
>
>
> > Hi Rick,
>
> > Re: i18n: It sounds like wxWidgets+unicode support was the magic
> > combination -- I strongly suspect somebody just forgot to i18n-ize
> > those few spots in the GUI.
>
> > Re OoM: I couldn't tell from your previous emails: were you able to
> > work around the error by setting -m smaller and/or increasing the disk
> > cache size?
>
> > Re GPU: Yes, the question is whether something is broken about GPU
> > +enblend+win32. It seems that CPU+enblend+win32 works, and GPU+preview
> > +win32 works, and GPU+enblend+linux works, which makes me suspect
> > there's simply a problem with enblend's GPU code under windows. AFAIK
> > mine is the only enblend+GPU+win32 in the wild. Allard's MSCV 2009.2
> > build uses the version of enblend that shipped with 0.7, and the
> > official 3.2 build from Sourceforge doesn't seem to use GPU (links
> > only to user32.dll and kernel32.dll).
>
> > If somebody could tell me what it takes to integrate an enblend-4.0
> > snapshot with hugin I'm game. I just need to know:
> > 1. How to download an enblend-4.0 snapshot -- the sourceforge site
> > doesn't make it obvious
> > 2. What hugin code needs to change to handle the changes to command-
> > line args in enblend-4.0 vs older releases.
>
> > Meanwhile, just to be sure, perhaps you could download the official
> > win32 enblend/enfuse from Sourceforge and see what happens with a GPU
> > stitch.
>
> > Regards,
> > Ryan
>
> > On Nov 2, 2:37 pm, RueiKe  wrote:
>
> > > Hi Yuv,
>
> > > Yes, that is the option I used for the test case that gave the out of
> > > memory error.  I think Ryan's comment was concerning if the error I
> > > observed was specific to his build.
>
> > > Regards,
> > > Rick
>
> > > On Nov 2, 9:24 pm, Yuval Levy  wrote:
>
> > > > Hi Rick,
>
> > > > RueiKe wrote:
> > > > > Re GPU:  This is the first time I have tested the GPU option.  If
> > > > > there is another build to try for comparison, just send me a link and
> > > > > I will give it a try.
>
> > > > to compare the GPU option with the traditional CPU stitching, just
> > > > enable/disable GPU stitching in the preferences setting.
>
> > > > Yuv- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

Re OoM:  I was not able to get enblend to work, even by setting "-m
2000".  I usually use "-m 3000" for 32bit windows version.  I am
trying it again with "-m 1000"... I will report back in the morning.
I don't know of a way to change disk cache settings.  I assumed hugin
just used as much as it needed.

Re GPU: SInce enblend did not run on most images, I asumed the problem
was with Nona.  If this feature is available in Allard's 2009.2 build,
I could give it a try tomorrow.

Regards,
Rick

On Nov 2, 10:22 pm, Ryan  wrote:
> Hi Rick,
>
> Re: i18n: It sounds like wxWidgets+unicode support was the magic
> combination -- I strongly suspect somebody just forgot to i18n-ize
> those few spots in the GUI.
>
> Re OoM: I couldn't tell from your previous emails: were you able to
> work around the error by setting -m smaller and/or increasing the disk
> cache size?
>
> Re GPU: Yes, the question is whether something is broken about GPU
> +enblend+win32. It seems that CPU+enblend+win32 works, and GPU+preview
> +win32 works, and GPU+enblend+linux works, which makes me suspect
> there's simply a problem with enblend's GPU code under windows. AFAIK
> mine is the only enblend+GPU+win32 in the wild. Allard's MSCV 2009.2
> build uses the version of enblend that shipped with 0.7, and the
> official 3.2 build from Sourceforge doesn't seem to use GPU (links
> only to user32.dll and kernel32.dll).
>
> If somebody could tell me what it takes to integrate an enblend-4.0
> snapshot with hugin I'm game. I just need to know:
> 1. How to download an enblend-4.0 snapshot -- the sourceforge site
> doesn't make it obvious
> 2. What hugin code needs to change to handle the changes to command-
> line args in enblend-4.0 vs older releases.
>
> Meanwhile, just to be sure, perhaps you could download the official
> win32 enblend/enfuse from Sourceforge and see what happens with a GPU
> stitch.
>
> Regards,
> Ryan
>
> On Nov 2, 2:37 pm, RueiKe  wrote:
>
>
>
> > Hi Yuv,
>
> > Yes, that is the option I used for the test case that gave the out of
> > memory error.  I think Ryan's comment was concerning if the error I
> > observed was specific to his build.
>
> > Regards,
> > Rick
>
> > On Nov 2, 9:24 pm, Yuval Levy  wrote:
>
> > > Hi Rick,
>
> > > RueiKe wrote:
> > > > Re GPU:  This is the first time I have tested the GPU option.  If
> > > > there is another build to try for comparison, just send me a link and
> > > > I will give it a try.
>
> > > to compare the GPU option with the traditional CPU stitching, just
> > > enable/disable GPU stitching in the preferences setting.
>
> > > Yuv- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Yuv,

Yes, that is the option I used for the test case that gave the out of
memory error.  I think Ryan's comment was concerning if the error I
observed was specific to his build.

Regards,
Rick

On Nov 2, 9:24 pm, Yuval Levy  wrote:
> Hi Rick,
>
> RueiKe wrote:
> > Re GPU:  This is the first time I have tested the GPU option.  If
> > there is another build to try for comparison, just send me a link and
> > I will give it a try.
>
> to compare the GPU option with the traditional CPU stitching, just
> enable/disable GPU stitching in the preferences setting.
>
> Yuv
--~--~-~--~~~---~--~~
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] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

I ran through my workflow with no unicode related errors.

Maybe not something your are working on, but just to thoroughly
document my observations, the following items are not translated:

"Loading images" - bottom of main window after opening project
"Cancel"  - button on fine tune all points status dialog box
"OK" - button on fine tune all points complete dialog box
"Strategy.." and other text of the optimizer status window
"YES" and "NO" buttons of optimizer dialog box
"Optimizing variables" of the optimizer status box
"YES" and "NO" buttons of exposure dialog box about linked parameters
"OK" and "Cancel" buttons of the exposure "number of pixels" dialog
box
"Cancel"  - button on expsosure status dialog box
"YES" and "NO" buttons of exposure dialog box about applying results
"Cancel"  - button on Align status dialog box
All text except dialog box name for filename selection after pressing
Stitch now.

Regards,
Rick

On Nov 2, 7:20 pm, RueiKe  wrote:
> Hi Ryan,
>
> I just tried the latest build and Chinese Traditional now works!  I
> probably need to run through a full test case to make sure there are
> no unicode issues (early builds of 0.8.0 had some that were cleaned up
> before release).  I will report back when complete.
>
> Regards,
> Rick
>
> On Nov 2, 6:47 pm, RueiKe  wrote:
>
>
>
> > Hi Ryan,
>
> > Re i18n: I am downloading the new version now.  I am using Vista in
> > English with the Traditional Chinese Language pack.  I don't any
> > errors; it just ignores the setting.  I have tried spanish and it
> > works fine.  I will post an update when I try your latest.
>
> > Re OoM:  The error I am getting is the same error I got in the past
> > when setting the memory cache size too large.  For this case, I set it
> > to 2GB (-m 2000).  I think a small setting should not cause a problem,
> > it should just go to disk cache.
>
> > Re GPU:  This is the first time I have tested the GPU option.  If
> > there is another build to try for comparison, just send me a link and
> > I will give it a try.
>
> > Regards,
> > Rick
>
> > On Nov 2, 5:45 pm, Ryan  wrote:
>
> > > Hi Rick,
>
> > > Can you try this version 
> > > out:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-uni...
>
> > > I think my machine must not have the Asian language packs installed
> > > because it still can't change the locale, but the binaries are now 3MB
> > > bigger compressed, so I'm pretty sure unicode is really there.
>
> > > Regards,
> > > Ryan
>
> > > On Nov 1, 5:34 am, RueiKe  wrote:
>
> > > > Hi Ryan,
>
> > > > I have finished running the first test case for hugin-2009.4.0_rc2-
> > > > win32-cygming-bin.zip.
>
> > > > Platform: Windows Vista 64bit on an i7 with 12GB memory and an ATI
> > > > Radeon HD 4800 series graphics card.
>
> > > > Project: 31 image 360x180 equirectangular projection aligned with
> > > > 7,129 control points.  No exposure bracketing in this project.
>
> > > > Observations:
> > > > GUI - Looks good.  Only concern found is it is in English even when
> > > > Chinese is selected.
> > > > Load images - No issues
> > > > Add Control Points - I used Autopano-sift-c with "--maxdim 4000 --
> > > > projection %f,%v --maxmatches %p %o %i" arguments.  It worked fine and
> > > > added as many control points as 2009.2 (Allard's build).  I found a
> > > > previous build of 2009.4 did not generate any control points when --
> > > > maxdim 4000 is specified, but this build doesn't have the issue/
> > > > Align - No problem
> > > > Fine Tune All control points - No issues
> > > > Control Point table - No problem, I removed bad control points with no
> > > > issues
> > > > Optimizer - No problems for position and everything
> > > > Exposure - No issues with Low Dynamic range 1000 points per image.
> > > > Stitching - Used Calculate Optimal Size -> 15,288 x 7,559.  Problems
> > > > in stitching a "Blended Panorama" for both with and without GPU:
> > > >    Without GPU - Out of memory error even with the arguments: -m 2000 -
> > > > b 4000
> > > >    With GPU - No errors, but during enblend most images were indicated
> > > > as redundant and not included in final image.  Final image was a large
> > &g

[hugin-ptx] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

I just tried the latest build and Chinese Traditional now works!  I
probably need to run through a full test case to make sure there are
no unicode issues (early builds of 0.8.0 had some that were cleaned up
before release).  I will report back when complete.

Regards,
Rick

On Nov 2, 6:47 pm, RueiKe  wrote:
> Hi Ryan,
>
> Re i18n: I am downloading the new version now.  I am using Vista in
> English with the Traditional Chinese Language pack.  I don't any
> errors; it just ignores the setting.  I have tried spanish and it
> works fine.  I will post an update when I try your latest.
>
> Re OoM:  The error I am getting is the same error I got in the past
> when setting the memory cache size too large.  For this case, I set it
> to 2GB (-m 2000).  I think a small setting should not cause a problem,
> it should just go to disk cache.
>
> Re GPU:  This is the first time I have tested the GPU option.  If
> there is another build to try for comparison, just send me a link and
> I will give it a try.
>
> Regards,
> Rick
>
> On Nov 2, 5:45 pm, Ryan  wrote:
>
>
>
> > Hi Rick,
>
> > Can you try this version 
> > out:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-uni...
>
> > I think my machine must not have the Asian language packs installed
> > because it still can't change the locale, but the binaries are now 3MB
> > bigger compressed, so I'm pretty sure unicode is really there.
>
> > Regards,
> > Ryan
>
> > On Nov 1, 5:34 am, RueiKe  wrote:
>
> > > Hi Ryan,
>
> > > I have finished running the first test case for hugin-2009.4.0_rc2-
> > > win32-cygming-bin.zip.
>
> > > Platform: Windows Vista 64bit on an i7 with 12GB memory and an ATI
> > > Radeon HD 4800 series graphics card.
>
> > > Project: 31 image 360x180 equirectangular projection aligned with
> > > 7,129 control points.  No exposure bracketing in this project.
>
> > > Observations:
> > > GUI - Looks good.  Only concern found is it is in English even when
> > > Chinese is selected.
> > > Load images - No issues
> > > Add Control Points - I used Autopano-sift-c with "--maxdim 4000 --
> > > projection %f,%v --maxmatches %p %o %i" arguments.  It worked fine and
> > > added as many control points as 2009.2 (Allard's build).  I found a
> > > previous build of 2009.4 did not generate any control points when --
> > > maxdim 4000 is specified, but this build doesn't have the issue/
> > > Align - No problem
> > > Fine Tune All control points - No issues
> > > Control Point table - No problem, I removed bad control points with no
> > > issues
> > > Optimizer - No problems for position and everything
> > > Exposure - No issues with Low Dynamic range 1000 points per image.
> > > Stitching - Used Calculate Optimal Size -> 15,288 x 7,559.  Problems
> > > in stitching a "Blended Panorama" for both with and without GPU:
> > >    Without GPU - Out of memory error even with the arguments: -m 2000 -
> > > b 4000
> > >    With GPU - No errors, but during enblend most images were indicated
> > > as redundant and not included in final image.  Final image was a large
> > > file with the dimensions specified in "Calculate Optimal Size", but
> > > was transparent except for an area the size and shape of the image
> > > anchored for position.  The area was the same size as that component
> > > image, but it had other images blended incorrectly into it.
>
> > > Let me know if you need any other details,
>
> > > Regards,
> > > Rick
>
> > > On Nov 1, 9:22 am, RueiKe  wrote:
>
> > > > Hi Ryan,
>
> > > > I am still working through my test case, but one observed issue so far
> > > > is that the interface is in English even when I select Traditional
> > > > Chinese.  I am running this out of the directory where I unzipped it
> > > > to, so maybe this is part of the issue.
>
> > > > Regards,
> > > > Rick
>
> > > > On Oct 31, 8:51 pm, Ryan  wrote:
>
> > > > > Correction to the 
> > > > > URLs:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cyg..
>
> > > > > Thanks,
> > > > > Ryan
>
> > > > > On Oct 31, 10:41 am, Ryan  wrote:
>
> > > > > > Hi all,
>
> > > > > > hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available 
> > > > > > atftp://hugin.panotools.

[hugin-ptx] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

Re i18n: I am downloading the new version now.  I am using Vista in
English with the Traditional Chinese Language pack.  I don't any
errors; it just ignores the setting.  I have tried spanish and it
works fine.  I will post an update when I try your latest.

Re OoM:  The error I am getting is the same error I got in the past
when setting the memory cache size too large.  For this case, I set it
to 2GB (-m 2000).  I think a small setting should not cause a problem,
it should just go to disk cache.

Re GPU:  This is the first time I have tested the GPU option.  If
there is another build to try for comparison, just send me a link and
I will give it a try.

Regards,
Rick

On Nov 2, 5:45 pm, Ryan  wrote:
> Hi Rick,
>
> Can you try this version 
> out:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-uni...
>
> I think my machine must not have the Asian language packs installed
> because it still can't change the locale, but the binaries are now 3MB
> bigger compressed, so I'm pretty sure unicode is really there.
>
> Regards,
> Ryan
>
> On Nov 1, 5:34 am, RueiKe  wrote:
>
>
>
> > Hi Ryan,
>
> > I have finished running the first test case for hugin-2009.4.0_rc2-
> > win32-cygming-bin.zip.
>
> > Platform: Windows Vista 64bit on an i7 with 12GB memory and an ATI
> > Radeon HD 4800 series graphics card.
>
> > Project: 31 image 360x180 equirectangular projection aligned with
> > 7,129 control points.  No exposure bracketing in this project.
>
> > Observations:
> > GUI - Looks good.  Only concern found is it is in English even when
> > Chinese is selected.
> > Load images - No issues
> > Add Control Points - I used Autopano-sift-c with "--maxdim 4000 --
> > projection %f,%v --maxmatches %p %o %i" arguments.  It worked fine and
> > added as many control points as 2009.2 (Allard's build).  I found a
> > previous build of 2009.4 did not generate any control points when --
> > maxdim 4000 is specified, but this build doesn't have the issue/
> > Align - No problem
> > Fine Tune All control points - No issues
> > Control Point table - No problem, I removed bad control points with no
> > issues
> > Optimizer - No problems for position and everything
> > Exposure - No issues with Low Dynamic range 1000 points per image.
> > Stitching - Used Calculate Optimal Size -> 15,288 x 7,559.  Problems
> > in stitching a "Blended Panorama" for both with and without GPU:
> >    Without GPU - Out of memory error even with the arguments: -m 2000 -
> > b 4000
> >    With GPU - No errors, but during enblend most images were indicated
> > as redundant and not included in final image.  Final image was a large
> > file with the dimensions specified in "Calculate Optimal Size", but
> > was transparent except for an area the size and shape of the image
> > anchored for position.  The area was the same size as that component
> > image, but it had other images blended incorrectly into it.
>
> > Let me know if you need any other details,
>
> > Regards,
> > Rick
>
> > On Nov 1, 9:22 am, RueiKe  wrote:
>
> > > Hi Ryan,
>
> > > I am still working through my test case, but one observed issue so far
> > > is that the interface is in English even when I select Traditional
> > > Chinese.  I am running this out of the directory where I unzipped it
> > > to, so maybe this is part of the issue.
>
> > > Regards,
> > > Rick
>
> > > On Oct 31, 8:51 pm, Ryan  wrote:
>
> > > > Correction to the 
> > > > URLs:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cyg..
>
> > > > Thanks,
> > > > Ryan
>
> > > > On Oct 31, 10:41 am, Ryan  wrote:
>
> > > > > Hi all,
>
> > > > > hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available 
> > > > > atftp://hugin.panotools.org/public_html/testing/hugin/. It works out 
> > > > > of
> > > > > the box -- just unzip and run hugin/bin/hugin.exe -- and there are no
> > > > > dependencies on either cygwin or the location it unzips to.
>
> > > > > In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is
> > > > > available for people who aren't troubled by patent issues. Just unzip
> > > > > it to the same directory that the hugin-*.zip went to and hugin should
> > > > > be able to use it (it's not a stand-alone executable and shares the
> > > > > same directory hierarchy).
>
> > > > > Fin

[hugin-ptx] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

I have finished running the first test case for hugin-2009.4.0_rc2-
win32-cygming-bin.zip.

Platform: Windows Vista 64bit on an i7 with 12GB memory and an ATI
Radeon HD 4800 series graphics card.

Project: 31 image 360x180 equirectangular projection aligned with
7,129 control points.  No exposure bracketing in this project.

Observations:
GUI - Looks good.  Only concern found is it is in English even when
Chinese is selected.
Load images - No issues
Add Control Points - I used Autopano-sift-c with "--maxdim 4000 --
projection %f,%v --maxmatches %p %o %i" arguments.  It worked fine and
added as many control points as 2009.2 (Allard's build).  I found a
previous build of 2009.4 did not generate any control points when --
maxdim 4000 is specified, but this build doesn't have the issue/
Align - No problem
Fine Tune All control points - No issues
Control Point table - No problem, I removed bad control points with no
issues
Optimizer - No problems for position and everything
Exposure - No issues with Low Dynamic range 1000 points per image.
Stitching - Used Calculate Optimal Size -> 15,288 x 7,559.  Problems
in stitching a "Blended Panorama" for both with and without GPU:
   Without GPU - Out of memory error even with the arguments: -m 2000 -
b 4000
   With GPU - No errors, but during enblend most images were indicated
as redundant and not included in final image.  Final image was a large
file with the dimensions specified in "Calculate Optimal Size", but
was transparent except for an area the size and shape of the image
anchored for position.  The area was the same size as that component
image, but it had other images blended incorrectly into it.

Let me know if you need any other details,

Regards,
Rick


On Nov 1, 9:22 am, RueiKe  wrote:
> Hi Ryan,
>
> I am still working through my test case, but one observed issue so far
> is that the interface is in English even when I select Traditional
> Chinese.  I am running this out of the directory where I unzipped it
> to, so maybe this is part of the issue.
>
> Regards,
> Rick
>
> On Oct 31, 8:51 pm, Ryan  wrote:
>
>
>
> > Correction to the 
> > URLs:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cyg..
>
> > Thanks,
> > Ryan
>
> > On Oct 31, 10:41 am, Ryan  wrote:
>
> > > Hi all,
>
> > > hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available 
> > > atftp://hugin.panotools.org/public_html/testing/hugin/. It works out of
> > > the box -- just unzip and run hugin/bin/hugin.exe -- and there are no
> > > dependencies on either cygwin or the location it unzips to.
>
> > > In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is
> > > available for people who aren't troubled by patent issues. Just unzip
> > > it to the same directory that the hugin-*.zip went to and hugin should
> > > be able to use it (it's not a stand-alone executable and shares the
> > > same directory hierarchy).
>
> > > Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the
> > > master Makefile and patches which were used to build and package hugin/
> > > autopano.
>
> > > It would be interesting if people with "real" workflows could try it
> > > out and see (a) whether it really works and (b) how it compares to the
> > > MSVC version -- I my biggest panorama only has like seven photos in
> > > it, and I don't usually play with multiple lenses or stacks.
>
> > > The uploaded version uses
> > > - hugin-2009.4.0_rc2
> > > - enblend-enfuse-3.2
> > > - libpano13-2.9.15_beta3
> > > - autopano-sift-C-2.5.1_rc2
>
> > > I'm willing to try other versions as appropriate, but wanted to close
> > > the loop first (in particular, enblend-4.0 sounds like it needs some
> > > integration work still).
>
> > > Regards,
> > > Ryan- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: hugin-2009.4 win32 (cygming) build available - please test

[RueiKe]

Hi Ryan,

I am still working through my test case, but one observed issue so far
is that the interface is in English even when I select Traditional
Chinese.  I am running this out of the directory where I unzipped it
to, so maybe this is part of the issue.

Regards,
Rick

On Oct 31, 8:51 pm, Ryan  wrote:
> Correction to the 
> URLs:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cyg...http://hugin.panotools.org/testing/hugin/autopano-sift-C-2.5.1_rc2-wi...http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cyg...
>
> Thanks,
> Ryan
>
> On Oct 31, 10:41 am, Ryan  wrote:
>
>
>
> > Hi all,
>
> > hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available 
> > atftp://hugin.panotools.org/public_html/testing/hugin/. It works out of
> > the box -- just unzip and run hugin/bin/hugin.exe -- and there are no
> > dependencies on either cygwin or the location it unzips to.
>
> > In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is
> > available for people who aren't troubled by patent issues. Just unzip
> > it to the same directory that the hugin-*.zip went to and hugin should
> > be able to use it (it's not a stand-alone executable and shares the
> > same directory hierarchy).
>
> > Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the
> > master Makefile and patches which were used to build and package hugin/
> > autopano.
>
> > It would be interesting if people with "real" workflows could try it
> > out and see (a) whether it really works and (b) how it compares to the
> > MSVC version -- I my biggest panorama only has like seven photos in
> > it, and I don't usually play with multiple lenses or stacks.
>
> > The uploaded version uses
> > - hugin-2009.4.0_rc2
> > - enblend-enfuse-3.2
> > - libpano13-2.9.15_beta3
> > - autopano-sift-C-2.5.1_rc2
>
> > I'm willing to try other versions as appropriate, but wanted to close
> > the loop first (in particular, enblend-4.0 sounds like it needs some
> > integration work still).
>
> > Regards,
> > Ryan- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: Windows 2009.2 installer package: please test

[RueiKe]

Hi Allard,

I have finished testing.  The 15,318 x 7,659 pixel equirectangular
projection I started stitching last night completed with no problems.
Today, I ran through the a similar set of tests using the Traditional
Chinese UI and had no issues, but I noticed there were still
untranslated strings.  I think Yuv made the changes that impact this
in 2009.04.  I just stitched an 8k by 8k stereographic projection with
no problems.  The build looks good to me.  Let me know if there is
anything else that I could check out.

Regards,
Rick

On Oct 26, 10:02 pm, RueiKe  wrote:
> Hi Allard,
>
> I had limited time this evening for testing, but I hope run through
> more tomorrow.   So far it looks good!
>
> Platform: Vista 64bit, using English interface for Hugin, Hugin
> installed over 0.8.0.
>
> Project: 155 image 360x180 with 5 shot 1EV step brackets aligned with
> ~17k alignment points.  Previously completed this project with Ryan's
> 64bit build of 0.8.0
>
> Observations:
> Align - Works with no issues
> Optimiser - Optimize Everything works with no issues
> Exposure - Optimize low dynamic range with 1000pts per image work with
> no issues
> Autopano-SIFT-C - This version is verified to fix the issue previously
> seen with the projection specification.  Also, using "--maxdim 4000"
> works with no issues.  Only tried one set of 5 images and results were
> good with max pts added with good spread.
> Stitcher - Stitching a 15,318 x 7,659 pixel equirectangular
> projection, fused and blended pano, with "-m 3000" for both enfuse and
> enblend - Still stitching, will report back tomorrow.
> Fast Preview - Photometrics, Identify, and Show CP verified working.
>
> I will continue checking it tomorrow.  I also plan to test in Chinese
> Traditional.
>
> Regards,
> Rick
>
> On Oct 26, 3:08 pm, allard  wrote:
>
>
>
> > Hi all,
>
> > I made an installer package for Hugin on 32-bit windows based on:
>
> > hugin tarball 2009.2 release
> > libpano svn 1098 (=beta3 + small changes)
> > autopano sift c 2.5.1 final
> > enblend binaries from hugin 0.7 release
>
> > You can download it 
> > athttp://hugin.panotools.org/testing/hugin/Hugin_2009_02_installer_w32_...
>
> > Even though this is based on what should be stable releases I call
> > this RC1 for this installer package, not in the least because I've had
> > very little time for testing. Haven't yet gotten around to making the
> > 'no control point generator' version but that should be
> > straightforward. I won't have any time for modifications this week
> > either, but please test and report problems to the list. If nobody
> > finds problems, any of the developers with sufficient permission
> > should feel free to upload this file to Sourceforge.
>
> > allard- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: *IMPORTANT* Credits

[RueiKe]

Hi Yuv,

One correction - I only provided original and updates to the
Traditional Chinese Translation, not the Simplified.

Regards,
Rick

On Oct 26, 9:40 pm, Yuval Levy  wrote:
> Hi all
>
> this community has been growing nicely for the past three years. I felt
> that the credits given to all of you contributors were not enough.
>
> The "about" dialog in the application had more content than it could
> display, and was incomplete. The AUTHORS file in the distribution, a GNU
> convention, was outdated and is anyway not much considered by users who
> get the binaries on all plattforms, including Linux.
>
> My intention is to recognize and give credit to *all* contributors.
> Unfortunately I don't know about all contributors to a history that goes
> back seven years. *You* can help, and here is how:
>
> I've started a webpage [0] that eventually will list as many
> contributors as known and their contributions.
>
> Currently it is just a scant two columns page with contributors listed
> alphabetically in the first column and some text describing their
> contribution on the right.
>
> First, we need to make sure that the list is complete. Have I forgot
> some names? Apology. Feel free to add them directly (preferred) or to
> tell me.
>
> Second, we need to make sure that people's contributions are properly
> listed. Have I forgot something on the right of *your* name (or of the
> name of somebody you know has contributed more than what is listed)?
> Apology. Feel free to add them directly (preferred) or to tell me.
>
> Third, we need to unify the content and language contribution column. As
> a minimum I'd like to have special mention for those who contributed
> initially or originally a feature or a translation.
>
> Fourth, which will come mch later: I would like to give "recognition
> badges", e.g. some sort of beautiful graphics that says "coder",
> "builder", "writer", "translator", "bug hunter", "bug fixer", "windows",
> "linux/bsd", "mac".
>
> Feel free to add!
> Yuv
>
> [0]http://hugin.sourceforge.net/community/authors.shtml
--~--~-~--~~~---~--~~
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] Re: Windows 2009.2 installer package: please test

[RueiKe]

Hi Allard,

I had limited time this evening for testing, but I hope run through
more tomorrow.   So far it looks good!

Platform: Vista 64bit, using English interface for Hugin, Hugin
installed over 0.8.0.

Project: 155 image 360x180 with 5 shot 1EV step brackets aligned with
~17k alignment points.  Previously completed this project with Ryan's
64bit build of 0.8.0

Observations:
Align - Works with no issues
Optimiser - Optimize Everything works with no issues
Exposure - Optimize low dynamic range with 1000pts per image work with
no issues
Autopano-SIFT-C - This version is verified to fix the issue previously
seen with the projection specification.  Also, using "--maxdim 4000"
works with no issues.  Only tried one set of 5 images and results were
good with max pts added with good spread.
Stitcher - Stitching a 15,318 x 7,659 pixel equirectangular
projection, fused and blended pano, with "-m 3000" for both enfuse and
enblend - Still stitching, will report back tomorrow.
Fast Preview - Photometrics, Identify, and Show CP verified working.

I will continue checking it tomorrow.  I also plan to test in Chinese
Traditional.

Regards,
Rick

On Oct 26, 3:08 pm, allard  wrote:
> Hi all,
>
> I made an installer package for Hugin on 32-bit windows based on:
>
> hugin tarball 2009.2 release
> libpano svn 1098 (=beta3 + small changes)
> autopano sift c 2.5.1 final
> enblend binaries from hugin 0.7 release
>
> You can download it 
> athttp://hugin.panotools.org/testing/hugin/Hugin_2009_02_installer_w32_...
>
> Even though this is based on what should be stable releases I call
> this RC1 for this installer package, not in the least because I've had
> very little time for testing. Haven't yet gotten around to making the
> 'no control point generator' version but that should be
> straightforward. I won't have any time for modifications this week
> either, but please test and report problems to the list. If nobody
> finds problems, any of the developers with sufficient permission
> should feel free to upload this file to Sourceforge.
>
> allard
--~--~-~--~~~---~--~~
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] Re: Canon 7D or SONY Alpha 850 - which one would you buy?

[RueiKe]

I tried again on the D3 just to be sure.  I verified that in live view
mode, I can see the mirror moving for each photo when in CH and
bracket mode.  I will raise this question in the D3 flickr group to
see if there is another approach.

On Sep 27, 3:31 pm, dmg  wrote:
> On Sat, Sep 26, 2009 at 9:20 PM, RueiKe  wrote:
>
> > Hi Daniel,
>
> > I just tried Live View on the D3.  No impact on the mirror lock up.
> > Too bad.  At high speed, it can induce significant camera shake.
>
> > Rick
>
> I can confirm that the 1ds3 brackets up to 7 shots, from 1/3 to up to
> 3 stops distance each.
>
> Also, I confirm that the 5D2, 40D and 1ds3 all shoot without moving
> the mirror when in liveView.
> Keep in mind, the shutter still releases, hence the noise. But it is
> not the mirror moving.
>
> But in normal mode (viewfinder) the mirror moves with every shot.
>
> ---
> Daniel M. Germanhttp://turingmachine.org
--~--~-~--~~~---~--~~
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] Re: Canon 7D or SONY Alpha 850 - which one would you buy?

[RueiKe]

Hi Daniel,

I just tried Live View on the D3.  No impact on the mirror lock up.
Too bad.  At high speed, it can induce significant camera shake.

Rick

On Sep 27, 6:46 am, dmg  wrote:
> > Definitely disappointing that camera manufacturers still have not
> > caught on to increased dynamic range work yet.  Even external camera
> > control software, which should have a lot more flexibility, doesn't
> > address the need (at least for Nikon).
>
> > Another aspect of bracketing that would be a factor for me would be
> > the ability to lock up the mirror for an entire bracket series.  Is it
> > really necessary to meter between brackets, especially in manual
> > mode?  Is there some other technical limitation for this?
>
> the 5dII does this when you enable live view.
>
> --
> --dmg
>
> ---
> Daniel M. Germanhttp://turingmachine.org
--~--~-~--~~~---~--~~
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] Re: Canon 7D or SONY Alpha 850 - which one would you buy?

[RueiKe]

Hi Yuv,

Definitely disappointing that camera manufacturers still have not
caught on to increased dynamic range work yet.  Even external camera
control software, which should have a lot more flexibility, doesn't
address the need (at least for Nikon).

Another aspect of bracketing that would be a factor for me would be
the ability to lock up the mirror for an entire bracket series.  Is it
really necessary to meter between brackets, especially in manual
mode?  Is there some other technical limitation for this?

Rick

On Sep 27, 4:26 am, Yuval Levy  wrote:
> Hi Rick,
>
> RueiKe wrote:
> > What type of bracketing capabilities do the A850D and the 7D have?
>
> the usual, plain, boring -2/0/+2 AEB. there are, of course, workarounds,
> but I am really fed up of camera manufacturers not understanding such a
> basic need and implementing such a simple function as
>
> for a= -x to +x
>    shoot a picture
>    increase the exposure value
>    a=a+y
> next
>
> and let the user define x and y through the UI.
>
> x=2 and y=2 is what Canon does.
>
> x=6 and y=2 is what I'd like to do in many cases.
>
> > heard that the Canons have only a max of 3 steps, but maybe this is
> > only consumer level.
>
> no, it's overall. I would call it engineer's deafness.
>
> > The Nikons support 3, 5, 7, and 9 steps at a max
> > increment of 1EV, while I heard that Pentax supports 2EV increments,
>
> the 1EV steps is what disturbs me with Nikon. creates a lot of
> unnecessary junk. so they fixed y at 1.
>
> Pentax has IMO the so far best implementation, but is also limited
> (reduced x range).
>
> > Have you considered the Nikon D3 (or D700)?  It has
> > excellent high ISO noise performance and prices have really come down.
>
> I've looked at Nikon too, yes. I have "good" (as in: similar to Canon;
> and not as in: how I would expect a customer-centric business to
> operate) experience with the brand (I own a Nikonos V with plenty of
> accessories). I end up coming back to the Canon or SONY choice because I
> already have lenses and moving to Nikon, Pentax, or any other contender
> would break the budget. I am not inclined to "top up" at this point.
>
> > Next question would be what is the best lens for high resolution
> > panos?  I am using the Voigtlander 20mm Color Skopar almost
> > exclusively now.  Very compact and great CA performance.
>
> indeed the question of the lens comes even before the body.
>
> If this was "web resolution full spherical", I would not consider a full
> frame sensor; and I would consider the 7D to be an overkill (no need for
> such a great viewfinder; and 18mpx on an APS-C is overkill for the
> softness of the current generation of fisheye lenses).
>
> For this specific work I'll be shooting in the 100mm to 200mm range -
> "pano" being a synonymous with composite or mosaic more than with wide
> field of view. And my good old Minolta AF 100-300mm F4.5-5.6 (APO D)
> fits the bill. The SONY body would add stabilization to it. Adding a
> comparable lens to a Canon or Nikon system would set me back of more
> than 1000$.
>
> I could justify the 1000$ on a Canon lens coupled with the 7D because
> the 7D fits in my existing system. The project's budget itself justifies
> the body only, which in the case of the Alpha 850 would give me the
> option to resell it with my good Minolta glasses and accessories after
> the project ended if I did not like them for whatever reason.
>
> What entices me is a full frame sensor - because of the increased depth
> of field control. I've recently allowed myself the luxury of exposing a
> 35mm film and it feels so gd. But going full frame on Canon is
> not really an option at this moment; and even less Nikon.
>
> Yuv
--~--~-~--~~~---~--~~
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] Re: Canon 7D or SONY Alpha 850 - which one would you buy?

[RueiKe]

What type of bracketing capabilities do the A850D and the 7D have?  I
heard that the Canons have only a max of 3 steps, but maybe this is
only consumer level.  The Nikons support 3, 5, 7, and 9 steps at a max
increment of 1EV, while I heard that Pentax supports 2EV increments,
but only 3 steps.  Have you considered the Nikon D3 (or D700)?  It has
excellent high ISO noise performance and prices have really come down.

Next question would be what is the best lens for high resolution
panos?  I am using the Voigtlander 20mm Color Skopar almost
exclusively now.  Very compact and great CA performance.

Regards,
Rick

On Sep 26, 10:45 am, Yuval Levy  wrote:
> Hi all,
>
> This time I *must* upgrade my kit. It's a requirement for a job I landed
> and the budget pays for it. HDR, partial panoramas, long focal distance.
>
> I currently use a Canon 350D. From the pre-digital era I am a long time
> Minolta user and have some good glass, flash, accessories.
>
> In the meantime Minolta sold to SONY and the Alpha 850 seems a nice
> proposition (with reservation about the brand. The memory stick stuff is
> pathetic).
>
> My 350D kit was used mainly for the production of web-based material,
> particularly full spherical panoramas (7000x3500). It's still the old
> Sigma 8mm F/4, complemented with very cheap Sigma APS-C lenses just to
> have something in the range up to 200mm for the occasional use (and with
> Hugin I can nicely correct them to perfect rectilinear).
>
> Besides the specific job, my interests have shifted to higher
> resolutions (large prints) and partial multi-row panoramas for large
> prints, so I will want better glass than I have now in the range of
> 20mm-200mm. I still do web-based full sphericals occasionally and if I
> had to change something for that application it would rather be the lens
> than the camera body.
>
>  From my starting point I'd have to shell out more money on the Canon to
> reach the same quality of glass as on the SONY (and if I did, I could as
> well go 5D MkII?) - and that extra money is not in the budget. The body
> (including 5D MkII if I wanted) is.
>
> What I like about the 7D is 8FPS continuous mode and 1.0x viewfinder
> magnification.
>
> The a850 has only 3FPS (but is full frame, and the a900, which I also
> could still get through the budget, has 5FPS which is better than the 5D
> MkII).
>
> What worries me a little about the a850 (and a900) is the noise at high
> ISO (compared to the 5D MkII). But isn't that an even bigger problem for
> the 7D (with 18mpx crammed on an APS-C sensor)? Anybody has some
> experience in low light with the SONYs?
>
> Exposure Bracketing seems to be a weakness of both contenders. I had
> considered a Pentax K-7, but that would be a completely new system with
> plenty of components to buy right from the start, not just the body. And
> there would be other brands and models to consider too. I am open for
> suggestions.
>
> Has anybody made any experience with SONY Alpha 550 and its HDR mode?
> but anyway, it is not present on the a850 (nor on the a950).
>
> Which brings me back to the original choice: Canon 7D or SONY Alpha 850?
>
> Yuv
--~--~-~--~~~---~--~~
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] Re: Control point generator incantations

[RueiKe]

Hi Bruno,

Hugin is able to estimate them from the EXIF data.   The values
immediately after loading are Normal (rectilinear), degrees of
view=84.00737, focal length=20, crop factor=1.

Here is text while processing one of the images:

Filename K:\HWD\RL3_8447.tif
  rectilinear  width 4256  height 2832  hfov 180
  reduce to 1600 x 1064 (Scale 2.6600)...
  convert to stereographic projection ...
  find keypoints ...
  69 keypoints found

For this set of images, it finds a bit more points, but all of them
are in very near the center of each image and much less than without
the projection specified.

Regards,
Rick

On Sep 14, 8:44 pm, Bruno Postle  wrote:
> On Sat 12-Sep-2009 at 07:38 -0700, RueiKe wrote:
>
>
>
> >Not sure if I found a bug or if I am doing something wrong.  I am
> >using SVN4352 of 2009.2.  I attempted to use the default arguments for
> >autopano-SIFT-C, and I found that it indicates conversion to a
> >stereographic projection in the control point generation window, even
> >though an equirectangular projection is indicated in both the stitcher
> >tab and quick preview window.  It only finds 3 control points.  When I
> >remove the "--projection %f,%v" option it finds over 500 control
> >points.
>
> The stereographic conversion is used for input images, the
> projection of the output shouldn't make any difference to
> control-point detection.
>
> I suspect that the initial field of view or projection of your
> photos is being misread.  Are you entering values manually when you
> load the photos? or is hugin estimating them from the EXIF info?
>
> i.e. what values are set in the Camera and Lens tab immediately
> before generating control points?
>
> --
> 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@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] Re: Control point generator incantations

[RueiKe]

Hi Bruno,

Not sure if I found a bug or if I am doing something wrong.  I am
using SVN4352 of 2009.2.  I attempted to use the default arguments for
autopano-SIFT-C, and I found that it indicates conversion to a
stereographic projection in the control point generation window, even
though an equirectangular projection is indicated in both the stitcher
tab and quick preview window.  It only finds 3 control points.  When I
remove the "--projection %f,%v" option it finds over 500 control
points.

Regards,
Rick

On Sep 7, 6:17 am, Bruno Postle  wrote:
> Hugin-2009.2.0 has the ability to configure multiple control point
> generators.  Currently the default and only control point generator
> setup is:
>
>     "Autopano-SIFT-C", "autopano-sift-c", "--maxmatches %p %o %i"
>
> Though actually you should get better results with these extra
> parameters as it enables feature classification in conformal space:
>
>     "Autopano-SIFT-C", "autopano-sift-c", "--maxmatches %p --projection %f,%v 
> %o %i"
>
> There is a newer, cleaner interface that also enables the conformal
> space thing, this involves passing a .pto project as input:
>
>     "Autopano-SIFT-C", "autopano-sift-c", "--maxmatches %p %o %s"
>
> (Unfortunately unless you are using an SVN snapshot of
> autopano-sift-C, this last one chokes on input filenames containing
> spaces)
>
> There is the autopano-noop.sh script which ships with Hugin, this
> gives a nice warning if autopano-sift-c isn't installed (recommended
> for linux distributions that can't ship SIFT):
>
>     "Autopano NOOP", "autopano-noop.sh", "--maxmatches %p --projection %f,%v 
> %o %i"
>
> There is match-n-shift, a Panotools::Script wrapper around
> autopano-sift-C, this is slow but the advantage is that it
> incorporates ptoclean, this would look like this:
>
>     "Match'n'Shift", "match-n-shift", "-b -a -f %f -v %v -c -p %p -o %o %i"
>
> There is Pan-o-matic which is also useful, the config looks like
> this:
>
>     "Pan-o-matic", "panomatic", "-o %o %i"
>
> Finally there is align_image_stack which is no good for general
> alignment of panoramas, but can be used to generate control points
> for photos within a single stack for which it is very good:
>
>     "Align image stack", "align_image_stack", "-f %v -p %o %i"
>
> Actually, something like this ought to work better (untested):
>
>     "Align image stack", "align_image_stack", "-f %v `[ %f == 2 ] || [ %f == 
> 3 ] && echo -n ' -e'` -p %o %i"
>
> I'm not sure why I started this, I guess some of these should be
> added as preset alternatives to the hugin control point preferences.
>
> Opinions?
>
> --
> 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@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] Re: hugin translators needed! (was:Hugin-2009.2.0-beta2)

[RueiKe]

Hi Bruno,

I found most of the fuzzy translations also need work.  I plan to
finish the Traditional Chinese translation tomorrow.

Regards,
Rick

On Sep 6, 5:40 pm, Bruno Postle  wrote:
> On Sat 05-Sep-2009 at 21:05 -0400, Yuval Levy wrote:
>
>
>
> >> Also the translation for the release of 2009.2 are behind the stand of
> >> 0.8
>
> >How can the translations be behind? all strings that were translated in
> >0.8 are still translated in 2009.2.0, so there can only be improvements?
>
> Some of the very prominent strings in the GUI have changed so it
> would be good to get some more translations updated before this next
> release.
>
> We need to make translators aware that there will be a release
> *soon*, I'm not sure we have done this.
>
> Translators start here, I think there are only 25 or so new
> strings, so it isn't a big job this time:
>
> http://wiki.panotools.org/Hugin_translation_guide
>
> --
> 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@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] Re: Exposure Bracket Control Points

[RueiKe]

Hi Bruno,

The work around worked great!  It still took a few hours to add all of
the control points with the 'g' option, since I had to set values in 2
dialog boxes each time, but a lot less work than my previous
approach.  I had spent a week of all of the free time I had manually
adding and adjusting control points to get the rim in this pano to be
sharp.
http://www.flickr.com/photos/rueike/3780733501/

Using the 'g' approach, I reduced the mean error from 0.5 pixels to
0.1 pixels.  Viewing at 200%, most of the rim had improved, but there
were a few locations where setting points manually improved sharpness,
probably since it compensated for camera movement due to wind or
mirror slap.

I really look forward to the stack number feature.  This will be
extremely useful!

Regards,
Rick

On Sep 3, 8:52 pm, Bruno Postle  wrote:
> On Thu 03-Sep-2009 at 01:19 -0700, RueiKe wrote:
>
>
>
> > Seems like control points would be greatly simplified if I could
> > just get hugin to assume the bracketed images were already
> > aligned.
>
> In the gsoc_layout branch we now have a 'stack number' which is
> analogous to the current 'lens number', this allows you to link the
> positions of bracketed photos without using control points (it isn't
> ready for merging with the trunk just yet).
>
> > I have done a case where I just picked alignment points on the 4
> > corners of a few photos and it seemed to work fine.  Is this a
> > reasonable approach?
> > Would it be possible to have an option to add a set of fixed
> > control points for a specified set of aligned images?
>
> Another workaround would be to select each pair of images that you
> want to link in the Control Points tab, and hit the 'g' key to
> create points linking them.  Don't fine tune these points and the
> two images will be permanently linked with the same relative
> position.
>
> --
> 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@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] Re: Exposure Bracket Control Points

[RueiKe]

Thanks Eduardo and Seb!  These are really great ideas.  I have tried
the "Apply template" idea and it works perfectly for the case of all
images being aligned.  It will certainly simplify the approach for
many projects.  The only issue I have is that the Nadir is handheld.
For this case, it will only be aligned for the original set used to
create the template.

The project I am working on is an exposure enfused pano made up of 5
shot, 1EV step brackets.  The Nadir is also a 5 shot bracket and is
handheld.  I am using a stereographic projection, so alignment of the
Nadir will be important.

Thanks,
Rick

On Sep 3, 6:27 pm, Seb Perez-D  wrote:
> I have a similar but more automatic approach. I create the pto project
> file for one exposure, and then use a custom script to generate the
> panoramas for the different exposures. One feature of nona is very
> useful: you can pass the names of the images on the command line and
> it will use those images instead of the ones in the pto file. What the
> script does is to increase the number in the filename of the images.
>
> An alternative would be to use the "Apply template" in Hugin (in the
> File menu), which reuses the settings of another pto file. You could
> then use ptomerge
> (http://search.cpan.org/dist/Panotools-Script/bin/ptomerge) to merge
> these different exposures into one.
>
> Cheers,
>
> Seb
>
> On Thu, Sep 3, 2009 at 12:16, Eduardo Perez
>
>
>
> Esteban wrote:
> > I guess you are doing HDR panoramas, aren't you? Me too, but I take a
> > completely different approach: instead of passing all the images to Hugin, I
> > make a separate panorama for each exposure, and merge them afterwards; when
> > the exposures are aligned, the control points and optimizations can be
> > shared, I just change the images.
>
> > My workflow is:
>
> > * Copy the files from the first exposure to IMG1, IMG2, ..., IMGn (actually,
> > I use symbolic links in Linux, but Windows users will probably have to copy
> > the files).
> > * Open IMG1, IMG2, ..., IMGn with Hugin, create the control points,
> > optimize, ...; save the project and create a panorama named PANO1.
> > * Now copy the files from the second exposure over IMG1, IMG2, ..., IMGn;
> > execute the project again, but save the result to PANO2.
> > * Repeat for each exposure, and you will obtain a set of bracketed panoramas
> > PANO1, PANO2, ..., PANOn.
> > * Do all the HDR work.
>
> > Hope this helps.
>
> > On Thu, Sep 3, 2009 at 10:19 AM, RueiKe  wrote:
>
> >> I am looking for ways to simplify some of my more complex projects
> >> which could be 217 images connected by >10,000 control points.  In
> >> these cases I am doing 7 shot brackets for 31 images for full 360 x
> >> 180 degree pano.
>
> >> Seems like control points would be greatly simplified if I could just
> >> get hugin to assume the bracketed images were already aligned.  I have
> >> done a case where I just picked alignment points on the 4 corners of a
> >> few photos and it seemed to work fine.  Is this a reasonable
> >> approach?  Would it be possible to have an option to add a set of
> >> fixed control points for a specified set of aligned images?
>
> >> Thanks,
> >> Rick- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Exposure Bracket Control Points

[RueiKe]

I am looking for ways to simplify some of my more complex projects
which could be 217 images connected by >10,000 control points.  In
these cases I am doing 7 shot brackets for 31 images for full 360 x
180 degree pano.

Seems like control points would be greatly simplified if I could just
get hugin to assume the bracketed images were already aligned.  I have
done a case where I just picked alignment points on the 4 corners of a
few photos and it seemed to work fine.  Is this a reasonable
approach?  Would it be possible to have an option to add a set of
fixed control points for a specified set of aligned images?

Thanks,
Rick
--~--~-~--~~~---~--~~
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] Re: Hugin 2009.2 release cycle

[RueiKe]

Bruno,

I am working on the Traditional Chinese translation updates.  Should
be able to complete by the middle of next week.

Regards,
Rick

On Aug 26, 9:29 pm, Bruno Postle  wrote:
> On Tue 25-Aug-2009 at 00:04 -0400, Yuval Levy wrote:
>
>
>
> >starting a new tradition, once a month we'll ask ourselves the question:
> >is there something in trunk worth releasing? if the answer is yes, and
> >there is enough support, and somebody takes on the task, we'll go into
> >release mode.
>
> Yes hugin should go for a release.
>
> These need doing but shouldn't block a release:
>
> There are some twenty new strings that need translating.
> The manual hasn't been updated (actually it still doesn't cover some
> of the last-minute 0.8.0 features).
>
> These need testing:
>
> 'Blended and fused panorama' mode in the Stitcher tab.
> Various combinations of new Preferences; checking they are
> applied properly between sessions, when reloading projects,
> mixing with old preferences, new installs etc...
>
> Does libpano13 need a release, are the recent bugs resolved?  Do we
> need to bump the soname?
> Hugin doesn't need to wait for an enblend or autopano-sift-C release
>
> --
> 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@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] Re: Control Point Error

[RueiKe]

Hi Bruno,

These 4 photos are all for the Nadir.  Since these are taken off the
nodal point, I usually manually assign a different lens number.  Is
this not appropriate?

Looks like with the initial Alignment after adding all of the control
points, odd fitting parameters were set due to many bad alignment
points.  Having the intial bad alignment points is typical.  I find I
usually need to delete 10% after the first alignment.  It looks like
Hugin is basing all future alignments or optimizations on the previous
results.  I had to reset all data and re-align and everything was
fine.  Maybe I should make this part of my standard flow.  Actaully,
for my last 2 projects I did modify my flow to include the Nadir in
the intial alignment, instead of adding after.  I am trying to
simplify my work flow, since I have much less time available and so
many hugin projects in queue!

Regards,
Rick

On Aug 21, 2:30 am, Bruno Postle  wrote:
> On Thu 20-Aug-2009 at 08:05 -0700, RueiKe wrote:
>
>
>
> >I uploaded the pto file:
> >http://groups.google.com/group/hugin-ptx/web/KL5_Rev1.pto?hl=en%05eeb...
>
> The problem is only with four photos 80,81,82,83 (this is a big
> project).  Basically, somehow they got a different lens number with
> an extreme barrel distortion (b = -0.113).  All the other photos are
> fine.
>
> I don't know how this happened, but select these photos in the
> Camera and Lens tab, and Change lens... so all photos are 'lens 0',
> reoptimise, and the maximum control point error goes down to 5.
>
> >> > I have found in the past sporadic control points that show very large
> >> > errors, but when reviewed look normal.  I have included a screen
> >> > capture http://groups.google.com/group/hugin-ptx/web/
> >> > Hugin_Error_20aug09.jpg?hl=en%05eeb80c98d0c9ce2">here
>
> --
> 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@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] Re: Control Point Error

[RueiKe]

Hi Gerry,

I uploaded the pto file:
http://groups.google.com/group/hugin-ptx/web/KL5_Rev1.pto?hl=en%05eeb80c98d0c9ce2

Also, I have completed the project by finally reseting all data for
all images and reailigning.  Before taking this action, I was deleting
the offending control points, but after optimizing more would just pop
up.  Maybe the issue was the result of many "real" bad alignment
points during the original alignment.

Regards,
Rick

On Aug 20, 10:19 pm, Gerry Patterson  wrote:
> On Aug 20, 2009, at 1:43 AM, RueiKe  wrote:
>
>
>
> > I have found in the past sporadic control points that show very large
> > errors, but when reviewed look normal.  I have included a screen
> > capture http://groups.google.com/group/hugin-ptx/web/
> > Hugin_Error_20aug09.jpg?hl=en%05eeb80c98d0c9ce2">here
>
> > I am using SVN4005 64bit Vista build.
>
> > Regards,
> > Rick
>
> Hello,
>
> Any chance you could post a pto or, even better, a complete project  
> that deomstrates this error?
>
> Looking at the screenshot something certainly seems fishy.
>
> Gerry
--~--~-~--~~~---~--~~
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] Control Point Error

[RueiKe]

I have found in the past sporadic control points that show very large
errors, but when reviewed look normal.  I have included a screen
capture http://groups.google.com/group/hugin-ptx/web/
Hugin_Error_20aug09.jpg?hl=en%05eeb80c98d0c9ce2">here

I am using SVN4005 64bit Vista build.

Regards,
Rick
--~--~-~--~~~---~--~~
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] Re: test version of official installers for Hugin 0.8 on Windows

[RueiKe]

Hi Allard,

The language problems are with some strings of some dialog boxes.
Looks like from comments in the source code repository that some of
these might have been fixed recently.  When I have time, I will
download the latest build and document all cases of untranslated
strings in a new discussion thread.  Also, to make it easier for
future translators, it may be a good idea to clean up the .po file.  I
had to translate many strings that I have never seen while running the
application.  The language problems are minor and since they display
in English when not translated, I don't think it is a significant
issue.

I don't see any issues from my tests, but sometimes I get the feeling
that my work flow may be non-typical, and maybe a bit extreme.  I
don't see any issues with the release, but seeing results from another
tester would be good confirmation.

Regards,
Rick

On Jul 29, 12:32 pm, allard  wrote:
> Rick, are those language problems windows-specific, or is it a more
> general thing? Apart from that, no complaints yet it seems. How long
> should we wait to release this?
>
> Allard
>
> On Jul 28, 8:37 am, RueiKe  wrote:
>
>
>
> > I had a little more time for testing.  I used the same project as
> > above, with the Traditional Chinese interface.  I verified the "Align"
> > function from the assitant tab, fine tune all points, optimize
> > everything, and optimized exposure with no problems.  The only
> > concerns, which are not new for this release, are I always get a TIFF
> > library error when I open an existing project.  Also, many strings
> > that should be translated, are still in English, some of which I am
> > pretty sure were in the po file, but still don't seem to be used.  I
> > don't consider either a big issue.
>
> > Regards,
> > Rick
>
> > On Jul 27, 10:50 pm, RueiKe  wrote:
>
> > > I just installed the complete version with no issues.  I only had time
> > > for some quick testing before I call it a day so I just loaded a
> > > recent project (93 8bit tiffs with 10,707 control points).  It loaded
> > > fine, optimize with no problems, quick preview has no issues, stitched
> > > a small pano out of it with no issues.  I also started it up in
> > > Chinese Traditional and went through the menus with no issues.  I
> > > could run through a complete project tomorrow night, but out of time
> > > now.
>
> > > Regards,
> > > Rick
>
> > > On Jul 27, 12:20 pm, allard  wrote:
>
> > > > Hi all,
>
> > > > I built two versions of installer files for Hugin 0.8 on Windows. One
> > > > version includes patented control point generators 
> > > > (http://hugin.panotools.org/testing/hugin/Hugin08_W32_complete_setup.exe
> > > > ) and one that does not include them 
> > > > (http://hugin.panotools.org/testing/hugin/Hugin08_W32_ncpg_setup.exe).
> > > > Please test them so they can be uploaded to the sourceforge
> > > > repository. The only thing that needs to be tested is the installer
> > > > itself, the program is the SVN4008 version that was decided to be the
> > > > official 0.8 release and should not require testing.
> > > > What I need to know is
> > > > -are the texts of the installer licence and release notes acceptable?
> > > > -is the program installed correctly with all the options as selected?
> > > > -any other issues regarding the installation?
>
> > > > Any suggestions on the installer licence texts are welcome, that's not
> > > > really my specialty. I haven't really had time to do a lot of testing
> > > > of things like installing parallel versions, but that seems to work in
> > > > the limited tests I did. If everyone agrees this is ok, someone with
> > > > access can upload these to sourceforge, I don't have access there.
>
> > > > allard- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: test version of official installers for Hugin 0.8 on Windows

[RueiKe]

I had a little more time for testing.  I used the same project as
above, with the Traditional Chinese interface.  I verified the "Align"
function from the assitant tab, fine tune all points, optimize
everything, and optimized exposure with no problems.  The only
concerns, which are not new for this release, are I always get a TIFF
library error when I open an existing project.  Also, many strings
that should be translated, are still in English, some of which I am
pretty sure were in the po file, but still don't seem to be used.  I
don't consider either a big issue.

Regards,
Rick

On Jul 27, 10:50 pm, RueiKe  wrote:
> I just installed the complete version with no issues.  I only had time
> for some quick testing before I call it a day so I just loaded a
> recent project (93 8bit tiffs with 10,707 control points).  It loaded
> fine, optimize with no problems, quick preview has no issues, stitched
> a small pano out of it with no issues.  I also started it up in
> Chinese Traditional and went through the menus with no issues.  I
> could run through a complete project tomorrow night, but out of time
> now.
>
> Regards,
> Rick
>
> On Jul 27, 12:20 pm, allard  wrote:
>
>
>
> > Hi all,
>
> > I built two versions of installer files for Hugin 0.8 on Windows. One
> > version includes patented control point generators 
> > (http://hugin.panotools.org/testing/hugin/Hugin08_W32_complete_setup.exe
> > ) and one that does not include them 
> > (http://hugin.panotools.org/testing/hugin/Hugin08_W32_ncpg_setup.exe).
> > Please test them so they can be uploaded to the sourceforge
> > repository. The only thing that needs to be tested is the installer
> > itself, the program is the SVN4008 version that was decided to be the
> > official 0.8 release and should not require testing.
> > What I need to know is
> > -are the texts of the installer licence and release notes acceptable?
> > -is the program installed correctly with all the options as selected?
> > -any other issues regarding the installation?
>
> > Any suggestions on the installer licence texts are welcome, that's not
> > really my specialty. I haven't really had time to do a lot of testing
> > of things like installing parallel versions, but that seems to work in
> > the limited tests I did. If everyone agrees this is ok, someone with
> > access can upload these to sourceforge, I don't have access there.
>
> > allard- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: test version of official installers for Hugin 0.8 on Windows

[RueiKe]

I just installed the complete version with no issues.  I only had time
for some quick testing before I call it a day so I just loaded a
recent project (93 8bit tiffs with 10,707 control points).  It loaded
fine, optimize with no problems, quick preview has no issues, stitched
a small pano out of it with no issues.  I also started it up in
Chinese Traditional and went through the menus with no issues.  I
could run through a complete project tomorrow night, but out of time
now.

Regards,
Rick

On Jul 27, 12:20 pm, allard  wrote:
> Hi all,
>
> I built two versions of installer files for Hugin 0.8 on Windows. One
> version includes patented control point generators 
> (http://hugin.panotools.org/testing/hugin/Hugin08_W32_complete_setup.exe
> ) and one that does not include them 
> (http://hugin.panotools.org/testing/hugin/Hugin08_W32_ncpg_setup.exe).
> Please test them so they can be uploaded to the sourceforge
> repository. The only thing that needs to be tested is the installer
> itself, the program is the SVN4008 version that was decided to be the
> official 0.8 release and should not require testing.
> What I need to know is
> -are the texts of the installer licence and release notes acceptable?
> -is the program installed correctly with all the options as selected?
> -any other issues regarding the installation?
>
> Any suggestions on the installer licence texts are welcome, that's not
> really my specialty. I haven't really had time to do a lot of testing
> of things like installing parallel versions, but that seems to work in
> the limited tests I did. If everyone agrees this is ok, someone with
> access can upload these to sourceforge, I don't have access there.
>
> allard
--~--~-~--~~~---~--~~
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] Re: Windows Users: please test

[RueiKe]

I am running Ryan's 64bit build of 4005 with no problems at all.

Regards,
Rick

On Jul 24, 9:16 am, Yuval Levy  wrote:
> https://sourceforge.net/tracker/?func=detail&atid=550441&aid=2824416&;...
>
> can a few windows users confirm the above report that the 
> SVN4007http://adhuikeshoven.pbworks.com/f/hugin-SVN4007-setup.exeand SVN4012
> snapshotshttp://adhuikeshoven.pbworks.com/f/hugin-SVN4012-setup.exe
> quit on start? and 
> thathttp://adhuikeshoven.pbworks.com/f/hugin-SVN3975-setup.exeworks fine?
>
> please try on both Windows 64bit and Windows 32bit.
>
> Are there any builds around, particularly of SVN4008, that are not from
> Ad's site?
>
> we need to establish if the problem is specific to the bug report, or if
> it is generic; and if it is generic we need to establish if it is in
> Ad's builds, or if other builds fail as well.
>
> This would be particularly embarassing because SVN4008 = 0.8.0 release
> and the error was introduced between SVN3975 and SVN4007 at the RC4/RC5
> stage.
>
> Developers: Potentially in one of the following commits:
>
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3978http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3980*http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3993http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3999*http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=4005http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=4007*
>
> two of them are translations and one of them is an image, so highly
> unlikely - marked with asterisk.
>
> Yuv
--~--~-~--~~~---~--~~
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] Re: hugin installer for Windows Vista SVN 3975

[RueiKe]

I have spent a few days with Ryan's 64bit build of hugin, and I think
"wow!" is the best way to summarize the experience so far.  Here are a
few observations:

I set the memory usage for enfuse and enblend to 7GB.  Both went upto
the limit while stitching a large project with no issues.  I also
noticed nona got upto about 5GB and hugin itself got to 3GB, even
though I had the image cache set to 500MB.

A 17k wide 360x180 blended/enfused equirectangular projection from
125, 70MB, 16bit TIFF files stitched in 72min!  Previous projects took
about 5hrs.

I tried one autopano-sift-c test case  for 15 images with --maxdim
4000 set and it found over 3000 control points.  Typically, I have
found the previous versions have issues adding control points when --
maxdim is set to > ~1200. I also tried adding a Nadir with these
settings, and ~10 control points were found for all adjacent images,
which never happened in previous runs.

The optimizer really didn't seem much faster.  Still only used about
12% of cpu resources.

Overall hugin interface was a bit perkier, especially when dealing
with control point editing and cropping.

Both preview windows were more responsive.  I had issues with every
previous build where I would get a boost thread resource error about 1
in 5 times when adjusting the projection in the regular preview
screen.  For this build, I could not make it crash!

Not a single crash since I started testing on large projects!  At
times, I have had a project active over days, without closing or re-
starting.

Definitely a much improved user experience for large projects.  It
looks like from the discussion threads that not many people in the
user community are dealing with such large projects, but that is all I
work with.  This build certainly makes that work more pleasant!  I
understand that it should not be critical path for 0.8.0, but it would
be a great enhancement for the next release.

Regards,
Rick

On Jul 8, 5:17 am, Bruno Postle  wrote:
> On Tue 07-Jul-2009 at 14:38 -0400, Ryan Sleevi wrote:
>
>
>
> >Well, it's only supported if those two patch sets get merged upstream prior
> >to 0.8 (your prior e-mail asking for thoughts). My belief is they should be
> >very minor (the patches to Hugin itself, really Vigra, were straight from
> >upstream just backported).
>
> Sorry these didn't get applied, I'm trying not to break anything
> that is currently already working and 64bit Windows is a new feature
> rather than a bugfix (this shouldn't stop anyone creating a 0.8.0
> 64bit binary installer, they will just have to patch first).
>
> --
> 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@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] Re: Release rc4 as 'final'?

[RueiKe]

Hi Bruno,

All of the issues I was having were resolved by reducing the image
cache size.  It looks good to me!

Regards,
Rick

On Jul 7, 6:17 am, Bruno Postle  wrote:
> Hi all, my mail has been down for a few days, so I'm not completely  
> up-to-date.
>
> Can anyone think of a really good reason why we should not release
> the current hugin rc4 as a 'final' 0.8.0?
>
> --
> 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@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] Re: Enfuse zenith

[RueiKe]

Hi Cristian,

I have been having the same problem for blended, exposure fused
panos.  The problem for me is more of issue for the Nadir.  Here is an
example: http://www.flickr.com/photos/rueike/3658984267/

>From my observations, it looks like the multiple exposures for the
Nadir are being ignored and only one image is being used to make the
final pano.  I have resorted to using only the nominal shot for the
Nadir and trying to blend in post processing, but it still looks bad.
The documentation for enblend/enfuse mentions this as a limitation.

I have also tried enfusing the Nadir before stitching in hugin, but I
found mixing TIFFs from CaptureNX with TIFFs from enfuse creates some
problems.  Seems like there are compatibility issues.

I have seen so many nice exposure enfused and HDR 360x180 panos out
there that there must be a work around.

Does anyone have a good work flow to avoid this issue?

Regards,
Rick

On Jul 5, 1:26 am, cri  wrote:
> Today I tried to stitch 48 images with hugin (16 per exposure) to make
> an equirectangular 360x180 panorama. I discovered that I always get a
> vortex with strange fading in the zenith. Later, I read the hugin
> readme and found out that this is a known issue. So I'm here to ask
> how you handle this problem.
> (to me the only solution seems to be enfusing the single bracketed
> images before importing them in hugin for later stitching using only
> enblend).
>
> Regards
> Cristian
--~--~-~--~~~---~--~~
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] Re: hugin-0.8.0_rc4 released

[RueiKe]

I have some good news.

I moved my latest large project to my wife's computer just to verify
if the problems I have reported would occur on a Vista 32bit machine,
and I found that SVN3975 had no issues in opening the quick preview
screen on project open.  It was a fresh install, so I checked the
settings and found that the image cache size was set to 75MB, so I
decided to check what it was set to on my machine.  I found that I had
it set to 2000MB which is the max allowed.  When I reduced it to
200MB, all the errors I was seeing no longer occur.

I suspect some of the slow openGL improvements to speed it up ended up
using the image cache more effectively which is why I don't see the
issue in SVN3884 or earlier.  I would say the only bug is that hugin
allows one to set the image cache too large.  Other than that, I would
say RC4 is ready to go!

Is there any where to download a 64bit Vista build?  I seem to be
pushing too many limits with the 32bit version!

Regards,
Rick

On Jul 1, 8:15 pm, RueiKe  wrote:
> I have just loaded SVN3975 and found that it still has the same
> issues.  I tried a couple other things to more fully document the
> issue.
>
> 1) If I open my recently completed large pano by double clicking on
> the pto file, hugin will crash right after loading the images and
> opening a blank quick preview window.
> 2) If I start hugin first (no preview window is open) and then use the
> open project option to open the same file, it opens without error.  If
> I then press the align button, it will crash during the "Loading
> Images..." stage.
> 3) If I start hugin first (no preview window is open), then use the
> open project option to open the same file, and then open the quick
> preview window, the preview window will be blank, all white, after it
> has finished loading all images.  If I then open the regular preview
> window, I get a "Bad Allocation" error.
> 4) If I start hugin first (no preview window is open), then use the
> open project option to open the same file, and then open the regular
> preview window, the preview window will have a black area the size of
> the pano, and I get a "Bad Allocation" error.
> 5) If I start hugin first (no preview window is open), then use the
> open project option to open the same file, and then choose "Optimize
> Everything" from the optimizer tab, it completes optimization with no
> error.  If I then optimze low dynamic range in the exposure tab, I get
> and unhandled exception error.
>
> Hope this helps.
> Rick
>
> On Jun 29, 6:55 pm, RueiKe  wrote:
>
>
>
> > Here are the observations I made about the error in a June 3rd posting
> > in the "OpenGL Slow" thread:
>
> >    I have just tried to load and align a project that I had
> > succesfully
> >    processed using SVN3884.  I found that with SVN3906, I get an
> >    "unhandled exception" after choosing "Align" from the assistant
> > tab,
> >    during the "Loading images..." stage.
>
> > "Loading Images" happens pretty late in the "Align" sequence of
> > events.
>
> > Also, to be more accurate in my previous post, almost all of the panos
> > with the error have been 360x180, but the 76 image pano was not.
>
> > Regards,
> > Rick
>
> > On Jun 29, 6:12 pm, RueiKe  wrote:
>
> > > Hi Yuv,
>
> > > One of the difficulties of remote troubleshooting is to clearly
> > > communicate the problem so that others can understand and it looks
> > > like I have not included enough detail!
>
> > > My flow is:
> > > 1) Use the Load button from the Assistant to load all images
> > > 2) Use the "Create Control Points" button from the Images tab to add
> > > control points.  I have the autopano-sift-c from 0.7.0 in my bin
> > > directory.  This is a complex process for me in which I first add
> > > control points to all nominal exposure images and then add control
> > > points for all images in each bracketed set.  This step has no
> > > problems with the newer releases.
> > > 3) Goto the Assistant Tab and press "Align".  This is where the new
> > > versions crash.  I have given some detail about what it was doing when
> > > in previous posts, but I forgot.  I could try again this evening and
> > > give you the last message displayed before the crash.
>
> > > Since this happens on every large project I have tried, maybe 6 or so
> > > projects since I first reported the issue, I don't think there is
> > > anything special about my test cases.  I have uploaded some pto files,
> > > RueiKe_76.pto for exam

[hugin-ptx] Re: hugin installer for Windows Vista SVN 3975

[RueiKe]

For Windows Vista, there is an option under "System Properties" ->
"Performance Options" to change the settings of DEP.  On my system, it
was set to be enable for essential Windows programs only.  When I
change it to be active for all programs, I sitll don't see it raising
any DEP error for hugin.  I am running 64bit, SP1, so maybe SP2 is
more sensitive.

Seems like I am the only one reporting major issues in not being able
to use anything newer than SVN3884 for large projects.  Are there
others using the latest builds on windows for large projects with no
problems?

Regards,
Rick

On Jul 2, 6:40 am, Bruno Postle  wrote:
> On Wed 01-Jul-2009 at 18:32 -0400, Yuval Levy wrote:
>
>
>
> >The big question is whether to release 0.8 before this bug is fixed, or
> >keep postponing 0.8. For users that are not affected by this bug, the
> >current snapshot is good enough for a release...
>
> Yes, I'd like to go with the current release candidate, but I'm not
> sure if these problems are in hugin, the windows build, windows
> itself or some 3rd party windows software.
>
> Does anyone else see these crashes on OS X or Linux?  (note that
> enblend or enfuse crashing during stitching isn't a hugin bug)
>
> --
> 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@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] Re: hugin-0.8.0_rc4 released

[RueiKe]

I have just loaded SVN3975 and found that it still has the same
issues.  I tried a couple other things to more fully document the
issue.

1) If I open my recently completed large pano by double clicking on
the pto file, hugin will crash right after loading the images and
opening a blank quick preview window.
2) If I start hugin first (no preview window is open) and then use the
open project option to open the same file, it opens without error.  If
I then press the align button, it will crash during the "Loading
Images..." stage.
3) If I start hugin first (no preview window is open), then use the
open project option to open the same file, and then open the quick
preview window, the preview window will be blank, all white, after it
has finished loading all images.  If I then open the regular preview
window, I get a "Bad Allocation" error.
4) If I start hugin first (no preview window is open), then use the
open project option to open the same file, and then open the regular
preview window, the preview window will have a black area the size of
the pano, and I get a "Bad Allocation" error.
5) If I start hugin first (no preview window is open), then use the
open project option to open the same file, and then choose "Optimize
Everything" from the optimizer tab, it completes optimization with no
error.  If I then optimze low dynamic range in the exposure tab, I get
and unhandled exception error.

Hope this helps.
Rick

On Jun 29, 6:55 pm, RueiKe  wrote:
> Here are the observations I made about the error in a June 3rd posting
> in the "OpenGL Slow" thread:
>
>    I have just tried to load and align a project that I had
> succesfully
>    processed using SVN3884.  I found that with SVN3906, I get an
>    "unhandled exception" after choosing "Align" from the assistant
> tab,
>    during the "Loading images..." stage.
>
> "Loading Images" happens pretty late in the "Align" sequence of
> events.
>
> Also, to be more accurate in my previous post, almost all of the panos
> with the error have been 360x180, but the 76 image pano was not.
>
> Regards,
> Rick
>
> On Jun 29, 6:12 pm, RueiKe  wrote:
>
>
>
> > Hi Yuv,
>
> > One of the difficulties of remote troubleshooting is to clearly
> > communicate the problem so that others can understand and it looks
> > like I have not included enough detail!
>
> > My flow is:
> > 1) Use the Load button from the Assistant to load all images
> > 2) Use the "Create Control Points" button from the Images tab to add
> > control points.  I have the autopano-sift-c from 0.7.0 in my bin
> > directory.  This is a complex process for me in which I first add
> > control points to all nominal exposure images and then add control
> > points for all images in each bracketed set.  This step has no
> > problems with the newer releases.
> > 3) Goto the Assistant Tab and press "Align".  This is where the new
> > versions crash.  I have given some detail about what it was doing when
> > in previous posts, but I forgot.  I could try again this evening and
> > give you the last message displayed before the crash.
>
> > Since this happens on every large project I have tried, maybe 6 or so
> > projects since I first reported the issue, I don't think there is
> > anything special about my test cases.  I have uploaded some pto files,
> > RueiKe_76.pto for example.  All are blended fused 360x180 panos.  If I
> > have time this evening, I could see how large a JPEG version of a
> > project is.
>
> > Regards,
> > Rick
>
> > On Jun 29, 5:41 pm, Yuval Levy  wrote:
>
> > > Hi Rick,
>
> > > RueiKe wrote:
> > > > I have just loaded SVN3966 and found that it still crashes during
> > > > "Align".  I am testing with a new project that I have just completed
> > > > with no issues using SVN3811.
>
> > > can you try the following thing that could wreck your SVN3966 install
> > > (nothing that can't be undone by re-installing)?
>
> > > I assume you have SVN3811 and SVN3966 installed in two different
> > > folders. Normally the installer installs the Hugin folder in ...Program
> > > Files\Hugin.
>
> > > I also assume that you hit "Align" on the Assistant Tab as the second
> > > step after loading the images in that same tab.
>
> > > Copy the file Hugin\bin\autopano-c.exe (or autopano-sift-c.exe? I have
> > > not turned on my Windows workstation yet since coming home) from SVN3811
> > > to replace the one in SVN3966. Then hit "Align" and pray.
>
> > > This shoul

[hugin-ptx] Re: hugin-0.8.0_rc4 released

[RueiKe]

Here are the observations I made about the error in a June 3rd posting
in the "OpenGL Slow" thread:

   I have just tried to load and align a project that I had
succesfully
   processed using SVN3884.  I found that with SVN3906, I get an
   "unhandled exception" after choosing "Align" from the assistant
tab,
   during the "Loading images..." stage.

"Loading Images" happens pretty late in the "Align" sequence of
events.

Also, to be more accurate in my previous post, almost all of the panos
with the error have been 360x180, but the 76 image pano was not.

Regards,
Rick

On Jun 29, 6:12 pm, RueiKe  wrote:
> Hi Yuv,
>
> One of the difficulties of remote troubleshooting is to clearly
> communicate the problem so that others can understand and it looks
> like I have not included enough detail!
>
> My flow is:
> 1) Use the Load button from the Assistant to load all images
> 2) Use the "Create Control Points" button from the Images tab to add
> control points.  I have the autopano-sift-c from 0.7.0 in my bin
> directory.  This is a complex process for me in which I first add
> control points to all nominal exposure images and then add control
> points for all images in each bracketed set.  This step has no
> problems with the newer releases.
> 3) Goto the Assistant Tab and press "Align".  This is where the new
> versions crash.  I have given some detail about what it was doing when
> in previous posts, but I forgot.  I could try again this evening and
> give you the last message displayed before the crash.
>
> Since this happens on every large project I have tried, maybe 6 or so
> projects since I first reported the issue, I don't think there is
> anything special about my test cases.  I have uploaded some pto files,
> RueiKe_76.pto for example.  All are blended fused 360x180 panos.  If I
> have time this evening, I could see how large a JPEG version of a
> project is.
>
> Regards,
> Rick
>
> On Jun 29, 5:41 pm, Yuval Levy  wrote:
>
>
>
> > Hi Rick,
>
> > RueiKe wrote:
> > > I have just loaded SVN3966 and found that it still crashes during
> > > "Align".  I am testing with a new project that I have just completed
> > > with no issues using SVN3811.
>
> > can you try the following thing that could wreck your SVN3966 install
> > (nothing that can't be undone by re-installing)?
>
> > I assume you have SVN3811 and SVN3966 installed in two different
> > folders. Normally the installer installs the Hugin folder in ...Program
> > Files\Hugin.
>
> > I also assume that you hit "Align" on the Assistant Tab as the second
> > step after loading the images in that same tab.
>
> > Copy the file Hugin\bin\autopano-c.exe (or autopano-sift-c.exe? I have
> > not turned on my Windows workstation yet since coming home) from SVN3811
> > to replace the one in SVN3966. Then hit "Align" and pray.
>
> > This should help narrow down *where* the bug hits.
>
> > Another thing that could help: I assume your input images are TIFF. If
> > you mass-convert them to JPEG and run the same steps, what happens?
>
> > And since you mass-converted them to JPEG, the test case should be small
> > enough to be zipped and uploaded somewhere? how heavy is it in JPEG? It
> > would be good to run the test case against a different platform (Linux /
> > OSX) with same SVN version to determine if the issue is in an upstream
> > library.
>
> > Yuv- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: hugin-0.8.0_rc4 released

[RueiKe]

Hi Yuv,

One of the difficulties of remote troubleshooting is to clearly
communicate the problem so that others can understand and it looks
like I have not included enough detail!

My flow is:
1) Use the Load button from the Assistant to load all images
2) Use the "Create Control Points" button from the Images tab to add
control points.  I have the autopano-sift-c from 0.7.0 in my bin
directory.  This is a complex process for me in which I first add
control points to all nominal exposure images and then add control
points for all images in each bracketed set.  This step has no
problems with the newer releases.
3) Goto the Assistant Tab and press "Align".  This is where the new
versions crash.  I have given some detail about what it was doing when
in previous posts, but I forgot.  I could try again this evening and
give you the last message displayed before the crash.

Since this happens on every large project I have tried, maybe 6 or so
projects since I first reported the issue, I don't think there is
anything special about my test cases.  I have uploaded some pto files,
RueiKe_76.pto for example.  All are blended fused 360x180 panos.  If I
have time this evening, I could see how large a JPEG version of a
project is.

Regards,
Rick

On Jun 29, 5:41 pm, Yuval Levy  wrote:
> Hi Rick,
>
> RueiKe wrote:
> > I have just loaded SVN3966 and found that it still crashes during
> > "Align".  I am testing with a new project that I have just completed
> > with no issues using SVN3811.
>
> can you try the following thing that could wreck your SVN3966 install
> (nothing that can't be undone by re-installing)?
>
> I assume you have SVN3811 and SVN3966 installed in two different
> folders. Normally the installer installs the Hugin folder in ...Program
> Files\Hugin.
>
> I also assume that you hit "Align" on the Assistant Tab as the second
> step after loading the images in that same tab.
>
> Copy the file Hugin\bin\autopano-c.exe (or autopano-sift-c.exe? I have
> not turned on my Windows workstation yet since coming home) from SVN3811
> to replace the one in SVN3966. Then hit "Align" and pray.
>
> This should help narrow down *where* the bug hits.
>
> Another thing that could help: I assume your input images are TIFF. If
> you mass-convert them to JPEG and run the same steps, what happens?
>
> And since you mass-converted them to JPEG, the test case should be small
> enough to be zipped and uploaded somewhere? how heavy is it in JPEG? It
> would be good to run the test case against a different platform (Linux /
> OSX) with same SVN version to determine if the issue is in an upstream
> library.
>
> Yuv
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

I am still using SVN3811 due to align crash issues, so maybe this
image loading problem has been fixed in later builds, but this is
something I have just discovered.  I am working with a large project
that includes 125 images which includes 5 shot brackets.  The project
aligned with no problem and I had stitched a low resolution trial
image.  The sky was a bit over exposed so I decided to remove the most
exposed shots from each bracket.  With the Quick Preview screen
displayed, I chose 10 images from hugin's "Images" tab and selected
"Remove Selected Images".  It then started reloading images.  I then
went to work and came home 5 hours later to find it still actively
reloading images with no indications of any errors.  It was still
actively loading from files on disk.  It appeared to be stuck in a
loop.

Regards,
Rick

On Jun 13, 12:34 am, Harry van der Wolf  wrote:
> Hi Habi,
>
> (I missed these posts, so I kick in a little late).
>
> It is not a problem of your laptop. George Row experiences exactly the same
> problems with large panorama's. It has to do with the way OSXes malloc badly
> deals with memory.
> That's also why I built a Hugin version against dmalloc instead of OSXes
> malloc. Unfortunately that didn't help George and probably won't help you
> either.
>
> I assume you are on a dual-core Intel macbook. That's a 64 bit machine. You
> might give the older 0.7 final version a go. It's a 64bit version and that
> might help but ONLY on Leopard. It didn't help George as George also used
> masks in his tiff's which was another reason for enblend to crash (and
> that's why I built a hugin with the latest enblend from Christoph Spiel that
> has much better mask handling, but that one crashed again on the malloc
> allocation error.)
>
> Harry
>
> 2009/6/9 David Haberthür 
>
>
>
>
>
> > Hello Guido.
>
> > On 09.06.2009, at 22:38, Guido Kohlmeyer wrote:
>
> > > The additional option is only a workaround that may work, but as you
> > > already percieved it will yield to higher memory consumption to
> > > generate
> > > the mask in a higher resolution.
> > > I guess the process runs out of memory.
>
> > > Guido
>
> > I suppose that must be the problem, since it crashes with the same
> > complaint in the logfile:
> > 
> > DSC_24160117.tif DSC_2284-DSC_24160118.tif DSC_2284-DSC_24160119.tif
> > DSC_2284-DSC_24160120.tif DSC_2284-DSC_24160121.tif DSC_2284-
> > DSC_24160122.tif
> > enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> > *** error: can't allocate region
> > *** set a breakpoint in malloc_error_break to debug
> > enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> > *** error: can't allocate region
> > *** set a breakpoint in malloc_error_break to debug
> > enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> > *** error: can't allocate region
> > *** set a breakpoint in malloc_error_break to debug
> > enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> > *** error: can't allocate region
> > *** set a breakpoint in malloc_error_break to debug
> > terminate called recursively
> > gnumake: *** [DSC_2284-DSC_2416.png] Abort trap
> > gnumake: *** Deleting file `DSC_2284-DSC_2416.png'
> > ---
> > even for the newest build from Harry (0.0.0-svn3923)
> > I guess I'll have to try at work, on a machine with 16 GB of RAM and
> > not on my puny laptop with 2GB :)
> > Habi
>
> > David Haberthür schrieb:
> > >> Dear Guido,
> > >> That only helped a bit, now enblend crashes lateron in the process.
> > >> The relevant lines of the stitching window are below:
>
> > >> ---
> > >> DSC_2284-DSC_24160114.tif DSC_2284-DSC_24160115.tif
> > >> DSC_2284-DSC_24160116.tif DSC_2284-DSC_24160117.tif
> > >> DSC_2284-DSC_24160118.tif DSC_2284-DSC_24160119.tif
> > >> DSC_2284-DSC_24160120.tif DSC_2284-DSC_24160121.tif
> > >> DSC_2284-DSC_24160122.tif
> > >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> > >> *** error: can't allocate region
> > >> *** set a breakpoint in malloc_error_break to debug
> > >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> > >> *** error: can't allocate region
> > >> *** set a breakpoint in malloc_error_break to debug
> > >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> > >> *** error: can't allocate region
> > >> *** set a breakpoint in malloc_error_break to debug
> > >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> > >> *** error: can't allocate region
> > >> *** set a breakpoint in malloc_error_break to debug
> > >> terminate called recursively
> > >> gnumake: *** [DSC_2284-DSC_2416.png] Abort trap
> > >> gnumake: *** Deleting file `DSC_2284-DSC_2416.png'
> > >> ---
> > >> using hugin svn-3888, will try tomorrow with harrys freshly
> > >> compiled rc3.
> > >> have a good night.
> > >> habi/david
>
> > >>> David Haberthür schrieb:
>
> >  On 07.06.2009, at 18:45, Harry van der Wolf wrote:
>
> > > 2009/6/5 David Haberthür  > >>>

[hugin-ptx] Re: some minor GUI ideas

[RueiKe]

When a control point is deleted from the control point table, it
should go to the next point in the list instead of the first point in
the list.

Rick

On Jun 28, 10:24 pm, Harry van der Wolf  wrote:
> With regard to the preferred output option: I would like Hugin to defaultly
> save in the input format.
> If I feed jpeg's to Hugin, the preferred output format is jpeg.
> If I feed tiff's to hugin, the preferred output format is tiff.
>
> Harry
>
> 2009/6/28 Guido Kohlmeyer 
>
>
>
>
>
> > I know only one drawback of using the lossless compression methods of
> > TIF file format: Some applications do not support all three methods, but
> > I expect "Packbits" and "LZW" are supported by many ones. A preselection
> > in the preferences would be fine to match the own workflow.
>
> > Guido
>
> > Andreas Metzler schrieb:
> > > Better: Add some way to set the prefered output format. (I wonder why
> > > tif with *no* compression is used by default. Is there any downside for
> > > using tif with any of the three lossless compression methods?)
> > > cu andreas- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: hugin-0.8.0_rc4 released

[RueiKe]

Hi Yuv,

I have just loaded SVN3966 and found that it still crashes during
"Align".  I am testing with a new project that I have just completed
with no issues using SVN3811.  It has 125 images and 8381 control
points.  There is no error if I use the optimizer, but I get a bad
allocation error if I open the preview window after opimize.  If I
ignore and try to optimize again, I get an error indicating not enough
memory.

Regards,
Rick

On Jun 18, 4:21 pm, Yuval Levy  wrote:
> hi Rick,
>
> RueiKe wrote:
> > I am not sure of the status of the large project Align crash issue,
>
> sorry I have not got back to you earlier on your June-5 mail re SVN3811
> vs. SVNHEAD. I am traveling and have limited time/access.
>
> The topic was Quick Preview, but I had Align crash on me as well.
>
> I've set up on both 3811 and the most recent HEAD on my Ubuntu notebook
> (an ailing Pentium M with 2GB RAM).
>
> On my 294 images project Align crashed as well. I found out that the
> problem was me: I had upgraded to the most recent libpano and I had not
> noticed the change in ABI that requires to rebuild dependent tools. I
> rebuilt Hugin and Autopano against the latest libpano and will test the
> 294 images project soon.
>
> The problem may be platform related but I won't have access to Windows
> until the end of the month.
>
> > Let me know if it would be useful
> > for me to provide a test case.  It is too large to upload anywhere
> > (~16G) have access to, so I would have to mail DVDs if it is
> > necessary.
>
> I assume you have TIFF images? for the test case, converting them to
> JPEG would help.
>
> Also if you test the latest Windows build, note that the one currently
> published by Ad, while it is the best in the 0.8 series, is not yet
> equivalent to rc4.
>
> Thanks for all the testing
> Yuv
--~--~-~--~~~---~--~~
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] Re: hugin-0.8.0_rc4 released

[RueiKe]

Hi Yuv,

Sorry for the delay, but I am just getting over a cold...

Yes, this topic was raised in the preview stream, but the slow update
to the preview may or may not be related to the crash.   I do use TIFF
files, so if a test case is needed I could convert to JPG.  It sounds
like you already have a huge project for testing, so maybe providing a
test case is not necessary.  Seems like there is nothing special about
the projects that crash hugin during alignment, as tests I documented
in the "OpenGL slow because of reloading" show that any large project
will crash during align.

Ad should have a new build available tomorrow, so I will report back
if that has the same problem or not.

Regards,
Rick

On Jun 18, 4:21 pm, Yuval Levy  wrote:
> hi Rick,
>
> RueiKe wrote:
> > I am not sure of the status of the large project Align crash issue,
>
> sorry I have not got back to you earlier on your June-5 mail re SVN3811
> vs. SVNHEAD. I am traveling and have limited time/access.
>
> The topic was Quick Preview, but I had Align crash on me as well.
>
> I've set up on both 3811 and the most recent HEAD on my Ubuntu notebook
> (an ailing Pentium M with 2GB RAM).
>
> On my 294 images project Align crashed as well. I found out that the
> problem was me: I had upgraded to the most recent libpano and I had not
> noticed the change in ABI that requires to rebuild dependent tools. I
> rebuilt Hugin and Autopano against the latest libpano and will test the
> 294 images project soon.
>
> The problem may be platform related but I won't have access to Windows
> until the end of the month.
>
> > Let me know if it would be useful
> > for me to provide a test case.  It is too large to upload anywhere
> > (~16G) have access to, so I would have to mail DVDs if it is
> > necessary.
>
> I assume you have TIFF images? for the test case, converting them to
> JPEG would help.
>
> Also if you test the latest Windows build, note that the one currently
> published by Ad, while it is the best in the 0.8 series, is not yet
> equivalent to rc4.
>
> Thanks for all the testing
> Yuv
--~--~-~--~~~---~--~~
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] Re: hugin-0.8.0_rc4 released

[RueiKe]

Hi Bruno,

I am not sure of the status of the large project Align crash issue,
but I have tried SVN3943 and found that it still crashes for my large
projects.  Same with 3929 and 3906.  I am currently using SVN3884 for
these projects with no problems.  Let me know if it would be useful
for me to provide a test case.  It is too large to upload anywhere
(~16G) have access to, so I would have to mail DVDs if it is
necessary.

Regards,
Rick

On Jun 18, 1:55 am, Bruno Postle  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> A hugin-0.8.0_rc4 (release candidate 4) tarball is available here:
>
> https://sourceforge.net/project/showfiles.php?group_id=77506&package_...
>
> This is a release candidate, i.e. The final release may be identical.
>
> Changes since 0.8.0 rc3:
>
> * Minor Hungarian translation update.
>
> * Fixes for Ev value bug that manifests as 'white' images.
>
> * Fix for Fast Preview Crop button crash.
>
> * Fix for crash opening projects without images or control points.
>
> * Some unused files removed.
>
> * LAPACK is disabled by default.  If you want to experiment then
> enable it by running cmake with -DENABLE_LAPACK=YES
>
> See README, ChangeLog and INSTALL_cmake for more information.
>
> SHA1SUM: 129a515300947be54b5b02f5c3b693647294961a  hugin-0.8.0_rc4.tar.gz
>
> This release is equivalent to svn 3945, links to recent hugin binary
> installers for testing can be found here:
>
> http://panospace.wordpress.com/downloads/
>
> - --
> Bruno
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFKOS4rFqOhwCjyCLoRAq/hAKDJ7uuPv5gjAZPGBXK/Uq4/7QnUdgCeM1i8
> sWwOIBLLmFcpt9fnr04/Jew=
> =KEO8
> -END PGP SIGNATURE-
--~--~-~--~~~---~--~~
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] Re: Interface consistency

[RueiKe]

I had also struggled with the Traditional Chinese translation for the
stitcher tab and used the approach of better describing them in
English when consulting others for the Chinese equivalent.  I agree
that the use of simpler more direct phrases here would be an
improvement.

Regards,
Rick

On Jun 14, 11:07 pm, Bruno Postle  wrote:
> Just had a discussion with Pablo about the text on the Stitcher tab
> and realised that it makes much more sense in the German translation
> than the English original.
>
> We use a lot of confusing phrases in hugin: normal output,
> blended panorama, exposure blending, etc...
>
> So maybe we should pick a small number of phrases and use them
> consistently:
>
> - Seam blending (enblend)
> - Exposure fusing (enfuse)
> - Focus stacking (enfuse)
> - HDR merging
>
> --
> 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@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] Re: OpenGL slow because of reloading

[RueiKe]

I have just tried out SVN 3929 on a large project with 161 images and
~12k control points.  I found that image reloading was improved for
the images tab.  When I selected Align from the assistant tab, I found
that during the "Leveling the Panorama" stage, hugin was reading in
every image.  When it was done reading all of the images, it started
to read them in again, and gave an unhandled exception fault.  Hugin
memory usage in this test was 1.6GB, which is more than what I have
seen in the past.

Regards,
Rick

On Jun 10, 5:05 am, David Haberthür 
wrote:
> Hello Guido.
>
> On 09.06.2009, at 22:38, Guido Kohlmeyer wrote:
>
>
>
> > The additional option is only a workaround that may work, but as you
> > already percieved it will yield to higher memory consumption to  
> > generate
> > the mask in a higher resolution.
> > I guess the process runs out of memory.
>
> > Guido
>
> I suppose that must be the problem, since it crashes with the same  
> complaint in the logfile:
> 
> DSC_24160117.tif DSC_2284-DSC_24160118.tif DSC_2284-DSC_24160119.tif  
> DSC_2284-DSC_24160120.tif DSC_2284-DSC_24160121.tif DSC_2284-
> DSC_24160122.tif
> enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> enblend(815) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> terminate called recursively
> gnumake: *** [DSC_2284-DSC_2416.png] Abort trap
> gnumake: *** Deleting file `DSC_2284-DSC_2416.png'
> ---
> even for the newest build from Harry (0.0.0-svn3923)
> I guess I'll have to try at work, on a machine with 16 GB of RAM and  
> not on my puny laptop with 2GB :)
> Habi
>
> David Haberthür schrieb:
>
>
>
> >> Dear Guido,
> >> That only helped a bit, now enblend crashes lateron in the process.
> >> The relevant lines of the stitching window are below:
>
> >> ---
> >> DSC_2284-DSC_24160114.tif DSC_2284-DSC_24160115.tif
> >> DSC_2284-DSC_24160116.tif DSC_2284-DSC_24160117.tif
> >> DSC_2284-DSC_24160118.tif DSC_2284-DSC_24160119.tif
> >> DSC_2284-DSC_24160120.tif DSC_2284-DSC_24160121.tif
> >> DSC_2284-DSC_24160122.tif
> >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> >> *** error: can't allocate region
> >> *** set a breakpoint in malloc_error_break to debug
> >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> >> *** error: can't allocate region
> >> *** set a breakpoint in malloc_error_break to debug
> >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> >> *** error: can't allocate region
> >> *** set a breakpoint in malloc_error_break to debug
> >> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> >> *** error: can't allocate region
> >> *** set a breakpoint in malloc_error_break to debug
> >> terminate called recursively
> >> gnumake: *** [DSC_2284-DSC_2416.png] Abort trap
> >> gnumake: *** Deleting file `DSC_2284-DSC_2416.png'
> >> ---
> >> using hugin svn-3888, will try tomorrow with harrys freshly  
> >> compiled rc3.
> >> have a good night.
> >> habi/david
>
> >>> David Haberthür schrieb:
>
>  On 07.06.2009, at 18:45, Harry van der Wolf wrote:
>
> > 2009/6/5 David Haberthür  > 
> > >
>
> >   i could help with providing a test-case, the panorama i shot  
> > last
> >   saturday evening [1] contains +100 images and +7000 control  
> > points
> >   generated with pan-o-matic. i'm still struggling with  
> > stitching it
> >   with full resolution, somehow i chokes at the fusing-step when
> > trying
> >   to stitch it in sizes bigger than 1px wide, now i've  
> > stitched it
> >   in "only" 2694 x 635 px (os x, with harrys newest svn-builld).
>
> > Hi Habi,
>
> > Nice pano.
> > You are saying that it chokes on 1px wide (1 by ?).
> > What error message do you get?
>
> > Harry
>
>  Hoi Harry.
>  Thanks, i've tried to make a night-version of the panorama i've  
>  shot
>  some weeks ago.
>  I've failed to thorougly investivate it, but the panorama fails to
>  stitch for sizes 1x4122 and 12000x4946 px. It actually fails  
>  with
>  an enblend warning:
>  "enblend: warning: failed to detect any seam
>  enblend: mask is entirely black, but white image was not  
>  identified as
>  redundant
>  gnumake: *** [DSC_2284-DSC2416.png] Error 1"
>  are the last entries in the log window. The complete log is  
>  attached
> >>>

[hugin-ptx] Re: error using autopano

[RueiKe]

I have encountered this message before.  I found it occurred when I
had many images selected for adding control points.  it goes through
the entire process of finding key points and in the very end, says it
can not execute command.  For my situation, it was related to a
Windows limitation to the length of a command line.  Ways around it is
to move the project to a directory with a shorter path or to select
less images for adding control points.

Regards,
Rick

On Jun 7, 11:15 pm, thomas hygum  wrote:
> ive downloaded and installed 0.7.0 on two different windows pc's, but
> i get the same error using "create control points" (autopano):
> "could not execute command ..."
>
> Is that a common error with a described solution?
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

I am now alignng a new project with SVN3811.  It has 155 images.  I
have finished adding over 12k control points and have started the
alignment and 1 hour into it I found that has been loading images for
a very long time.  I have uploaded a screen shot, Hugin_Align2.jpg.
Seems like reading the original image files is really slowing things
down.  Barely any CPU activity and only ~300K of memory committed.
Though SVN3811 manages without crashing, it does seem to be also
imacted by image caching issues.  Even during the process of adding
control points, I had to be careful never to have only a single image
selected to prevent it from loading images...

I have not been able to access a RC3 installer yet, so I won't be able
to try the latest until next weekend.

Regards,
Rick

On Jun 5, 6:57 pm, RueiKe  wrote:
> Hi Yuv,
>
> I have stitched some of my largest projects with SVN3811.  I have just
> re-verified that there are no issues loading and aligning large
> projects with this build.  Another major difference is that SVN3811
> opens the old preview by default.  To see if Quick Preview was a
> factor, I closed the original preview, opened Quick Preview and did an
> Align.  It still re-opens the original preview, but also updates the
> Quick Preview with no problems.  Looks like SVN3811 doesn't have the
> issue.
>
> Regards,
> Rick
>
> On Jun 5, 7:37 am, Yuval Levy  wrote:
>
>
>
> > Hi all,
>
> > Gerry Patterson wrote:
> > > I don't have a project that large.  I tired with a few I have that have 8
> > > picts or less, but I am unable to reproduce this problem.
>
> > > I develop under Linux...
>
> > > Does it happen on other projects you have?
> > > Can you reproduce your problem if you try separating out the steps?
> > > (optimize, straighten, photometric optimize..)
>
> > I don't know if it is related: I currently have access to an Ubuntu
> > notebook only and I am traveling so I can't test much.
>
> > I shot some large panos. I tried to stitch one with 294 images and
> > autopano-sift-C died on me with an error 255. rebuilding the whole chain
> > (libpano, autopano-sift-C, hugin) solved the problem.
>
> > I read somewhere that there has been a break in the API of libpano13.
> > maybe this causes headache to the current Windows SDK? Would be
> > interesting to test the same project with an early 0.8 snapshot 
> > from:http://adhuikeshoven.pbworks.com/hugin%20installer%20for%20Windows%20...
>
> > Yuv- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

Hi Yuv,

I have stitched some of my largest projects with SVN3811.  I have just
re-verified that there are no issues loading and aligning large
projects with this build.  Another major difference is that SVN3811
opens the old preview by default.  To see if Quick Preview was a
factor, I closed the original preview, opened Quick Preview and did an
Align.  It still re-opens the original preview, but also updates the
Quick Preview with no problems.  Looks like SVN3811 doesn't have the
issue.

Regards,
Rick

On Jun 5, 7:37 am, Yuval Levy  wrote:
> Hi all,
>
> Gerry Patterson wrote:
> > I don't have a project that large.  I tired with a few I have that have 8
> > picts or less, but I am unable to reproduce this problem.
>
> > I develop under Linux...
>
> > Does it happen on other projects you have?
> > Can you reproduce your problem if you try separating out the steps?
> > (optimize, straighten, photometric optimize..)
>
> I don't know if it is related: I currently have access to an Ubuntu
> notebook only and I am traveling so I can't test much.
>
> I shot some large panos. I tried to stitch one with 294 images and
> autopano-sift-C died on me with an error 255. rebuilding the whole chain
> (libpano, autopano-sift-C, hugin) solved the problem.
>
> I read somewhere that there has been a break in the API of libpano13.
> maybe this causes headache to the current Windows SDK? Would be
> interesting to test the same project with an early 0.8 snapshot 
> from:http://adhuikeshoven.pbworks.com/hugin%20installer%20for%20Windows%20...
>
> Yuv
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

Hi Habi,

I had a similar problem that may be related.  I was using SVN3811 and
was finally sucessfull stitching a 15338x7669 pano after I modified
the -m option of enfuse and enblend to "-m 2000".  See discussion at
the Hugin Users Group: 
http://www.flickr.com/groups/hugin/discuss/72157615431955909/

Regards,
Rick

On Jun 5, 4:22 pm, David Haberthür  wrote:
> hello all
>
>
>
> On Thu, Jun 4, 2009 at 20:36, Gerry Patterson wrote:
> > Hello,
>
> > I downloaded the files...
>
> > What is striking about the 76 image pano is the number of control points:
> > 7890+.  Wow...  I have to see if I can generate a simlair setup as a test
> > case.
> [snip]
>
> > Anyways. Having a large test case on hand would be a good thing. :-)
>
> > - Gerry
>
> i could help with providing a test-case, the panorama i shot last
> saturday evening [1] contains +100 images and +7000 control points
> generated with pan-o-matic. i'm still struggling with stitching it
> with full resolution, somehow i chokes at the fusing-step when trying
> to stitch it in sizes bigger than 1px wide, now i've stitched it
> in "only" 2694 x 635 px (os x, with harrys newest svn-builld).
> i'll try to look into it this weekend and try to find out where the
> stitching chokes.
> i remember that i've also seen the slowing of the fast preview due to
> reloading, but haven't been really been able to reproduce it...
> habi
>
> [1]http://habi.gna.ch/2009/06/01/baldachin-by-night-ii/
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

Hi Gerry,

I did not realize that my project sizes were that out of the ordinary,
but I did need to get a Core i7 based machine with 12GB of memory.  My
largest project uses over 11k control points: 
http://www.flickr.com/photos/rueike/3493769918/
I usually use the control points tab to add the max of 100 points for
all nominal exposure images in 2 rows, and then a second time for 2
rows with the middle row included both times.  Then I add control
points for each bracket set.  After first alignment, I use the control
point table to delete the worst, usually about 10%. Then I fine tune
the remainder until I get to a reasonable error.

Yes, I am using Vista.  I think that corrupt file occured when my
computer crashed during a file save due to a video driver error I have
been having.  Seems like 0.7.0 handles the corrupt file better than
SVN3906.

Regards,
Rick


On Jun 5, 2:36 am, Gerry Patterson  wrote:
> Hello,
>
> I downloaded the files...
>
> What is striking about the 76 image pano is the number of control points:
> 7890+.  Wow...  I have to see if I can generate a simlair setup as a test
> case.
>
> The corrupt 18 image pto file is certainly that.  It is filled with null
> characters.  I used to see that with some journalled filesystems such as XFS
> if they were knocked over in the middle of a transaction.  You said you were
> running vista?
>
> Anyways. Having a large test case on hand would be a good thing. :-)
>
> - Gerry
>
>
>
> On Thu, Jun 4, 2009 at 8:49 AM, RueiKe  wrote:
>
> > Hi Gerry,
>
> > I have uploaded the requested pto files.
>
> > Regards,
> > Rick
>
> > On Jun 4, 9:30 pm, Gerry Patterson  wrote:
> > > Hello,
>
> > > OK.  Looks like I need to have a fairly large test case on hand.  Would
> > you
> > > attach a .pto file of your 4, 18 and 76 image panos?
>
> > > Best Regards,
>
> > > - Gerry
>
> > > On Thu, Jun 4, 2009 at 7:51 AM, RueiKe  wrote:
>
> > > > ok, I found that the 18 image pano above that crashes on open is due
> > > > to a corrupt pto file.  When I open it with 0.7.0, it opens with no
> > > > errors, but has no photos.  In wordpad, there is no text.  I had
> > > > another version of the pto file for that project which opened fine
> > > > with 0.7.0.  With SVN3906, it opens fine, it completes the align with
> > > > no error, but when the Quick preview window opens, there are no
> > > > images.  When I optimize, hugin just hangs with no error. If I close
> > > > the quick preview window after align, and then open the regular
> > > > preview window it crashes with a boost thread resource error.
>
> > > > I reduced the same project to 12 images, and found that it hung while
> > > > doing the align.  I killed the process and reopend the project, and it
> > > > opened with the aligned image in the quick preview window, I then
> > > > aligned with no error.
>
> > > > Seems like the issues scale with the size of the project and start
> > > > causing problems at 12, 70MB 16bit tiffs.
>
> > > > Rick
>
> > > > On Jun 4, 6:01 pm, RueiKe  wrote:
> > > > > Quick set of tests before dinner:
>
> > > > > 4 image pano - No Crash
> > > > > 76 image pano - Crash as before
> > > > > 11 image pano - No Crash
> > > > > 5 image pano - No Crash
> > > > > 18 image pano - Crash while opening pto file (tried twice)
>
> > > > > I will collect more details this evening.
>
> > > > > Rick
>
> > > > > On Jun 4, 10:31 am, RueiKe  wrote:
>
> > > > > > Hi Gerry,
>
> > > > > > I have not tried any other projects yet.  After work today (in
> > 8hrs),
> > > > > > I will attempt to duplicate the issue with a smaller project.  I
> > have
> > > > > > 6 image project readily available that I could work with.  I will
> > also
> > > > > > see what the results are for manually running the various steps.
>
> > > > > > Regards,
> > > > > > Rick
>
> > > > > > On Jun 4, 9:04 am, Gerry Patterson  wrote:
>
> > > > > > > Hi,
>
> > > > > > > I don't have a project that large.  I tired with a few I have
> > that
> > > > have 8
> > > > > > > picts or less, but I am unable to reproduce this problem.
>
> > > > > > > I develop under Linux...
>
> > > > > > > Does it happen on oth

[hugin-ptx] Re: OpenGL slow because of reloading

[RueiKe]

Hi Gerry,

I have uploaded the requested pto files.

Regards,
Rick

On Jun 4, 9:30 pm, Gerry Patterson  wrote:
> Hello,
>
> OK.  Looks like I need to have a fairly large test case on hand.  Would you
> attach a .pto file of your 4, 18 and 76 image panos?
>
> Best Regards,
>
> - Gerry
>
>
>
> On Thu, Jun 4, 2009 at 7:51 AM, RueiKe  wrote:
>
> > ok, I found that the 18 image pano above that crashes on open is due
> > to a corrupt pto file.  When I open it with 0.7.0, it opens with no
> > errors, but has no photos.  In wordpad, there is no text.  I had
> > another version of the pto file for that project which opened fine
> > with 0.7.0.  With SVN3906, it opens fine, it completes the align with
> > no error, but when the Quick preview window opens, there are no
> > images.  When I optimize, hugin just hangs with no error. If I close
> > the quick preview window after align, and then open the regular
> > preview window it crashes with a boost thread resource error.
>
> > I reduced the same project to 12 images, and found that it hung while
> > doing the align.  I killed the process and reopend the project, and it
> > opened with the aligned image in the quick preview window, I then
> > aligned with no error.
>
> > Seems like the issues scale with the size of the project and start
> > causing problems at 12, 70MB 16bit tiffs.
>
> > Rick
>
> > On Jun 4, 6:01 pm, RueiKe  wrote:
> > > Quick set of tests before dinner:
>
> > > 4 image pano - No Crash
> > > 76 image pano - Crash as before
> > > 11 image pano - No Crash
> > > 5 image pano - No Crash
> > > 18 image pano - Crash while opening pto file (tried twice)
>
> > > I will collect more details this evening.
>
> > > Rick
>
> > > On Jun 4, 10:31 am, RueiKe  wrote:
>
> > > > Hi Gerry,
>
> > > > I have not tried any other projects yet.  After work today (in 8hrs),
> > > > I will attempt to duplicate the issue with a smaller project.  I have
> > > > 6 image project readily available that I could work with.  I will also
> > > > see what the results are for manually running the various steps.
>
> > > > Regards,
> > > > Rick
>
> > > > On Jun 4, 9:04 am, Gerry Patterson  wrote:
>
> > > > > Hi,
>
> > > > > I don't have a project that large.  I tired with a few I have that
> > have 8
> > > > > picts or less, but I am unable to reproduce this problem.
>
> > > > > I develop under Linux...
>
> > > > > Does it happen on other projects you have?
> > > > > Can you reproduce your problem if you try separating out the steps?
> > > > > (optimize, straighten, photometric optimize..)
>
> > > > > If you can reproduce it with a smaller project, it may be easier to
> > transfer
> > > > > it around.
>
> > > > > Best Regards,
>
> > > > > - Gerry
>
> > > > > On Wed, Jun 3, 2009 at 9:28 AM, RueiKe  wrote:
>
> > > > > > Yes, I am using Vista.  I duplicated this issue in Traditional
> > Chinese
> > > > > > and English, just to be sure it was not a wide character issue.
>
> > > > > > I loaded a project file from a project I previoulsy complete, 94
> > > > > > images enfused blended pano. Then press align button.  After the
> > > > > > "Levelling panorama" step, it starts "Loading Images" and crashes
> > > > > > about 10 seconds into that after loading a few images.  The Fast
> > > > > > Preview window never opens.
>
> > > > > > Let me know if you additional details.
>
> > > > > > Rick
>
> > > > > > On Jun 3, 9:40 pm, Bruno Postle  wrote:
> > > > > > > On Wed 03-Jun-2009 at 08:29 -0500, Gerry Patterson wrote:
>
> > > > > > > >What platform are you using?
>
> > > > > > > >So understand, the steps to reproduce this problem are:
>
> > > > > > > >   1. load a project .pto file
> > > > > > > >   2. press the align button on the assistant tab.
>
> > > > > > > Rick is using Windows, but possibly this only appears with a
> > zh_TW
> > > > > > > locale.
>
> > > > > > > --
> > > > > > > Bruno- Hide quoted text -
>
> > > > > - Show quoted text -- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

ok, I found that the 18 image pano above that crashes on open is due
to a corrupt pto file.  When I open it with 0.7.0, it opens with no
errors, but has no photos.  In wordpad, there is no text.  I had
another version of the pto file for that project which opened fine
with 0.7.0.  With SVN3906, it opens fine, it completes the align with
no error, but when the Quick preview window opens, there are no
images.  When I optimize, hugin just hangs with no error. If I close
the quick preview window after align, and then open the regular
preview window it crashes with a boost thread resource error.

I reduced the same project to 12 images, and found that it hung while
doing the align.  I killed the process and reopend the project, and it
opened with the aligned image in the quick preview window, I then
aligned with no error.

Seems like the issues scale with the size of the project and start
causing problems at 12, 70MB 16bit tiffs.

Rick

On Jun 4, 6:01 pm, RueiKe  wrote:
> Quick set of tests before dinner:
>
> 4 image pano - No Crash
> 76 image pano - Crash as before
> 11 image pano - No Crash
> 5 image pano - No Crash
> 18 image pano - Crash while opening pto file (tried twice)
>
> I will collect more details this evening.
>
> Rick
>
> On Jun 4, 10:31 am, RueiKe  wrote:
>
>
>
> > Hi Gerry,
>
> > I have not tried any other projects yet.  After work today (in 8hrs),
> > I will attempt to duplicate the issue with a smaller project.  I have
> > 6 image project readily available that I could work with.  I will also
> > see what the results are for manually running the various steps.
>
> > Regards,
> > Rick
>
> > On Jun 4, 9:04 am, Gerry Patterson  wrote:
>
> > > Hi,
>
> > > I don't have a project that large.  I tired with a few I have that have 8
> > > picts or less, but I am unable to reproduce this problem.
>
> > > I develop under Linux...
>
> > > Does it happen on other projects you have?
> > > Can you reproduce your problem if you try separating out the steps?
> > > (optimize, straighten, photometric optimize..)
>
> > > If you can reproduce it with a smaller project, it may be easier to 
> > > transfer
> > > it around.
>
> > > Best Regards,
>
> > > - Gerry
>
> > > On Wed, Jun 3, 2009 at 9:28 AM, RueiKe  wrote:
>
> > > > Yes, I am using Vista.  I duplicated this issue in Traditional Chinese
> > > > and English, just to be sure it was not a wide character issue.
>
> > > > I loaded a project file from a project I previoulsy complete, 94
> > > > images enfused blended pano. Then press align button.  After the
> > > > "Levelling panorama" step, it starts "Loading Images" and crashes
> > > > about 10 seconds into that after loading a few images.  The Fast
> > > > Preview window never opens.
>
> > > > Let me know if you additional details.
>
> > > > Rick
>
> > > > On Jun 3, 9:40 pm, Bruno Postle  wrote:
> > > > > On Wed 03-Jun-2009 at 08:29 -0500, Gerry Patterson wrote:
>
> > > > > >What platform are you using?
>
> > > > > >So understand, the steps to reproduce this problem are:
>
> > > > > >   1. load a project .pto file
> > > > > >   2. press the align button on the assistant tab.
>
> > > > > Rick is using Windows, but possibly this only appears with a zh_TW
> > > > > locale.
>
> > > > > --
> > > > > Bruno- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

Quick set of tests before dinner:

4 image pano - No Crash
76 image pano - Crash as before
11 image pano - No Crash
5 image pano - No Crash
18 image pano - Crash while opening pto file (tried twice)

I will collect more details this evening.

Rick

On Jun 4, 10:31 am, RueiKe  wrote:
> Hi Gerry,
>
> I have not tried any other projects yet.  After work today (in 8hrs),
> I will attempt to duplicate the issue with a smaller project.  I have
> 6 image project readily available that I could work with.  I will also
> see what the results are for manually running the various steps.
>
> Regards,
> Rick
>
> On Jun 4, 9:04 am, Gerry Patterson  wrote:
>
>
>
> > Hi,
>
> > I don't have a project that large.  I tired with a few I have that have 8
> > picts or less, but I am unable to reproduce this problem.
>
> > I develop under Linux...
>
> > Does it happen on other projects you have?
> > Can you reproduce your problem if you try separating out the steps?
> > (optimize, straighten, photometric optimize..)
>
> > If you can reproduce it with a smaller project, it may be easier to transfer
> > it around.
>
> > Best Regards,
>
> > - Gerry
>
> > On Wed, Jun 3, 2009 at 9:28 AM, RueiKe  wrote:
>
> > > Yes, I am using Vista.  I duplicated this issue in Traditional Chinese
> > > and English, just to be sure it was not a wide character issue.
>
> > > I loaded a project file from a project I previoulsy complete, 94
> > > images enfused blended pano. Then press align button.  After the
> > > "Levelling panorama" step, it starts "Loading Images" and crashes
> > > about 10 seconds into that after loading a few images.  The Fast
> > > Preview window never opens.
>
> > > Let me know if you additional details.
>
> > > Rick
>
> > > On Jun 3, 9:40 pm, Bruno Postle  wrote:
> > > > On Wed 03-Jun-2009 at 08:29 -0500, Gerry Patterson wrote:
>
> > > > >What platform are you using?
>
> > > > >So understand, the steps to reproduce this problem are:
>
> > > > >   1. load a project .pto file
> > > > >   2. press the align button on the assistant tab.
>
> > > > Rick is using Windows, but possibly this only appears with a zh_TW
> > > > locale.
>
> > > > --
> > > > Bruno- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

Hi Gerry,

I have not tried any other projects yet.  After work today (in 8hrs),
I will attempt to duplicate the issue with a smaller project.  I have
6 image project readily available that I could work with.  I will also
see what the results are for manually running the various steps.

Regards,
Rick

On Jun 4, 9:04 am, Gerry Patterson  wrote:
> Hi,
>
> I don't have a project that large.  I tired with a few I have that have 8
> picts or less, but I am unable to reproduce this problem.
>
> I develop under Linux...
>
> Does it happen on other projects you have?
> Can you reproduce your problem if you try separating out the steps?
> (optimize, straighten, photometric optimize..)
>
> If you can reproduce it with a smaller project, it may be easier to transfer
> it around.
>
> Best Regards,
>
> - Gerry
>
>
>
> On Wed, Jun 3, 2009 at 9:28 AM, RueiKe  wrote:
>
> > Yes, I am using Vista.  I duplicated this issue in Traditional Chinese
> > and English, just to be sure it was not a wide character issue.
>
> > I loaded a project file from a project I previoulsy complete, 94
> > images enfused blended pano. Then press align button.  After the
> > "Levelling panorama" step, it starts "Loading Images" and crashes
> > about 10 seconds into that after loading a few images.  The Fast
> > Preview window never opens.
>
> > Let me know if you additional details.
>
> > Rick
>
> > On Jun 3, 9:40 pm, Bruno Postle  wrote:
> > > On Wed 03-Jun-2009 at 08:29 -0500, Gerry Patterson wrote:
>
> > > >What platform are you using?
>
> > > >So understand, the steps to reproduce this problem are:
>
> > > >   1. load a project .pto file
> > > >   2. press the align button on the assistant tab.
>
> > > Rick is using Windows, but possibly this only appears with a zh_TW
> > > locale.
>
> > > --
> > > Bruno- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

Yes, I am using Vista.  I duplicated this issue in Traditional Chinese
and English, just to be sure it was not a wide character issue.

I loaded a project file from a project I previoulsy complete, 94
images enfused blended pano. Then press align button.  After the
"Levelling panorama" step, it starts "Loading Images" and crashes
about 10 seconds into that after loading a few images.  The Fast
Preview window never opens.

Let me know if you additional details.

Rick

On Jun 3, 9:40 pm, Bruno Postle  wrote:
> On Wed 03-Jun-2009 at 08:29 -0500, Gerry Patterson wrote:
>
> >What platform are you using?
>
> >So understand, the steps to reproduce this problem are:
>
> >   1. load a project .pto file
> >   2. press the align button on the assistant tab.
>
> Rick is using Windows, but possibly this only appears with a zh_TW
> locale.
>
> --
> 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@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] Re: OpenGL slow because of reloading

[RueiKe]

I have just tried to load and align a project that I had succesfully
processed using SVN3884.  I found that with SVN3906, I get an
"unhandled exception" after choosing "Align" from the assistant tab,
during the "Loading images..." stage.

On Jun 3, 4:33 pm, Lukáš Jirkovský  wrote:
> 2009/6/3 Gerry Patterson :
>
>
>
>
>
> > Hi All,
>
> > I have checked in a fix for this as of Rev 3908.  I was able to trigger the
> > error by:
>
> > loading project (this project only had 2 images)
> > opening gl preview
> > removing image
> > dragging image
>
> > Once I let go of the left mouse button, it would crash every time.
>
> > Best Regards,
>
> > - Gerry
>
> > 2009/6/2 Lukáš Jirkovský 
>
> >> 2009/6/2 Gerry Patterson :
>
> >> > Hello,
>
> >> > Crash?  My memory is fuzzy, I don't remember a crash.  Is there a bug
> >> > report
> >> > in the tracker on this I can check?
>
> >> > - Gerry
>
> >> > 2009/6/2 Lukáš Jirkovský 
>
> >> >> 2009/6/2 Gerry Patterson :
>
> >> >> > Hi All,
>
> >> >> > I believe I have found the problem.  I have commit-ed a fix as of rev
> >> >> > 3904.
> >> >> > The fast preview would realize it needed to regenerate textures, but
> >> >> > wouldn't store their metadata properly.  So it kept regenerating
> >> >> > again,
> >> >> > and
> >> >> > again
>
> >> >> > Best Regards,
>
> >> >> > - Gerry
>
> >> >> > On Mon, Jun 1, 2009 at 9:13 PM, Gerry Patterson
> >> >> > 
> >> >> > wrote:
>
> >> >> >> Hello,
>
> >> >> >> Just posting my findings...
>
> >> >> >> I believe I am seeing this problem under linux.  If I load a pano
> >> >> >> project
> >> >> >> and open the fast preview window.  There is a slight delay and then
> >> >> >> I
> >> >> >> can
> >> >> >> smoothly move the pano around as excepted.  If I then re-optimize
> >> >> >> the
> >> >> >> pano
> >> >> >> and try to drag around, the performace has dropped considerably.  I
> >> >> >> profiled  and found that vigra::resizeImageNoInterpolation() from
> >> >> >> resizeimage.hxx line 279 is using 88% of cpu time when this is
> >> >> >> happening.
> >> >> >> Profiling the good case shows the same function using 11%.  I am
> >> >> >> sure
> >> >> >> this
> >> >> >> would drop if I ran the program longer.
>
> >> >> >> So...why is vigra::resizeImageNoInterpolation() getting called so
> >> >> >> often
> >> >> >> when dragging the pano  around after re-optimizing?  This is
> >> >> >> something
> >> >> >> to
> >> >> >> look into.  My free time has dropped to zero lately, so it may be a
> >> >> >> while
> >> >> >> before I can look at this futher.   But it may point someone in the
> >> >> >> right
> >> >> >> direction.
>
> >> >> >> Best Regards,
>
> >> >> >> - Gerry
>
> >> >> >> On Mon, Jun 1, 2009 at 6:02 PM, Benjamin Schnieders
> >> >> >>  wrote:
>
> >> >> >>> I first couldn't decide here, but after an evening of
> >> >> >>> waiting-for-preview-to-close, saving panorama and reloading it,
> >> >> >>> just
> >> >> >>> to
> >> >> >>> be able to quickly identify some freak images in between the others
> >> >> >>> and
> >> >> >>> deleting them I vote for fixing this bug as soon as possible, and
> >> >> >>> if
> >> >> >>> needed waiting with the 0.8 release until it is fixed, as it is -
> >> >> >>> in
> >> >> >>> my
> >> >> >>> opinion - pretty simple to reproduce this bug (I can't imagine this
> >> >> >>> won't happen to anyone) by just removing an image while using the
> >> >> >>> preview or re-optimizing while the preview is closed.
>
> >> >> >>> If there might be a fix for this I'll try a recent trunk version by
> >> >> >>> tomorrow... :)
>
> >> >> >>> Benjamin
>
> >> >> I can't see any slowdown now. Only the crash (but It crashed also with
> >> >> the svn 3888). I don't know if this crash is there for a long time or
> >> >> not, because in fact today was the first day I've tried to reproduce
> >> >> the slowdown which after a while causes crash.
>
> >> I'm not sure, I'll take a look into bugtracker. Anyway, debugger gave
> >> me this info:
>
> >> hugin:
> >> /home/lukas/DEBUG/test-build/src/hugin-build/src/hugin_base/panodata/Panora­ma.cpp:1489:
> >> virtual void HuginBase::Panorama::setSrcImage(unsigned int, const
> >> HuginBase::SrcPanoImage&): Assertion `imgNr < state.images.size()'
> >> failed.
>
> >> So it may not be a crash but an assertion error.
>
> >> I don't know what exactly triggers it, but it seems that when I open
> >> the GL preview then remove some image, re-optimize it (It's exactly
> >> the same process as what I needed for reproduce slowdown in GL
> >> preview) then open the preview, select drag and play a bit it aborts.
>
> Wow, that was fast. Thanks a lot, it would take me much more time to
> find where the problem is, because I'm unfamiliar with the preview
> code.
>
> Lukáš- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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 

[hugin-ptx] Re: german translation of tips

[RueiKe]

His latest weekly build is at: http://hugin.huikeshoven.org/


On Jun 2, 7:09 pm, "finbref.2006"  wrote:
> On Jun 1, 3:53 am, RueiKe  wrote:
>
> > You might want to look for the
> > latest build from Ad, as there have been several posted since 3811.
>
> On the 
> websitehttp://adhuikeshoven.pbworks.com/hugin%20installer%20for%20Windows%20...
> the 3811 is the most recent, no? this is the link given 
> athttp://panospace.wordpress.com/downloads/
> perhaps there is a Vista version of 0.8.0 rc2?
> thomas
--~--~-~--~~~---~--~~
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] Re: german translation of tips

[RueiKe]

Hi Thomas,

I am not a speaker of German, but I did notice that SVN 3815 included
an update to the German translation.  You might want to look for the
latest build from Ad, as there have been several posted since 3811.

I have completed the Traditional Chinese translation and hoping to get
some user feedback before the 0.8.0 release.

Regards,
Rick

On Jun 1, 6:35 am, Thomas Steiner  wrote:
> Hi
> I use Version 0.8.0.3811 by Ad Huikeshoven under Vista. Up to my
> knowledge this is the latest windows installer version (although RC1
> appeared later?).
> In the hints of the german version these are some minorities taht
> could be improved perhaps:
>
> "Ein Panorama mit gekrümmtem Horizont kannen durch Hinzufügen von
> vertikalen Kontrollpunkten begradigt werden. Siehe auch 
> unterhttp://hugin.sf.net/tutorials";
> should be:
> "Ein Panorama mit gekrümmtem Horizont kann durch Hinzufügen von
> vertikalen Kontrollpunkten begradigt werden. Siehe dazu 
> auchhttp://hugin.sf.net/tutorials";
>
> "Kontrollpunkte sollten auf unbewegten Objekten gesetzt werden.
> Vermeiden Sie, Kontrollpunkte auf Menschen, Bäumen, Wolken oder
> anderen sich bewegenden oder verformenden Objekten."
> should be:
> "Kontrollpunkte sollten auf unbewegte Objekte gesetzt werden.
> Vermeiden Sie, dass Kontrollpunkte auf Menschen, Bäumen, Wolken oder
> andere sich bewegende oder verformende Objekte gesetzt werden."
>
> "Gimp 2.0 oder höher kann die von Hugin erzeugten TIFF-Dateien mit
> mehreren Ebenen lesen."
> should be:
> "Gimp 2.0 und spätere Versionen können die von Hugin erzeugten
> TIFF-Dateien mit mehreren Ebenen lesen."
>
> And finally the message
> "Willkommen bei Hugin. Um ein Panorama zu erstellen, folgen Sie
> einfach den 3 Schritten auf dem Assistent-Reiter."
> appeared as the "last" hint and not as the first, perhaps this should be 
> fixed?
>
> I enjoy it very much...
> Thomas
--~--~-~--~~~---~--~~
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] Re: OpenGL slow because of reloading

[RueiKe]

My experience with this problem on Windows Vista is that it is bad
enough to degrade the overalll user expereince from 0.7.0.  If it does
get released without fixing it, then there should be an option to use
the old preview as a default, so that the problem can be avoided.

Rick

On May 28, 6:12 am, Bruno Postle  wrote:
> [reviving this thread] I don't see this problem but I'd like to hear
> opinions as to whether this is a critical bug and should block the
> 0.8.0 release?
>
> On Fri 27-Mar-2009 at 06:42 +0100, Seb Perez-D wrote:
>
>
>
> >On Fri, Mar 27, 2009 at 00:50, allard  wrote:
>
> >> Did anybody else notice the OpenGL preview slows down sometimes
> >> because it reloads the images with every change you make? I've been
> >> seeing that off and on since the beta2 mark but it does not happen all
> >> the time. I'm not sure what's going on. At least in this build I was
> >> seeing it in the only test I did so far.
>
> >I have also noticed this (Linux x64). It has happened since the OpenGL
> >preview was added. It renders the OpenGL preview useless; the only
> >solution is to close and restart hugin. However this bug is hard to
> >repeat: it just "happens" after you start optimizing, adding control
> >points, changing the lens settings, etc.- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
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] Re: Windows testers please

[RueiKe]

I have just finished going through my full workflow with SVN3884 in
Traditional Chinese with no problems.  The 2 crashes reported earlier
with align and fine tune all control points are fixed.  In this test,
I have also tried optimize from the edit menu, Celeste, Optimize All
from the Optimizer tab, and optmize exposure with no crashes.  I
successfully stitched a 90 image enfused/blended equirectangular pano!
The only related problem I see is that many of the strings in the
dialog boxes releated to these are still in English.

Rick

On May 23, 4:39 pm, "T. Modes"  wrote:
> > When clicking "Fine tune all points" it still crashing.
>
> It's now also fixed (rev 3876).
>
> Thomas
--~--~-~--~~~---~--~~
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] Re: new hugin installer for Windows Vista/XP

[RueiKe]

Thanks for sharing the weekly Windows builds!  It has been very
useful.

One minor issue I am having is a TIFF library warning.  Here are the
first few lines:
20:18:44: tiff module: TIFFReadDirectory
20:18:44: TIFF library warning.

I mentioned it to Bruno, and he suggested it may be an installer
issue.  After I hit ok, everything seems to work fine.  I don't get
this warning when running 0.7.0.

Rick


On May 20, 3:52 pm, Ad Huikeshoven  wrote:
> Hi,
>
> A new hugin installer for Windows Vista/XP based on SVN 3865 (jump from 3845
> - a lot of work has been done this week) can be found at:
> hugin installer for Windows
> Vista
> .
>
> Dedalus

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