[hugin-ptx] Re: APSCpp, enhanced Autopano-sift-c fails on 32 bit tif with Displayimage: Unsupported pixel size error

2009-05-30 Thread Ravikanth Samatham
Hi Bruno,

 Thank you for message. I capture images as text file for the same reason,
because image file can not handle floating point data. My research involves
in dealing with quantitative analysis of images. I was trying to load 32 bit
floating point tiff images saved using 'ImageJ' and load them in hugin to
make a panorama. So, my aim is to somehow preserve the 32 bit floating point
values when I save the panorama.

 The image that is being saved has 32 bit floating point numbers in the
pixel. But, none of software can read the 2 channel image that is being
saved. It will great if I can extract the channel with the image data. I
generally do post-processing in matlab. Is it possible to save the final
panorama as a ASCII text file or image (where image is just an array of
numbers).

 I am working on to know more of the inner workings of hugin and panotools.
I appreciate any help.

Have a great weekend,
Ravi.

On Sat, May 30, 2009 at 3:03 AM, Bruno Postle  wrote:

>
> On Fri 29-May-2009 at 15:53 -0700, Ravi wrote:
> >
> > My name is Ravi and I am PhD student. I am using hugin to stitch
> >multiple pictures as part of my project. I work with 32 bit float
> >images. I was able to load the images into hugin and stitch them. I
> >also got similar problem where the panorama is either completely black
> >or completely white. I am sure the procedure as described by Tom in
> >the previous message will work fine, because I have been following
> >similar procedure for a different application. But, I am having with
> >the output. I am saving the images as tiff images but I am can not
> >view the images. I tried to open the image using ImageJ, Matlab and
> >Gimp.
>
> Floating-point image data isn't normally usable by paint programs
> like the Gimp, the image needs to be processed somehow to fit the
> data to the capability of your screen.
>
> So either use a tool like cinepaint that lets you view HDR data
> while editing, or tonemap with a tool like qtpfsgui to create an LDR
> version.
>
> --
> 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: Segfault Ubuntu 9.04

2009-05-30 Thread Yuv

Yuval Levy wrote:
> Bruno Postle wrote:
> > On Tue 19-May-2009 at 07:38 -0700, Yuv wrote:
> >> 3838 works, 3839 segfaults
> >
> > I know Guido says he needs to fix this code, but since you have the
> > hardware that fails, it would be very useful if you can figure-out
> > which bit of this commit causes the segfault.
>
>   holiday. I'll have a look as soon as I can.

good news

rainy day. I had a little time to test the latest trunk. SVN3899 no
longer segfaults

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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread Bruno Postle

On Sat 30-May-2009 at 09:32 -0700, Habi wrote:

>When re-opening old .pto-Files I - only sometimes - get the error
>"Panorama Tools: Unsupported Panorama Format".

I've seen this after experimenting with vig_optimize.  In order to 
use this you need to set photometric parameters on 'v' lines in the 
.pto file, however if you then try to load such a project in hugin, 
libpano13 complains (but the project opens ok anyway).

This is a bug in libpano13, the 'v' variable parser expects single 
character parameters only.

No idea if this is your problem though.

-- 
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread grow

