[hugin-ptx] Re: Moving between fields with the Tab key
Andrew H schrieb: Is there an anomaly in the GUI when tabbing between fields in Hugin on Mac OSX, please? When I am editing values in, say, the Stitcher tab and moving between fields using Tab or Shift-Tab the focus moves to the new field but inserts a cursor, rather than highlighting the previous value. ... Do other users experience this, or have I set something incorrectly, please? With 0.8.0 on WinXP I experience the same but in other places: - Control point tab: coordinate fields at the very bottom - Assistant tab: crop factor field. regards Joachim --~--~-~--~~~---~--~~ 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: Problem compiling on Windows -- wxWidgets not found
Thanks Guido Installing CMake 2.6.3 did the trick. Thank you very much for setting up this build environment. I know how much work it took! -- Tom --~--~-~--~~~---~--~~ 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: What is the status of keypoint detection and keypoint matching: machpoint (gsoc2007) and feature_matching (gsoc2008)
Hi I too would like to know the status of the various control point finders associated with Hugin. And I don't think Harry and I are alone in this. Is it possible that someone who knows (maybe that means a committee??) could publish an authoritative and intelligible summary of this topic? I could contribute a bit on Autopano-sift-c but am wholly ignorant of the others. -- Tom On Feb 25, 8:19 am, Harry van der Wolf hvdw...@gmail.com wrote: All, I've been searching my archives but I'm a bit lost (or actually: completely lost). During gsoc 2007 Zoran Mesec created/worked on matchpoint: the patent free keypoint detector. As far as I'm aware matchpoint works fine, but still has problems dealing with transparency masks. True or wrong? Anyone who does know, please explain. Any relevant info that I didn't ask here is welcome too. During gsoc 2008 Onur Küçüktunç created/worked on feature_matching to be used in combination with matchpoint. Is this now (relatively) mature or not? Can we use it? As far as I know this still hasn't been integrated into the main Hugin trunk or has it? (and am I a complete moron for missing that?) Finally: Combination of matchpoint and match-n-shift: Is this now a working keypoint detection/matching combination as such or does match-n-shift just use autopano for the keypoint matching? (I'm almost sure about the latter, but maybe I also miss some details here). I know match-n-shift does much more, but I'm now only referring to keypoint detection/matching. hoi, Harry --~--~-~--~~~---~--~~ 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: Photo Mosaic (Sort of linear panorama)
2008/5/27 Klaus k...@ph.ed.ac.uk: So in the suggested work flow; * would it not work to enter the lens parameters for all lenses in the linear panorama, and just don´t optimize these any further, You first have to produce a set of distortion-free images. Hugin's sequence for applying the parameter groups d,e and a,b,c is not the correct order if one wants to produce a linear panorama. Hence one need two separate steps. Hugin allows you to edit script before optimizing. Would it be possible to use this in order to make a linear panorama, not having to do lens correction in beforehand in a separate step, but rather seed the optimization with the correct values. Have I understand the problem right, that hugin prioritizes and optimizes a,b,and,c before d and e as it is intended to be used with nodal panoramas, while in the linear case one would like to optimize on d, e first combined with yaw, pitch, roll. (leaving a,b and c out) Cheers /O --~--~-~--~~~---~--~~ 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: Problem compiling SVN 3665 on AMD 64b, Ubuntu 8.10
Yeah, I think it is, but unfortunately I've no idea what can cause it. I though it was fixed by this optimization flag but it doesn't seem so. --~--~-~--~~~---~--~~ 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: Simple lens calibration
The box would be the lens housing, the lens itself consists of a certain number of glass elements with air between those. In most cases there is second box behind box #1: the camera body, also filled with air. If the whole combination is surrounded by water it's either a underwater camera or broken ;-) Note that also underwater cameras can get very wet inside if not maintained properly. Light rays (emitted by sun or underwater flash) are reflected by an object and travel through water - glass - air (awfully simplified) to the sensor/film surface. A similar problem is IR photography: the focus index is calculated for a certain bandwidth of light. Try to only use the IR spectrum and you will notice that these rays also behave in a different fashion. After rereading this I think it's a wonder if a photographer is still able to focus on the main subject :-) Cheers, Carl michael crane wrote: 2009/2/25 Carl von Einem c...@einem.net: Yes, but a different medium (water instead of air) is used at one surface of the glass. That's where the angle of the light ray changes. Oh you mean the lens is inside a box ? I thought that the lens would be in the water. regards mick --~--~-~--~~~---~--~~ 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: Panini 0.62 released
Hi Luca On Feb 25, 5:36 pm, luca vascon luca.vas...@gmail.com wrote: If you let us settle down in the new office, Officine Panottiche Venezia will be happy to donate the web design and look.. so the PNG file and SVG logos etc.. It will take time. Wonderful, thanks. I hope your office is comfortable and your business is a big success. Regards, Tom --~--~-~--~~~---~--~~ 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: Problem compiling on Windows -- wxWidgets not found
But now another problem. The install script is failing because there
is no enblend in my build.
There now seems to be conditional code in cmake_install.cmake for
various components, such as enblend; however it doesn't seem to
work. Here is the block for enblend:
IF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
FILE(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/doc/enblend TYPE
FILE FILES
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/AUTHORS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/ChangeLog
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/COPYING
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/NEWS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README_WINDOWS.txt
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/TODO
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/VIGRA_LICENSE
)
ENDIF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
That DIR-NOTFOUND suggests that something higher up in the script
generating chain is not doing its job.
Either CMake support for installing is not good enough, or we aren't
using it right. Or both.
BTW where am I supposed to get enblend, and how integrate it in the
build? Could I do somethng similar for autopano-sift-c?
-- Tom
On Feb 26, 9:14 am, Tom Sharpless tksharpl...@gmail.com wrote:
Thanks Guido
Installing CMake 2.6.3 did the trick.
Thank you very much for setting up this build environment. I know how
much work it took!
-- Tom
--~--~-~--~~~---~--~~
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] jerkiness in panosalado, now spincontrol:vr (was: [OSX] hugin0.8_svn3662_20090221 for download and 2 wintersport pano's)
The jerkyness in the pano's had to do with the big steps I defined for the autorotation in combination with the one big image instead of 6 smaller cubefases. I created a new combined 2-in-1 pano with the new spincontrol:vr demo version. This is a combined tour. If you click the drop down arrow in the bottom left of the bar, you can select the second. A very nice feature! I used smaller autorotation steps but as I don't have a full 360x180 pano I'm still limited to one big cylinder (or equirectangular for that matter). *http://tinyurl.com/KleinWalsertal * Hoi, Harry* * 2009/2/24 Harry van der Wolf hvdw...@gmail.com No, it's not the latest version. It is the latest downloadable binary version: 128 or 129. I just compiled the lastest svn (135) and uploaded that one but that doesn't make a difference. With jerky I suppose you mean the stuttering movement of the auto rotation. Wel, I did a fast copypaste to the website and I need to investigate whether it's my pano settings or whether it really is panosalado moving so slow. When rotating with the mouse there is no stuttering at all. However, when you take a look at the demo tour for the new spincontrol:vr application ( http://www.panosalado.com/images/spincontrol_examples/demo/New_Orleans_2007/index.html), it shows the same stuttering on autorotation. Is it size, settings or ..? Maybe I post a question in the forum to ask patrick co.about this stuttering. Harry 2009/2/24 Yuval Levy goo...@levy.ch Harry van der Wolf wrote: http://tinyurl.com/kanselwand http://tinyurl.com/fellhorn (both can be viewed fullscreen) nice panos, happy to see you had beautiful blue sky! I'm surprised that panosalado is so jerky. is this the latest version? 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: Photo Mosaic (Sort of linear panorama)
On Thu 26-Feb-2009 at 15:35 +0100, Oskar Sander wrote: Hugin's sequence for applying the parameter groups d,e and a,b,c is not the correct order if one wants to produce a linear panorama. Hence one need two separate steps. Hugin allows you to edit script before optimizing. Would it be possible to use this in order to make a linear panorama, not having to do lens correction in beforehand in a separate step, but rather seed the optimization with the correct values. The problem is that the d,e parameters define the optical centre of the image, so the large values you get from sideways camera displacement misplace the lens and perspective correction. So currently the way to get linear panoramas working with hugin is to remove any trace of an 'optical centre': fix lens distortion and perspective, then all you need to do to align them is scale (with 'v' field of view parameter), rotate (with 'r' roll parameter) and translate (with 'd,e' offset parameters). -- 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: Generalised stereographic projections
On Wed 25-Feb-2009 at 14:53 +, Peter Gawthrop wrote: I have been playing with generalisations of the stereographic projection. Given a view sphere of a 360 panorama, the basic idea is the float around inside that sphere and then project on to either a plane or a cylinder. Conventional perspective comes from projecting from the centre of the sphere, and stereographic from the back, onto a plane. I never really got around to describing the panini projection, but basically it is set out exactly the same as stereographic except using an intermediate cylinder instead of a sphere. e.g. a stereographic image is what you would get by sitting at the back row of a planetarium and photographing the ceiling with a 'normal' camera. ..and a panini image is what you get if you photographed inside a Victorian painted cylinder panorama, but stood as far from the centre as possible with your back against the wall. This goes some way towards explaining why these painted panoramas don't get any better if you stand in the dead-centre (and an extreme example of Zeeman's Paradox). At the moment, it's a mathmap implementation. But I would like to think about putting it in hugin and/or panini. Note that, unlike the Panini projection, the aim is to distort - albeit in a meaningful way. I still can't get Tom's Panini to run (wrong version of QT on EL4, grr), but as I understand this is more or less how it currently works. -- 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: Photo Mosaic (Sort of linear panorama)
Bruno Postle twisted the bytes to say: Bruno On Thu 26-Feb-2009 at 15:35 +0100, Oskar Sander wrote: Hugin's sequence for applying the parameter groups d,e and a,b,c is not the correct order if one wants to produce a linear panorama. Hence one need two separate steps. Hugin allows you to edit script before optimizing. Would it be possible to use this in order to make a linear panorama, not having to do lens correction in beforehand in a separate step, but rather seed the optimization with the correct values. Bruno The problem is that the d,e parameters define the optical centre of Bruno the image, so the large values you get from sideways camera Bruno displacement misplace the lens and perspective correction. Bruno So currently the way to get linear panoramas working with hugin is Bruno to remove any trace of an 'optical centre': fix lens distortion and Bruno perspective, then all you need to do to align them is scale (with Bruno 'v' field of view parameter), rotate (with 'r' roll parameter) and Bruno translate (with 'd,e' offset parameters). I want to add to libpano the ability to specify a parameter that indicates where in axis the projection should be computed from. By default it is r (from the center of the sphere) but it can be any point (0 is the center of it). It is not difficult, since I have added support for arbitrary parameters long time ago. --dmg --~--~-~--~~~---~--~~ 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: Photo Mosaic (Sort of linear panorama)
I want to add to libpano the ability to specify a parameter that indicates where in axis the projection should be computed from. By default it is r (from the center of the sphere) but it can be any point (0 is the center of it). It is not difficult, since I have added support for arbitrary parameters long time ago. --dmg I feel very stupid :) I replied to the wrong message ;) sorry -- --dmg --- Daniel M. German http://turingmachine.org --~--~-~--~~~---~--~~ 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: Generalised stereographic projections
Bruno On Wed 25-Feb-2009 at 14:53 +, Peter Gawthrop wrote: I have been playing with generalisations of the stereographic projection. Given a view sphere of a 360 panorama, the basic idea is the float around inside that sphere and then project on to either a plane or a cylinder. Conventional perspective comes from projecting from the centre of the sphere, and stereographic from the back, onto a plane. Bruno I never really got around to describing the panini projection, but Bruno basically it is set out exactly the same as stereographic except Bruno using an intermediate cylinder instead of a sphere. Bruno e.g. a stereographic image is what you would get by sitting at the Bruno back row of a planetarium and photographing the ceiling with a Bruno 'normal' camera. Bruno ..and a panini image is what you get if you photographed inside a Bruno Victorian painted cylinder panorama, but stood as far from the Bruno centre as possible with your back against the wall. This goes some Bruno way towards explaining why these painted panoramas don't get any Bruno better if you stand in the dead-centre (and an extreme example of Bruno Zeeman's Paradox). At the moment, it's a mathmap implementation. But I would like to think about putting it in hugin and/or panini. Note that, unlike the Panini projection, the aim is to distort - albeit in a meaningful way. I want to add to libpano the ability to specify a parameter that indicates where in axis the projection should be computed from. By default it is r (from the center of the sphere) but it can be any point (0 is the center of it). It is not difficult, since I have added support for arbitrary parameters long time ago. Of course, this is only in one dimension, not in 3 as you are experimenting. But the functions for panini can be generalized... --dmg --~--~-~--~~~---~--~~ 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: Problem compiling on Windows -- wxWidgets not found
Hi Tom,
enblend is the second pitfall to trip into. I included it not in the
SDK, but I know this was a fault.
You can download it here:
http://downloads.sourceforge.net/enblend/enblend-enfuse-3.2.zip
Decompress it to SDK's directory, that the application is in directory
enblend-enfuse-3.2.
Autopano-sift-C is missing too, but the install script will work without
it. You can simply use the version 2.5.0 that was already included in
hugin 0.7.0 distribution.
Guido
Tom Sharpless schrieb:
PS I guess the faulty script is hugin/CMakeModules/win-bundle.cmake.
On Feb 26, 1:18 pm, Tom Sharpless tksharpl...@gmail.com wrote:
But now another problem. The install script is failing because there
is no enblend in my build.
There now seems to be conditional code in cmake_install.cmake for
various components, such as enblend; however it doesn't seem to
work. Here is the block for enblend:
IF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
FILE(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/doc/enblend TYPE
FILE FILES
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/AUTHORS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/ChangeLog
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/COPYING
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/NEWS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README_WINDOWS.txt
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/TODO
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/VIGRA_LICENSE
)
ENDIF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
That DIR-NOTFOUND suggests that something higher up in the script
generating chain is not doing its job.
Either CMake support for installing is not good enough, or we aren't
using it right. Or both.
BTW where am I supposed to get enblend, and how integrate it in the
build? Could I do somethng similar for autopano-sift-c?
-- Tom
On Feb 26, 9:14 am, Tom Sharpless tksharpl...@gmail.com wrote:
Thanks Guido
Installing CMake 2.6.3 did the trick.
Thank you very much for setting up this build environment. I know how
much work it took!
-- Tom
--~--~-~--~~~---~--~~
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: New windows installer: 3652
Hi Allard, something is wrong on your side, but I can't tell what. Because I know that the repository works fine and just running CMake (no need to do the MSVC stuff) sets up the installer properly. here is what I did: * inside an SDK folder, I created two folders: hugin.trunk and hugin.build. * checked out with TortoiseSVN https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk into hugin.trunk * run CMakesetup v2.7 20090130 with source hugin.trunk and build hugin.build * when CMake was finished and configured all the files for the installer where properly located in hugin.build\INSTALL of course at this point the installer compilation won't work because there are no binaries inside FILES, but the skeleton to make it work is there and when I look at hugin.build\INSTALL\url.txt it has correctly replaced the @HUGIN_WC_REVISION@ string with the SVN revision that I just checked out. allard wrote: most likely the INSTALL target in MSVC is deselected. Nope. It is deselected at first, but I built 'install' after the 'build solution', as Guido had prescribed. sorry, my mistake - the InnoSetup installer files are not MSVC dependent, as described above. When I do another build I will completely clear out everything, (backing up the cmakelists.txt and the iss file just in case) might be an issue with your cmakelists.txt - that's where the files are copied into the right location. 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 -~--~~~~--~~--~--~---
