|Microsoft DirectX 9.0|
A number of subtypes are defined for DV video. Each has a FOURCC code and a corresponding GUID value. Not all of these formats are supported; see the Remarks section for more information.
|'dvsl'||MEDIASUBTYPE_dvsl||12.5 Mbps||SD-DVCR 525-60 or SD-DVCR 625-50|
|'dvsd'||MEDIASUBTYPE_dvsd||25 Mbps||SDL-DVCR 525-60 or SDL-DVCR 625-50|
|'dvhd'||MEDIASUBTYPE_dvhd||50 Mbps||HD-DVCR 1125-60 or HD-DVCR 1250-50|
Refer to IEC-61834 for more information about these formats.
|'dv25'||MEDIASUBTYPE_dv25||25 Mbps||DVCPRO 25 (525-60 or 625-50)|
|'dv50'||MEDIASUBTYPE_dv50||50 Mbps||DVCPRO 50 (525-60 or 625-50)|
|'dvh1'||MEDIASUBTYPE_dvh1||100 Mbps||DVCPRO 100 (1080/60i, 1080/50i, or 720/60P)|
Refer to SMPTE 314M for more information about dv25 and dv50, and SMPTE 370M for more information about dvh1.
Two additional DV subtypes are defined in the header file Uuids.h. These correspond to FOURCC codes that are produced by certain DV codecs; they do no correspond to any defined DV standards. These subtypes are obsolete and should not be used.
When data is captured from an external DV device, the MSDV driver parses the transport data, while the DV Splitter and DV Video Decoder filters parse the contents of the data packets. Currently, these components provide the following support:
In practice, this means applications can capture both 25-Mbps formats, SDL-DVCR and DVCPRO 25. Application can transmit both formats to tape, as long as the target device matches the capture device. In other words, if you capture DVCPRO 25 from a device, you can transmit it back to the same device, but not to an SDL-DVCR device.