Share via

HEVC Fuzz DXVA Test

  • Article

This test verifies DXVA decoding on the graphics adapter, and DXVA-HD quality on the graphics adapter.

Test details

Associated requirements

Device.Graphics.WDDM12.Render.D3D11VideoDecoding

See the device hardware requirements.

Platforms

Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86

Expected run time

~2 minutes

Categories

Certification

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Graphic Adapter or Chipset Testing Prerequisites.

Before you run the test, download the Supplemental Content for Windows HCK Tests for DXVA Multimedia Tests. You can use the content in the following ways:

  1. You can put the content on the Windows Hardware Certification Kit (Windows HCK) Server under the path %DTMBIN%..\Tests\DXVAContent, and use the default value for ContentSource when you schedule the tests. In this case, each test will copy over the input content that is required only for that single test, and then delete the content after the test has completed. This method is useful when you test machines that have less than 75GB free space available.

  2. You can put the content in a different location on the Windows HCK Server, or on a network share that is accessible to the client machines. In this case, when you schedule the tests you must update the value of ContentSource to point to the location that contains the copied files. This method has the same result as the previous option, but provides flexibility in where the input content is located.

  3. You can copy the content locally onto each client machine before you run the tests and update the value of ContentSource to be the local path on the machine. For example, if you use an external drive with letter d: and place the content in d:\DXVAContent, when you schedule the test you must set ContentSource to d:\DXVAContent. Note that this parameter is passed to all client machines against which the tests are scheduled, so you must make sure that the content exists in an identical path on all client machines.

    This method causes the test to use the locally cached content – the test does not copy each file for each test. This method requires at least 75GB free space on the client machine, but speeds up the test run because the content does not have to be copied for each test.

  4. Copy the content to each client machine before you run the tests and add the content path to the %PATH% environment variable. When you schedule the test, use the default value for ContentSource (the value is irrelevant in this case). You can use a combination of the third method and this method to make sure that ContentSource points to the content path for machines that use the third option.

    This method causes the tests to behave the same way as when using the third option because the content is not copied for each test; this method speeds up test run time and requires at least 75GB free space on the client machine. The advantage of this option is that the content does not have to exist in the same path on all client machines as long as the %PATH% environment variable is set correctly for each machine.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

Error Description/Workaround

Content not available to client machine

ERROR>> Failed to find input source file …

Confirm that the ContentSource parameter is pointing to the location of the source content at run time.

 

More information

Command syntax

Command option Description

ContentSource

The location of the DXVA and DXVAHD input source content files. Client machines must have access to this location)

Default value: [WTT\TestBinRoot]\..\DXVAContent

 

DXVA Tests

 

 

Send comments about this topic to Microsoft