|
Managing MIDI Thru
You can connect a MIDI input device directly to a MIDI output device so that
when the input device receives an MIM_DATA message, the system sends a message with the same MIDI event data to the
output device driver. To connect a MIDI output device to a MIDI input device, use
the midiConnect function.
To achieve the best possible performance with multiple outputs, an application
can choose to supply a special form of MIDI output driver, called a thru driver. Although the system allows only one MIDI output device to be connected to a
MIDI input device, multiple MIDI output devices can be connected to a thru
driver. An application on such a system could connect the MIDI input device to this
thru device and connect the MIDI thru device to as many MIDI output devices as
needed. For more information about thru drivers, see the Windows device-driver
documentation.
Using Messages to Manage MIDI Recording
The following messages can be sent to a window or thread callback procedure
for managing MIDI recording:
MM_MIM_CLOSE
| Sent when a MIDI input device is closed by using the midiInClose function.
| MM_MIM_DATA
| Sent when a complete MIDI message is received. (This message is used for all
MIDI messages except system-exclusive messages.)
| MM_MIM_ERROR
| Sent when an invalid MIDI message is received. (This message is used for all
MIDI messages except system-exclusive messages.)
| MM_MIM_LONGDATA
| Sent when either a complete MIDI system-exclusive message is received or when
a buffer has been filled with system-exclusive data.
| MM_MIM_LONGERROR
| Sent when an invalid MIDI system-exclusive message is received.
| MM_MIM_MOREDATA
| Sent when an application is not processing MIM_DATA messages fast enough to keep up with the input device driver.
| MM_MIM_OPEN
| Sent when a MIDI input device is opened by using the midiInOpen function.
|
A wParam parameter and an lParam parameter are associated with each of these messages. The wParam parameter always specifies the handle of an open MIDI device. The lParam parameter is unused for the MM_MIM_CLOSE and MM_MIM_OPEN messages.
For the MM_MIM_LONGDATA message, lpMidiHdr specifies an address of a MIDIHDR structure that identifies the buffer for system-exclusive messages. The
buffer may not be completely filled, because the size of the system-exclusive
messages is usually not known before being recorded and because buffers whose total
size can contain the largest expected message must be allocated. To determine
the amount of valid data present in the buffer, use the dwBytesRecorded member of the MIDIHDR structure.
Using a Callback Function to Manage MIDI Recording
You can define your own callback function to manage recording for MIDI input
devices. The callback function is documented as MidiInProc.
The following messages can be sent to the wMsg parameter of the MidiInProc callback function:
MIM_CLOSE
| Sent when the device is closed by using the midiInClose function.
| MIM_DATA
| Sent when a complete MIDI message is received (this message is used for all
MIDI messages except system-exclusive messages).
| MIM_ERROR
| Sent when an invalid MIDI message is received (this message is used for all
MIDI messages except system-exclusive messages).
| MIM_LONGDATA
| Sent when either a complete MIDI system-exclusive message is received or when
a buffer has been filled with system-exclusive data.
| MIM_LONGERROR
| Sent when an invalid MIDI system-exclusive message is received.
| MIM_MOREDATA
| Sent when an application is not processing MIM_DATA messages fast enough to keep up with the input device driver.
| MIM_OPEN
| Sent when the MIDI input device is opened by using the midiInOpen function.
|
These messages are similar to those sent to window procedure functions, but
the parameters are different. A handle of the open MIDI device is passed as a
parameter to the callback function, along with the doubleword of instance data
that was passed by using midiInOpen.
For the MIM_LONGDATA message, lpMidiHdr specifies an address of a MIDIHDR structure that identifies the buffer for system-exclusive messages. The
buffer might not be completely filled. To determine the amount of valid data present
in the buffer, use the dwBytesRecorded member of the MIDIHDR structure.
After the device driver is finished with a data block, you can clean up and
free the data block.
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers
Software for Delphi and C++ Builder developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET More Online Helps Win32 Programmer's Reference
Win32 Multimedia Programmer's Reference
OLE Programmer's Reference
Microsoft Windows Pen API Programmer's Reference
Microsoft Windows Sockets 2 Reference
Microsoft Windows Telephony API (TAPI) Programmer's Reference
Unix Manual Pages
|
