Date: Sat, 26 May 2012 23:05:23 +0200 (CEST) From: Juergen Lock <nox@jelal.kn-bremen.de> To: kob6558@gmail.com Cc: multimedia@freebsd.org Subject: Re: xine no longer plays WMV files Message-ID: <201205262105.q4QL5N2R013397@triton8.kn-bremen.de> In-Reply-To: <CAN6yY1ux22AD2jpNckAjOW-T_Wv2pf0op6Zz0V4=QBU1DjFW6g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <CAN6yY1ux22AD2jpNckAjOW-T_Wv2pf0op6Zz0V4=QBU1DjFW6g@mail.gmail.com> you write: >Since I updated xine about two months ago, it has not played WMV >files. I get an occasional bits of an image, but mostly just stripes >of varying colors, often green or pastels, also often followed by a >jump to the next file in the playlist. >Here are errors reported to STDERROR: >wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] concealing 198 DC, 198 AC, 198 MV errors >[wmv2 @ 0x33c0db20] ac-tex damaged at 11 4 >[wmv2 @ 0x33c0db20] >error while decoding intra block: 11 x 4 (0) >[wmv2 @ 0x33c0db20] Error at MB: 103 >[wmv2 @ 0x33c0db20] concealing 346 DC, 346 AC, 346 MV errors >[wmv2 @ 0x33c0db20] ignoring overflow at 0 0 >[wmv2 @ 0x33c0db20] ac-tex damaged at 3 4 >[wmv2 @ 0x33c0db20] >error while decoding intra block: 3 x 4 (1) >[wmv2 @ 0x33c0db20] Error at MB: 95 >[wmv2 @ 0x33c0db20] concealing 354 DC, 354 AC, 354 MV errors >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv2 @ 0x33c0db20] warning: first frame is no keyframe >[wmv3 @ 0x33c0db20] Extra data: 8 bits left, value: 0 >[wmv3 @ 0x33c0db20] warning: first frame is no keyframe >[wmv3 @ 0x33c0db20] Bits overconsumption: 1567 > 1536 >[wmv3 @ 0x33c0db20] concealing 1185 DC, 1185 AC, 1185 MV errors >[wmv3 @ 0x33c0db20] warning: first frame is no keyframe >[wmv3 @ 0x33c0db20] Bits overconsumption: 67 > 64 at 1x0 >[wmv3 @ 0x33c0db20] concealing 1348 DC, 1348 AC, 1348 MV errors >[wmv3 @ 0x33c0db20] Bits overconsumption: 1631 > 1592 >[wmv3 @ 0x33c0db20] concealing 1335 DC, 1335 AC, 1335 MV errors >[wmv3 @ 0x33c0db20] Bits overconsumption: 779 > 776 >[wmv3 @ 0x33c0db20] concealing 1343 DC, 1343 AC, 1343 MV errors >[wmv3 @ 0x33c0db20] Bits overconsumption: 278 > 256 >[wmv3 @ 0x33c0db20] concealing 1346 DC, 1346 AC, 1346 MV errors >[wmv3 @ 0x33c0db20] Bits overconsumption: 150 > 144 >[wmv3 @ 0x33c0db20] concealing 1347 DC, 1347 AC, 1347 MV errors >[wmv3 @ 0x33c0db20] Bits overconsumption: 1111 > 1088 >[wmv3 @ 0x33c0db20] concealing 1332 DC, 1332 AC, 1332 MV errors > >When I try to play a WMV, the CPU goes through the roof and trying to >skip to the next file or enter any other command is often delayed vor >many seconds. > >Going back to the last 1.1 version works as do other media players >including vlc, totem, and mplayer. > >Any idea what happened? Any fix available? I'll admit that I waited >assuming that someone else would report the problem. > >System is 9-Stable, updated about once a month and last updated on >April 28. Running amd64 on a Sandybridge CPU. Problem is there with >Intel-KMS or VESA video driver. > >Please keep me in the CC as I am not currently subscribed to the list. >Thanks! I just reproduced this here, and reported it upstream. I hope it'll be fixed with the next version... Thanx, :) Juergen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201205262105.q4QL5N2R013397>