On 6 March 2012 01:05, JohnG <[email protected]> wrote: > Thank you Lukas, > >> ... copying enblend and enfuse executable from the older >> build to your current installation should be enough. > > Yes that seems to have done the trick; at least on my "awkward.pto" - > testing memory limits obviously requires big projects which takes a > long time ...
I'm glad to hear that… > >> IIRC the reason why the new build has the image cache disabled is that >> the image cache sometimes causes black lines with large panoramas and >> it doesn't work with multithreading. > > If the Hugin FAQ [1] is still up-to-date, enfuse.exe enables > image_cache and enfuse_openmp.exe doesn't. I found copies of both in > my "program files/Hugin/bin". > > Though I haven't tried it, perhaps setting enfuse_openmp as the > "alternative" to enfuse in Preferences/Programs dialogue might be a > more obvious way to disable image_cache when necessary ? The same > trick might also work for enblend.exe and enblend_openmp.exe ? > > [1] > http://wiki.panotools.org/Hugin_FAQ#Selecting_right_version_of_enblend-enfuse_binary_for_Windows > > Many thanks for your help, > John. > Well, there are separate versions for enblend if you download it from enblends website [1]. They should behave as you describe. However I'm not of a much help when it comes to windows binaries, since I don't use Windows. Lukas [1] http://sourceforge.net/projects/enblend/files/enblend-enfuse/enblend-enfuse-4.0/enblend-enfuse-4.0-win32.zip/download -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
