Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-10-08, 11:41 AM   #253
duc
Registered User
 
Join Date: Apr 2006
Posts: 10
Default Re: mplayer vdpau

ok now. first problem is solved. there was a codecs.conf file in the .mplayer folder in user home. after deleting this folder the new codecs are available. very bad error ...

now i tested the codecs MPEG, H.264, WMV3 with the three samples from the Readme:
http://inventaaustralia.zftp.com.nyu...3MBPS30sec.mpg
http://samples.mplayerhq.hu.nyud.net...4/PAFF/Grey.ts
http://download.microsoft.com.nyud.n..._Caves_720.exe

only the MPEG file worked, the other two codecs showed a short green screen and crashed.
i attach four logfiles:
- nvidia-bug-report.log
- wmv3.log
- h264.log
- mpeg.log
Attached Files
File Type: log nvidia-bug-report.log (131.9 KB, 120 views)
File Type: log wmv3.log (3.9 KB, 116 views)
File Type: log h264.log (5.2 KB, 133 views)
File Type: log mpeg.log (7.9 KB, 106 views)
duc is offline   Reply With Quote
Old 12-10-08, 04:59 PM   #254
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: mplayer vdpau

@duc,

H.264: You're running out of video memory allocating surfaces. You should have a BIOS option that allows you to control the amount of RAM to allocate to the GPU. Bump this up, and hopefully it'll work. Also, you could try hacking MPlayer to attempt to allocate fewer surfaces for reference frames if that doesn't work (libvo/vo_vdpau.c vdp_video_surface_create loop).

VC-1/WMV 3: I think this is a bug. Let me look into it.
Stephen Warren is offline   Reply With Quote
Old 12-10-08, 05:40 PM   #255
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: mplayer vdpau

@duc,

Yes, there's a bug for VC-1 on chipset GPUs. It should be fixed in a future driver release.

Thanks for taking the time to generate all that bug report and trace information. It was very useful.
Stephen Warren is offline   Reply With Quote
Old 12-10-08, 10:14 PM   #256
mitchell2345
Registered User
 
Join Date: Dec 2006
Posts: 43
Default Re: mplayer vdpau

Quote:
Originally Posted by Stephen Warren View Post
@duc,

H.264: You're running out of video memory allocating surfaces. You should have a BIOS option that allows you to control the amount of RAM to allocate to the GPU. Bump this up, and hopefully it'll work. Also, you could try hacking MPlayer to attempt to allocate fewer surfaces for reference frames if that doesn't work (libvo/vo_vdpau.c vdp_video_surface_create loop).

VC-1/WMV 3: I think this is a bug. Let me look into it.
I know there have been lots of post about how much memory is required. Stephen can you comment on what, from a driver perspective, should be on the video card?

I know for myth right now its 512mb but should 256 cards work if the code is optimized?

Mitchell
mitchell2345 is offline   Reply With Quote
Old 12-11-08, 12:01 AM   #257
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: mplayer vdpau

We haven't characterized memory requirements yet. Off the top of my head, 256M should work just fine. However, it all depends on what else is using memory; X drawables, OpenGL drawables, pixmap caches, etc.
Stephen Warren is offline   Reply With Quote
Old 12-11-08, 03:59 AM   #258
duc
Registered User
 
Join Date: Apr 2006
Posts: 10
Default Re: mplayer vdpau

Quote:
Originally Posted by Stephen Warren View Post
@duc,

H.264: You're running out of video memory allocating surfaces. You should have a BIOS option that allows you to control the amount of RAM to allocate to the GPU. Bump this up, and hopefully it'll work. Also, you could try hacking MPlayer to attempt to allocate fewer surfaces for reference frames if that doesn't work (libvo/vo_vdpau.c vdp_video_surface_create loop).

VC-1/WMV 3: I think this is a bug. Let me look into it.
thank you for that information. i have a ASUS M3N78 mainboard and i can't find any BIOS option to increase GPU memory. in the mainboard documentation says: maximum 256MB shared memory...

so i would try the mplayer hack you suggested. can you pleas tell me what exactly i have to change? i'm not a experienced programmer...

edit
i had a look into libvo/vo_vdpau.c and found the definittions for allocation of surfaces:
Code:
/* Numbers of video and ouput Surfaces */
#define NUM_OUTPUT_SURFACES                2
#define NUM_VIDEO_SURFACES_MPEG2           3  // (1 frame being decoded, 2 reference)
#define NUM_VIDEO_SURFACES_H264            17 // (1 frame being decoded, up to 16 references) 
#define NUM_VIDEO_SURFACES_VC1             3  // (same as MPEG-2)
#define NUM_VIDEO_SURFACES_NON_ACCEL_YUV   1  //  surfaces for YV12 etc. 
#define NUM_VIDEO_SURFACES_NON_ACCEL_RGB   0 // surfaces for RGB or YUV4:4:4
what would you suggest for NUM_VIDEO_SURFACES_H264 ?
17 seems to a little bit high, compared to the other values of the surfaces.
edit

