Re: [hugin-ptx] Re: New hugin-mac-2010.5.0-4854_d29b1d6da0e0 incl. Thoby projection, new cpfind and gsoc 2010 panorama projection
Hey! If one of these tests are successful, the echo utility may be the culprit. Sir, you are a scholar, and I thank you. I downloaded the Macintosh ptbatcher GUI having not previously needed it or having ever used it. I loaded my .pto file into the batch processor, and voila, obtained a fine stitched pano output image. Your above theory seems to be quite correct, and because I was thinking the problem was related to a specific OS version, we appear to both be vindicated. myself with my suspicion and yourself with your solution. Last October one version of hugin wasn't able to stitch for me, I only could get a successful stitch using PTBatcher [1]. Maybe your problems are somehow related to this... Cheers, Habi [1]: http://is.gd/6kSFf8 -- 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 plugin interface - developers please liaise
Hi all! First of all, thank you all for your assistance! The code is in the SF repo all right, I made sure by going through a complete pull-up-clone- branch-compile cycle, and it's looking just fine. Phew... this was a major piece of work - kept me busy for a good two weeks, every day all day. Of course a good part of the time went into learning the tools - first I had to decide which tools to use, then I hadn't used SWIG before, and I also had to read up a great deal about Python/C++ integration to make it all come out nicely. I hope to see some use of this branch and a discussion of how the new possibilities can be turned into a benefit for the users and developers alike. Of course it's all still very rough-and-ready, there may be bits missing or failing here and there, but I hope the big picture is all right. On 20 Jan., 00:38, Pablo d'Angelo pablo.dang...@web.de wrote: From http://mercurial.selenic.com/wiki/Export, it seems that hg bundle is the preferred way for contributing changesets. I have tried to import your changes into the sourceforge repository using hg import, I hope it worked fine. Pablo, thank you for taking time off your busy schedule with cpfind to help me get my code in! I think you may have misunderstood the mercurial documentation. It says in there that 'hg bundle' is to export merge changesets, but there weren't any merges in mine, it was just composed of two successive changesets, applied to the branch as created by you, each only with one parent. In this case I take it the export command is the one to use, as I gleaned from the export tutorial http://mercurial.selenic.com/wiki/TutorialExport Anyway, it worked - and since I don't expect to throw such patches at you guys all too often and the effort to put them in doesn't seem to be excessive, I hope this is an acceptable method for you for now. I'm considering setting up a repo with bitbucket, as you recommended, but I'm not there yet. Kay -- 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: cmake help needed for python interface
On 19 Jan., 20:49, T. Modes thomas.mo...@gmx.de wrote: Hi Kay, On 19 Jan., 09:32, kfj _...@yahoo.com wrote: This may work, but is it necessary? Until then, as posted previously, use the getVar() method as a workaround. Yes, it is necessary. The workaround works only for some variables like yaw, pitch and so on. But with this I don't get e.g. the projection or the crop region of the image, just to name some of the also. Also without the macros I can not access the information about linked variables (isLinked/isLinkedWith) in python. Okay. Can you please point out where the lazy metaprogramming - so, the multiple inclusion of SrcPanoImage.h which instantiates the getXXX macros etc. with different variables - is happening? Or am I maybe misunderstanding the mechanism? - in which case please clarify how the accessor functions come to be. Then I can try and emulate the process in the interface definition file and make it generate the accessor functions. Now that the first step is done and the branch is established in the SF repo, I can start looking at details. Sory for having ben sloppy - I should have noticed the omission earlier. Blame it on my inexperience with the hugin body of code. Kay -- 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: cmake help needed for python interface
On 18 Jan., 16:47, kfj _...@yahoo.com wrote: Help with these problems would be greatly appreciated That was, help with cmake, as stated on the thread headline and requested in the initial posting. I would really appreciate if someone could actually at least touch the issue. I set up a thread http://groups.google.com/group/hugin-ptx/browse_thread/thread/9a8e2872f77c41b6/0edb8167dc8c4c38#0edb8167dc8c4c38 for developers to discuss the scripting interface in general, so the discussion about the accessor macros in SrcPanoImage.h would probably fit in there better. Kay -- 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
Re: [hugin-ptx] Re: Cpfind for Dummies
Hi harry, yes, I used the latest one. -- 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: Cpfind for Dummies
Hi Pablo, Thanks for the explanation. A couple questions and clarifications: On Wednesday, January 19, 2011 10:46:59 PM UTC+1, Pablo d'Angelo wrote: 2) is cpfind supposed to use the crop in hugin (so that there should not be CP's outside the crop)? Yes, it should. I have seen that the circle in your example was a bit offset. This might be related to the center on d/e in the crop panel. This means that the circle is always centered on the d/e parameters, which worked nicely with my peleng. If bad d/e parameters are used, the circle will be shifted. You could try without the center on d/e. with my example, the vertical offset is about 100 pixels - due to the lens being on an adapter, maybe. anyway, I filed a bug report about this yesterday. https://bugs.launchpad.net/hugin/+bug/704884 i am using the command line to do this stuff, is this maybe where my problem is? -- 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
Re: [hugin-ptx] 2010.5.0.1dd7fc1aa696 problem with Windows XP
Hi Brian, 2011/1/19 brian_ims im...@netspace.net.au i have just built 2010.5.0.1dd7fc1aa696 for windows. When I try to open the fast preview window, the preview flashes up briefly then a new window opens and the program then crashes offering to send error message to Microsoft. Everything else appears to behave OK Does anyone else have this problem? I had this problem about a week ago. In between many bugfixes have been applied to the trunk. Please sync your trunk to the latest version and try to build again. Harry Hi Harry I have built the latest version (as of this evening) - same behaviour! Brian -- View this message in context: http://old.nabble.com/2010.5.0.1dd7fc1aa696-problem-with-Windows-XP-tp30706271p30718353.html Sent from the hugin ptx mailing list archive at Nabble.com. -- 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
Re: [hugin-ptx] Re: New hugin-mac-2010.5.0-4854_d29b1d6da0e0 incl. Thoby projection, new cpfind and gsoc 2010 panorama projection
On Thu, Jan 20, 2011 at 3:28 AM, David Haberthür david.haberth...@gmail.com wrote: Last October one version of hugin wasn't able to stitch for me, I only could get a successful stitch using PTBatcher [1]. Maybe your problems are somehow related to this... Cheers, Habi [1]: http://is.gd/6kSFf8 The indicated link appears to relate to a problem that Hugin had, or has, with locating the automatic control points creation routine. That can occur in the most recent Hugin releases if a previous Hugin preferences file is installed in the users Library/Preferences folder. Similar control points failures can occur in any part of the path in which the Hugin application resides contains any blank spaces in any of the path names. Steve -- 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: cmake help needed for python interface
On 20 Jan., 09:53, kfj _...@yahoo.com wrote: On 18 Jan., 16:47, kfj _...@yahoo.com wrote: Help with these problems would be greatly appreciated That was, help with cmake, as stated on the thread headline and ... oops... I'm sorry, I'll have to swallow my words, since the problem has been adressed already! I must have overlooked the relevant bit in T. Modes' initial reply. I apologize. Kay -- 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: cmake help needed for python interface
Hi Kay, Help with these problems would be greatly appreciated That was, help with cmake, as stated on the thread headline and I sent you yesterday a patch with a modified cmake system, which fixes most of the problems (I commited it in the meanwhile to the repository). Thomas -- 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 plugin interface - developers please liaise
Hi Kay, continue the accessor issue mentioned in the other thread. The accessor functions are defined in SrcPanoImage.h, lines 117 - 172 by using macros and inclusion of image_variables.h multiple times. Thomas PS: hsi and hpi compiles on windows. Importing the python lib works also. But when running a script inside hugin it return value is always -2 and the script is not executed. Ideas? -- 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 hugin-mac-2010.5.0-4854_d29b1d6da0e0 incl. Thoby projection, new cpfind and gsoc 2010 panorama projection
Sure. Here is the info:
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
+++
It is already bash as I expected.
Please check which shell is associated with /bin/sh. Maybe there are
different shells linked to sh in different mac versions.
Gnu make seems to have a bug with the shell variable, as I have see
already in windows.
Even when setting SHELL=cmd.exe in the makefile an other shell
(sh.exe) is used if sh.exe found in the path.
Also in a unix shell (tested in ubuntu) the SHELL variable of the
shell is not used by gnu make.
You need a file test_make with following content:
all:
@echo ${SHELL}
(the second line have to start with a tab and no white spaces)
Then run the following commands:
$ set | grep SHELL
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-
comments:monitor
$ make -f test_make
/bin/sh
Thomas
--
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: Cpfind for Dummies
Am 20.01.2011 10:48, schrieb Jeffrey Martin: Hi Pablo, Thanks for the explanation. A couple questions and clarifications: On Wednesday, January 19, 2011 10:46:59 PM UTC+1, Pablo d'Angelo wrote: Yes, it should. I have seen that the circle in your example was a bit offset. This might be related to the center on d/e in the crop panel. This means that the circle is always centered on the d/e parameters, which worked nicely with my peleng. If bad d/e parameters are used, the circle will be shifted. You could try without the center on d/e. with my example, the vertical offset is about 100 pixels - due to the lens being on an adapter, maybe. anyway, You can savely untick the center on d/e, then you move the crop circle freely. I filed a bug report about this yesterday. https://bugs.launchpad.net/hugin/+bug/704884 I can confirm that. I tried searching for the right spot in the code, but I'm not very familiar with the refactoring that James had done on SrcPanoImage class. Where can I insert a hook for intercepting changes to the d/e parameters? Maybe some other Developers (Thomas, James?) can give me a small hint. i am using the command line to do this stuff, is this maybe where my problem is? Can you give a summary what you have done (in hugin and on the command line?) ciao Pablo -- 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 plugin interface - developers please liaise
On 20 Jan., 18:54, T. Modes thomas.mo...@gmx.de wrote: Hi Kay, continue the accessor issue mentioned in the other thread. The accessor functions are defined in SrcPanoImage.h, lines 117 - 172 by using macros and inclusion of image_variables.h multiple times. Thanks. I'm working on the issue, and I must say I'm having a hard time - the code is quite intransparent. But I hope I'll manage to have the accessors soon. I'll keep you all posted. It would help if I had a technical outline of how and where precisely they are made, but maybe I'll manage with a bit of intelligent guesswork... PS: hsi and hpi compiles on windows. great. Importing the python lib works also. But when running a script inside hugin it return value is always -2 and the script is not executed. Ideas? Try and run hugin from the command line and see what the python interface says why it fails. Most likely it can't load the modules hpi and hsi because they're not in the module path. Remember hpi.py is not output, but handcoded and therefore lives in the hsi directory initially - if you want all the files in one place, copy it over to where hsi.py and _hsi.so (or whatever they're called on Windows) live in the target directory (like, hugin.hg-build/src/hsi). I haven't yet figured out how to tell CMake that something is just there and doesn't have to be generated from somewhere. The code where the error originates is in hpi.cpp. try: export PYTHONPATH=whatever directory your hsi.py _hsi.so and hpi.py are in path to hpi-linked hugin/hugin I have also put more up-to-date documentation in README.hsi in the hsi directory, if you need to read up on what does what, but of course I'm always happy to help here. Kay -- 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: cmake help needed for python interface
On 20 Jan., 18:41, T. Modes thomas.mo...@gmx.de wrote: Hi Kay, Help with these problems would be greatly appreciated That was, help with cmake, as stated on the thread headline and I sent you yesterday a patch with a modified cmake system, which fixes most of the problems (I commited it in the meanwhile to the repository). Yes, thank you, that's why I had to swallow my words. I had in the meantime figured it out from your initial reply to my post, just that I had to change it so that swigpyrun.h appears in the source directory, not in the target. I'll see if I can get your patch from the repo. Thanks again. Sometimes I really wish I was back in the old times when it was just writing makefiles, I was quite good at that in my time... but I realize that CMake is a great help - once one has mastered it :( Kay -- 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 plugin interface - developers please liaise
On 20 Jan., 21:34, kfj _...@yahoo.com wrote: On 20 Jan., 18:54, T. Modes thomas.mo...@gmx.de wrote: Hi Kay, continue the accessor issue mentioned in the other thread. The accessor functions are defined in SrcPanoImage.h, lines 117 - 172 by using macros and inclusion of image_variables.h multiple times. Hi Thomas! I think I've finally understood the code. I suppose it'll be best to mess with the code a bit - as I said earlier, SWIG can either include one level or all levels, two levels would be just what's needed. I can probably make a modified version of SrcPanoImage.h that does the trick, or some such manoevre... Partial preprocessing might do the trick. I'll have good hard look at it tomorrow and call it a day now Kay -- 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 plugin interface - developers please liaise
Hi Kay, Try and run hugin from the command line and see what the python interface says why it fails. Most likely it can't load the modules hpi and hsi because they're not in the module path. Remember hpi.py is not output, but handcoded and therefore lives in the hsi directory initially - if you want all the files in one place, copy it over to where hsi.py and _hsi.so (or whatever they're called on Windows) live in the target directory (like, hugin.hg-build/src/hsi). I haven't yet figured out how to tell CMake that something is just there and doesn't have to be generated from somewhere. The code where the error originates is in hpi.cpp. try: export PYTHONPATH=whatever directory your hsi.py _hsi.so and hpi.py are in path to hpi-linked hugin/hugin Thanks for you help. I finally got it to run. There were some errors in hpi.py (fixed in repository). Thomas -- 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] Hugin for newbies
Hi all! I really appreciate hugin 2004.4.0, it rocks on ubuntu. Thank you for giving it us! Notwithstanding the overall value of hugin, I'm still very confused from its UI: 1. The user still isn't told whether the changes he does in one of the preview windows are saved or not when he closes the windows. I think something is to be put in the preview windows so that the user knows that every change made there will reflect in the final result. Besides that, a revert button is missed, in order to forget all changes made in the preview window 2. The user can't understand the relation between the assistant actions and the other tabs settings: does any change made in another tab influence the result got with the align or the create panorama buttons? I suppose yes, but nothing says it, and the user is let confused. 3. In my view, the assistant should give the user a resume of at least the most important settings changed in the other tabs 4. I think it would be better that some little thumbnails of the images to align be shown in the assistant 5. The Note above the create panorama... button in the assistant: it's not clear. It speaks of some particular settings that aren't going to affect some assistant action, but the user keeps confused: should the user use the custom actions suggested in the note instead of the align... button or instead of the create panorama... one? After thinking a lot it seems that the custum actions substitute the align action, or am I wrong? in any case the user can misunderstand that. Besides that, is the user that customize something allowed to use the create panorama... button, of must he go to the stitch tab? The user is confused with that. Just my 2 c. -- 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
