[hugin-ptx] Re: *IMPORTANT* Credits
prokoudine wrote: > On 26 окт, 16:40, Yuval Levy wrote: > >> Second, we need to make sure that people's contributions are properly >> listed. > > What did you mean with "Initial Russian translation"? Is there some > other newer translation I'm not aware of? :) not yet, but wouldn't it be nice to have offsprings ;-) ? the point is that the contributor making the "initial" or "original" (I have not been very consistent, help welcome) translation has done the big job opening the way for further contributions. 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
Erik Krause wrote: > However, my main > intent where the enfuse droplets, the enblend ones where a mere byproduct... ...I finally managed to change the entry myself... best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ 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: Smartblend source code not yet released
Bart van Andel wrote: > I just got a reply to my previously sent email (after sending a > reminder today) about the Smartblend sources. Unfortunately, we will > have to wait a bit longer. A pity. However, perhaps it is worthwhile to have a look at how smartblend searches the seam. About two weeks ago Pablo, Andrew and Rogier discussed how the best seams line should be computed. smartblend can be called with the parameter --seamverbose in order to output images that contain the seam line and more information. Could well be someone experienced can tell from the seam line how the algorithm works. Those additional parameters are mentioned in the readme file which is contained in the smartblend .zip best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ 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: Smartblend source code not yet released
Bart, Thank you for your work on this. I'm hoping that his customers won't object either. Dale > Date: Tue, 3 Nov 2009 08:55:44 -0800 > Subject: [hugin-ptx] Smartblend source code not yet released > From: bavanan...@gmail.com > To: hugin-ptx@googlegroups.com > > > I just got a reply to my previously sent email (after sending a > reminder today) about the Smartblend sources. Unfortunately, we will > have to wait a bit longer. I quote: > > "Hi Bart. > > I have to confirm agreement with SB customrs before to publish SB > sources. It is in process. > In near future SB sources will not be availible. Sorry." > > Let's hope Michael's customers won't object against releasing SB > sources into the public. To be continued... > > -- > Bart > > On 28 sep, 15:54, Bart van Andel wrote: > > About a year and a half ago, this was also the topic of a thread here > > [1]. Both Yuv and myself have emailed MichaelNorel(the author) about > > releasing the source code of SmartBlend, and he replied back then that > > he'd "At least i'll find time to publicsh sources." So far he hasn't, > > unfortunately, but maybe he has more time to spend now than he had > > back then. I'll mail him again and post his reply here (unless he > > responds here himself, which I actually hope). > > > > By the way, the website you've mentioned does not contain the most > > recent version, which is 1.2.5. This newer version can be found at the > > PanoTools wiki [2]. > > > > [1]http://groups.google.com/group/hugin-ptx/browse_thread/thread/b11d91a... > > [2]http://wiki.panotools.org/SmartBlend > > > > -- > > Bart > > _ Windows 7: Unclutter your desktop. http://go.microsoft.com/?linkid=9690331&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009 --~--~-~--~~~---~--~~ 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 26 окт, 16:40, Yuval Levy wrote: > Second, we need to make sure that people's contributions are properly > listed. What did you mean with "Initial Russian translation"? Is there some other newer translation I'm not aware of? :) Alexandre --~--~-~--~~~---~--~~ 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 Rick, I suspect the dynamic libraries in my distribution are the problem: looking at the process map for hugin while running shows DLLs scattered all over the address space. The biggest gap is only about 1GB, which would explain why you couldn't allocate a bigger chunk than that. Unfortunately, it's surprisingly hard to make a pure static build of hugin under mingw32 -- cmake *really* wants to use dlls and things break without them. I muddled through and got it to compile but the resulting binaries were so big I ran out of disk space (laptop's almost full anyway)... have to delete some files and try again. Given that GPU blending also works on Allard's build it might be best to stick with it for now. Regards, Ryan On Nov 3, 12:37 pm, RueiKe wrote: > Hi Ryan, > > I have run this test project with Allard's build of 2009.2 SVN4461 and > had no issues with or without the GPU option. Both produced identical > 450MB tif tiles. I used "-m 3000" for enblend. > > Regards, > Rick > > On Nov 3, 6:59 am, RueiKe wrote: > > > Ryan, > > > Re OoM: My test run with "-m 1000" did not get the out oe memory > > error, but afterward I tested again with "-m 2000" and got the same > > out of memory error - St9bad_alloc. I have always used "-m 2000" or "- > > m 3000" in the past with 32bit builds. I use "-m 8000" for 64bit > > builds. One other error is after making the final image with "-m > > 1000", it gets an error when deleting the working files. > > > I will try 2009.2 later tonight for the GPU issue... > > > Regards, > > Rick > > > On Nov 2, 11:11 pm, RueiKe wrote: > > > > Hi Ryan, > > > > Re OoM: I was not able to get enblend to work, even by setting "-m > > > 2000". I usually use "-m 3000" for 32bit windows version. I am > > > trying it again with "-m 1000"... I will report back in the morning. > > > I don't know of a way to change disk cache settings. I assumed hugin > > > just used as much as it needed. > > > > Re GPU: SInce enblend did not run on most images, I asumed the problem > > > was with Nona. If this feature is available in Allard's 2009.2 build, > > > I could give it a try tomorrow. > > > > Regards, > > > Rick > > > > On Nov 2, 10:22 pm, Ryan wrote: > > > > > Hi Rick, > > > > > Re: i18n: It sounds like wxWidgets+unicode support was the magic > > > > combination -- I strongly suspect somebody just forgot to i18n-ize > > > > those few spots in the GUI. > > > > > Re OoM: I couldn't tell from your previous emails: were you able to > > > > work around the error by setting -m smaller and/or increasing the disk > > > > cache size? > > > > > Re GPU: Yes, the question is whether something is broken about GPU > > > > +enblend+win32. It seems that CPU+enblend+win32 works, and GPU+preview > > > > +win32 works, and GPU+enblend+linux works, which makes me suspect > > > > there's simply a problem with enblend's GPU code under windows. AFAIK > > > > mine is the only enblend+GPU+win32 in the wild. Allard's MSCV 2009.2 > > > > build uses the version of enblend that shipped with 0.7, and the > > > > official 3.2 build from Sourceforge doesn't seem to use GPU (links > > > > only to user32.dll and kernel32.dll). > > > > > If somebody could tell me what it takes to integrate an enblend-4.0 > > > > snapshot with hugin I'm game. I just need to know: > > > > 1. How to download an enblend-4.0 snapshot -- the sourceforge site > > > > doesn't make it obvious > > > > 2. What hugin code needs to change to handle the changes to command- > > > > line args in enblend-4.0 vs older releases. > > > > > Meanwhile, just to be sure, perhaps you could download the official > > > > win32 enblend/enfuse from Sourceforge and see what happens with a GPU > > > > stitch. > > > > > Regards, > > > > Ryan > > > > > On Nov 2, 2:37 pm, RueiKe wrote: > > > > > > Hi Yuv, > > > > > > Yes, that is the option I used for the test case that gave the out of > > > > > memory error. I think Ryan's comment was concerning if the error I > > > > > observed was specific to his build. > > > > > > Regards, > > > > > Rick > > > > > > On Nov 2, 9:24 pm, Yuval Levy wrote: > > > > > > > Hi Rick, > > > > > > > RueiKe wrote: > > > > > > > Re GPU: This is the first time I have tested the GPU option. If > > > > > > > there is another build to try for comparison, just send me a link > > > > > > > and > > > > > > > I will give it a try. > > > > > > > to compare the GPU option with the traditional CPU stitching, just > > > > > > enable/disable GPU stitching in the preferences setting. > > > > > > > Yuv- Hide quoted text - > > > > > - Show quoted text -- 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-pt
[hugin-ptx] Re: hugin-2009.4 win32 (cygming) build available - please test
Hi Ryan, I have run this test project with Allard's build of 2009.2 SVN4461 and had no issues with or without the GPU option. Both produced identical 450MB tif tiles. I used "-m 3000" for enblend. Regards, Rick On Nov 3, 6:59 am, RueiKe wrote: > Ryan, > > Re OoM: My test run with "-m 1000" did not get the out oe memory > error, but afterward I tested again with "-m 2000" and got the same > out of memory error - St9bad_alloc. I have always used "-m 2000" or "- > m 3000" in the past with 32bit builds. I use "-m 8000" for 64bit > builds. One other error is after making the final image with "-m > 1000", it gets an error when deleting the working files. > > I will try 2009.2 later tonight for the GPU issue... > > Regards, > Rick > > On Nov 2, 11:11 pm, RueiKe wrote: > > > > > Hi Ryan, > > > Re OoM: I was not able to get enblend to work, even by setting "-m > > 2000". I usually use "-m 3000" for 32bit windows version. I am > > trying it again with "-m 1000"... I will report back in the morning. > > I don't know of a way to change disk cache settings. I assumed hugin > > just used as much as it needed. > > > Re GPU: SInce enblend did not run on most images, I asumed the problem > > was with Nona. If this feature is available in Allard's 2009.2 build, > > I could give it a try tomorrow. > > > Regards, > > Rick > > > On Nov 2, 10:22 pm, Ryan wrote: > > > > Hi Rick, > > > > Re: i18n: It sounds like wxWidgets+unicode support was the magic > > > combination -- I strongly suspect somebody just forgot to i18n-ize > > > those few spots in the GUI. > > > > Re OoM: I couldn't tell from your previous emails: were you able to > > > work around the error by setting -m smaller and/or increasing the disk > > > cache size? > > > > Re GPU: Yes, the question is whether something is broken about GPU > > > +enblend+win32. It seems that CPU+enblend+win32 works, and GPU+preview > > > +win32 works, and GPU+enblend+linux works, which makes me suspect > > > there's simply a problem with enblend's GPU code under windows. AFAIK > > > mine is the only enblend+GPU+win32 in the wild. Allard's MSCV 2009.2 > > > build uses the version of enblend that shipped with 0.7, and the > > > official 3.2 build from Sourceforge doesn't seem to use GPU (links > > > only to user32.dll and kernel32.dll). > > > > If somebody could tell me what it takes to integrate an enblend-4.0 > > > snapshot with hugin I'm game. I just need to know: > > > 1. How to download an enblend-4.0 snapshot -- the sourceforge site > > > doesn't make it obvious > > > 2. What hugin code needs to change to handle the changes to command- > > > line args in enblend-4.0 vs older releases. > > > > Meanwhile, just to be sure, perhaps you could download the official > > > win32 enblend/enfuse from Sourceforge and see what happens with a GPU > > > stitch. > > > > Regards, > > > Ryan > > > > On Nov 2, 2:37 pm, RueiKe wrote: > > > > > Hi Yuv, > > > > > Yes, that is the option I used for the test case that gave the out of > > > > memory error. I think Ryan's comment was concerning if the error I > > > > observed was specific to his build. > > > > > Regards, > > > > Rick > > > > > On Nov 2, 9:24 pm, Yuval Levy wrote: > > > > > > Hi Rick, > > > > > > RueiKe wrote: > > > > > > Re GPU: This is the first time I have tested the GPU option. If > > > > > > there is another build to try for comparison, just send me a link > > > > > > and > > > > > > I will give it a try. > > > > > > to compare the GPU option with the traditional CPU stitching, just > > > > > enable/disable GPU stitching in the preferences setting. > > > > > > Yuv- Hide quoted text - > > > > - Show quoted text -- 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 -~--~~~~--~~--~--~---
