Namespace: radio42.Multimedia.Midi
Assembly: Bass.Net (in Bass.Net.dll) Version: 2.4.17.2
Member name | Value | Description | |||||||
---|---|---|---|---|---|---|---|---|---|
MIM_OPEN | 961 |
The MIM_OPEN message is sent to a MIDI input callback function when a MIDI input device is opened.
| |||||||
MIM_CLOSE | 962 |
The MIM_CLOSE message is sent to a MIDI input callback function when a MIDI input device is closed.
The device handle is no longer valid after this message has been sent. | |||||||
MIM_DATA | 963 |
The MIM_DATA message is sent to a MIDI input callback function when a MIDI message is received by a MIDI input device.
MIDI messages received from a MIDI input port have running status disabled; each message is expanded to include the MIDI status byte. This message is not sent when a MIDI system-exclusive message is received. You might used the MidiShortMessage class to construct and or unpack the message into it's components. | |||||||
MIM_LONGDATA | 964 |
The MIM_LONGDATA message is sent to a MIDI input callback function when a system-exclusive buffer has been filled with data and is being returned to the application.
The returned buffer might not be full. To determine the number of bytes recorded into the returned buffer, use the Data member of the MIDI_HEADER structure specified by param1. | |||||||
MIM_ERROR | 965 |
The MIM_ERROR message is sent to a MIDI input callback function when an invalid MIDI message is received.
| |||||||
MIM_LONGERROR | 966 |
The MIM_LONGERROR message is sent to a MIDI input callback function when an invalid or incomplete MIDI system-exclusive message is received.
The returned buffer might not be full. To determine the number of bytes recorded into the returned buffer, use the Data member of the MIDI_HEADER structure specified by param1. | |||||||
MIM_MOREDATA | 972 |
The MIM_MOREDATA message is sent to a MIDI input callback function when a MIDI message is received by a MIDI input device but the application is not processing MIM_DATA messages fast enough to keep up with the input device driver. The callback function receives this message only when the application specifies MIDI_IO_STATUS in the call to the MIDI_InOpen(IntPtr, Int32, MIDIINPROC, IntPtr, MIDIFlags) function.
An application should do only a minimal amount of processing of MIM_MOREDATA messages. (In particular, applications should not call the PostMessage function while processing MIM_MOREDATA.) Instead, the application should place the event data into a buffer and then return. When an application receives an MIM_DATA message after a series of MIM_MOREDATA messages, it has caught up with incoming MIDI events and can safely call time-intensive functions. MIDI messages received from a MIDI input port have running status disabled; each message is expanded to include the MIDI status byte. This message is not sent when a MIDI system-exclusive message is received. You might used the MidiShortMessage class to construct and or unpack the message into it's components. | |||||||
MOM_OPEN | 967 |
The MOM_OPEN message is sent to a MIDI output callback function when a MIDI output device is opened.
| |||||||
MOM_CLOSE | 968 |
The MOM_CLOSE message is sent to a MIDI output callback function when a MIDI output device is closed.
The device handle is no longer valid after this message has been sent. | |||||||
MOM_DONE | 969 |
The MOM_DONE message is sent to a MIDI output callback function when the specified system-exclusive or stream buffer has been played and is being returned to the application.
|