[MPlayer-users] NO-SPAM Xvmc? Nvidia or mplayer issue?

Bill Broadley bill at cse.ucdavis.edu
Wed Mar 16 08:37:55 CET 2005


I'm running a mostly stock fc3 x86-64, 2.6.11.3 kernel, nvidia 7167 driver,
6600GT, amd64-3200 (s939), and 1.0pre6a.

I used ./configure ..  --with-xvmclib=XvMCNVIDIA --with-x11libdir=/usr/X11R6/lib64 --enable-xvmc.

This works:
./mplayer -vo gl foo1.2.ts
...
VIDEO:  MPEG2  1280x720  (aspect 3)  59.940 fps  14800.0 kbps (1850.0 kbyte/s)
...
vo: X11 running at 1600x1200 with depth 16 and 16 bpp (":0.0" => local display)
...

Works great, cept for dropping frames.

./mplayer -vo xv foo1.2.ts

Works great, high cpu usage, minimal if any dropped frames.

I'd like to try xvmc, so I tried:

export XVMC_DEBUG=2
mplayer -vo xvmc -vc ffmpeg12mc  foo1.2.ts
VIDEO MPEG2(pid=17)...AUDIO A52(pid=20) NO SUBS (yet)!  PROGRAM N. 1
Opened TS demuxer, audio: 2000(pid 20), video: 10000002(pid 17)...POS=16168
VIDEO:  MPEG2  1280x720  (aspect 3)  59.940 fps  14800.0 kbps (1850.0 kbyte/s)
==========================================================================
Opening audio decoder: [liba52] AC3 decoding with liba52
No accelerated IMDCT transform found
AC3: 5.1 (3f+2r+lfe)  48000 Hz  384.0 kbit/s
No accelerated resampler found
AUDIO: 48000 Hz, 2 ch, 16 bit (0x10), ratio: 48000->192000 (384.0 kbit)
Selected audio codec: [a52] afm:liba52 (AC3-liba52)
==========================================================================
vo: X11 running at 1600x1200 with depth 16 and 16 bpp (":0.0" => local display)
vo_xvmc: X-Video extension 2.2
vo_xvmc: X-Video MotionCompensation Extension version 1.0
==========================================================================
Forced video codec: ffmpeg12mc
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
vd_ffmpeg: XVMC accelerated codec
Selected video codec: [ffmpeg12mc] vfm:ffmpeg (FFmpeg MPEG 1/2 (XvMC))
==========================================================================
Checking audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/16bit...
AF_pre: af format: 2 bps, 2 ch, 48000 hz, little endian signed int
AF_pre: 48000Hz 2ch Signed 16-bit (Little-Endian)
AO: [oss] 48000Hz 2ch Signed 16-bit (Little-Endian) (2 bps)
Building audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/16bit...
Starting playback...
vd_ffmpeg: XVMC accelerated MPEG2
trying pixfmt=0
VDec: vo config request - 1280 x 720 (preferred csp: MPEG1/2 Motion Compensation and IDCT)
VDec: using MPEG1/2 Motion Compensation and IDCT as output csp (no 0)
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [xvmc] 1280x720 => 1280x720 MPEG1/2 Motion Compensation and IDCT
vo_xvmc: Port 127 grabed
vo_xvmc: Found matching surface with id=54434449 on 127 port at 0 adapter
FATAL: Cannot initialize video driver.
trying pixfmt=1
Only buffers allocated by vo_xvmc allowed
mplayer: vd_ffmpeg.c:970: mc_get_buffer: Assertion `0' failed.

I tred the same thing with 24bpp (and restarting X) and:
Dec: vo config request - 1280 x 720 (preferred csp: MPEG1/2 Motion Compensation and IDCT)
VDec: using MPEG1/2 Motion Compensation and IDCT as output csp (no 0)
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [xvmc] 1280x720 => 1280x720 MPEG1/2 Motion Compensation and IDCT
NV-XVMC (WARN): failed to allocate AGP DMA buffer
NV-XVMC (WARN): allocated framebuffer DMA buffer instead
X11 error: BadMatch (invalid parameter attributes)
vo_xvmc: Port 177 grabed
vo_xvmc: Found matching surface with id=54434449 on 177 port at 0 adapter
vo_xvmc: Allocated Direct Context
vo_xvmc: data_blocks allocated
vo_xvmc: mv_blocks allocated
vo_xvmc: Motion Compensation context allocated - 8 surfaces
vo_xvmc: idct=1 unsigned_intra=0
vo_xvmc: looking for OSD support
Subpicture id 0x34344149
vo_xvmc: OSD support by additional frontend rendering
MPlayer interrupted by signal 6 in module: decode_video

Any ideas what the most critical errors imply:
X11 error: BadMatch (invalid parameter attributes)
Only buffers allocated by vo_xvmc allowed
mplayer: vd_ffmpeg.c:970: mc_get_buffer: Assertion `0' failed.

Anything else to try?  Additional info to report?  Is it likely to
be a nvidia driver issue (unlrelated to mplayer)?

-- 
Bill Broadley
Computational Science and Engineering
UC Davis




More information about the MPlayer-users mailing list