It would appear that if you use a losslevel of 100 (the recommended value, and the value used by -lossy) the problem disappears. The resulting file size increase is under 3%.
Unless you object (perhaps by suggesting a patch to the place in the documentation that led you to use 200 there) I would be inclined to mark this bug as closed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
