Troubleshooting the DirectShow Performance Tests (Windows Embedded CE 6.0)
1/6/2010
For more troubleshooting help, see Troubleshooting the CETK Tests.
You can often get better performance from your Windows Embedded CE-based device by increasing the number of backbuffers used and by switching the video renderer mode used. In addition, be sure your device's network card supports DMA and that your audio, video, and network drivers and cards are production-quality.
This test may not pass 100% of the test runs, nor may it be expected to do so. However, you should anticipate a very low failure rate, no more than 1% for all the media that you expect the device to play successfully. If the test fails inordinately or will not run correctly, check the following:
- Check that the URL works and can be correctly accessed on the device. Microsoft Internet Explorer for Windows Embedded CE might be useful in determining this. Specifically:
- The test will fail if the media information in the XML file is not updated to point to valid URLs.
- The tests will fail if they cannot access the media server.
- The tests will fail if they cannot access the exact URL on the media server.
- Check that the correct SYSGENs are all present in your OS build.
- Check that that you can initialize COM.
- Check that the URL can be rendered and you can achieve an end-to-end, completely connected graph.
- Check that the media files can be played successfully from beginning to end.
- Check that there is sufficient memory, especially for the higher bitrates and larger encodings.
- Make sure the test can find the XML file, and that it parses correctly.
- The test will also pass or fail based on the criteria specified in the <QualityControl> tag of the XML file. So if the test fails, check that the criteria listed in your XML file are valid.
- For example, the following Quality Control block:
<QualityControl>
will cause the test to check each clip to see that: - the number of frames dropped in the renderer equals or is less than the total number of frames specified in the tag (0), within the specific margin of error (0);
- the number of frames dropped in the decoder equals or is less than the total number of frames specified in the tag (0), within the specific margin of error (0);
- the number of frames drawn equals the total number of frames specified in the tag (3180), within the specific margin of error (5).
- The test will fail if the media information in the XML file is not updated to point to valid URLs.
- The tests will fail if they cannot access the media server.
- The tests will fail if they cannot access the exact URL on the media server.