Harry,
I am back again with more bad news.  Sorry!  :-(

I tried the new version again this time with one of the projects that
suffered the "1-pixel Horizontal black line" problem and it still
happened.
There is a small fragment of the file here:
http://hugin-ptx.googlegroups.com/web/1-Pixel_line.jpg?gsc=aBooSgsAAADHF4wKJ-WozJHD5Wi4qwz2
just to illustrate  the point.  This was  a stitch with 27 source
images.  9 shots on a 16mm lens each bracketed by three exposures.
They were TIFF files.  Some of them had small Alpha Channel masks.

I have checked the "...exposure_layer..." files and they DON'T have
the horizontal line.

I am sure I used to have the "...ldr..." files left behind at the end
but they haven't been recently.  So I can't check one of those.

I have:
Blended panorama (enfuse),
Blended Exposure Layers and
Remapped images
all selected is the something else I should also select in order to
have Hugin leave behind the "...LDR..." files?

all the best

George
PS for anyone who is a fan of the comedy TV series "Father Ted" you
might be entertained to know that the VR I was stitching in this case
was of the wrecked ship that is shown in the title  sequence ... the
one  stranded on a rocky beach on "Craggy Island"  I have actually got
a reasonable stitch using the "reduce dimensions by 10%" dodge ... so
I  will post a link when I finally get a make the VR of it made.

On May 30, 8:04 am, cspiel  wrote:
> George -
>
> On May 30, 1:35 am, grow  wrote:
>
> > It is running on my, now infamously problematic, "Village_Hotel"
> > panorama.  I see it is producing a lot more commentary than it used
> > to.
>
>         Probably you run Enblend with a high
> verbosity setting, i.e. lots of "-v" options.
> Without any "-v" you should get only warning or
> error messages and no "info"-class messages.
>
> BTW, the verbosity setting even reaches as far
> as the output of "--version":
>
>     $ ~/projects/enblend-staging-hg/BUILD/src/enblend --version --
> verbose
>     enblend 3.2-staging-rev335
>
>     Extra feature: image cache: no
>     Extra feature: GPU acceleration: no
>     Extra feature: OpenMP: yes - version 2005-5 using 4 processor(s)
> and up to 4 thread(s)
>
>     Supported image formats: BMP EXR GIF HDR JPEG PNG PNM SUN TIFF
> VIFF
>     Supported file extensions: bmp exr gif hdr jpeg jpg pbm pgm png
> pnm ppm ras tif tiff xv
>
>     Copyright (C) 2004-2009 Andrew Mihal.
>     License GPLv2+: GNU GPL version 2 or later  licenses/gpl.html>
>     This is free software: you are free to change and redistribute it.
>     There is NO WARRANTY, to the extent permitted by law.
>
>     Written by Andrew Mihal and others.
>
> As you see, a verbose "--version" tells about
> all extra features that have been compiled into
> a particular Enblend or Enfuse binary and about
> the supported image formats and file extensions.
>
> > It is about a third of the way through at "exposure_layers"  number 8
> > in the "enblending"  of 27 such layers.  So far there are more than
> > 20,000 lines of text in the commentary window 18,000 of which start
> > "enblend: info:".  So we should at least get lots of debugging data!
>
>         Actually, "info"-class messages do not
> carry debug information though they surly could
> aid debugging.  To get debug information compile
> with "-DDEBUG".  Real debug messages start with
> "+"-signs to set them apart from normal output.
>
> Infos tell the user about Enblend's or Enfuse's
> normal actions.  Their cousins, warnings, state
> that the normal execution path has been left,
> but the program is able to take corrective
> measures itself.  Errors, oh well...
>
> > I will go to sleep and let it run ... I'll let you know in the
> > morning ... here is hoping that when I get back here I am NOT
> > delivering a massive debugging data file.
>
>         If the version you are running has
> OpenMP support _and_ you use a multi-processor
> machine, I'd be interested whether you see a
> performance increase compared to older versions.
>
> Best regards,
>         Chris
--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread Harry van der Wolf
I have seen it too and I think I can explain it also.
Lately there were some changes in projection naming in the libpano versions.
I try to keep up with the versions. There were some name changes in the some
projections. This Hugin version uses the new libpano13-2.9.14. The last
build, svn 3855, contained a relatively new libpano but one just before
these name changes (and not the rc1 version).
So, all pto's are correct and Hugin has no problem with it, it's just the
projection that's  not recognised.

If someone thinks I'm incorrect, please mention it.

Harry



2009/5/30 Habi 

>
> Hey again
>
> On 30.05.2009, at 18:19, Habi wrote:
> >
> > Hoi Harry (et al.)
> >
> > On May 29, 11:11 pm, Harry van der Wolf  wrote:
> >> Hi Mac users,
> >>
> >> I just published a hugin 0.8.0 svn 3888 bundle
> > [snip]
> >> Hoi,
> >> Harry
> >
> > I've just stitched several panoramas, one with 59 images in total and
> > it worked just fine [1,2].
> > I don't have a complicated test-case like George, so I can just
> > comment one small thing. I've started the above panorama with your
> > hugin-version released before this one and when I opened the .pto-File
> > I got a Error claiming that "The panorama file is not compatible with
> > this version of hugin" (or something similar, I didn't take a
> > screenshot). Weirdly, once I clicked this window away, hugin loaded
> > all the images without another complaint and stitched it just fine. I
> > cannot reproduce this window with any other .pto-File and it also
> > didn't show up again, so I think it's not really worth a bug-report,
> > maybe just a heads-up...
> > have a nice weekend and thanks for your work!
> > habi
>
> I was a tad too fast with sending this mail, I should have tested
> that
> little problem a bit more.
> When re-opening old .pto-Files I - only sometimes - get the error
> "Panorama Tools: Unsupported Panorama Format".
> The only thing that I can see in Console.app that seem to be of
> relevance is this Console Message:
> ---
> 30.05.09 18:23:28 [0x0-0x1f81f8].net.sourceforge.hugin.Hugin[7907]
> MainFrame::RestoreLayoutOnNextResize()
> ---
> I've never seen this before, so I suppose it's something that newly
> introduced in version 0.8.0 svn 3888.
> Hope that helps a bit.
> Habi
> >
>

