Posts: 666
Joined: Dec 2008
Reputation:
0
motd2k
Team-XBMC Developer
Posts: 666
If its a revo, it's a G98 card, which has a documented issue with certain video widths (784, 864, 944, 1024, 1808, 1888 pixels).
It's possible you're being affected by this i suppose - as I recall it would manifest like this.
Perhaps pastebin a full xbmc.log.
Posts: 666
Joined: Dec 2008
Reputation:
0
motd2k
Team-XBMC Developer
Posts: 666
Its a tricky one to code around - there are ways to grab the card's type but i'd need to add them in order to add an auto-fallback method.
I'll put it on the list.
motd
Posts: 666
Joined: Dec 2008
Reputation:
0
motd2k
Team-XBMC Developer
Posts: 666
Its to do with the number of macroblock, so the macroblock size influences the outcome too. Its annoying but is a problem on the silicon so there's nothing that can be done about it.
motd
Posts: 18
Joined: Jul 2009
Reputation:
0
Clodo
Junior Member
Posts: 18
Sorry if i up this topic.
I have found a video avc1/x264 with a resolution of 1920 x 1152 that give the same problem.
If can help, i can upload the video and send to you a PM with a link (it's copyrighted material).
Posts: 38
Joined: Jan 2006
Reputation:
0
I have this problem also with a video file. It is avc1 1024X576.
If I turn vdpau off it plays fine. I am using asrock ht330 with camelot.
Is this a harware or a software problem? Are there certain codecs/ resolutions that I should avoid ?
Posts: 3,805
Joined: Mar 2004
Reputation:
3
elupus
Team-XBMC Developer
Posts: 3,805
marathont:
Yea, that size is a HW problem. Nothing you can do about it.
Any video with width/16 rounded up to nearest integer, that matches the folowing values will fail on your hardware:
49, 54, 59, 64, 113, 118, 123, 128