|
|
#1 | |
|
Registered User
Join Date: Nov 2008
Posts: 15
|
Hi
Dell xps M1530 Geforce 8600M GT Kernel: 2.6.36.1 system: Archlinux Nvidia driver: 260.19.21-2 Xorg: 1.9.2-2 I don't know why but after some nvidia driver update there are problems with slow video decoding using VDPAU. The power mizer is set to max performance, but still the video is not smooth as it suppose to be, it hangs, stops for seconds. I am sure that this is related to the nvidia driver because vdpau worked for me great before. Quote:
|
|
|
|
|
|
|
#2 | |
|
FFmpeg developer
Join Date: Jan 2009
Location: Vienna, Austria
Posts: 467
|
|
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Nov 2008
Posts: 15
|
Well, maybe, but all movies that doesn't play smooth, were playing ok before update.
|
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Feb 2007
Posts: 115
|
interesting your vdpautest looks right because mine doesn't at all (i've 15fps) but i've noticed small gaps like described above even on the 720p video which are still above the 30fps needed to playback them.
|
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Feb 2009
Posts: 56
|
Well, it seems the 260.19.xx series lags behind the previous drivers in particular what concerns decoding speed.
qvdpautest 0.5.1 Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz NVIDIA GPU GeForce 8400M GS (G86M) at PCI:1:0:0 (GPU-0) VDPAU API version : 1 VDPAU implementation : NVIDIA VDPAU Driver Shared Library 260.19.21 Thu Nov 4 21:46:12 PDT 2010 SURFACE GET BITS: 694.095 M/s SURFACE PUT BITS: 854.917 M/s MPEG DECODING (1920x1080): 38 frames/s MPEG DECODING (1280x720): 84 frames/s H264Decoder: FATAL: Can't create required surfaces!! Can't initialize H264 decoder! H264 DECODING (1280x720): 35 frames/s VC1 DECODING (1440x1080): 48 frames/s Profile unsupported. MIXER WEAVE (1920x1080): 282 frames/s MIXER BOB (1920x1080): 385 fields/s MIXER TEMPORAL (1920x1080): 101 fields/s MIXER TEMPORAL + IVTC (1920x1080): 57 fields/s MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 130 fields/s MIXER TEMPORAL_SPATIAL (1920x1080): 32 fields/s MIXER TEMPORAL_SPATIAL + IVTC (1920x1080): 25 fields/s MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 36 fields/s MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 127 fields/s qvdpautest 0.5.1 Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz NVIDIA GPU GeForce 8400M GS (G86M) at PCI:1:0:0 (GPU-0) VDPAU API version : 1 VDPAU implementation : NVIDIA VDPAU Driver Shared Library 256.53 Fri Aug 27 20:54:24 PDT 2010 SURFACE GET BITS: 751.805 M/s SURFACE PUT BITS: 871.177 M/s MPEG DECODING (1920x1080): 64 frames/s MPEG DECODING (1280x720): 135 frames/s H264Decoder: FATAL: Can't create required surfaces!! Can't initialize H264 decoder! H264 DECODING (1280x720): 86 frames/s VC1 DECODING (1440x1080): 108 frames/s Profile unsupported. MIXER WEAVE (1920x1080): 308 frames/s MIXER BOB (1920x1080): 432 fields/s MIXER TEMPORAL (1920x1080): 107 fields/s MIXER TEMPORAL + IVTC (1920x1080): 66 fields/s MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 146 fields/s MIXER TEMPORAL_SPATIAL (1920x1080): 34 fields/s MIXER TEMPORAL_SPATIAL + IVTC (1920x1080): 26 fields/s MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 38 fields/s MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 126 fields/s |
|
|
|
|
|
#6 | |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
lgolebio, are you using VDPAU for decoding, or just for display? I notice that your put/get-bits values are pretty slow compared to other people. However, as cehoyos pointed out, your decoding speed values look like they should be fine.
|
|
|
|
|
|
|
#7 |
|
Registered User
Join Date: Nov 2008
Posts: 15
|
@stephen, can you explain ? I don't know what you mean. I'm using mplayer with smplayer gui (vdpau selected in settings). And also if I run mplayer from command, with all parameters.
For example Code:
mplayer -vo vdpau -vc ffh264vdpau movie.file |
|
|
|
|
|
#8 |
|
Registered User
Join Date: Feb 2009
Posts: 56
|
@Stephen, can you comment on the difference of the decoding speed I mentioned before?
|
|
|
|
|
|
#9 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
We do have a bug filed for this issue, although we haven't yet managed to reproduce it. We'll let you know more when we have.
|
|
|
|
![]() |
| Thread Tools | |
|
|