--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread Habi

Hey again

On 30.05.2009, at 18:19, Habi wrote:
>
> Hoi Harry (et al.)
>
> On May 29, 11:11 pm, Harry van der Wolf  wrote:
>> Hi Mac users,
>>
>> I just published a hugin 0.8.0 svn 3888 bundle
> [snip]
>> Hoi,
>> Harry
>
> I've just stitched several panoramas, one with 59 images in total and
> it worked just fine [1,2].
> I don't have a complicated test-case like George, so I can just
> comment one small thing. I've started the above panorama with your
> hugin-version released before this one and when I opened the .pto-File
> I got a Error claiming that "The panorama file is not compatible with
> this version of hugin" (or something similar, I didn't take a
> screenshot). Weirdly, once I clicked this window away, hugin loaded
> all the images without another complaint and stitched it just fine. I
> cannot reproduce this window with any other .pto-File and it also
> didn't show up again, so I think it's not really worth a bug-report,
> maybe just a heads-up...
> have a nice weekend and thanks for your work!
> habi

I was a tad too fast with sending this mail, I should have tested
that
little problem a bit more.
When re-opening old .pto-Files I - only sometimes - get the error
"Panorama Tools: Unsupported Panorama Format".
The only thing that I can see in Console.app that seem to be of
relevance is this Console Message:
---
30.05.09 18:23:28 [0x0-0x1f81f8].net.sourceforge.hugin.Hugin[7907]
MainFrame::RestoreLayoutOnNextResize()
---
I've never seen this before, so I suppose it's something that newly
introduced in version 0.8.0 svn 3888.
Hope that helps a bit.
Habi
--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread David Haberthür
Hey again

On 30.05.2009, at 18:19, Habi wrote:
>
> Hoi Harry (et al.)
>
> On May 29, 11:11 pm, Harry van der Wolf  wrote:
>> Hi Mac users,
>>
>> I just published a hugin 0.8.0 svn 3888 bundle
> [snip]
>> Hoi,
>> Harry
>
> I've just stitched several panoramas, one with 59 images in total and
> it worked just fine [1,2].
> I don't have a complicated test-case like George, so I can just
> comment one small thing. I've started the above panorama with your
> hugin-version released before this one and when I opened the .pto-File
> I got a Error claiming that "The panorama file is not compatible with
> this version of hugin" (or something similar, I didn't take a
> screenshot). Weirdly, once I clicked this window away, hugin loaded
> all the images without another complaint and stitched it just fine. I
> cannot reproduce this window with any other .pto-File and it also
> didn't show up again, so I think it's not really worth a bug-report,
> maybe just a heads-up...
> have a nice weekend and thanks for your work!
> habi

