Reference

This section lists the functions, messages, and structures provided by Windows for use by audio device drivers.

Windows communicates with audio device drivers through messages sent to the driver. The driver processes these messages with its wodMessage, widMessage, modMessage, midMessage, or auxMessage entry-point function. The function used depends on the type of device the driver supports. Drivers can also send messages to client applications with the DriverCallback function.

This section contains an alphabetical list of all messages that can be received and sent by audio device drivers. Each message name contains a prefix, identifying the type of the message. The following list identifies the prefixes used for audio device driver messages:

Prefix

Description

AUXDM

Sent by MMSYSTEM to an auxiliary audio device driver's auxMessage function.

MIDM

Sent by MMSYSTEM to a MIDI input driver's midMessage function.

MIM

Sent by MIDI input drivers to notify client applications.

MODM

Sent by MMSYSTEM to a MIDI output driver's modMessage function.

MOM

Sent by MIDI output drivers to notify client applications.

MXDM

Sent by MMSYSTEM to a mixer driver's mxdMessage function

WIDM

Sent by MMSYSTEM to a waveform input driver's widMessage function.

WIM

Sent by waveform input drivers to notify client applications.

WODM

Sent by MMSYSTEM to a waveform output driver's wodMessage function.

WOM

Sent by waveform output drivers to notify client applications.


A message consists of three parts: a message number and two DWORD parameters. Message numbers are identified by predefined message names. The two DWORD parameters contain message-dependent values.

The stream buffer enhancement to the MIDI device architecture not only affects the MIDI SDK functions, data structures, and messages, but also reaches to the DDK level as driver messages. Many of the new MIDI driver messages documented in this section support the block data transfer of the stream buffer.