2008-12-13, 21:07
I have some preliminary VDPAU test results with mplayer:
System specs --
mobo: Gigabyte GA-MA78GM-S2H
cpu: AMD Phenom 9850 [1]
ram: 4 GB DDR 800 dual-channel [2]
vga: 512MB 9300GS
os: 32-bit Kubuntu
hd: 2 x 80GB Seagate SATA (AHCI mode) in RAID 0 on XFS
display: 17" LCD 1280x1024 (LOL)
Some "before" test results with unpatched mplayer:
480i mpeg2: 3-6% cpu
1080i mpeg2: 14-17% cpu
These are both high-action clips that I recorded with mythtv.
And "before" with the video clip samples from the nvidia mplayer patches README:
"Grey.ts" (H.264): Segmentation Fault
"Amazing_Caves_720.wmv": 12-15% cpu
"nature_704x576_25Hz_1500kbits.h264": 8-10% cpu
"FlightSimX_720p60_51_15Mbps.wmv" (VC-1): 20-32% cpu
Some "after" results with the 180.11 beta driver and patched mplayer:
480i mpeg2: 1-3% cpu (usu. <1% ... some tearing is evident)
1080i mpeg2: 1-3% cpu (usu. around 1.4% ... looks more "blocky" than normal)
"Grey.ts": 1-3% cpu
"Amazing_Caves_720.wmv": 1.5-4% cpu (usu. around 3% ... looks awesome)
"nature_704x576_25Hz_1500kbits.h264": <1 - 2% (usu. <1% ... some tearing)
"FlightSimX_720p60_51_15Mbps.wmv": ~2.2% cpu (only very slight tearing)
I understand that nvidia is aware of the minor tearing issues and they plan to resolve them, but their primary concern right now is just making sure that everything is functional.
I'll be testing with mythtv trunk over the weekend.
[1] Even though it works, this cpu isn't officially supported by this mobo. It doesn't appear to be using the L3 cache.
[2] Only 3 GB of ram are currently being used because of the 32-bit os.
System specs --
mobo: Gigabyte GA-MA78GM-S2H
cpu: AMD Phenom 9850 [1]
ram: 4 GB DDR 800 dual-channel [2]
vga: 512MB 9300GS
os: 32-bit Kubuntu
hd: 2 x 80GB Seagate SATA (AHCI mode) in RAID 0 on XFS
display: 17" LCD 1280x1024 (LOL)
Some "before" test results with unpatched mplayer:
480i mpeg2: 3-6% cpu
1080i mpeg2: 14-17% cpu
These are both high-action clips that I recorded with mythtv.
And "before" with the video clip samples from the nvidia mplayer patches README:
"Grey.ts" (H.264): Segmentation Fault
"Amazing_Caves_720.wmv": 12-15% cpu
"nature_704x576_25Hz_1500kbits.h264": 8-10% cpu
"FlightSimX_720p60_51_15Mbps.wmv" (VC-1): 20-32% cpu
Some "after" results with the 180.11 beta driver and patched mplayer:
480i mpeg2: 1-3% cpu (usu. <1% ... some tearing is evident)
1080i mpeg2: 1-3% cpu (usu. around 1.4% ... looks more "blocky" than normal)
"Grey.ts": 1-3% cpu
"Amazing_Caves_720.wmv": 1.5-4% cpu (usu. around 3% ... looks awesome)
"nature_704x576_25Hz_1500kbits.h264": <1 - 2% (usu. <1% ... some tearing)
"FlightSimX_720p60_51_15Mbps.wmv": ~2.2% cpu (only very slight tearing)
I understand that nvidia is aware of the minor tearing issues and they plan to resolve them, but their primary concern right now is just making sure that everything is functional.
I'll be testing with mythtv trunk over the weekend.
[1] Even though it works, this cpu isn't officially supported by this mobo. It doesn't appear to be using the L3 cache.
[2] Only 3 GB of ram are currently being used because of the 32-bit os.