Thomas, How good a debugger are you? This is a bug where a good programmer/debugger just has to spend a day or two finding/fixing it.
This bug resides in the image library that allows the image to be moved to disk if it becomes too large (I forgot its name). So reducing the output image size will reduce/eliminate the problem. I think there is a dangling pointer or memory corruption problem somehow.... The strategy to finding it would be as follows: * compile your own version from source. * verify it still happens. * Find the smallest example that causes the problem. * verify it doesn't happen when you disable that disk swapping of images. (e.g. add -m <largernumber> on the commandline). * check out valgrind for memory problems. See if it catches something. * start debugging..... -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/721136 Title: enblend creates an unexplainable black area. Status in Enblend: Confirmed Bug description: enblending http://prive.bitwizard.nl/t80001.tif and http://prive.bitwizard.nl/t80003.tif results in http://prive.bitwizard.nl/t8a.tif I cannot say I expected that black triangle in the output. My enblend was pulled from hg this morning (no changes) and built without imagecache or openMP. (imagecache causes corruption of the output similar but different to this. ) To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/721136/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