I was a tad too fast with sending this mail, I should have tested that  
little problem a bit more.
When re-opening old .pto-Files I - only sometimes - get the error  
"Panorama Tools: Unsupported Panorama Format" (see attached screenshot).
The only thing that I can see in Console.app that seem to be of  
relevance is this Console Message:
---
30.05.09 18:23:28 [0x0-0x1f81f8].net.sourceforge.hugin.Hugin[7907]  
MainFrame::RestoreLayoutOnNextResize()
---
I've never seen this before, so I suppose it's something that newly  
introduced in version 0.8.0 svn 3888.
Hope that helps a bit.
Habi

  
--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread Habi

Hey again

On 30.05.2009, at 18:19, Habi wrote:
>
> Hoi Harry (et al.)
>
> On May 29, 11:11 pm, Harry van der Wolf  wrote:
>> Hi Mac users,
>>
>> I just published a hugin 0.8.0 svn 3888 bundle
> [snip]
>> Hoi,
>> Harry
>
> I've just stitched several panoramas, one with 59 images in total and
> it worked just fine [1,2].
> I don't have a complicated test-case like George, so I can just
> comment one small thing. I've started the above panorama with your
> hugin-version released before this one and when I opened the .pto-File
> I got a Error claiming that "The panorama file is not compatible with
> this version of hugin" (or something similar, I didn't take a
> screenshot). Weirdly, once I clicked this window away, hugin loaded
> all the images without another complaint and stitched it just fine. I
> cannot reproduce this window with any other .pto-File and it also
> didn't show up again, so I think it's not really worth a bug-report,
> maybe just a heads-up...
> have a nice weekend and thanks for your work!
> habi

I was a tad too fast with sending this mail, I should have tested
that
little problem a bit more.
When re-opening old .pto-Files I - only sometimes - get the error
"Panorama Tools: Unsupported Panorama Format".
The only thing that I can see in Console.app that seem to be of
relevance is this Console Message:
---
30.05.09 18:23:28 [0x0-0x1f81f8].net.sourceforge.hugin.Hugin[7907]
MainFrame::RestoreLayoutOnNextResize()
---
I've never seen this before, so I suppose it's something that newly
introduced in version 0.8.0 svn 3888.
Hope that helps a bit.
Habi
--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread Habi

Hoi Harry (et al.)

On May 29, 11:11 pm, Harry van der Wolf  wrote:
> Hi Mac users,
>
> I just published a hugin 0.8.0 svn 3888 bundle
[snip]
> Hoi,
> Harry

I've just stitched several panoramas, one with 59 images in total and
it worked just fine [1,2].
I don't have a complicated test-case like George, so I can just
comment one small thing. I've started the above panorama with your
hugin-version released before this one and when I opened the .pto-File
I got a Error claiming that "The panorama file is not compatible with
this version of hugin" (or something similar, I didn't take a
screenshot). Weirdly, once I clicked this window away, hugin loaded
all the images without another complaint and stitched it just fine. I
cannot reproduce this window with any other .pto-File and it also
didn't show up again, so I think it's not really worth a bug-report,
maybe just a heads-up...
have a nice weekend and thanks for your work!
habi

[1]: http://www.flickr.com/photos/habi/3577575849/
[2]: http://www.flickr.com/photos/habi/3577574019/
--~--~-~--~~~---~--~~
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: Fusing before or after

2009-05-30 Thread Habi

Hello all.

On May 23, 2:50 am, DaveN  wrote:
> I don't know if this has been asked before (hard question to ask in a
> search) but why don't people fuse their images before making
> panoramas?  By that I mean the software for making panoramas (the
> hugin clone ptgui and autopano pro) seem to remap all the images to
> create differently exposed panoramas and then blend the panoramas.
> Wouldn't it be more efficient to exposure fuse the images and then
> make the panorama?

I'm very late to this thread, but I'm catching up.
I was wondering if I've been doing it entirely wrong "all the time".
All the time means that I havent made that many fused panoramas.
With my main example of the entrance to the train station in Bern [1]
i remember that I just dumped all the 87 images (29 photos for each
exposure step) into hugin and stitched a fused image in one single
output. It took a long time for Pan-O-Matic to find the control points
but in the end I got a quite impressive result.

