Paul--yes, I see the same thing you describe but there is nothing I can do about it since it is caused by the Xuggle video engine over which I have no direct control. I saw errors like this (but worse) with the Xuggle 5.4 release several years ago which is why I stopped using it and went back to the 3.4 release. Doug
There's nothing to be done. The Xuggle development team is non-existent. They abandoned the project a few years ago and AFAIK nobody has picked it up :-( Doug