Configuring Data Unit Extensions
[The feature associated with this page, Windows Media Format 11 SDK, is a legacy feature. It has been superseded by Source Reader and Sink Writer. Source Reader and Sink Writer have been optimized for Windows 10 and Windows 11. Microsoft strongly recommends that new code use Source Reader and Sink Writer instead of Windows Media Format 11 SDK, when possible. Microsoft suggests that existing code that uses the legacy APIs be rewritten to use the new APIs if possible.]
Samples written to ASF files can contain additional information apart from the media samples themselves. This information is included using data unit extensions. For more information about data unit extensions, see Data Unit Extensions.
To use data unit extensions, you must configure the stream in the profile to accept them. To configure a data unit extension for a stream, perform the following steps.
- Obtain a pointer to the IWMStreamConfig2 interface by calling the QueryInterface method of IWMStreamConfig.
- Call IWMStreamConfig2::AddDataUnitExtension to register a type of data unit extension for the stream.
You can examine all of the data unit extension types currently registered for a stream by calling IWMStreamConfig2::GetDataUnitExtensionCount to retrieve the number of registered data unit extension types. Then you can loop through all of the types using calls to IWMStreamConfig2::GetDataUnitExtension for each.
Data unit extensions are assigned a size when configured for a stream. Many data unit extension systems use data that is a constant size (usually a structure). However, you can also configure your data unit extensions to be of variable size by setting the size to 0xFFFF. Each data unit extension assigned at encoding time can then be of any size between 1 byte and 65534 bytes. Variably sized data unit extensions are also called dynamic data unit extensions.
The advantage of using dynamic data unit extensions is that you can attach extension data as needed. If you define a data unit extension with a set size, every sample for the stream must contain extension data of that size, even if you have no data for some samples. With dynamic data unit extensions, you can omit data unit extensions from some samples, which saves space and reduces bandwidth requirements. However, if data unit extensions are of variable size, the reading object cannot verify the received extension data against a static size. You must verify that the extension data that you receive is valid, and not malicious distortion of the bit stream.
Individual data unit extensions must be set on samples by using the INSSBuffer3::SetProperty method. For more information, see Setting Data Unit Extensions.
Related topics