Comment 9 for bug 108453

Not only wmv8. _Some_ wmv9 and wmv7 videos are affected. They play fine in ffmpeg, mplayer (ffmpeg backend), mplayer (win32 backend), and xine (win32 backend) but are broken with xine (ffmpeg backend).

wmv9 example: http://www.gamevideos.com/video/watch?video=14503&largeFormat=wmv

Stuff like this on the output with wmv7:
...
[wmv1 @ 0xb6474b48]ignoring overflow at 39 21
[wmv1 @ 0xb6474b48]concealing 80 DC, 80 AC, 80 MV errors
[wmv1 @ 0xb6474b48]invalid picture type
[wmv1 @ 0xb6474b48]header damaged
[wmv1 @ 0xb6474b48]error, slice code was 10
[wmv1 @ 0xb6474b48]header damaged
[wmv1 @ 0xb6474b48]invalid picture type
[wmv1 @ 0xb6474b48]header damaged
[wmv1 @ 0xb6474b48]overreading 12836 bits
...

and with wmv9:
[wmv3 @ 0xb5c73b48]warning: first frame is no keyframe
[wmv3 @ 0xb5c73b48]Bits overconsumption: 26660 > 26656 at 8x17
[wmv3 @ 0xb5c73b48]Bits overconsumption: 8839 > 8672
[wmv3 @ 0xb5c73b48]Bits overconsumption: 40536 > 40448
...

Again, it works fine with ffmpeg, and mplayer using ffmpeg. It's just broken with xine (kaffeine and xine-ui) using ffmpeg