Kodi Community Forum

Full Version: XBMC for Linux VDPAU - NVIDIA GPU video decoding support (now in the mainline SVN)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Rand Al Thor Wrote:Hey guys,

VDPAU was working quite well for me a few weeks back. Unfortunately, now it fails completely. Auto Refresh is off. I have tried setting renderer to Auto Detect and VDPAU ( in the hopes of forcing VDPAU).

Info:
Gentoo 2.6.23.8
Intel Celeron 3.2ghz
4gb Ram
Nvidia GeForce 8400 (180.44 Drivers)

Log

Cheers.

Still experiencing this same issue with 19134. I did make clean, make distclean, make reallyclean, fresh install, and I renamed my .xbmc folder. Anyone have any other thoughts?
I only have stutter on 1080p videos when I apply VDPAU grain removal / sharpness filters - but only on some videos... maybe you should make sure you've turned yours back to 0?

Randalthor - make sure you have the most recent drivers and nvidia-180-libvdpau-dev installed (or whatever name your package is) before you .configure. Here's a repo for ubuntu that has the latest beta nvidia drivers (185.13), libvdpau, and libvdpau-dev debs. They worked for me.

http://ubuntuforums.org/showpost.php?p=6...ostcount=4
Antioch Wrote:I'll try to - supposing I can figure out how to get an mplayer-vdpau build easily up and running.

Either way, I'm glad it's a known bug. Seems like nVidia released another beta driver in the 180.xx series a week ago with more "vdpau fixes" and will hopefully keep doing so -- too bad we're stuck using 185.13 for now Sad

You can use any driver v180.35 or later.
motd2k Wrote:You can use any driver v180.35 or later.

I think we have to mention, that this is only true, if one are not going to use auto-refresh with xrandr.

Without forcing glXBindTexImageEXT spec compliance (which is only available in 185.13), xbmc is crashing on video closure, if autorefresh is enabled. Sad

I have to stuck at 185.13 because of that.
Yesterday I upgraded my r18735 version to r19144 version. I noticed that still some 23.976 fps 1080p MKV's occasionally stutters while some MKV's plays fine without stuttering. Movement is stutterfree for a minute or two, but suddenly movie jumps suddenly forward one or two frames, which is easy to notice on fast tracking and panning scenes. XBMC's info shows that frames aren't dropping. I'm using latest beta nvidia drivers (185.13). When I tested yesterday XBMC new version, I noticed that it seems like that occasionally suttering appears only 'DXVA' compliant MKV's. I'm not 100% sure about this. Maybe these stuttering problems depends on MKV's encoding methods?
Antioch Wrote:Randalthor - make sure you have the most recent drivers and nvidia-180-libvdpau-dev installed (or whatever name your package is) before you .configure. Here's a repo for ubuntu that has the latest beta nvidia drivers (185.13), libvdpau, and libvdpau-dev debs. They worked for me.

http://ubuntuforums.org/showpost.php?p=6...ostcount=4

I have the latest available from portage, 180.44. As far as I know, gentoo does not have any libvdpau packages separate from the ebuild for nvidia drivers. It worked before, but as the log shows, now it just fails.

Everything looks right in ./configure. I am at a loss. I guess that is why we have geniuses like Motd2k around, huh?
My configure ran fine having only had the libvdpau package but NOT the source installed. I then crashed when I tried to compile - it couldnt find the source files. I installed the source files and then compiled without re-.configure'ing which caused vdpau to not work for me. I then c re .configure'd and recompiled and all worked.

I think maybe the dev files are included in the nvidia driver archive file?
As of R19139 don't you have to specifically enable vdpau for ./configure?
yep
Encountered another bug. I imagine it's known, but again as I'm not sure what is and isn't 'known' I'll report it just incase.

I often experience hangs when I stop playback of mkv files - they usually lock gdm and I have to ctrl+alt+backspace to get out. This time xbmc actually crashed. Using main svn r19113, streaming a 1080p h264 file from a rar set via an NFS mounted folder I received the following message on the command line:

Code:
xbmc.bin: ../../src/xcb_io.c:176: process_responses: Assertion `!(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))' failed.

I believe it said it dumped the core, not sure where to find it, but here is the log file. I wasn't running in debug mode unfortunately but hopefully it will help. Either way, I imagine this is a known issue.
http://pastebin.com/m27fd676c

nVidia 9300 IGP, driver 185.13, 2GB RAM, Intel e5200.
I haven't been able to use the latest SVN build for a few weeks now because of a really weird issue... Anything I play is blue (?).

Any ideas? Is it a known issue?

I'm using Intrepid and nvidia 185.13 driver on a P5N7A-VM mobo. A build from the beginning of last month works fine and is quite stable, so I'm using that.
hey guys... updated to the newest svn today... running 180.44 nvidia drivers and had the libvdpau libs installed before compiling and enabled vdpau and disabled pulse when configuring... just to refresh i've got nvidia 8200 integrated gpu, 512mb enabled in bios, running at 1920x1080 @ 60 hz... when video render is set to auto it appears to not even use vdpau as the cpus are both around 50%... when i select vdpau i am still once again getting way more skips and frame drops, whether 720p or 1080p video..... i used a 1080p rip of casino royale, lots of drops and running about 19-20 fps, and i included new logs here:

http://halo.anarchic-x.net/gotoman/xbmc2.log

http://halo.anarchic-x.net/gotoman/nvidi...eport2.log
rev 19251:
changed: vdpau must now be explicitly selected from gui options to be active

Looks like setting the renderer to Auto will not use VDPAU anymore.
I'd like to say that the latest linuxport SVN (19284) fixes my video stuttering issues on my 8200 IGP! Yay!

I've been using MythTV w/VDPAU since it's been stable on the 8200, but now I can finally use XBMC. Way cool!

-- Kevin
I noticed that auto refresh rate does indeed work with strict bindings enabled (as mentioned here). However, there was a catch with the strict bindings right? Was it performance? What does it do?