Porting Applications from the Windows Media Audio SDK
This section describes some of the issues in porting code that uses the Windows Media Audio SDK.
The main issues to consider are:
- This SDK supports many more interfaces than does the Windows Media Audio SDK, in particular interfaces to handle video streaming. However, all of the functionality of the Windows Media Audio SDK can be found in just a few of these interfaces.
- This SDK is quite different and encoder output configuration has been simplified by the use of predefined profiles (output file configurations). Although it is possible to set up your own profiles, it is highly likely one of the predefined profiles will match your requirements exactly. For more information, see the IWMProfile Interface topic.
- This SDK includes a separate interface to handle editing only the header information. However the opening and closing of a file just for this purpose is handled by a different interface, so there is none of the duplication of methods that were found in the IWMAudioInfo interface in the Windows Media Audio SDK.
- Writing samples is handled through the use of the INSSBuffer interface, so a quick port can involve making a copy of the data into an INSSBuffer object created by the SDK.
- This SDK supports more features, even for audio streaming, such as reading audio files faster than in real time and streaming live audio over a network.
- Some terminology has been changed. For example the Flush method in the IWMAudioWriter interface does not equate to the Flush method in the IWMWriter interface, but is closer to the new EndWriting method.
Although most of the methods in the Windows Media Audio SDK have equivalents in this SDK, they do not always perform in exactly the same way For more information about the differences that must be considered, see the following two topics, which make up the remainder of this section:
© 1999 Microsoft Corporation. All rights reserved.
