[hugin-ptx] Re: Integration Queue - how do we add features to trunk and to release
Bruno Postle wrote: Cpclean is ready to go in as far as I'm concerned, the only question is do we run it automatically with the Align... button?: If in doubt: Make it configurable. I guess that it should be done for people that use the automatic method. However, if somebody adds some control points manually and presses Align again, it might remove the manually added points, which is probably not desired... 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] Building Hugin
High all, I´m new to this group and sort of dummy in softwaredevelopment. Nevertheless I tried to start building hugin on windows using the sdk. It seems to me that enblend has moved to http://enblend.hg.sourceforge.net/hgweb/enblend Using this adress cloning worked as described in the panotools wiki. The adress still given there will cause a HTTP Error 400: Bad Request message. If what I mentioned is right, I may start building hugin the first time this week end. regards Andreas --~--~-~--~~~---~--~~ 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: Integration Queue - how do we add features to trunk and to release
Hi all, 2009/9/19 Bruno Postle br...@postle.net: On Thu 17-Sep-2009 at 21:24 -0400, Yuval Levy wrote: to list the PROJECTS: Layout still needs some work: - gsoc_2009_layout (James' project) Deghosting shouldn't cause problems as the code doesn't alter the existing workflow, I'd like to hear if Lukáš thinks it is ready to go in: - gsoc_2009_deghosting (Lukáš' project) I've committed probably the last change seconds ago. Now I'm going to begin new thread with call for testing. Vigra would be nice, though as Pablo says ideally we would merge the hugin bits with upstream: - vigra-1.6 (Lukáš' patch from before 0.8.0) Yep, I think too. The only big change is support of OpenEXR. The other changes are rather small, IIRC it's only some Point2D stuff or something similar which I'm not sure if it's really necessary. I should note that there's one thing I'd like to change about EXR implementation. I think I'll start another thread so I don't pollute this one. Cpclean is ready to go in as far as I'm concerned, the only question is do we run it automatically with the Align... button?: - control-point cleaning (Thomas patch) auto-crop is looking good, but needs a couple of things (like an icon) and some more testing: - auto-crop (Gary's patch) These need a lot of work: - gsoc_2008_masking (Fahim's project) - gsoc_2008_feature_atching (Onur's project) -- Bruno Lukáš --~--~-~--~~~---~--~~ 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] gsoc2009_deghosting call for testing
Hello everyone! From today I'm finally quite content about state of the deghosting project. Everything is tested and I don't see any major problems with it. With this mail I ask everyone willing to test some new code. What I need most: Compilation on frequently used platforms: Linux – it works here on Archlinux so I guess that it should work in other distributions but I'll still welcome reports from other distributions Windows – with Thomas' help it have been made to compile on widows Mac OS X – I don't know about any attempts to compile it on OS X Testing hugin_hdrmerge: Windows and OS X testing is needed. Since I've completely rewrote deghosting implementation it would be nice to test it. But please, do not consider different results as regression. There are also some other fixes (eg. avg_slow should work now) Testing deghosting_mask: I hope the usage text is self explaining. Area where ghosting appear should be black in resulting masks. These masks can be used with enfuse-mask to allow deghosting in enfuse. Unfortunately it doesn't work with small artifacts (like moving branches). I hope I'll be able to improve this in future. To be honest integration directly into the enfuse has much worse results than this but I've different approach in mind. final note: Yes, I know that it's slow. You can get noticeable speedup by passing -a f option to both deghosting_mask and hugin_hdrmerge. This will turn off using processing images as color but it also results in worse results. This option is similar to the old deghosting code. thanks for your time, Lukáš --~--~-~--~~~---~--~~ 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: please re-open bug https://sourceforge.net/tracker/index.php?func=detailaid=2720906gro up_id=77506atid=550441
Andreas Metzler ametz...@downhill.at.eu.org wrote: Gerry Patterson thedeepvo...@gmail.com wrote: On Sun, Sep 13, 2009 at 9:36 AM, Andreas Metzler ametz...@downhill.at.eu.org wrote: https://sourceforge.net/tracker/index.php?func=detailaid=2720906group_id=77506atid=550441 is closed, being marked as fixed in rev 4219. It is not. If I open the testcase from Ubuntu LP in hugin 2009.2.0 (4385) I still get the segfault. [...] http://launchpadlibrarian.net/24483478/errorprobe%20hugin.zip. Hello, sorry for pestering, but the bugreport is still marked as fixed. Can you reproduce the problem with testcase linked to above? thanks, cu and- really hating that sf's bug tracker forces us to have this discussion on a different medium -reas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --~--~-~--~~~---~--~~ 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: OpenEXR three bands
Hi Lukas, Lukáš Jirkovský wrote: Hi, while working on my GSoC project I've noticed that current OpenEXR implementation has only 4 bands. This makes it's usage inconvenient sometimes because it makes everyone to use ImportImageAlpha even when alpha is not necessary. It seems that OpenEXR is almost exclusively used with RGBA but when someone doesn't need alpha it should be allowed to use it with assumption that all pixels are opaque. Actually, its not that simple, as the alpha is usually pre-multiplied: value_in_file = value * alpha. This makes alpha blending in computer graphics applications faster. Hugin doesn't use anything of that though (only 0 and 1 alpha...), but a general solution needs to take care of that. The best solution would be to write a RGBA - RGB vigra accessor that could be passed to import image and would convert the RGBA - RGB. the importImageAlpha() functionality is also a hugin/enblend only feature, I haven't submitted that to the main vigra branch last time I sent my changes there. However, that is not really a problem, as its just an extension and could easily be moved into our own vigra_ext lib. I'd like to try to implement this. My question is: Is it acceptable or not? I mean when OpenEXR is stored as RGBA is it against some non-written rules in VIGRA to allow loading/storing with using only RGB values? Vigra is a multi purpose lib, and not restricted to a specific number of channels. For example, many remote sensing satellites have blue, green, red and infrared channels (The infrared channel contains valuable information about vegetation). Vigra is pretty dumb when it comes to image import/export, as it doesn't have a proper handling for alpha channels. I have added the ImageInfo::getExtraSamples() (or something similar), so that it is at least possible to differentiate between real channels and mask or alpha channels. I don't want to block it's way into upstream only because of this. If you want to hear my opinion I don't see any problem here because eg. tiff allows using from 1 to 4 bands. I don't think that this will be a problem, as the vigra import/export is quite bare bones anyway. One also needs to submit test cases for the new functionality, otherwise it won't be accepted by the vigra maintainers. 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 Qt
Lukáš Jirkovský wrote: Hello, there's one part of hugin code which I'm thinking of. I have many questions about it. It's code in src/hugin_qtbase. Is it alive? Is there anyone who actually cares about it? For now it seems dead. This is part of Ippei' GSOC 2007 project, where he did a lot of refactoring in the hugin core and started to lay a foundation for a QT based GUI, however, due to lack of development manpower and improvements in wxWidgets, we haven't really started developing a QT based GUI. 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: please re-open bug https://sourceforge.net/tracker/index.php?func=detailaid=2720906gro up_id=77506atid=550441
Andreas Metzler ametz...@downhill.at.eu.org wrote: [...] sorry for pestering, but the bugreport is still marked as fixed. [...] Nevermind. It is not *still* marked as fixed, but marked as fixed *again*. r4436 does the trick. Sorry for the noise. cu andreas --~--~-~--~~~---~--~~ 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: Building Hugin
Hi Andreas, anbue wrote: It seems to me that enblend has moved to http://enblend.hg.sourceforge.net/hgweb/enblend I do not recall if the Windows instructions still point to the old CVS repository; or they point to the old Hg repository. We moved the project from CVS to Hg. Then Sourceforge moved it again when it made it possible to have multiple Hg repositories per project. Actually what you are looking for is http://enblend.hg.sourceforge.net/hgweb/enblend/enblend please use that one, and be so kind to update the wiki. Also note that we're adding a CMake build. It should be easier to build with that on Windows. Please try it - the steps are very similar to the steps described for Hugin with CMake. I may start building hugin the first time this week end. if this is an exercise and you want to build your skill slowly but surely, start with a slightly older version - I would recommend a released tarball. You're more likely to succeed at first; and if you bump into problems you can solve them by looking at the wiki's page history. Once you've dipped your toes this way, you can move to build the bleeding edge with more confidence. good luck! 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: Integration Queue - how do we add features to trunk and to release
Pablo d'Angelo wrote: Bruno Postle wrote: Cpclean is ready to go in as far as I'm concerned, the only question is do we run it automatically with the Align... button?: If in doubt: Make it configurable. same for adding autocrop. default for both should be on as the features are more likely to be useful than harmful for the occasional user. An unobtrusive warning (on the Control Points tab?) that cpclean is enabled (not a pop up, but rather an informative text on red background in the tab itself, saying something like Cpclean is active and could remove manually added CPs) would be nice for advanced users. 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: Integration Queue - how do we add features to trunk and to release
T. Modes wrote: I have feedback that the current version run on all platforms (Win/ Linux/MacOS). +1 here There's a point more to consider: there are changes in libpano (multiviewpoint panorama, parameter Tx, Ty, Tz and Ts). Hugin needs to extend to make use of these new parameters. This should done after integration of layout-branch, because many internal were changed in it. this code is not even written yet. I'd call it future planning rather than integration queue. It probably does not make sense to start writing it before the layout codeline is integrated. 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] Added tests to pano13-cmake
Actually this was interesting. This built-in test of cmake is worth to learn. The only difficulty was the preparation of test-environment, because the used perl-script was not configurable. It assumed, it would work in the source directory. How to test: in the build-tree 1.) cmake ...source-dir -D 2.) make (or make package) 3.) make test Now have to find out, where is the output of this perl call. Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Integration Queue - how do we add features to trunk and to release
Bruno Postle wrote: On Thu 17-Sep-2009 at 21:24 -0400, Yuval Levy wrote: to list the PROJECTS: Layout still needs some work: - gsoc_2009_layout (James' project) so this is the most critical / important change of magnitude. What work does it still need? 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: gsoc2009_deghosting call for testing
2009/9/19 Lukáš Jirkovský l.jirkov...@gmail.com Hello everyone! From today I'm finally quite content about state of the deghosting project. Everything is tested and I don't see any major problems with it. With this mail I ask everyone willing to test some new code. What I need most: Compilation on frequently used platforms: Linux – it works here on Archlinux so I guess that it should work in other distributions but I'll still welcome reports from other distributions Windows – with Thomas' help it have been made to compile on widows Mac OS X – I don't know about any attempts to compile it on OS X It compiles fine on OSX using cmake, already for quite some time. I never mentioned it or tested it as you were continuously developing (I don't like chasing a moving target) and, off course, I had this 6 weeks black hole when I didn't have a mac. I just added it to the Xcode project. It took some Sherlock Holmes like detective work before I understood that the complete old deghosting folder had been replaced. I can't add this XCode changes to the gsoc2009_deghosting trunk for merge later on as that doesn't work. I have to redo this when when your work is merged to the development trunk (or 2009.4) but that's no problem. Now that I've worked it out and written it down it's 10 minutes work. Testing hugin_hdrmerge: Windows and OS X testing is needed. Since I've completely rewrote deghosting implementation it would be nice to test it. But please, do not consider different results as regression. There are also some other fixes (eg. avg_slow should work now) Since you've been working so hard on this, I assume you have one or more test sets with final images/panos (with/without deghosting). Could you make them available to us? In this case we can compare results and track down where it functions well and where not (and why). Testing deghosting_mask: I hope the usage text is self explaining. Area where ghosting appear should be black in resulting masks. These masks can be used with enfuse-mask to allow deghosting in enfuse. Unfortunately it doesn't work with small artifacts (like moving branches). I hope I'll be able to improve this in future. To be honest integration directly into the enfuse has much worse results than this but I've different approach in mind. Again: Do you have test sets? final note: Yes, I know that it's slow. You can get noticeable speedup by passing -a f option to both deghosting_mask and hugin_hdrmerge. This will turn off using processing images as color but it also results in worse results. This option is similar to the old deghosting code. thanks for your time, Lukáš 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: Studying the Source code of Hugin
Hi Bob, I redirected your question to the hugin-ptx group. Next time please mail your questions to the hugin-ptx list. I'm not a C/C++ developer and can not really help you with this questions other than pointing you to better qualified sources/persons. (another reason to send your mail to the community). As far as I know there is no simpler version of the source code: Hugin comes as it is. There is no Hugin light version. Doxygen is being used as documenting tool for the source code. I did not really dive into that yet and don't know how up-to-date it is. Not being a developer I hope someone else can help you with that. About your images mosaic system: Dev g. has been working on a mosaic mode for Hugin as part of the GSOC 2009 (see http://wiki.panotools.org/SoC_2009_student_proposals#Dev_Ghosh:_Mosaic_Mode_for_Hugin.2FPanotools ). You might also take a look at http://socghop.appspot.com/student_proposal/show/google/gsoc2009/dkg/t123865551999, but I'm not sure whether you have access to that part. Please get in contact with Dev and maybe something can be worked out that benefits both your project as well as Hugin or even merge them. Kind regards, Harry 2009/9/19 Bob Yiu boo...@gmail.com Dear Harry, Currently I've been studying the source code of Hugin. I successfully compiled the source code, but when I started to read the source code, I found it very much complicated. Do you have a simpler version of source code of Hugin for experiment? Just can stitching images and blending is enough. Or do you have any document about the source code? I've developed a images mosaic system using OpenCV and VC9 before(results shows in the attachment) , I want to do further studies about this topic by studying the source code of Hugin. How would you suggest me to get started this research? Best regards! Bob --~--~-~--~~~---~--~~ 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: Seg-Fault - Build 4421, 20090914
Bruno Postle wrote: I don't build with LAPACK, i.e. can you try building with: I do, and it does not crash. Ubuntu 9.04 32 bit. 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: gsoc2009_deghosting call for testing
2009/9/19 Harry van der Wolf hvdw...@gmail.com: 2009/9/19 Lukáš Jirkovský l.jirkov...@gmail.com Hello everyone! From today I'm finally quite content about state of the deghosting project. Everything is tested and I don't see any major problems with it. With this mail I ask everyone willing to test some new code. What I need most: Compilation on frequently used platforms: Linux – it works here on Archlinux so I guess that it should work in other distributions but I'll still welcome reports from other distributions Windows – with Thomas' help it have been made to compile on widows Mac OS X – I don't know about any attempts to compile it on OS X It compiles fine on OSX using cmake, already for quite some time. I never mentioned it or tested it as you were continuously developing (I don't like chasing a moving target) and, off course, I had this 6 weeks black hole when I didn't have a mac. I just added it to the Xcode project. It took some Sherlock Holmes like detective work before I understood that the complete old deghosting folder had been replaced. I can't add this XCode changes to the gsoc2009_deghosting trunk for merge later on as that doesn't work. I have to redo this when when your work is merged to the development trunk (or 2009.4) but that's no problem. Now that I've worked it out and written it down it's 10 minutes work. Thank you very much! Testing hugin_hdrmerge: Windows and OS X testing is needed. Since I've completely rewrote deghosting implementation it would be nice to test it. But please, do not consider different results as regression. There are also some other fixes (eg. avg_slow should work now) Since you've been working so hard on this, I assume you have one or more test sets with final images/panos (with/without deghosting). Could you make them available to us? In this case we can compare results and track down where it functions well and where not (and why). I don't have enough time today (going out in a while) but I'll make (and upload) some nice set tomorrow. Testing deghosting_mask: I hope the usage text is self explaining. Area where ghosting appear should be black in resulting masks. These masks can be used with enfuse-mask to allow deghosting in enfuse. Unfortunately it doesn't work with small artifacts (like moving branches). I hope I'll be able to improve this in future. To be honest integration directly into the enfuse has much worse results than this but I've different approach in mind. Again: Do you have test sets? final note: Yes, I know that it's slow. You can get noticeable speedup by passing -a f option to both deghosting_mask and hugin_hdrmerge. This will turn off using processing images as color but it also results in worse results. This option is similar to the old deghosting code. thanks for your time, Lukáš Hoi, Harry Lukáš --~--~-~--~~~---~--~~ 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: Integration Queue - how do we add features to trunk and to release
On Sat 19-Sep-2009 at 09:16 +0200, Pablo d'Angelo wrote: If in doubt: Make it configurable. I guess that it should be done for people that use the automatic method. However, if somebody adds some control points manually and presses Align again, it might remove the manually added points, which is probably not desired... In principle it should only remove such a point if it was inconsistent with the rest of the points - i.e. if was 'bad'. -- 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: gsoc2009_deghosting call for testing
other distributions but I'll still welcome reports from other distributions Windows – with Thomas' help it have been made to compile on widows If you can make the windows build available I would like to test them on some fresh test cases that I have got in my pipeline anyway. 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] enblend --verbose --version / enblend image cache
Hi, me again with some more confusion about options and settings. I read in the new enblend/enfuse documentation (http://panorama.dyndns.org/EandE-documentation/enblend.html#Tuning-Memory-Usage; thanks al lot for this!) about how to tune enblend's options to suit my 2GB RAM system. The documentation says To find out whether your version uses the image cache say enblend --verbose --version. Unfortunately this gives an error enblend: illegal option -- verbose. All other combinations with -verbose and -v and -version result in analogous errors. My enblend is version 3.2 with a file date 16.03.2009 23:06 (windows version). Anyway: If my enblend help text contains the options -m and -b, shouldn't it have this compiled in? If it is not compiled in then it should not display this help text. Next question: I just want to try, so I specify in the preferences -l29 -a -z -m512 -b1024. When I stitch I can't see -m512 -b1024 in the commandline displayed in the verbose output window. Next try: set the Use alternative Enblend program checkbox because I don't know if the arguments specified here are respected if the checkbox is not checked. After all the Default arguments line is indented as if it were only applied if the checkbox is checked. Same result: not passed to enblend. Next try: put -m512 -b1024 additionally in the options dialogue box that can be accessed from the stitcher tab. Are these options project specific, do they add to those specified in the preferences (if they were respected at all), do they override the preferences, is this another way to access the same preferences that are accessed via the preferences dialogue? Anyway: The arguments are passed and there is no error message, so I believe it principally works. Now I have to test with more than a pair of tiny test images if they actually improve anything (in my case: responsiveness of the system while blending). hugin 2009.2.0.4352 build by Ad. 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] 4 fatal errors
Hi Yuv, The number of fatal errors while trying to compile has doubled this week (please read as as statement of fact and nothing else). As requested I sent the error messages I could retrieve: First Creating library C:\SDK\hugin20092_build\src\tools\Release\autooptimiser.lib and object C:\SDK\hugin20092_build\src\tools\Release\autooptimiser.exp autooptimiser.obj : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function _main huginbase.lib(PTOptimizer.obj) : error LNK2001: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) C:\SDK\hugin20092_build\src\tools\Release\autooptimiser.exe : fatal error LNK1120: 1 unresolved externals Second Creating library C:\SDK\hugin20092_build\src\hugin1\hugin\Release\hugin.lib and object C:\SDK\hugin20092_build\src\hugin1\hugin\Release\hugin.exp OptimizePanel.obj : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function protected: void __thiscall OptimizePanel::runOptimizer(class std::set,class std::allocator const ) (?runoptimi...@optimizepanel@@iaexabv?$...@iu?$less@i...@std@@v?$alloca...@i@2@@std@@@Z) huginbase.lib(PTOptimizer.obj) : error LNK2001: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) C:\SDK\hugin20092_build\src\hugin1\hugin\Release\hugin.exe : fatal error LNK1120: 1 unresolved externals Third Creating library C:\SDK\hugin20092_build\src\tools\Release\tca_correct.lib and object C:\SDK\hugin20092_build\src\tools\Release\tca_correct.exp tca_correct.obj : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function int __cdecl optimize_old(class HuginBase::Panorama ) (?optimize_old@@yahaavpanor...@huginbase@@@Z) C:\SDK\hugin20092_build\src\tools\Release\tca_correct.exe : fatal error LNK1120: 1 unresolved externals Fourth Creating library C:\SDK\hugin20092_build\src\tools\Release\vig_optimize.lib and object C:\SDK\hugin20092_build\src\tools\Release\vig_optimize.exp huginbase.lib(PTOptimizer.obj) : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function public: virtual bool __thiscall HuginBase::PTOptimizer::runAlgorithm(void) (?runalgori...@ptoptimizer@HuginBase@@UAE_NXZ) C:\SDK\hugin20092_build\src\tools\Release\vig_optimize.exe : fatal error LNK1120: 1 unresolved externals For the record libpano is at revision 1071. Assuming this reports helps development, Regards, Ad Huikeshoven --~--~-~--~~~---~--~~ 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: Seg-Fault - Build 4421, 20090914
Am Samstag 19 September 2009 schrieb Kornel Benko: Am Samstag 19 September 2009 schrieb Kornel Benko: Am Samstag 19 September 2009 schrieb Yuval Levy: Bruno Postle wrote: I don't build with LAPACK, i.e. can you try building with: I do, and it does not crash. Ubuntu 9.04 32 bit. Yuv I use LAPACK too. But now, as soon as I open a project, hugin crashes. (Align images after loading is _not_ checked) It is independent of creating libpano13 with autotools, or with cmake. Kornel Verified that revision 4432 does not crash. (svn up -r4432 ...) Kornel Sorry, I cannot reproduce anymore. At the time of crashes i got this output: ... f58b5f63000-7f58b5fa r-xp 08:01 12083347 /lib/libdbus-1.so.3.4.0 7f58b5fa-7f58b61a ---p 0003d000 08:01 12083347 /lib/libdbus-1.so.3.4.0 7f58b61a-7f58b61a1000 r--p 0003d000 08:01 12083347 /lib/libdbus-1.so.3.4.0 7f58b61a1000-7f58b61a2000 rw-p 0003e000 08:01 12083347 /lib/libdbus-1.so.3.4.0 7f58b61a2000-7f58b61b7000 r-xp 08:01 2041402 /usr/lib/libgvfscommon.so.0.0.0 7f58b61b7000-7f58b63b7000 ---p 00015000 08:01 2041402 /usr/lib/libgvfscommon.so.0.0.0 7f58b63b7000-7f58b63b8000 r--p 00015000 08:01 2041402 /usr/lib/libgvfscommon.so.0.0.0 7f58b63b8000-7f58b63b9000 rw-p 00016000 08:01 2041402 /usr/lib/libgvfscommon.so.0.0.0 7f58b63ca000-7f58b63e4000 r--s 08:01 2310911 /usr/share/mime/mime.cache 7f58b63e4000-7f58b63e5000 r--s 08:31 28737812 /mnt/usr2/kornel/.local/share/mime/mime.cache 7f58b63e5000-7f58b63e6000 r--p 08:01 2549093 /usr/share/locale-langpack/en_GB/LC_MESSAGES/atk10.mo 7f58b63e6000-7f58b6404000 r-xp 08:01 2072650 /usr/lib/gio/modules/libgvfsdbus.so 7f58b6404000-7f58b6603000 ---p 0001e000 08:01 2072650 /usr/lib/gio/modules/libgvfsdbus.so 7f58b6603000-7f58b6604000 r--p 0001d000 08:01 2072650 /usr/lib/gio/modules/libgvfsdbus.so 7f58b6604000-7f58b6605000 rw-p 0001e000 08:01 2072650 /usr/lib/gio/modules/libgvfsdbus.so 7f58b6605000-7f58b6665000 rw-s 00:09 14024747 /SYSV (deleted) 7f58b6665000-7f58b000 rw-s fd001000 00:0e 7172 /dev/nvidia0Abort (core dumped) but now nothing. So not hugin was aborting but nvidia. Don't have a clue, why it stopped. Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: enblend --verbose --version / enblend image cache
J. Schneider wrote: hugin 2009.2.0.4352 build by Ad. Afaik Ad does not yet put the new Enblend 4.0 pre-release in his installer. Yes. The manual mentioned on Harry's site is for the 4.0 pre-release that is bundled with the OSX version of Hugin. This manual is for Enblend (version 3.2-staging-rev343, 12 August 2009), it says. But there may have been more changes in between. Anyway the confusion stays about which entries get respected in which case and combination and why. At the moment I believe: Those in the preferences should be valid for all new projects and all projects that don't get individual settings. It seems to be a bug that they are not respected. Those accessible from the stitcher tab should be project specific and override the general ones from the preferences. If so this should be be clearly understandable from the GUI text. At the moment these settings are kept between sessions - which is not what I expected but it's a workaround for the preferences that are not respected. 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] Build 20090918
Friday's build was good. All other older builds I consider moot at this point. Enblend hg-4.x (20090918) LibPano13 Beta 2 svn-1064 (20090918) Hugin 2.x Beta 4 svn-4456 (20090918) AutoPano-Sift-C svn-4456 (20090918) Image ExifTool 7.94 (20090914) PanoMatic 0.9.4 (20090914) Thanks. I'll keep doing nightly builds (Ubuntu 9.04). Dale _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009 --~--~-~--~~~---~--~~ 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: enblend --verbose --version / enblend image cache
2009/9/19 J. Schneider j-schn...@gmx.de J. Schneider wrote: hugin 2009.2.0.4352 build by Ad. Afaik Ad does not yet put the new Enblend 4.0 pre-release in his installer. Yes. The manual mentioned on Harry's site is for the 4.0 pre-release that is bundled with the OSX version of Hugin. This manual is for Enblend (version 3.2-staging-rev343, 12 August 2009), it says. But there may have been more changes in between. Hi Joachim, You are right as such that the documents themselves mention version 3.2-staging-rev343, 12 August 2009. It actually means 3.2 and a lot of developments further. The webpage itself says: *Note: These documents describe features that are not available in the 3.2 version of enblend and enfuse. These documents can be considered as early version 4.0 documents, even though version 4.0 is not released yet. The development tree is currently in a state of bugfixing before release*. When being busy with such things it is very obvious. I now understand that that's not the case for an end-user. I will update the documentation and manually add some explanation. I might also add some warning like Note that these versions from enblend/enfuse might or might not be delivered with your version of Hugin., or something like that. The documents are automatically generated from source code. There have been some changes to the code and a lot of changes for the building (switching to cmake), but not in the documentation since 12 August 2009. 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: 4 fatal errors
thanks for the report, Ad. It surely helps. have you tried from scratch, or is this the automated script? I will have access to my windows box only Sunday night late or Monday (and my Hugin build chain is anyway not up to date). Can anybody else with a Windows tool chain confirm? Yuv Ad Huikeshoven wrote: Hi Yuv, The number of fatal errors while trying to compile has doubled this week (please read as as statement of fact and nothing else). As requested I sent the error messages I could retrieve: First Creating library C:\SDK\hugin20092_build\src\tools\Release\autooptimiser.lib and object C:\SDK\hugin20092_build\src\tools\Release\autooptimiser.exp autooptimiser.obj : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function _main huginbase.lib(PTOptimizer.obj) : error LNK2001: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) C:\SDK\hugin20092_build\src\tools\Release\autooptimiser.exe : fatal error LNK1120: 1 unresolved externals Second Creating library C:\SDK\hugin20092_build\src\hugin1\hugin\Release\hugin.lib and object C:\SDK\hugin20092_build\src\hugin1\hugin\Release\hugin.exp OptimizePanel.obj : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function protected: void __thiscall OptimizePanel::runOptimizer(class std::set,class std::allocator const ) (?runoptimi...@optimizepanel@@iaexabv?$...@iu?$less@i...@std@@v?$alloca...@i@2@@std@@@Z) huginbase.lib(PTOptimizer.obj) : error LNK2001: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) C:\SDK\hugin20092_build\src\hugin1\hugin\Release\hugin.exe : fatal error LNK1120: 1 unresolved externals Third Creating library C:\SDK\hugin20092_build\src\tools\Release\tca_correct.lib and object C:\SDK\hugin20092_build\src\tools\Release\tca_correct.exp tca_correct.obj : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function int __cdecl optimize_old(class HuginBase::Panorama ) (?optimize_old@@yahaavpanor...@huginbase@@@Z) C:\SDK\hugin20092_build\src\tools\Release\tca_correct.exe : fatal error LNK1120: 1 unresolved externals Fourth Creating library C:\SDK\hugin20092_build\src\tools\Release\vig_optimize.lib and object C:\SDK\hugin20092_build\src\tools\Release\vig_optimize.exp huginbase.lib(PTOptimizer.obj) : error LNK2019: unresolved external symbol void __cdecl HuginBase::PTools::optimize(class HuginBase::PanoramaData ,char const *) (?optim...@ptools@HuginBase@@yaxaavpanoramad...@2@p...@z) referenced in function public: virtual bool __thiscall HuginBase::PTOptimizer::runAlgorithm(void) (?runalgori...@ptoptimizer@HuginBase@@UAE_NXZ) C:\SDK\hugin20092_build\src\tools\Release\vig_optimize.exe : fatal error LNK1120: 1 unresolved externals For the record libpano is at revision 1071. Assuming this reports helps development, Regards, Ad Huikeshoven --~--~-~--~~~---~--~~ 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: Build 20090918
Thanks for the report, Dale. Dale Beams wrote: Friday's build was good. All other older builds I consider moot at this point. just because it builds/works for you it does not mean that it is good. and the opposite is true as well. there are many reasons, known and unknown, why a build works or fails. the first thing I do when I have an error is to note down the details. Then I uninstall everything, wipe out my source code folders and build folders and start a clean build from scratch. had I not done this, I would have had a number of conflicts / bugs to report - e.g. at some point I installed libpano13 that is standard with Ubuntu 9.04 and was missing the Pannini and other newer projections and of course I feared a regression. As I said, making a truly clean slate helped. Thanks. I'll keep doing nightly builds (Ubuntu 9.04). please do - thorough feedback is always helpful. 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: Integration Queue - how do we add features to trunk and to release
On Sat 19-Sep-2009 at 14:05 -0400, Yuval Levy wrote: Bruno Postle wrote: In principle it should only remove such a point if it was inconsistent with the rest of the points - i.e. if was 'bad'. sometimes the manually added point is what the user intends - and it is the rest of the points which are 'bad'. Good or bad is very subjective... Yes probably cpclean should only work with the Align... button immediately after running a control point generator. If there are already points in the project then you should have to go to the Images tab an click the button to run it. -- 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: problem with align_image_stack
On Sat 19-Sep-2009 at 18:13 +0200, J. Schneider wrote: Bruno Postle schrieb: Yes, try this entry in the Control point generator preferences: Align image stack align_image_stack -f %v -p %o %i Thank you! it works. Just the number of cps to generate per pair (set on the image tab) is not handed to align_image_stack, so it always adds several hundred. You can control the number of points with the align_image_stack -c parameter: -f %v -c %p -p %o %i ..but according to the align_image_stack usage this will actually generate 25x the specified numer of points, i.e. specify 10 and you will get 250 points, specify 1 and you will 25 points. -- 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] Slow Manual Point Addition
With the new hugin (svn) etc. manually adding points went from a seconds to minutes. So long one could get coffee, and the paper at the same time. _ Microsoft brings you a new way to search the web. Try Bing™ now http://www.bing.com?form=MFEHPGpubl=WLHMTAGcrea=TEXT_MFEHPG_Core_tagline_try bing_1x1 --~--~-~--~~~---~--~~ 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] HDR
HDR is failing (perhaps - hasn't completed yet) on build 20090918 Can't locate File/RandomAccess.pm in @INC (@INC contains: /usr/local/bin/lib /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/local/share/perl/5.10.0/Image/ExifTool.pm line 21. BEGIN failed--compilation aborted at /usr/local/share/perl/5.10.0/Image/ExifTool.pm line 21. Compilation failed in require at /usr/local/bin/exiftool line 28. BEGIN failed--compilation aborted at /usr/local/bin/exiftool line 28. make: [courthouse_stack_ldr_0006.tif] Error 2 (ignored) I assume that Hugin now has an additional dependency? _ Bing™ brings you maps, menus, and reviews organized in one place. Try it now. http://www.bing.com/search?q=restaurantsform=MLOGENpubl=WLHMTAGcrea=TEXT_MLOGEN_Core_tagline_local_1x1 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
