[hugin-ptx] hugin 0.80 beta for windows
Where can I get pre-compiled version of hugin 0.8 for windows xp. --~--~-~--~~~---~--~~ 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: fov computation from exifless data
alf wrote: No. I didn't even run the optimization process. The fov I'm referring to was computed in the file dialog after loading the images. You can verify this by simply creating an image of size 2272 x 1704 without exif data (simply save in PPM format for example) and upon loading it give it a focal length of 35 mm and a crop factor of 1. Hugin automatically fills the fov entry box with 52.62 degrees. Heh. Perhaps that's just a hard coded default, and you're gettin' lucky. Pixel count and focal length is NOT enough information to calculate a FOV. Can anyone be bothered to check the source to end this question? BugBear --~--~-~--~~~---~--~~ 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: fov computation from exifless data
Can anyone be bothered to check the source to end this question? As I mentioned earlier: calculation is done in the SrcPanoImage::calcHFOV(...) function, see http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/src/hugin_base/panodata/SrcPanoImage.cpp?view=markup. It takes 4 parameters: - type of projection (e.g., rectangular) - focal length - crop factor - image size These parameters are exactly what is needed to compute the hfov. Check the source to see how it's done. Best, Bart --~--~-~--~~~---~--~~ 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.80 beta for windows
Where can I get pre-compiled version of hugin 0.8 for windows xp. If you had bothered to try the search function using hugin 0.8 beta as keywords (even without the quotes) [1], you'd have found the answer in the very first post of the very first search result [2]. But okay, to answer your question: go to http://panospace.wordpress.com/downloads/ to find the installers. [1] http://groups.google.com/group/hugin-ptx/search?group=hugin-ptxq=hugin+0.8+beta [2] http://groups.google.com/group/hugin-ptx/browse_thread/thread/4db69067e6ac15ea/081e1645bfffea28?lnk=gstq=hugin+0.8+beta#081e1645bfffea28 --~--~-~--~~~---~--~~ 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: fov computation from exifless data
As I pointed out earlier in this thread it actually works with my scans from rectilinear images shot with 12 and 15 mm wide angle lenses. Also a nice starting value for fov is computed for scans from a 43 mm lens shot with a Mamiya 7II using 120/220 film rolls. Pixel count (x and y) gives you the correct aspect ratio. hugin doesn't need EXIF data or some link to my paperpen Book of EXIF to guess the pixel count. Hint: also Apple's OS X Finder is smart enough to instantly show the pixel count... (see http://en.wikipedia.org/wiki/Finder_(software)) alf also manually provided hugin with lens data: - focal length: 35 mm - crop factor: 1x I can see no magic here, sorry. Carl paul womack wrote: alf wrote: No. I didn't even run the optimization process. The fov I'm referring to was computed in the file dialog after loading the images. You can verify this by simply creating an image of size 2272 x 1704 without exif data (simply save in PPM format for example) and upon loading it give it a focal length of 35 mm and a crop factor of 1. Hugin automatically fills the fov entry box with 52.62 degrees. Heh. Perhaps that's just a hard coded default, and you're gettin' lucky. Pixel count and focal length is NOT enough information to calculate a FOV. Can anyone be bothered to check the source to end this question? BugBear --~--~-~--~~~---~--~~ 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.80 beta for windows
Emad ud din Butt wrote: Where can I get pre-compiled version of hugin 0.8 for windows xp. I usually link them from http://panospace.wordpress.com/ 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: fov computation from exifless data
paul womack wrote: Pixel count and focal length is NOT enough information to calculate a FOV. I think what would be missing to the above information is pixel pitch or another relationship of the pixel dimensions to the sensor dimensions. sensor size would give a good enough approximation. 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: fov computation from exifless data
Yuval Levy wrote: paul womack wrote: Pixel count and focal length is NOT enough information to calculate a FOV. I think what would be missing to the above information is pixel pitch or another relationship of the pixel dimensions to the sensor dimensions. sensor size would give a good enough approximation. Correct me if I'm wrong, but I believe that's what the crop factor is for. It serves as a factor between the sensor size and 36x24mm film, like this: [diagonal of sensor] x [crop factor] = [diagonal of 36x24mm film] --~--~-~--~~~---~--~~ 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: fov computation from exifless data
On 14 apr, 18:37, Yuval Levy goo...@levy.ch wrote: Bart.van.Andel wrote: Correct me if I'm wrong, but I believe that's what the crop factor is for. It serves as a factor between the sensor size and 36x24mm film, like this: [diagonal of sensor] x [crop factor] = [diagonal of 36x24mm film] you're right - crop factor is another approximation of size relative to 36x24. If the form factor is the same, it works. Else it is an approximation. What do you mean by form factor? If you mean the relation between width and height - that has been taken account for, since the diagonal is used, or am I mistaken here? Bart --~--~-~--~~~---~--~~ 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: Powermac G5 compiling Hugin from svn. No joy. Possible LAPACK problem
Hello Harry, No, I do not have vigra or jhead installed as a part of MacPorts... BigDaddy:Application meleschi$ port installed | grep -i vigra BigDaddy:Application meleschi$ port installed | grep -i jhead Thanks... Anything else I can check? Ricardo On Apr 13, 1:29 pm, Harry van der Wolf hvdw...@gmail.com wrote: Hi Ricardo, Did you install vigra and/or jhead via MacPorts for some reason? If you did, please deactivate them (sudo port deactivate vigra; sudo port deactivate jhead) and reconfigure and recompile Hugin. If the configure script finds vigra outside hugin it will use that one. You can find installed packages by running port installed or port installed | grep package. The deactivate command will not uninstall the packages. It will only remove them from the install libraries. If you want them back you can simply use sudo port activate package. Hoi, Harry 2009/4/13 RickyRicky meles...@gmail.com Hey Seth, Thanks for the tip on running Hugin from the command line. I did so, and here are the lines before the big crash. I hope someone can recognize my problem!: Determining placement of the images: 53% Number of images 2 Hugin(77452,0xa06cd830) malloc: *** error for object 0x2a2c200: double free *** set a breakpoint in malloc_error_break to debug Optimizing Variables Strategy 1 Average (rms) distance between Controlpoints after 0 iteration(s): 801.152704448697 units Strategy 1 Average (rms) distance between Controlpoints after 1 iteration(s): 801.019725960169 units Optimizing Variables Strategy 2 Average (rms) distance between Controlpoints after 0 iteration(s): 57.1154776303789 units Strategy 2 Average (rms) distance between Controlpoints after 1 iteration(s): 56.9698889445181 units Strategy 2 Average (rms) distance between Controlpoints after 2 iteration(s): 8.60724772529945 units Strategy 2 Average (rms) distance between Controlpoints after 3 iteration(s): 7.72758159217231 units Strategy 2 Average (rms) distance between Controlpoints after 4 iteration(s): 6.58494386005708 units Strategy 2 Average (rms) distance between Controlpoints after 5 iteration(s): 5.40204786941155 units Strategy 2 Average (rms) distance between Controlpoints after 6 iteration(s): 3.79597859019421 units Strategy 2 Average (rms) distance between Controlpoints after 7 iteration(s): 1.66872838105291 units Strategy 2 Average (rms) distance between Controlpoints after 8 iteration(s): 0.479946564550839 units Strategy 2 Average (rms) distance between Controlpoints after 9 iteration(s): 0.479481987047642 units Strategy 2 Average (rms) distance between Controlpoints after 10 iteration(s): 0.479481986986529 units Bus error Thanks, Ricardo Meleschi On Apr 13, 10:58 am, Seth Berrier seth.berr...@gmail.com wrote: Hmm, well I got this compiler problem while compiling on my MacBook (incidentally, I didn't think 10.5 would run on powerpc arch anymore, glad to know). However, I ignored the error message and things still seem to work okay for me. The Hugin.app and all the supporting applications are built and installed correctly. I had to monkey with the path setting a little bit. For that, you can check out this thread http://groups.google.com/group/hugin-ptx/browse_thread/thread/3efbca4 However, the path problem will come up when you do auto control point detection or with the final stitch as this is when external programs are used. I don't think this woulod cause problems at position optimization. My best advice would be to run hugin from the terminal shell (just run path to hugin.app/Hugin.app/Contents/MacOS/Hugin) You might get more messages from the terminal output. Seth On Mon, Apr 13, 2009 at 9:34 AM, RickyRicky meles...@gmail.com wrote: Gents, I've been working on compiling Hugin these last few days and have succeeded in getting it compiled, but for some reason whenever I run Hugin and attempt to align images, hugin always crashes when determining placement of the image, after Celeste is run. I don't see a log file being generated anywhere. I'm not too familiar with Hugin so I may be looking in the wrong places. When I review my compile log, I see I was having problems with LAPACK: --- [ 3%] Building CXX object src/foreign/jhead/CMakeFiles/huginjhead.dir/ exif.o In file included from /Users/meleschi/src/hugin/src/foreign/levmar/ misc.c:42: /Users/meleschi/src/hugin/src/foreign/levmar/misc_core.c:562:2: warning: #warning LAPACK not available, LU will be used for matrix inversion when computing the covariance; this might be unstable at times In file included from /Users/meleschi/src/hugin/src/foreign/levmar/ misc.c:57:
