DMO Basics
This topic provides a brief overview of DMOs, but is not intended as a replacement for the complete documentation for DMOs in the DirectX documentation in the MSDN® Library.
A DMO is a COM object that transforms data. You pass data to it, and it returns the transformed data. In the case of a codec encoder DMO, you input uncompressed media data and the DMO delivers compressed media data. The primary advantage of using DMOs is that they all implement the same base interface, IMediaObject, which simplifies working with them because you can use the same object, regardless of the type of transformation being performed.
Because there are variables involved in any sort of data transformation, audio and video transformation must take into account the wide range of possible media configurations. The Windows Media Audio and Video codecs also support a number of special features that you must be able to configure by using the DMO.
In general, the variable information that is needed by the codec DMOs to compress and decompress digital media is conveyed in one of three ways:
- Set the input type on the DMO to convey the characteristics of the uncompressed media that you pass to an encoder DMO, and the characteristics of the compressed media that you pass to a decoder DMO.
- Set the output type on the DMO to convey the characteristics of the compressed media that are delivered by an encoder DMO, and the characteristics of the uncompressed media that are delivered by a decoder DMO.
- Using the methods of the IPropertyBag interface, configure other settings that support the various features of the codec DMOs as properties. IPropertyBag is a standard COM interface that is supported by all of the codec DMOs.
Additionally, some codec features are managed by using other interfaces that are specific to the codec DMOs. Reference information about these interfaces is provided in the Interfaces section of this documentation.
Input and output types are specific to input and output streams. Each stream represents a discrete representation of the content. For example, the Windows Media Video encoder DMO has a single input stream, and two output streams. The input stream accepts uncompressed video samples. The first of the two output streams delivers compressed samples; the other provides uncompressed samples. The individual samples in one output stream represent the same content as the corresponding samples in the other stream, but each stream delivers those samples in a different format.
Each stream (input or output) supports one or more types of media. A media type, or format, is described by a DMO_MEDIA_TYPE structure. You can query the DMO for the types that are supported by an output stream by calling IMediaObject::GetOutputType. This method returns a valid (though in some cases partially incomplete) output type for that stream. You can enumerate the supported media types for an output stream by making repeated calls to GetOutputType, incrementing the type parameter with each call. When the type index that you pass is out of bounds, the method returns DMO_E_NO_MORE_ITEMS. Input formats can be enumerated in the same way by using the IMediaObject::GetInputType method.
The types that are enumerated by the DMO are only the "preferred" types, however, other types may be supported. You can validate an output type by calling IMediaObject::SetOutputType. Use IMediaObject::SetInputType to validate an input type. Both methods will return DMO_E_TYPE_NOT_ACCEPTED if the DMO_MEDIA_TYPE structure you passed is invalid. Some DMOs require you to set an output type before enumerating any input types. The Windows Media Audio and Video codec DMOs all have inputs and outputs that have interdependent validation. That is, the output type you set will set the validation criteria for the input type. There are also some properties that, when set, alter the valid input and output types. For this reason, you should set all of the desired properties on the DMO before enumerating types.
When you have set the output and input types for the DMO, you can begin processing samples. Each input sample is passed to the codec using a call to IMediaObject::ProcessInput, and each output sample is delivered by the codec when you make a call to IMediaObject::ProcessOutput.
See Also
Send comments about this topic to Microsoft
Build date: 4/7/2010