[hugin-ptx] Re: enblend --verbose --version / enblend image cache
On Sep 19, 7:32 pm, J. Schneider j-schn...@gmx.de wrote: I read in the new enblend/enfuse documentation (http://panorama.dyndns.org/EandE-documentation/enblend.html#Tuning-Me... thanks al lot for this!) about how to tune enblend's options to suit my 2GB RAM system. As has been said before, an online documentation may or may not match _your_ program version[s]. The only way to be absolutely and positively sure is to compare the version identifiers of both the binary and the documentation. I have a set of patches here, that will increase the coupling of source-code, configuration, and documentation. * Source-Doc-Coupling: Add syntactic comments to the C++-sources that get included in the Texinfo sources. This allows for easy integration of default values and valid ranges in the manuals. BTW, this patch revealed both, bugs in the code and faulty documentation. * Config-Doc-Coupling: Convert config.h into Texinfo format and included it into enblend.texi and enfuse.texi. With this patch, we can write configuration dependent documentation parts. * Move CACHE_IMAGES into Config: The image-cache feature was defined as an additional command-line switch. Thus, we would not have access to it through the previous patch. This patch moves it into config.h and therefore makes it usable in the documentation. A small drawback of the above changes is that they break vcproj files and very likely also Kornel's painstakingly macgyvered cmake setup. 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). There you go, you found an ancient version and tried novel options on it. Version 3.2 neither has --verbose, only -v, nor has it a verbosity-sensitive version output. 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. Blunder. The documentation _must_ contain all information about a program regardless of the program's actual configuration. Imagine someone who has a variant without image cache and there is no information at all about it in the (admittedly matching) documentation, and she runs out of memory? Currently, the documentation shows her the way out of it: get the variant with image cache. 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. Your test is unreliable. If you want to be sure how Enblend or Enfuse are invoked - call them directly from the command line, - use an absolute path to avoid PATH or shell command hash interference, - ensure you call the intended version with /MY/BIN/DIR/enblend --version or /MY/BIN/DIR/enfuse --version (bordering paranoia, but safe) /Chris --~--~-~--~~~---~--~~ 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
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] 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 -~--~~~~--~~--~--~---
