WMAPRO r22146 SVN Broken? - Printable Version
+- Kodi Community Forum (http://forum.kodi.tv)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: Kodi General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: Linux and Live support (/forumdisplay.php?fid=52)
+---- Thread: WMAPRO r22146 SVN Broken? (/showthread.php?tid=56339)
WMAPRO r22146 SVN Broken? - johoja - 2009-08-14 16:00
Just wondering if anyone had noticed if WMAPRO in WMV files was broken in the latest SVN.
It was working a few iterations ago (using the SVN PPA for ubuntu). But I just tried to play a file back recently and it wouldn't get audio back, and it would eventually freeze. Then pick up again.
I tried a VC1/DTS file to confirm if the decoder was the culprit or not, it doesn't look like it since that file played back fine.
Anyone else seeing this or is it just me?
- Maxim - 2009-08-14 18:34
Might be just you, I don't have any WManything so i'm not sure. Post up a debug log in the mean time maybe someone will see something.
- kurai - 2009-08-15 02:22
I've noticed it too - it started somewhere around the time of the inclusion of the updated ffmpeg patch.
As per O.P., CPU @ 100% even though VDPAU is active (according to onscreen codec info), no audio, then video freezes up after about 25 seconds. Not a full lock up - video can be stopped and system returns to normal performance.
It played fine previously, albeit unable to skip/seek as per the longstanding wmv bug (which, as an aside, the ffmpeg update didn't fix)
Ubuntu - 9.04, up to date as of today
Kernel - 2.6.28-14-generic #47-Ubuntu SMP i686
XBMC - SVN#22146 (PPA build xbmc-9.04.2+svn22146-jaunty1)
Skin - Transparency v1.3
Acer Aspire Revo
NVIDIA MC79 "Ion" platform, Atom N230 CPU, GeForce 9400M GPU
2Gb RAM, 512MB dedicated as VRAM
2Gb 1080p 29.97 fps wmv
video - VC-1 (WMV 9 Advanced Profile) 8Mbit
audio - WMAPRO (WMA 10 Professional) 192Kbit 48KHz stereo
- johoja - 2009-08-15 18:19
Same Problem Here - octagon2000 - 2009-08-16 12:04
I have also noticed this, everything works well with latest SVN except VC1 movies. They 'freeze' almost right away, these all worked fine before I updated to the latest.
- Bad_CRC - 2009-08-16 23:11
In my case, I've lost audio in menus, mp3, divx/mp3 movies.. with the last svn updates, only ac3 movies work...
- stoli - 2009-08-18 00:18
Same issue here:
- johoja - 2009-08-18 05:34
Bad_CRC Wrote:In my case, I've lost audio in menus, mp3, divx/mp3 movies.. with the last svn updates, only ac3 movies work...
Yours sounds unrelated.
- alanwww1 - 2009-08-18 09:08
There is a new version of the codec just implemented.
I think we should give the devs a little time until they fine tune things. After that i am sure it will work much better than before as it is a brand new version.
- johoja - 2009-08-18 16:53
Yup, I noticed that. I was just giving a heads up or so, not many people use WMV/WMAPRO, so there's a high chance the dev's might not have been aware of the issue (along with other users).
Also the new version check in to xbmc was reverted i think.
- erhnam - 2009-08-25 09:59
Any news on this item?
- p1nky - 2009-09-14 00:15
the whole WMV playback is broken - total time displayed wrong on 90% of files, jumping/skipping/go to time/fast forward all completely broken and that for about a year now. there have been numerous posts but no one cares. looks like the devs don't give a damn about WMV playback.
- rodalpho - 2009-09-14 01:40
Yes, WMV has been broken forever, but I believe (and someone please correct me if I'm wrong) that the WMAPRO audio component is a separate entity.
- Maxim - 2009-09-14 02:05
Probably, anyone in this thread created a trac ticket for it yet? http://trac.xbmc.org
You can use your forum login on trac.
- erhnam - 2009-09-14 15:48
rodalpho Wrote:Yes, WMV has been broken forever, but I believe (and someone please correct me if I'm wrong) that the WMAPRO audio component is a separate entity.
It's strange that this has been brooken forever because this worked for me a couple of week before (just before the big merge with boxee). I really hope to see this fixed soon.