From owner-freebsd-multimedia@FreeBSD.ORG Sun May 27 00:33:16 2012 Return-Path: Delivered-To: multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 80283106564A for ; Sun, 27 May 2012 00:33:16 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 056148FC0A for ; Sun, 27 May 2012 00:33:15 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id DAEB01E00118; Sun, 27 May 2012 02:33:08 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.4/8.14.4) with ESMTP id q4QL5Nk5013398; Sat, 26 May 2012 23:05:23 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.4/8.14.3/Submit) id q4QL5N2R013397; Sat, 26 May 2012 23:05:23 +0200 (CEST) (envelope-from nox) Date: Sat, 26 May 2012 23:05:23 +0200 (CEST) From: Juergen Lock Message-Id: <201205262105.q4QL5N2R013397@triton8.kn-bremen.de> To: kob6558@gmail.com X-Newsgroups: local.list.freebsd.multimedia In-Reply-To: Organization: Cc: multimedia@freebsd.org Subject: Re: xine no longer plays WMV files X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2012 00:33:16 -0000 In article 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