[hugin-ptx] libpano with Mercurial

I use Mercurial infrequently. I just grabbed the tip of libpano but noticed that there is a branch "libpano 13-2.9.18" that is not merged into the default branch. http://panotools.hg.sourceforge.net/hgweb/panotools/libpano/graph Reviewing the changes, I see that the same one have been added t

Re: [hugin-ptx] Re: "linefind.exe has stopped working"

My experience is that linefind doesn't work on 16-bit images. On 11/12/2012 10:24 AM, alouest wrote: Well I had the same problem on 16 bits tiff, I ended up using cpfind in command line and the problem is solve give it a try! Le lundi 12 novembre 2012 07:47:26 UTC-9, agb a écrit : Hi!

[hugin-ptx] Re: "linefind.exe has stopped working"

Well I had the same problem on 16 bits tiff, I ended up using cpfind in command line and the problem is solve give it a try! Le lundi 12 novembre 2012 07:47:26 UTC-9, agb a écrit : > > Hi! > > I'm using Hugin.2012.0.0 on Windows 7 64bits to stich a long panorama of > 33 16bit tifs. > I'm using t

Re: [hugin-ptx] Re: Hugin 2012.0.0 released

Thanks. Updated. The hugin website has a delayed update mechanism but the correct page should be visible somewhere this evening after 21:00 CET. Harry 2012/11/12 zarl > First of all thanks to everybody for their energy! > > I just started the German version of the 2012.0.0 release notes and > n

[hugin-ptx] Re: Hugin 2012.0.0 released

First of all thanks to everybody for their energy! I just started the German version of the 2012.0.0 release notes and noticed a minor glitch: the title tag of incorrectly says "Hugin-2011.4.0 release notes". Cheers, Carl On Monday, No

Re: [hugin-ptx] Stitching without control points

Yes, that is how Charlie said. Imagine a panorama with 12.000 pixels wide - a common one. Each pixel is 0.03 degrees. On the other side, if you make a 1 degree mistake when shooting it will mean a 33 pixel error, which, in my opinion, is not acceptable. Cheers, Carlos E G Carvalho (Cartola) http

Re: [hugin-ptx] Stitching without control points

Yes, you can. Technically. However, you'll need extreme accuracy in all that mechanical data. It's not impossible to get that kind of mechanical accuracy but it is very hard and probably harder than you think. I shoot with a fisheye on a pano head and still require control points and fine tuning to

[hugin-ptx] Stitching without control points

Would I be right in assuming that if you provide HUGIN with a set of fisheye images where you know the precise yaw, pitch, tilt, fov, focal length of each lens and the a, b, c, d, e individual lens parameters - you can in fact process those images without requiring control points? AB -- You r

Re: [hugin-ptx] Re: "linefind.exe has stopped working" error

Hi! This thread is from a while ago but I also have the "linefind.exe has stopped working" error. Did you ever find a workaround? On Wednesday, June 20, 2012 6:27:33 AM UTC+2, nick wrote: > > >> > In my previous post I linked to a large 250 mb set of files. Here is a >> > link to just 1.5 mb of

[hugin-ptx] "linefind.exe has stopped working"

Hi! I'm using Hugin.2012.0.0 on Windows 7 64bits to stich a long panorama of 33 16bit tifs. I'm using the fix at https://groups.google.com/forum/?fromgroups#!msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4Jand control points are found. I get the error "linefind.exe has stopped working" and so far I did

Re: [hugin-ptx] Use of Hugin in remote sensing

Enblend gave me the redundant error because I didn't have any value for yaw pitch and roll, if i run the optimizer it's ok. Now I just have to apply that to my 5000 pictures and cross my fingers, thanks a lot for your help! Le dimanche 11 novembre 2012 14:39:36 UTC-9, JohnPW a écrit : > > I'd be