> Sorry I can't help you here - I'm on Linux and I'm not doing HDR, but > your description of what you are trying to do on a 2G Windows machine > sounds like asking for trouble - you're right insofar as enblend > should use swap space if it can't manage with the memory it has, but I > think it doesn't, and a quick rule-of-thumb calculation I did told me > that your anticipated result would take up just under 2G - by itself.
The enblend bundled in Hugin is some modified or at least recompiled version of enblend 4, it does not have disk cache. I switched it for the original enblend 4 and that does have disk cache and the -m -b parameters work. The panorama from reduced images looks the same on both enblend 4 versions. Version 3.2 looks better, shows more in the output panorama but still has the same errors on the same places, but the black area is smaller. 2GB ram should not be a problem, unless the program tries to do something that the OS doesn't allow (allocating too much memory), otherwise the OS will just swap it, there is enough space for that. > I can help you here: try > > https://bugs.launchpad.net/enblend/+bugs Thanks, I'll give it a try if I pin point something down precisely. > > I'll try different outputs and formats, but it's annoying and takes > > time. > > You could try and create parts of the panorama sequentially, like left > third, middle third and right third, if you have to create a very big > image. I' trying to get a correct result with a smaller amount if images, removing parts of the panorama. Or how can I split the panorama into more parts/jobs? I saw some gigatile around here mentioned to split it into more jobs. I was trying to find something about making and browsing huge giga panoramas, seems like I ran into problems even with just a small HDR panorama :( > IMHO, doing HDR and tonemapping the image is really only necessary for > very special purposes. Usually the results you get from using enblend (ENFUSE) > on the stacks are more pleasing to the eye than tonemapped HDRs. That > way, the processing is possible with less memory consumption - even if > you work in, say, 16 bit TIFF, you still need only about half of what > HDR takes. Yes fused outputs work here. I was making a small panorama only 160° and the HDR was quite some trouble as well but all outputs were correct, just my trouble with masks. Fused output is weird sometimes, or in some parts and I have no control over it. I don't know what the problem with enblend is, LDR is usually ok if I remove the overlapping images but HDR produces errors (black areas) in the output without any warnings. And that is for a 1000x750 images 1/4 of the full size. The images fed into enblend are correct, no black areas. > > Don't they test and debug these tools at all? > > Who is 'they'? We're in FOSS world here. To me 'they' is the guys who > SELL you software that doesn't work, and 'us' is the guys who are > trying to get a good thing going without commercial constraints - and > without commercial rewards either. So it's 'us' debugging and testing > the stuff, and you're welcome to join in. If you're unhappy with what > we have to offer, make it better by getting involved or throw your lot > with the next best free open source panorama package (and when you > find one that's so good you want to settle with it, drop us a line ;-) They = developers of the tools. I don't mind joining in or debugging the problems I encounter, but is there any documentation of the code? That's usually the biggest issue with open source, no documentation :( I already got one idea, putting the images into stacks automatically, it's "real fun" clicking a hundred of images into stacks... Or should I just ignore stacks with HDR and don't use align_image_stack.exe? I doubt that. -- 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
