[hugin-ptx] Re: Windows 2009.2 installer package: please test
On 31 Oct, 00:59, Yuval Levy goo...@levy.ch wrote: namklim wrote: The project.pto file for the images in the long path directory works without any problems when run with the Ubuntu version of Hugin. you may want to checkhttp://wiki.panotools.org/Hugin_FAQ#Special_Characters_in_Paths while some special characters are better supported in some O/S than others, this is not dependent on Hugin and to stay on the safe side, the above listed characters should be avoided. At some point we may introduce checks to refuse some of them in the project files. Yuv I haven't added any control characters. The path is a normal Windows path. The .pto.mk file was generated by Hugin and it appears Hugin has added the extra character (if that is the problem?). As I said, the batch processor works without any changes. --~--~-~--~~~---~--~~ 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-2009.4 win32 (cygming) build available - please test
Hi all, hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available at ftp://hugin.panotools.org/public_html/testing/hugin/. It works out of the box -- just unzip and run hugin/bin/hugin.exe -- and there are no dependencies on either cygwin or the location it unzips to. In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is available for people who aren't troubled by patent issues. Just unzip it to the same directory that the hugin-*.zip went to and hugin should be able to use it (it's not a stand-alone executable and shares the same directory hierarchy). Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the master Makefile and patches which were used to build and package hugin/ autopano. It would be interesting if people with real workflows could try it out and see (a) whether it really works and (b) how it compares to the MSVC version -- I my biggest panorama only has like seven photos in it, and I don't usually play with multiple lenses or stacks. The uploaded version uses - hugin-2009.4.0_rc2 - enblend-enfuse-3.2 - libpano13-2.9.15_beta3 - autopano-sift-C-2.5.1_rc2 I'm willing to try other versions as appropriate, but wanted to close the loop first (in particular, enblend-4.0 sounds like it needs some integration work still). Regards, Ryan --~--~-~--~~~---~--~~ 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-2009.4 win32 (cygming) build available - please test
One quick addendum: I just figured out that you have to enable GPU stitching explicitly... and it fails on my machine, reporting that a bunch of shaders are missing (GL_ARB_fragment_shader, etc). I suspect that it's just my laptop's underpowered graphics card, but it would be good for somebody with a decent GPU to verify that GPU stitching works. GPU-assisted preview seems to work fine for me -- enabling photometrics in 0.8 overwhelms my machine, and other than a brief spike to get it started, 2009.4 doesn't use any CPU as I drag the image around and change crop settings. Regards, Ryan On Oct 31, 10:41 am, Ryan scov...@gmail.com wrote: Hi all, hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available atftp://hugin.panotools.org/public_html/testing/hugin/. It works out of the box -- just unzip and run hugin/bin/hugin.exe -- and there are no dependencies on either cygwin or the location it unzips to. In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is available for people who aren't troubled by patent issues. Just unzip it to the same directory that the hugin-*.zip went to and hugin should be able to use it (it's not a stand-alone executable and shares the same directory hierarchy). Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the master Makefile and patches which were used to build and package hugin/ autopano. It would be interesting if people with real workflows could try it out and see (a) whether it really works and (b) how it compares to the MSVC version -- I my biggest panorama only has like seven photos in it, and I don't usually play with multiple lenses or stacks. The uploaded version uses - hugin-2009.4.0_rc2 - enblend-enfuse-3.2 - libpano13-2.9.15_beta3 - autopano-sift-C-2.5.1_rc2 I'm willing to try other versions as appropriate, but wanted to close the loop first (in particular, enblend-4.0 sounds like it needs some integration work still). Regards, Ryan --~--~-~--~~~---~--~~ 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-2009.4 win32 (cygming) build available - please test
Hello Ryan As a regular reader of this groupI tried to download your version and autopano SIFT, but I don't have access to the FTP server. Need a user name and password for getting access? How can I get that? Kind regards, Henk Tijdink On 31 okt, 10:53, Ryan scov...@gmail.com wrote: One quick addendum: I just figured out that you have to enable GPU stitching explicitly... and it fails on my machine, reporting that a bunch of shaders are missing (GL_ARB_fragment_shader, etc). I suspect that it's just my laptop's underpowered graphics card, but it would be good for somebody with a decent GPU to verify that GPU stitching works. GPU-assisted preview seems to work fine for me -- enabling photometrics in 0.8 overwhelms my machine, and other than a brief spike to get it started, 2009.4 doesn't use any CPU as I drag the image around and change crop settings. Regards, Ryan On Oct 31, 10:41 am, Ryan scov...@gmail.com wrote: Hi all, hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available atftp://hugin.panotools.org/public_html/testing/hugin/. It works out of the box -- just unzip and run hugin/bin/hugin.exe -- and there are no dependencies on either cygwin or the location it unzips to. In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is available for people who aren't troubled by patent issues. Just unzip it to the same directory that the hugin-*.zip went to and hugin should be able to use it (it's not a stand-alone executable and shares the same directory hierarchy). Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the master Makefile and patches which were used to build and package hugin/ autopano. It would be interesting if people with real workflows could try it out and see (a) whether it really works and (b) how it compares to the MSVC version -- I my biggest panorama only has like seven photos in it, and I don't usually play with multiple lenses or stacks. The uploaded version uses - hugin-2009.4.0_rc2 - enblend-enfuse-3.2 - libpano13-2.9.15_beta3 - autopano-sift-C-2.5.1_rc2 I'm willing to try other versions as appropriate, but wanted to close the loop first (in particular, enblend-4.0 sounds like it needs some integration work still). Regards, Ryan --~--~-~--~~~---~--~~ 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-2009.4 win32 (cygming) build available - please test
Henk Tijdink wrote: Hello Ryan As a regular reader of this groupI tried to download your version and autopano SIFT, but I don't have access to the FTP server. Need a user name and password for getting access? How can I get that? http://hugin.panotools.org/testing/hugin/ the ftp URL is only for those uploading. and it would be good if FTP would be replaced by SFTP, SCP, or rsync over SSH. 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: *IMPORTANT* Credits
Bruno Postle wrote: I really think the list of authors needs to be in the tarball, the copyright license needs to be accompanied by the 'owners'. I'm not happy with the current solution either, but it is better than the previous one. Nobody looks at AUTHORS in the tarball, not even Linux users that get the software through their package manager. The solution is to put it in the About window (which is also delivered in the tarball and is visible in the GUI application), but it has reached its useful limits. Will think of something. Please use URIs that don't expose the filename like (most of) the rest of the site e.g: http://hugin.sourceforge.net/community/authors/ I thought the URIs that don't expose the filename are for pages intended to be translated? I intentionally do not want a translation of this page. Maintenance nightmare. 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: Windows 2009.2 installer package: please test
namklim wrote: I haven't added any control characters. The path is a normal Windows path. The .pto.mk file was generated by Hugin and it appears Hugin has added the extra character (if that is the problem?). can you post the .pto and .pto.mk files somewhere? Ideally in a bug report at [0] with a complete description of the case. These things get lost in time in the mailing list. [0] https://sourceforge.net/tracker/?group_id=77506atid=550441 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: hugin-2009.4 win32 (cygming) build available - please test
On Oct 31, 1:14 pm, Henk Tijdink h.tijd...@gmail.com wrote: Hello Ryan As a regular reader of this groupI tried to download your version and autopano SIFT, but I don't have access to the FTP server. Need a user name and password for getting access? How can I get that? That's a very good question... I had assumed it would either be world- readable or available through http, but I guess not. --~--~-~--~~~---~--~~ 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-2009.4 win32 (cygming) build available - please test
Correction to the URLs: http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cygming-bin.zip http://hugin.panotools.org/testing/hugin/autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cygming-build.tar.gz Thanks, Ryan On Oct 31, 10:41 am, Ryan scov...@gmail.com wrote: Hi all, hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available atftp://hugin.panotools.org/public_html/testing/hugin/. It works out of the box -- just unzip and run hugin/bin/hugin.exe -- and there are no dependencies on either cygwin or the location it unzips to. In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is available for people who aren't troubled by patent issues. Just unzip it to the same directory that the hugin-*.zip went to and hugin should be able to use it (it's not a stand-alone executable and shares the same directory hierarchy). Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the master Makefile and patches which were used to build and package hugin/ autopano. It would be interesting if people with real workflows could try it out and see (a) whether it really works and (b) how it compares to the MSVC version -- I my biggest panorama only has like seven photos in it, and I don't usually play with multiple lenses or stacks. The uploaded version uses - hugin-2009.4.0_rc2 - enblend-enfuse-3.2 - libpano13-2.9.15_beta3 - autopano-sift-C-2.5.1_rc2 I'm willing to try other versions as appropriate, but wanted to close the loop first (in particular, enblend-4.0 sounds like it needs some integration work still). Regards, Ryan --~--~-~--~~~---~--~~ 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: Windows 2009.2 installer package: please test
On 31 Oct, 13:38, Yuval Levy goo...@levy.ch wrote: namklim wrote: I haven't added any control characters. The path is a normal Windows path. The .pto.mk file was generated by Hugin and it appears Hugin has added the extra character (if that is the problem?). can you post the .pto and .pto.mk files somewhere? Ideally in a bug report at [0] with a complete description of the case. These things get lost in time in the mailing list. [0]https://sourceforge.net/tracker/?group_id=77506atid=550441 Yuv OK - I've now found the problem. I'd changed my import-from-camera program and there was a space in front of the camera jpg files. It just didn't show up when looking at the directory as all files looked the same. . I first loaded the files into Hugin 0.8 running under Ubuntu and they processed without any problems even with the space in front of the file names. I then loaded the project saved by the Ubuntu Hugin into this Windows Hugin test version and it failed with the error indicated (and also failed in the Windows Hugin v0.7 and 0.8 when I tested it in those) So there is a difference in the behaviour of the Ubuntu and Windows versions when the jpg file starts with a space. Do you still want a bug report filed? --~--~-~--~~~---~--~~ 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: Exif Information. Automatic Computing
Thanks, I'll try your advice. On 25 oct, 19:40, Nicolas Pelletier nicolas.pellet...@gmail.com wrote: If the information is not in the EXIF, then it is not provided to the software, and it has to guess or optimize to what seems the best value. Typical algorithms are very good at finding those values (both Hugin and Autopano according to your results). I've not played with autopano, but I can tell that hugin can figure out what lens you used (Field of View and focal length). The way it will do so is by starting with a value that may not be exact, and converge to the best value it can. With hugin, you must give it a starting value (even quite imprecise) and it will figure out the values. I remember one time I shot a pano and gave hugin the information from the wrong lens. After optimization, it had changed everything back to what it should. My recommendation, put what you think and let hugin figure out the details! When you optimize, FOV may not be checked as something that can be changed, so if it does not work, go on the optimizer tab to see if FOV is indeed checked. nick On Sun, Oct 25, 2009 at 4:47 AM, villa fjgarc...@gmail.com wrote: Hi all I've been evaluating several programs for mosaic generation, one of them is free (hugin) while the other is commercial (Autopano Pro). Both are very good but the Autopano Pro has a feature that I find very interesting but I don't really know how it works. When you upload photos to hugin if the photos don't have EXIF information you need to include the hfov and the focal length to continue the process, but the Autopano Pro if the photos don't have EXIF information it seems that somehow calculates the hfov and the focal length. This information autopano computes is provided subsequently to hugin and this program works perfectly, therefore the values are correct. My question is if there a technique or algorithm that allows to obtain this information if not included in the EXIF Best regards. --~--~-~--~~~---~--~~ 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] Temp files issues
Hi all, Two questions: 1. 2009.4 leaves all the temp files laying around after a stitch completes, where the old version used to delete them afterwards. Is this new behavior a bug or a feature? It might make some sense if the GUI were willing to let the makefile track dependencies, but it just overwrites all the files anyway. Note that manually calling make clean on the .pto.mk file does the right thing, but only if the file which was stitched shares the same root as the .pto. 2. In both 2009.4 and the older windows version, the temp files go wherever the final stitched image is being sent. This can be a major pain when sending the final image to a (slow) shared filesystem; I really want the temp files to go to local storage, and the stitched image to go in the image archive where it belongs. Thoughts? Ryan --~--~-~--~~~---~--~~ 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: *IMPORTANT* Credits
On Sat 31-Oct-2009 at 08:36 -0400, Yuval Levy wrote: Please use URIs that don't expose the filename like (most of) the rest of the site e.g: http://hugin.sourceforge.net/community/authors/ I thought the URIs that don't expose the filename are for pages intended to be translated? I intentionally do not want a translation of this page. Maintenance nightmare. Pages that are not intended for translation are named index.shtml which is handled by the apache DirectoryIndex directive so the filename doesn't appear. Pages for translation are en.shtml which could also be handled by DirectoryIndex, but I never got around to it and have a RedirectMatch instead. -- 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: Windows 2009.2 installer package: please test
On Sat 31-Oct-2009 at 08:53 -0700, namklim wrote: OK - I've now found the problem. I'd changed my import-from-camera program and there was a space in front of the camera jpg files. It just didn't show up when looking at the directory as all files looked the same. So there is a difference in the behaviour of the Ubuntu and Windows versions when the jpg file starts with a space. The problem is that \ is the standard character used for escaping 'special' characters such as a space, it is also used by windows for marking folders. It works most of the time on Windows, a \ followed by a 'normal' character is understood to be a folder, but if you start a folder or filename with a space things fall apart because you get this ambiguous '\\ ' stuff. Lukáš figured out that we can fix this by using / as a folder delimiter for all platforms, but nobody has done the work yet to make the switch. -- 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: Temp files issues
On Nov 1, 12:08 am, Bruno Postle br...@postle.net wrote:
On Sat 31-Oct-2009 at 13:05 -0700, Ryan wrote:
1. 2009.4 leaves all the temp files laying around after a stitch
completes, where the old version used to delete them afterwards. Is
this new behavior a bug or a feature?
There has been no change as far as I know, the behavior from the
GUI should be:
All intermediate files (including a temporary .pto .pto.mk pair) are
created in a temporary folder and deleted afterwards. Unless you
specify 'Remapped Images', in which case some of them are created in
the output folder and saved.
Hmm. My usual workflow is to create the .pto in the folder that
contains photos I want to stitch, and then send stitched results there
as well. During a stitch, all the files are created in the same
working directory (except, apparently, hug7E.tmp, whatever that is).
Afterward everything gets deleted except for the .pto, .pto.mk, and
the final stitched image. With my 2009.4 build, the tmp files no
longer get deleted. Here's an extract of the output from hugin-0.8;
the same happens with 2009.4:
C:\Program\ Files\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o tmp -
i 0 C:\DOCUME~1\Ryan\LOCALS~1\Temp\hug7E.tmp
C:\Program\ Files\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o tmp -
i 1 C:\DOCUME~1\Ryan\LOCALS~1\Temp\hug7E.tmp
C:\Program\ Files\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o tmp -
i 2 C:\DOCUME~1\Ryan\LOCALS~1\Temp\hug7E.tmp
C:\Program\ Files\Hugin\bin\enblend --compression 85 -f4750x1485+74+0 -
o tmp.jpg tmp.tif tmp0001.tif tmp0002.tif
Loading next image: tmp.tif
Loading next image: tmp0001.tif
Creating blend mask: 1/4 2/4 3/4 4/4
Optimizing 1 distinct seam.
The tmp*.tif mentioned above are created in the final destination dir,
not in ...\Temp\ (you can see them appear/disappear if you have the
folder open) -- there's plenty of time when this happens over a slow
network share to my wife's laptop. When stitching in 2009.4 the
tmp*.tif files remain. Then, next time you stitch, it pops up a list
of all those temp files and asks if you want to overwrite them ('no'
cancels the stitch).
Can anyone else verify this behavior? Is it a win32 problem only?
There is a bug where this temporary folder is always the system
default and isn't changed by the Hugin tempDir Preference setting.
A workaround (on Linux at least) is to set TMPDIR in your
environment. There will be an equivalent Windows workaround, but I
don't know what it is.
Hugin seems able to find my temp folder... it just doesn't put many
files into it.
When stitching on the command-line, all intermediate files are
created in the same folder as the output and are only deleted if you
supply the 'clean' make target.
That makes sense, but I've only ever used the GUI.
Regards,
Ryan
--~--~-~--~~~---~--~~
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-2009.4 win32 (cygming) build available - please test
Hi Ryan, I have finished running the first test case for hugin-2009.4.0_rc2- win32-cygming-bin.zip. Platform: Windows Vista 64bit on an i7 with 12GB memory and an ATI Radeon HD 4800 series graphics card. Project: 31 image 360x180 equirectangular projection aligned with 7,129 control points. No exposure bracketing in this project. Observations: GUI - Looks good. Only concern found is it is in English even when Chinese is selected. Load images - No issues Add Control Points - I used Autopano-sift-c with --maxdim 4000 -- projection %f,%v --maxmatches %p %o %i arguments. It worked fine and added as many control points as 2009.2 (Allard's build). I found a previous build of 2009.4 did not generate any control points when -- maxdim 4000 is specified, but this build doesn't have the issue/ Align - No problem Fine Tune All control points - No issues Control Point table - No problem, I removed bad control points with no issues Optimizer - No problems for position and everything Exposure - No issues with Low Dynamic range 1000 points per image. Stitching - Used Calculate Optimal Size - 15,288 x 7,559. Problems in stitching a Blended Panorama for both with and without GPU: Without GPU - Out of memory error even with the arguments: -m 2000 - b 4000 With GPU - No errors, but during enblend most images were indicated as redundant and not included in final image. Final image was a large file with the dimensions specified in Calculate Optimal Size, but was transparent except for an area the size and shape of the image anchored for position. The area was the same size as that component image, but it had other images blended incorrectly into it. Let me know if you need any other details, Regards, Rick On Nov 1, 9:22 am, RueiKe ruei...@yahoo.com wrote: Hi Ryan, I am still working through my test case, but one observed issue so far is that the interface is in English even when I select Traditional Chinese. I am running this out of the directory where I unzipped it to, so maybe this is part of the issue. Regards, Rick On Oct 31, 8:51 pm, Ryan scov...@gmail.com wrote: Correction to the URLs:http://hugin.panotools.org/testing/hugin/hugin-2009.4.0_rc2-win32-cyg.. Thanks, Ryan On Oct 31, 10:41 am, Ryan scov...@gmail.com wrote: Hi all, hugin-2009.4.0-rc2-win32-cygming-bin.zip is now available atftp://hugin.panotools.org/public_html/testing/hugin/. It works out of the box -- just unzip and run hugin/bin/hugin.exe -- and there are no dependencies on either cygwin or the location it unzips to. In addition, autopano-sift-C-2.5.1_rc2-win32-cygming-bin.zip is available for people who aren't troubled by patent issues. Just unzip it to the same directory that the hugin-*.zip went to and hugin should be able to use it (it's not a stand-alone executable and shares the same directory hierarchy). Finally, hugin-2009.4.0_rc2-win32-cygming-build.tar.gz contains the master Makefile and patches which were used to build and package hugin/ autopano. It would be interesting if people with real workflows could try it out and see (a) whether it really works and (b) how it compares to the MSVC version -- I my biggest panorama only has like seven photos in it, and I don't usually play with multiple lenses or stacks. The uploaded version uses - hugin-2009.4.0_rc2 - enblend-enfuse-3.2 - libpano13-2.9.15_beta3 - autopano-sift-C-2.5.1_rc2 I'm willing to try other versions as appropriate, but wanted to close the loop first (in particular, enblend-4.0 sounds like it needs some integration work still). Regards, Ryan- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
