headers
Peter Suetterlin | 1 Aug 2007 15:56
Picon

Re: patch for enblend 3.0 and HDR images


  Hi Pablo,

> I have uploaded my (experimental) improved version of enblend (both source 
> and win32 binaries).
> 
> sourcecode: http://hugin.sf.net/snapshots/enblend-3.0_hdr.tar.gz

I tried compiling it, and configure did not show any problems, however
compile fails in vigra_impex:  it is missing exr.hxx.  I copied a
file with that name from the hugin src, and it continued compiling
(are those two files supposed to be the same?).  However, linking fails:

enblend-enblend.o: In function `enblend::GDAConfiguration<vigra::CachedFileImage<unsigned
char>, vigra::CachedFileImage<vigra::RGBValue<unsigned char, 0u, 1u, 2u> > >::calculateStateProbabilitiesGPU()':
/usr/src/Apps/enblend-3.0/src/anneal.h:512: undefined reference to `gpuGDAKernel(unsigned int,
unsigned int, double, float*, float*, float*)'
enblend-enblend.o: In function `enblend::GDAConfiguration<vigra::CachedFileImage<unsigned
char>, vigra::CachedFileImage<vigra::RGBValue<unsigned char, 0u, 1u, 2u> > >::run()':
/usr/src/Apps/enblend-3.0/src/anneal.h:311: undefined reference to `clearGPUTextures()'

Any clues?

  Pit

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic
software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx <at> googlegroups.com
(Continue reading)

Permalink | Reply | 3 comments |
headers
Klaus Foehl | 1 Aug 2007 17:08
Picon
Picon

Re: Testing svn20070709 snapshot on Mac


Hi Pablo,

On Tue, 31 Jul 2007, Pablo d'Angelo wrote:

>> www.foehl.net/falkirkwheel_investigate.tar ball.

> I haven't been able to spot any grey rims, not in your images
> (no tiff files included in you tar)

The tiffs are gzipped.

>nor in the output tif I created myself. Where do I need to look for them?

There is no rim in the hugin output tiffs, but in the enblend output
2nd left there is some darkening at the top rim.
That's enblend for Mac, 3.0 (pre-included in Ippei's package?
although I had downloaded enblend 3.0 for Mac seperately before).

>> Then you see that the original material has only 10-20% overlap.
>> I found that the optimisation process is unstable here,
>
> Yes, ideally there should be somewhere close to 50% overlap in at least one 
> pair. However, I have noticed that it often works fine with less overlap too. 
> I should reduce the vignetting correction polynomial to a simple
> r^2 one in this case. This will be more stable.

With the lense these photos were taken I found that 1-0.2*r^4 was
a reasonably good description. Optimising one class of parameters
at a time did the trick for me here. That's good enough a workaround.
(Continue reading)

Permalink | Reply | 1 comment |
headers
dkloi | 1 Aug 2007 17:27

Re: patch for enblend 3.0 and HDR images


Re: Experimental Enblend 3.0 version
>   - BigTIFF support (tif bigger than 2/4 GB), using libtiff 4 alpha
>     (not tested)

I tried stitching a large pano which previously appeared to work with
the official version of Enblend 3.0 (though I haven't been able to
open the
resultant 3.6GB TIFF in any program so I don't know whether it worked
properly or not). With the patched version, I get an error a while
into
the stitch:
"enblend: out of memory
St9bad_alloc"

This is under Win XP x64 SP2, 8GB RAM, Dual Xeon 5150, lots
of HDD space. I'm calling Enblend directly from the command line
after Hugin 0.7b4 has created the remapped files (though Enblend
also fails when called from Hugin). Pano consists of 95 6MP
16bit/channel source images, 43267 x 11263 pixels. I used
the -v -a options. I'll try without -a to see if it works. Smaller
versions of the pano (30k wide, 1.7GB) stitch properly with the
official
Enblend and can be opened by PS CS3.

Cheers,
Daniel.

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

Permalink | Reply | 3 comments |
headers
Pablo d'Angelo | 1 Aug 2007 18:03
Picon

Re: patch for enblend 3.0 and HDR images


dkloi wrote:
 > Re: Experimental Enblend 3.0 version
 >>   - BigTIFF support (tif bigger than 2/4 GB), using libtiff 4 alpha
 >>     (not tested)

Note that bigtiff is not compatible with tif, so the programs need to be 
updated in order to read BigTIFF. For example, it won't work in Photoshop.

 > I tried stitching a large pano which previously appeared to work with
 > the official version of Enblend 3.0 (though I haven't been able to
 > open the
 > resultant 3.6GB TIFF in any program so I don't know whether it worked
 > properly or not). With the patched version, I get an error a while
 > into
 > the stitch:
 > "enblend: out of memory
 > St9bad_alloc"

Strange. This means out of RAM. Unfortunately, it is not a 64 bit 
application yet, so it cant take advantage of your 8 GB directly.
I don't have access to a 64 bit compiler for windows, so I can't provide a 
suitable binary.

Can you copy the command line (with all arguments) and the output until it 
crashed? By default enblend should only use 1GB of RAM.

