Windows XP Media Center Edition Test Kit v2.0
Posted by Daniel Fleshbourne on 09 November 2004 - 17:12 · 12 comments & 979 views
About the Author
Full name: Daniel Fleshbourne
Forum name: Daniel
Contact: via forum PM
Submissions: Normal · Headline
Full name: Daniel Fleshbourne
Forum name: Daniel
Contact: via forum PM
Submissions: Normal · Headline
Slashdot It!
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
Add to Google- Advertisement
-
-
#1 Posted by fdlazarte on 09 Nov 2004 - 17:34
- and so?
-
#2 Posted by Falsante on 09 Nov 2004 - 18:31
-
-
#3 Posted by tkukoc2200 on 09 Nov 2004 - 19:00
-
-
#4 Posted by Moe Szyslak on 09 Nov 2004 - 19:03
- ooo arrrr
-
(1 reply)
#5 Posted by Shagadelic, Baby! on 09 Nov 2004 - 22:28
- *snipped*
Last edited by 52 on 10 Nov 2004 - 04:29 -
#5.1 Posted by cooldude7273 on 09 Nov 2004 - 22:42
- ?????????
-
#6 Posted by Lasker on 09 Nov 2004 - 23:09
- wtf is this?
-
#7 Posted by soldier1st on 09 Nov 2004 - 23:37
- stupid useless troll spam
ban this useless troll from all the forums
-
#8 Posted by greg098 on 10 Nov 2004 - 01:12
- umm guess he wants banning LOL
-
#9 Posted by buzz99 on 10 Nov 2004 - 13:21
- ZZZzzzzzz.....
-
#10 Posted by eXtermia on 11 Nov 2004 - 05:27
- 1.0 Introduction
This paper provides information on the purpose and usage of the Microsoft Media Center Test Kit or Media Center Partner Test (a.k.a. supplemental test tools). These test tools do not serve as comprehensive test coverage by any means and do not guarantee that the system is ready to ship or fully functional. The test tools are providing as a means to assist OEMs building Media Center PCs to diagnose or detect common device driver or system configuration issues. The advanced tools are also provided to assist hardware vendors developing hardware device drivers for Media Center PCs.
2.0 Components
The Media Center Test Kit setup (MCtestkit.msi) installs the following supplemental test tools and documents.
2.1 Supplemental Test Tools
Media Center Diagnostic Tool System diagnostic tests for high level feedback on components
Advanced Tests
BobWeave Test Verifies video card capability to do de-interlacing and mixing simultaneously
De-interlacing Test Automated Tests for de-interlacing abilities of Video card
Encoder WHQL Test Tests MPEG2 encoder for compliance with Encoder API
MPEG Encoder Test Tests MPEG2 streams coming out of encoder for compliance with MPEG2 syntax.
ProcAmpControl Tests Validates the DXVA ProcAmp controls in the graphics driver
VidCtlXDS Advanced tool to for verification of TV playback functionality using same underlying infrastructure as Media Center.
VBITest DShow filter to be used in Graph Edit to assess the quality of VBI data delivered by a TV tuner
TV Stats Tool for monitoring Media Center performance including CPU usage Video frames and other metrics.
MCMon or DeviceMon MCMon or DeviceMon is an eventing mechanism and test infrastructure component that will allow testing to be done on Media Center Extenders in much the same way that it is done with local Media Center sessions.
Blink Blink is a test for multimedia Video Capture (VidCap) devices.
2.2 Documents
Getting Started.doc This document provides a brief on the various tools that are included in the Partner Test kit as mentioned in section 1.
Media Center Video Quality.doc This document provides information about components that contribute to video quality on computers running the Microsoft® Windows® XP Media Center Edition operating system.
VideoControl Whitepaper.doc This document is for hardware vendors who are building video capture and encoding subsystems for use in computers running Microsoft Windows XP Media Center Edition.
-
#11 Posted by neufuse on 11 Nov 2004 - 16:42
- if you don't know what it is you probably don't need it and don't need to comment on it like this first 6 stupid posts on here... this is mainly for OEM's not a standard user
Other
Ben Goodger has updated his Blog with some interesting stuff concerning the 1.0 release. Read the whole entry here.
This day has come a lot later than any of us originally planned, but that's the way software goes. I've learned a lot about a huge number of things in the process, have had the opportunity to talk to a lot of different people about their experiences with the software, etc. It's been a long road but we're finally here. No software is perfect, we did not fix every bug, implement every feature, but what we did do was create what we believe to be the best browser around. I want to thank you all again for the support over the past few years.
We also asked Ben what the progress was after 1.0 :
"After 1.0 we plan to resync our development work with the Mozilla trunk so that we can immediately pick up the great work that's been going on with Gecko since we've been away, continue our HIG compliance efforts for MacOS X, improve existing systems and plan for the next major release. The first interim release will be 1.1 in or around March 2005. ".