From: "Lan, Hai" <hai.lan@intel.com>
To: SSD-OTC GFX QA <ssd-otc.gfx.qa@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Q1 RC2 test report for SNB H264 encoding driver
Date: Sat, 9 Apr 2011 15:42:05 +0800 [thread overview]
Message-ID: <625BA99ED14B2D499DC4E29D8138F1505A6B7E22A9@shsmsx502.ccr.corp.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 849 bytes --]
The second round test result for the Linux SNB H264 encoding driver has come out. This version can support P frames now. Totally there are 1 P1 bug(Bug 464) and 4 P2 bugs(Bug 459, Bug 460, Bug 462, Bug 463). Following is the result for FVDO_Shore_4cif.yuv(704x576, QP=26).
H264 encoding quality
Linux driver PSNR (RC1, I frames only)
Linux driver PSNR (RC2, with 29 P frames per 30 frames)
Windows driver PSNR(I frames only)
SNR Y(dB)
14.15
41.23
43.38195
SNR U(dB)
11.42
47.92
49.67663
SNR V(dB)
10.68
48.62
49.02728
H264 encoding performance
Linux driver FPS (RC1, I frames only)
Linux driver FPS (RC2, with 29 P frames per 30 frames)
Windows driver FPS(I frames only)
FPS
6
104
516.61
The detailed result can be found in the attachment. Thanks.
Hai Lan
[-- Attachment #1.2: Type: text/html, Size: 10258 bytes --]
[-- Attachment #2: h264encoder_ww15.xlsx --]
[-- Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Size: 130776 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2011-04-09 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=625BA99ED14B2D499DC4E29D8138F1505A6B7E22A9@shsmsx502.ccr.corp.intel.com \
--to=hai.lan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ssd-otc.gfx.qa@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).