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 <scov...@gmail.com> 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 <ruei...@yahoo.com> 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 <goo...@levy.ch> 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 - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
