Re: [hugin-ptx] Fused exposures are too light!

On 23 October 2010 04:54, Robert Krawitz wrote: > I'm trying to build panoramas with multiple exposures (-2, 0, +2), but > the results (particularly the sky) are much too pale.  This is with > basically the 2010.3 release (maybe a few commits before, but nothing > in the hg log jumps out at me). >

Re: [hugin-ptx] Re: Terminology

On October 21, 2010 03:06:02 am Bruno Postle wrote: > They are only horizon lines when you are stitching a spherical panorama, > with rectilinear output they can be anywhere in the picture just like > vertical lines. I forgot that not everybody has my habit of stitching equirectangular no matter

Re: [hugin-ptx] Fused exposures are too light!

On Fri, 22 Oct 2010 23:41:19 -0400, Yuval Levy wrote: > > On October 22, 2010 10:54:31 pm Robert Krawitz wrote: >> I'm trying to build panoramas with multiple exposures (-2, 0, +2), but >> the results (particularly the sky) are much too pale. This is with >> basically the 2010.3 release (maybe a f

Re: Nona fail: "caught exception: std::bad_alloc" [Was Re: [hugin-ptx] Help with automated stitching (for scanned images)]

On October 22, 2010 07:09:14 pm Ognjen Bezanov wrote: > And why is the image so large? Each scan is 1578x935 and there are 15 of > them. Assuming they are put end to end (which is not the case, as there > is like 70% overlap between them) we'd get a maximum size of 1578x14025 > This is far less th

Re: [hugin-ptx] Fused exposures are too light!

On October 22, 2010 10:54:31 pm Robert Krawitz wrote: > I'm trying to build panoramas with multiple exposures (-2, 0, +2), but > the results (particularly the sky) are much too pale. This is with > basically the 2010.3 release (maybe a few commits before, but nothing > in the hg log jumps out at m

[hugin-ptx] Fused exposures are too light!

I'm trying to build panoramas with multiple exposures (-2, 0, +2), but the results (particularly the sky) are much too pale. This is with basically the 2010.3 release (maybe a few commits before, but nothing in the hg log jumps out at me). This seems to be happening at the very start; nona is pro

Re: Nona fail: "caught exception: std::bad_alloc" [Was Re: [hugin-ptx] Help with automated stitching (for scanned images)]

On Sat, 2010-10-23 at 00:09 +0100, Ognjen Bezanov wrote: > #>> pano_modify --center --fov=AUTO --canvas=AUTO --crop=AUTO > --projection=0 -o project.pto ./project.pto > > Setting projection to Rectilinear > Center panorama > Fit panorama field of view to best size > Setting field of view to 179 x

Re: Nona fail: "caught exception: std::bad_alloc" [Was Re: [hugin-ptx] Help with automated stitching (for scanned images)]

On 22/10/10 00:17, James Legg wrote: > On Thu, 2010-10-21 at 22:00 +0100, Ognjen Bezanov wrote: >> Never mind, I found out that I had to update hugin to 2010.2.0 in order >> to get it. Now I have a new issue. >> >> after setting projection to rectilinear, nona fails with "caught >> exception: std::

[hugin-ptx] Re: Best control point finder for different lenses in same pano?

On 13 Okt., 21:23, Jan Martin wrote: > HI all, > > I have 8 images around with hfov of 50 degrees  and one fisheye with hfov > with 120 degrees for the Zenith. > So autopano-sift-c 2.5.2 fails, because it assumes all image > - having the same hfov. > - having the same projection. > > Any ideas w

[hugin-ptx] Autopano SIFT-C-2.5.1 downloadsite.

Hello All It is not my own build, but I found on a downloadsite autopano-SIFT-C 2.5.1. Discovered it in a french panotools forum.. It's already there since april 2010. There you can sometimes find new binaries too of Hugin, not mentioned on this

Re: [hugin-ptx] Re: Best control point finder for different lenses in same pano?

Thank you Tom for your testing and feedback. I had the auto control point generators fail also on a past project where I was taking a pano each day setting a tripod in roughly the same place. The cp generators would find matches within a days images but would never find matches from one day

[hugin-ptx] Re: Best control point finder for different lenses in same pano?

I had a whack at one of Jeffrey's examples using PTGui and APSCpp and have to admit that I was unable to find a way to get automatic control points between the fisheye zenith shot and the 8 rectilinear equatorial ones. PTGui does let you assign different lenses to different images (by a rather ha

[hugin-ptx] Re: hugin-mac-2010.3.0-bc9a38b15b66 and PTBatcherGui bundle with new cpfind and makefilelib

On Oct 22, 12:09 pm, Harry van der Wolf wrote: > Hi all, > > I had a reply from a user that he still encounters errors with the message > "External program not found in the bundle, reverting to > system path". This should no longer occur, but for him it does. > Where is one or each of: > icpfi

[hugin-ptx] Re: [OSX] hugin-mac-2010.3.0-bc9a38b15b66 and PTBatcherGui bundle with new cpfind and makefilelib

Hi all, I had a reply from a user that he still encounters errors with the message "External program not found in the bundle, reverting to system path". This should no longer occur, but for him it does. Where is one or each of: icpfind autooptimiser celeste_standalone checkpto cpclean gnumake pa

Re: Nona fail: "caught exception: std::bad_alloc" [Was Re: [hugin-ptx] Help with automated stitching (for scanned images)]

Hi James I also recently had Nona crash with "bad allocation", while trying to reproject a 300 Mpix equirectangular image on a Win32 box with 3 GB RAM using Hugin version 2010-5063. Nona succeeded when I reduced the output dimensions from 23000 x 13000 to 2 x 9600. PTGui had no trouble doing

Re: [hugin-ptx] Re: Windows binaries for Hugin 2010.2.0

Hallo Matthew, Wednesday, October 20, 2010, 1:10:45 AM, you wrote: Matthew> in the process of uploading zip files to SourceForge. While they are Matthew> considerably larger, they should prove to be more reliable. Thanks for your effort, much appreciated. I will have opportunity to download and

Re: [hugin-ptx] Re: Best control point finder for different lenses in same pano?

Is the SURF scale and orientation independent per each identified "feature" or ar they somehow liked within an image? Is distorsion somehow factored in? A thought on unevenly placed CP that often turns out to be a problem for me. Maybe look at what align_image_stack does. It seems to divide th