thanks
duc is offline   Reply With Quote
Old 12-11-08, 10:33 AM   #259
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: mplayer vdpau

@duc,

H.264 can theoretically use 16 reference frames, hence 16+1 (1 for current frame) == 17 max.

You can probably bump this number down to somwhere between 5 and 7 depending on what stream you're playing.
Stephen Warren is offline   Reply With Quote
Old 12-11-08, 01:57 PM   #260
duc
Registered User
 
Join Date: Apr 2006
Posts: 10
Default Re: mplayer vdpau

now i made some tests. first i changed the value for
NUM_VIDEO_SURFACES_H264 8
this didn't work, but this generated a new error. i used the same h.264 video. (Grey.ts)
see attached logfile h264-8.log

then i tried out, if something would change when i try other values, so i tried out all values from 5 to 10 (always make && make install after changing the source of course). nothing, always the same result.

then i set the value to 8 and tested with other h264 files, one in 1080p and one in 720p.
this produced two new errors, please look at attached log file h264-8-720.log and h264-8-720.log

seems to be a lot work to find out every bug ;-)
Attached Files
File Type: log h264-8.log (4.6 KB, 122 views)
File Type: log h264-8-720.log (5.4 KB, 114 views)
File Type: log h264-8-1080.log (5.1 KB, 98 views)
duc is offline   Reply With Quote

Old 12-11-08, 05:44 PM   #261
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: mplayer vdpau

@duc,

All your logs show this error:
VDPAU nvidia: Error detected 1002 35 15
This isn't preventing anything from working for you, although I've filed a bug to fix this.

h264-8.log and h264-8-1080.log show this error:
VDPAU nvidia: Error detected 1020 1416 7
This indicates you're running out of video RAM attempting to create some VDPAU object. You may want to:
* Try running MPlayer right after starting X, without starting other apps first
* Run a bare/minimal X server, rather than a complete desktop environment
* Turn off any X server features that use video RAM, like the pixmap cache

h264-8-720.log shows this error:
[VD_FFMPEG] Only buffers allocated by vo_vdpau allowed.
mplayer: libmpcodecs/vd_ffmpeg.c:1207: vdpau_get_buffer: Assertion `0' failed.
This is a problem with our MPlayer patches. I'm not quite sure why it happens right now. Its on our list of things to look at.
Stephen Warren is offline   Reply With Quote
Old 12-12-08, 03:39 AM   #262
duc
Registered User
 
Join Date: Apr 2006
Posts: 10
Default Re: mplayer vdpau

ok, i will try to save more video memory. actually i use fluxbox and have no other apps running.
so i think, i have to wait for driver/software updates, right?

i also made a change request at ASUS for a BIOS update with adjustable shared video memory.

thanks for your help
duc is offline   Reply With Quote
Old 12-12-08, 06:24 AM   #263
flux
Registered User
 
Join Date: Aug 2004
Posts: 9
Default Re: mplayer vdpau

Quote:
Originally Posted by Stephen Warren View Post
We haven't characterized memory requirements yet. Off the top of my head, 256M should work just fine. However, it all depends on what else is using memory; X drawables, OpenGL drawables, pixmap caches, etc.
should we still post bug reports concerning 256MB cards or is it not on your priority list at the moment ?
I manage to find a quite dreadful crash on my 8400GS 256M 180.11, playing a 720p h264 mkv that got my X to crash completely..
flux is offline   Reply With Quote
Old 12-12-08, 02:42 PM   #264
duc
Registered User
 
Join Date: Apr 2006
Posts: 10
Default Re: mplayer vdpau

today i found out that ther is a undocumented BIOS feature for increasing the shared memory.
the default value was 128MB, so i don't wonder that it ran out of memory. now i set the memory to maximum of 512MB and now it works with some movies, but some movies produce errors.

but there are some issues:
- when twinview is activated mplayer shows only a green screen.
- the are two error types with some movies. i will collect error logs and post them.
duc is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
xorg locks-up with newest nvidia drivers w/ vdpau. theroot NVIDIA Linux 1 06-24-12 11:04 AM
NVIDIA VDPAU Reference Benchmarks News Archived News Items 0 06-11-12 05:30 AM
VDPAU and KDE 4.8 compositing = slow Pie-rate NVIDIA Linux 30 05-23-12 07:07 AM
VDPAU testing tool crisalide NVIDIA Linux 392 04-29-12 06:01 PM
mplayer & xmms problems! replys2me NVIDIA Linux 5 09-06-02 02:34 PM

All times are GMT -5. The time now is 12:33 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.