Building custom plug-ins using the Windows Media Player (WMP) 9 Series SDK involves creating Component Object Model (COM) objects that interface directly with the player’s core rendering engine and user interface. While Microsoft has shifted focus to the modern MediaPlayer API for Windows 10 and 11, understanding the 9 Series SDK architecture is essential for maintaining legacy media infrastructure or managing classic Win32 systems. Core Plug-in Types
The SDK categorizes plug-ins based on where they intercept or alter the media playback pipeline:
User Interface (UI) Plug-ins: Add custom elements (like text boxes, buttons, or metadata fields) directly to the “Now Playing” pane of the player. They can run as integrated sub-panes or detached floating windows.
Digital Signal Processing (DSP) Plug-ins: Intercept raw audio or video streams before rendering. They allow you to apply real-time modifications like equalizers, custom audio effects, or video filters.
Visualization Plug-ins: Render dynamic, mathematical graphics synchronized to the audio frequencies and waveform of the currently playing track.
Rendering and Conversion Plug-ins: Handle specialized data or decode unique formats embedded inside Advanced Systems Format (ASF) containers. Key Architectural Interfaces
WMP plug-ins are essentially Dynamic Link Libraries (DLLs) written primarily in C++ due to COM requirements. The underlying engine interacts with your custom code through specific interface entry points:
IWMPPluginUI: The primary interface required for UI plug-ins, responsible for managing the lifecycle, display state, and embedded windows inside the player.
IWMPEvents: Allows your plug-in to listen to structural player occurrences, such as play, pause, stop, track changes, or media item updates.
IMediaObject: For DSP plug-ins, WMP relies on the DirectX Media Object (DMO) architecture. Your code must implement standard DMO data stream interfaces to process input and output buffers. The Step-by-Step Build Workflow
[Install Requirements] ➔ [Run Plug-in Wizard] ➔ [Implement Interfaces] ➔ [Register COM DLL] 1. Set Up Your Environment
To compile legacy WMP 9 plug-ins, your developer environment must include:
An older version of Microsoft Visual Studio (e.g., VS .NET 2003 or later standard Win32 C++ tooling).
The Windows SDK containing the Windows Media Player SDK headers and libraries.
The Windows Media Player Plug-in Wizard, a native project template installer. 2. Generate the Boilerplate
The easiest way to initialize a project is via the WMP Plug-in Wizard:
Open Visual Studio and create a new project using the installed WMP Plug-in template.
Choose your plug-in type (e.g., UI Plug-in vs. DSP Plug-in).
Specify whether your plug-in should have a visible user interface window or run silently in the background.
The wizard outputs a standard C++ ATL/COM DLL shell with pre-configured GUIDs and stub methods. 3. Implement Custom Logic
Open the generated source files to inject your functional logic: Getting Started with the Plug-in Wizard | Microsoft Learn
Leave a Reply