So I'm asking: would I get another result if I'd have generated three
panoramas, one for each exposure step and then enfuse them to one
final panorama?

Greetings from Switzerland
Habi

[1]: http://www.flickr.com/photos/habi/sets/72157614221776963/
--~--~-~--~~~---~--~~
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: APSCpp, enhanced Autopano-sift-c fails on 32 bit tif with Displayimage: Unsupported pixel size error

2009-05-30 Thread Bruno Postle

On Fri 29-May-2009 at 15:53 -0700, Ravi wrote:
>
> My name is Ravi and I am PhD student. I am using hugin to stitch
>multiple pictures as part of my project. I work with 32 bit float
>images. I was able to load the images into hugin and stitch them. I
>also got similar problem where the panorama is either completely black
>or completely white. I am sure the procedure as described by Tom in
>the previous message will work fine, because I have been following
>similar procedure for a different application. But, I am having with
>the output. I am saving the images as tiff images but I am can not
>view the images. I tried to open the image using ImageJ, Matlab and
>Gimp.

Floating-point image data isn't normally usable by paint programs 
like the Gimp, the image needs to be processed somehow to fit the 
data to the capability of your screen.

So either use a tool like cinepaint that lets you view HDR data 
while editing, or tonemap with a tool like qtpfsgui to create an LDR 
version.

-- 
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread grow

Harry, Chris,

Sadly it crashed ... it looks like the usual reason.

You were right about the "verbose" mode I had the settings in the
project file set to  v v v verbose from the earlier testing.   Below I
have appended the first and last few hundred lines.

I have made a zipped file of the whole log that I will email to Harry
separately.  It is a Mac Text file.

all the best

George

Checking nona...[OK]
Checking enblend...[OK]
Checking enfuse...[OK]
Checking hugin_hdrmerge...[OK]
Checking exiftool...[OK]
Checking rm...[FAIL]
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
0 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
1 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
2 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
3 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
4 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
5 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
6 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
7 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
8 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
9 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
10 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
11 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
12 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
13 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
14 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
15 /private/var/tmp/folders.501/TemporaryItems/huginpto_Y3QkZl
/Applications/QuicktimeTools/Hugin/Hugin_0_8.0_RC1_3888/Hugin.app/
Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z
PACKBITS -r ldr -e 0 -m TIFF_m -o Village_Hotel_38_exposure_layers_ -i
16 /private/var/

[hugin-ptx] Re: Fusing before or after

2009-05-30 Thread Pablo d'Angelo

Hi all,

This description is correct. Note that align_image_stack was really 
written more like a proof of concept and is not really well optimized. 
Actually, the implementation of the normalized cross correlation in 
hugin is very basic and thus quite slow. Replacing it with a properly 
optimized version (I believe opencv has a nicely optimized correlator) 
would make both align_image_stack and the fine tune functionality much 
faster.

ciao
   Pablo

Bruno Postle wrote
> On Thu 28-May-2009 at 07:52 -0700, Tom Sharpless wrote:
>> So align_image_stack does use local correlations, then generates CP's
>> as a way of communicating the required alignment to other tools?
> 
> It generates control points because it uses the hugin optimiser to 
> do the alignment (which is also why it accepts projection and field 
> of view parameters).
> 
>> Is this done in such a way as to allow some warping as well as simple
>> shifting in the final alignment step?
> 
> The alignment uses the usual roll, pitch, yaw and fov distortion.
> 
>> That is, are the CP's based only or mainly on local shifts?
> 
> No idea, the image is divided up into a grid and a feature detector 
> tries to place an even distribution of points over the image area.
> 
> In practice, with the -p option it behaves like a control point 
> generator that only works with stacked photos, but which produces 
> very few 'bad' points and which works very well with large exposure 
> differences.
> 


--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread Harry van der Wolf
All,

George is running the new Hugin OSX svn3888 build which comes with
Christoph's enblend and enfuse version 336 [1]

