Implementing Your DSP Code
[The feature associated with this page, Windows Media Player SDK, is a legacy feature. It has been superseded by MediaPlayer. MediaPlayer has been optimized for Windows 10 and Windows 11. Microsoft strongly recommends that new code use MediaPlayer instead of Windows Media Player SDK, when possible. Microsoft suggests that existing code that uses the legacy APIs be rewritten to use the new APIs if possible.]
Once you have built the sample DSP plug-in, you can modify the code to create your own Windows Media Player DSP plug-in. Which methods you change and which you can leave as they are depends upon the following factors:
- The number of properties you want to allow the user to change. You will certainly want to change the default property page implementation to suit your needs, and you may need to add additional properties.
- Whether your DSP plug-in needs to allocate any streaming resources. Your plug-in may require additional buffers.
- Whether your audio DSP plug-in needs to continue to output data after Windows Media Player has stopped supplying data in the input buffer.
The following sections use the DSP plug-in sample code generated by the Windows Media Player Plug-in Wizard to illustrate important concepts. You might find it helpful to open Microsoft Visual Studio and generate the sample code first so you can refer to it as you read this section. For details about how to use the Windows Media Player Plug-in Wizard, see Building a DSP Plug-in.
| Section | Description |
|---|---|
| Implementing an Audio DSP Plug-in | Discusses what you need to know to create your own audio DSP plug-in based on the sample generated by the wizard. |
| Implementing a Video DSP Plug-in | Discusses what you need to know to create your own video DSP plug-in based on the sample generated by the wizard. |
Related topics