I have compiled the binary using gcc (mingw), while the official binary is 
compiled using Microsoft Visual Studio. Maybe that also makes a difference?
I haven't touched any memory related code, so I don't really know why it
(Continue reading)

Permalink | Reply | 2 comments |
headers
dkloi | 1 Aug 2007 19:49

Re: patch for enblend 3.0 and HDR images


>  >>   - BigTIFF support (tif bigger than 2/4 GB), using libtiff 4 alpha
>  >>     (not tested)
> Note that bigtiff is not compatible with tif, so the programs need to be
> updated in order to read BigTIFF. For example, it won't work in Photoshop.

Bummer. I'm really up against the wall with this large pano.

> Can you copy the command line (with all arguments) and the output until it
> crashed? By default enblend should only use 1GB of RAM.

The command line was:
E:\Photos\LochMaree>c:\Photos\hugin-0.7_beta4_windows\enblend-3.0_hdr
\enblend.exe -v -a -o LochMareeBigF.tif LochMareeBig00*.tif

I was only able to capture the last couple of screenfuls of output:

----Begin Included Text----
3606
Input image "LochMareeBig0034.tif" RGB ICC UINT16 position=33652x4086
size=2644x
3366
Input image "LochMareeBig0035.tif" RGB ICC UINT16 position=34854x4086
size=2404x
3606
Input image "LochMareeBig0036.tif" RGB ICC UINT16 position=35815x4086
size=2404x
3606
Input image "LochMareeBig0037.tif" RGB ICC UINT16 position=36777x4086
size=2404x
(Continue reading)

Permalink | Reply | 1 comment |
headers
DanielG | 2 Aug 2007 10:54
Picon

Compile on Windows


Hi

I would like to compile my own Hugin on windows. Can I use Visual
Studio Express tool to compile (and witch one) or do I need the real
thing?

I would also like to ask witch type of wxWidgets i need to compile on
windows

hope your answers will get me going.
Thanks
Daníel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic
software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
jens.birch | 2 Aug 2007 15:08
Picon

Re: [Hugin] How to treat a PC-lens?


By comminications with BrunoI, which became private by my mistake, I
finally came to a solution regarding how to treat a PC lens.

I'll recap our mails here for completeness in case someone is
searching the list for a similar project:

I wrote:
>>>
>>> However, as my images are already rectilinear and distortion free, I
>>> would like to stitch them without applying any particular projection -
>>> just use as small transformations as possible to make them fit the
>>> control points. All projections in Hugin apply severe distortions and
>>> the rectilinear projection, which is of interest for me, stretches the
>>> flanks a lot which causes a strong blurring of the final panorama. I
>>> don't need that stretching so how can I avoid it?

then Bruno wrote:
>>Your input images are 'rectilinear' projection, if you set the
>>output projection to rectilinear then you will get exactly the same
>>image out as you put in.  So there shouldn't be a downside to
>>treating the images as photos and letting hugin optimise out minor
>>perspective errors and barrel distortion.
>>
>>If your pictures _really_ don't have any lens or perspective
>>distortion then you can treat the whole process as if you were
>>stitching two halves of a scanned poster:
>>
>>http://hugin.sourceforge.net/tutorials/scans/
>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jim Watters | 2 Aug 2007 15:24
Picon
Favicon

Re: Compile on Windows


Daniel,
There is some information here using VS Express for panotools.
http://wiki.panotools.org/Build_pano12_from_sourcecode_MSVC
You should be able to use this to compile Hugin too.
The VS Express version lacks a resource editor, but can still compile
resources.  It lacks a few other things that should not effect compiling
Hugin, but I have not tried so can not be sure.

Jim

DanielG wrote:
> Hi
>
> I would like to compile my own Hugin on windows. Can I use Visual
> Studio Express tool to compile (and witch one) or do I need the real
> thing?
>
> I would also like to ask witch type of wxWidgets i need to compile on
> windows
>
> hope your answers will get me going.
> Thanks
> Daníel
>   

--

-- 
Jim Watters

jwatters  <at>  photocreations . ca
(Continue reading)

Permalink | Reply | 0 comments |
headers
Klaus | 2 Aug 2007 16:13
Picon
Picon

Re: How to treat a PC-lens?


Hello Jens,

> The only problem I encountered was that the Hugin preview
> showed the composite image rotated and non-centered with
> an output image in the form of a skewed polygon. That was easy enough
> to tweak by left and right clicking in the preview window.

You may want to consider to place a few (2,3,4) horizontal/vertical
control lines
(hugin tries to position them that they appear horizontal/vertical on
the display
in the chosen output projection) and then optimise with some of the
non-top
choices in the optimisation pull-down menu. This can be even more
accurate
than clicking around in the preview window.

Regards

Klaus

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

Permalink | Reply | 0 comments |
headers
dkloi | 2 Aug 2007 17:28

Re: patch for enblend 3.0 and HDR images


I tried stitching without the -a switch and it seemed to complete,
producing a 2.47GB file (instead of a 3.6GB file which the unpatched
version produced). I still can't open this file in PS CS3.

Cheers,
Daniel.

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

Gmane