2009/5/30 cspiel 

>
> George -
>
> On May 30, 1:35 am, grow  wrote:
> > It is running on my, now infamously problematic, "Village_Hotel"
> > panorama.  I see it is producing a lot more commentary than it used
> > to.
>
> Probably you run Enblend with a high
> verbosity setting, i.e. lots of "-v" options.
> Without any "-v" you should get only warning or
> error messages and no "info"-class messages.
>

@George,

Please check your Hugin Preferences on the enblend tab in the parameter
field: Do you have one (or multiple) parameter(s) "-v"  or "--verbose"
there? If so, and you want to get rid of all the messages, remove that
parameter.


>
> > I will go to sleep and let it run ... I'll let you know in the
> > morning ... here is hoping that when I get back here I am NOT
> > delivering a massive debugging data file.
>
> If the version you are running has
> OpenMP support _and_ you use a multi-processor
> machine, I'd be interested whether you see a
> performance increase compared to older versions.
>
>
> Best regards,
>Chris
>


The enblend 336 version inside the Hugin svn3888 bundle comes without OpenMP
support and therefore can't use multiple cores on a multi-core machine. I'm
still googling whether it is possible to use this on OSX or not. At least
the make macro does not find it on my OSX system (and as I'm the builder
others get what I create ;-)  )

As for GCC: I still use the default gcc4.1 on Leopard. I could compile with
4.2, but not with 4.3 (AFAIK). For 4.3 I have to completely re-install,
re-configure, etc my build environment with the possibility that I can no
longer use XCode (as that's 4.1 and 4.2 based). I like a little adventure,
but I'm not that adventurous.

Harry


[1]: https://code.launchpad.net/~cspiel/enblend/staging

--~--~-~--~~~---~--~~
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-mac-0.8.0-svn3888_20090529 released

2009-05-30 Thread cspiel

George -

On May 30, 1:35 am, grow  wrote:
> It is running on my, now infamously problematic, "Village_Hotel"
> panorama.  I see it is producing a lot more commentary than it used
> to.

Probably you run Enblend with a high
verbosity setting, i.e. lots of "-v" options.
Without any "-v" you should get only warning or
error messages and no "info"-class messages.

BTW, the verbosity setting even reaches as far
as the output of "--version":

$ ~/projects/enblend-staging-hg/BUILD/src/enblend --version --
verbose
enblend 3.2-staging-rev335

Extra feature: image cache: no
Extra feature: GPU acceleration: no
Extra feature: OpenMP: yes - version 2005-5 using 4 processor(s)
and up to 4 thread(s)

Supported image formats: BMP EXR GIF HDR JPEG PNG PNM SUN TIFF
VIFF
Supported file extensions: bmp exr gif hdr jpeg jpg pbm pgm png
pnm ppm ras tif tiff xv

Copyright (C) 2004-2009 Andrew Mihal.
License GPLv2+: GNU GPL version 2 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Andrew Mihal and others.

As you see, a verbose "--version" tells about
all extra features that have been compiled into
a particular Enblend or Enfuse binary and about
the supported image formats and file extensions.


> It is about a third of the way through at "exposure_layers"  number 8
> in the "enblending"  of 27 such layers.  So far there are more than
> 20,000 lines of text in the commentary window 18,000 of which start
> "enblend: info:".  So we should at least get lots of debugging data!

Actually, "info"-class messages do not
carry debug information though they surly could
aid debugging.  To get debug information compile
with "-DDEBUG".  Real debug messages start with
"+"-signs to set them apart from normal output.

Infos tell the user about Enblend's or Enfuse's
normal actions.  Their cousins, warnings, state
that the normal execution path has been left,
but the program is able to take corrective
measures itself.  Errors, oh well...


> I will go to sleep and let it run ... I'll let you know in the
> morning ... here is hoping that when I get back here I am NOT
> delivering a massive debugging data file.

If the version you are running has
OpenMP support _and_ you use a multi-processor
machine, I'd be interested whether you see a
performance increase compared to older versions.


Best regards,
Chris

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