Comment 18 for bug 787387

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