|
|
#1 | ||
|
Registered User
Join Date: Oct 2009
Posts: 17
|
Hello guys:
watching a certain x264 video with the recent svn mplayer, the 190.42 nvidia-driver and the following options: Quote:
Sometimes there is some time left before it freezes, so i was lucky to capture the output below and save it to a file before the screen got locked. The options above are used by some gui for mplayer, which is called smplayer. Using the driver xv, the film gets rendered fine. Interestingly, when I watch the film by calling mplayer directly with just one option, namely -vo vdpau, mplayer renders the film correctly. Well, but here is the mplayer log that I could save before my screen got freezed: Quote:
|
||
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Oct 2009
Posts: 17
|
Quote:
I use is a gentoo 64 bit distro. The above behavior was on a thinkpad T61 with an Quadro NVS 140M (GPU 0). Bios: 60.86.3e.00.00, Memory: 512 MB for the graphics card. The screen was 1680x1050 pixels (331x210 millimeters), resolution: 129x127 dots per inch, depth: 24. The system has a core duo with 1 GB Ram and 2GB swap space. Watching the film with the driver xv and similar options is perfectly possible and works without errors. Furthermore, calling mplayer directly with the only option -vo vdpau also works and the film can be displayed. |
|
|
|
|
|
|
#3 | |
|
FFmpeg developer
Join Date: Jan 2009
Location: Vienna, Austria
Posts: 467
|
Your mplayer log is cut, that makes it less helpful!
Quote:
mplayer -vo vdpau -vc ffh264vdpau /Files/Filme/2001-Space_Odyssey.mkv Code:
[vdpau] Failed creating VDPAU decoder: The system does not have enough resources to complete the requested operation at this time. Carl Eugen |
|
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Sep 2009
Posts: 45
|
Can you play other h264 videos of similar resolution? How much video RAM does your laptop have? That "Failed creating VDPAU decoder: The system does not have enough resources to complete the requested operation at this time." error suggests the VDPAU implementation has some resource problem, and insufficient available video RAM is the most obvious possibility. Other people have reported memory problems on cards with 256 MiB RAM.
|
|
|
|
|
|
|
#5 | |||||
|
Registered User
Join Date: Oct 2009
Posts: 17
|
Quote:
Bios: 60.86.3e.00.00, Memory: 512 MB for the graphics card. The system itself has a core duo with 1 GB Ram and 2GB swap space. The screen was 1680x1050 pixels (331x210 millimeters), resolution: 129x127 dots per inch, depth: 24. Quote:
Quote:
Quote:
Now when I run the commend with -vc option, that is: Quote:
|
|||||
|
|
|
|
|
#6 | |||
|
Registered User
Join Date: Oct 2009
Posts: 17
|
Quote:
Why does Quote:
Quote:
|
|||
|
|
|
|
|
#7 | |
|
Registered User
Join Date: Oct 2009
Posts: 17
|
With the debug variables on, I get this here with the command
Quote:
|
|
|
|
|
|
|
#8 |
|
Registered User
Join Date: Oct 2009
Posts: 17
|
Interestingly, I can't capture the output of the console with the debug variables on and the -vc ffh264vdpau option.
There would be much output, the screen would freeze and the logfile, generated by tee, or just by >> in bash, would not show the console output after restarting the computer. Instead, when I restarted my computer with the off/on button, I found some other random file from my computer under the name of the logfile! |
|
|
|
|
|
#9 |
|
Registered User
Join Date: Mar 2009
Posts: 47
|
I have an R61 with the exact same graphicscard. I have the same problem, but figured out that when using a DE without compositing, I can play even 1080p material without problems using VDPAU. I have therefore installed fluxbox to watch HD-material with hardware-acceleration. To me it seems, that using a compositing window-manager like compiz or even a recent metacity where compositing is turned on by default, the video-ram will be eaten up so that there isn't enough left for vdpau.
Regarding video-RAM, I've just double-checked: nvidia-settings reports 512MB and from X11-Log: (II) Nov 29 16:52:04 NVIDIA(0): NVIDIA GPU Quadro NVS 140M (G86) at PCI:1:0:0 (GPU-0) (--) Nov 29 16:52:04 NVIDIA(0): Memory: 524288 kBytes (--) Nov 29 16:52:04 NVIDIA(0): VideoBIOS: 60.86.3e.00.00 (II) Nov 29 16:52:04 NVIDIA(0): Detected PCI Express Link width: 16X (--) Nov 29 16:52:04 NVIDIA(0): Interlaced video modes are supported on this GPU |
|
|
|
|
|
#10 | |
|
Registered User
Join Date: Oct 2009
Posts: 17
|
Quote:
Now I tried to disable compositing and the desktop effects in Kde4.3. At least the screen does not freeze, but there is still no picture when viewing the film with -vc ffh264vdpau option. However, since the screen did not freeze, I was able to make a log file with the detailed debug variables enabled. |
|
|
|
|
|
|
#11 |
|
Registered User
Join Date: Oct 2009
Posts: 17
|
By the way, if someone names me a tool how that is able to cut out a few seconds of the film in question without altering it, i can perhaps upload a few seconds of the film in question to nvidia's ftp.
The problem is that the film is an 8GB *.mkv file. Therefore it must be cut somehow before I can upload it to Nvidia's ftp. However I don't know a method that can cut a few seconds of an *.mkv film without changing the file content. Last edited by Benni1233444; 11-29-09 at 02:37 PM. Reason: attaching the nvidia bug report |
|
|
|
|
|
#12 |
|
Registered User
Join Date: Oct 2009
Posts: 17
|
I have now made a change in xorg.conf. I have added:
Section "Extensions" Option "Composite" "Enable" Option "RENDER" "True" Option "DAMAGE" "True" EndSection and Option "RenderAccel" "True" Option "AllowGLXWithComposite" "True" in the device section. Now I can view the film even with the -vc option. Hoewever, there are still errors: |
|
|
|
![]() |
| Thread Tools | |
|
|