DirectMusic Miniport Driver Interface
The DMus miniport driver interface is based on the MIDI miniport driver interface, but it adds the following extensions to support advanced synthesizers:
DLS downloads greater than 16 channels per instance
Sequencing of note events in hardware
The DMus miniport driver interface differs from the MIDI miniport driver interface in several ways. A DMus miniport driver implements the interface IMiniportDMus as opposed to IMiniportMidi. This interface is similar to IMiniportMidi, but the IMiniportDMus::NewStream method creates an IMXF (MIDI transform filter) interface and connects to an IAllocatorMXF interface in the DMus port driver, as opposed to implementing an IMiniportMidiStream interface. IAllocatorMXF and IMXF wrap the standard GetMessage and PutMessage calls (see IAllocatorMXF::GetMessage and IMXF::PutMessage). These calls deal with packaged events rather than with raw MIDI bytes.
The DMus miniport driver for a synthesizer can implement some or all of the DirectMusic properties. These properties allow the system to manage DLS downloads and channel allocations for the device. The dmusprop.h header file defines DirectMusic-specific property items. For a list of these properties, see KSPROPSETID_Synth and KSPROPSETID_Synth_Dls.
DMus miniport drivers are expected to allow the creation of multiple pin instances. Each pin instance acts as one virtual synthesizer and contains a set of channels and DLS downloads independent of the other pin instances.
Some of the synth properties described in Audio Drivers Property Sets act on a pin instance, and others are global. To process the global properties, the synthesizer must have a synthesizer node in its topology. The description of each property item indicates whether that item is sent to the synthesizer node or to a pin instance. For each piece of hardware supporting synthesis, there exists a port driver object and a miniport driver object, as shown in the following figure.
The port driver object exposes one instance of an IPortDMus interface, which is held by the miniport driver object. The miniport driver exports one instance of an IMiniportDMus interface, which is held by the port driver. For every instantiated pin, the port driver requests a matching IMXF interface. Communication between the system and this instance is the combination of property requests addressed to the pin and events flowing to or from the IMXF stream interface.
Two objects must be passed to the miniport driver when it is created:
The clock is very important for render and capture operations. The miniport driver needs to render notes at their specified times; when the miniport driver reads in MIDI data, it needs to know the time so it can time-stamp the kernel event. For more information, see Latency Clocks.
The allocator object, which has an IAllocatorMXF interface, is used as a memory pool to recycle memory. All MIDI messages in the system are allocated from this common pool. The allocator object should be used to create or destroy the individual messages.
This section includes: