Am 28.02.2012 16:01, schrieb rew: > Kay, > > How big is your output image?
400MB > Does the problem go away if you make your output image size half that > what it is now? (both X and Y). ... I'm not sure if I want to go down this road any further. With the original bug in enfuse, which seems to have been fixed by now, I managed to reduce the problem to a manageable size. I've tried the approach here, but failed. Even though I could reproduce the bug with the original big image set, it was exotic data, so it may just have been a freak incident never to show up again. I had to revert back to an earlier stable enblend version anyway, because the bleeding edge was too slow (even though I compiled the Release version and used --primary-seam-generator=nearest-feature-transform or whatever the relevant flag was called...). > What happens if you start with horribly compressed jpg images? If you > set the quality very low, they will become very ugly, but this doesn't > matter for the computer. I'd first have to create all the horribly compressed JPEGs... I may try again later, but just now I'm too busy with other stuff. Kay -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/787387 Title: small artifacts in fused 16bit TIFFs Status in Enblend: Confirmed Bug description: When blending a set of 16bit TIFF images, I noticed artifacts in the output. Depending on the enfuse setting used, these occur in different places and look different. When I used the default setting, the artifacts looked like groups of coloured dots (see enfuse_problem_fused_default.tif) and when I used exposure only, they came as single pixels (see enfuse_problem_fused_only_exposure.tif), also see the respective jpg screenshots where the artifacts are enlarged. The images were created by hugin's nona, I tried several sizes and also the original unmodified images, the effects were the same. The 16bit TIFFs were created by digiKam's batch RAW import from Canon CR2, using conversion to 16bit and storage as TIFF as the only active processing steps. I converted the images to JPG with gimp, and when I fused the JPGs, there was no problem. I also opened the images with fotoxx and saved them in a different file but the same format, in which case the problem persisted. I suspect the problem may stem from the 16bit format. Here's my session which produced the flawed results: >enfuse enfuse_problem_[0-2].tif -o enfuse_problem_fused_default.tif enfuse: info: loading next image: enfuse_problem_0.tif 1/1 enfuse: info: loading next image: enfuse_problem_1.tif 1/1 enfuse: info: loading next image: enfuse_problem_2.tif 1/1 >enfuse enfuse_problem_[0-2].tif --saturation-weight=0 -o enfuse_problem_fused_only_exposure.tif enfuse: info: loading next image: enfuse_problem_0.tif 1/1 enfuse: info: loading next image: enfuse_problem_1.tif 1/1 enfuse: info: loading next image: enfuse_problem_2.tif 1/1 >enfuse --version enfuse 4.1-101796703d73 I use a Kubuntu 11.4 system on an intel processor. Find enclosed a tar file of the files in this session. Kay To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/787387/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
