|
About Device Handles
Each function that opens an audio device takes as parameters a device
identifier, a pointer to a memory location, and some parameters unique to each type of
device. The memory location is filled with a device handle. Use this device
handle of identify the open audio device when calling other audio functions.
The distinction between audio-device identifiers and audio-device handles is
subtle, but very important. Don't confuse the two in your application. The
following are differences between device identifiers and device handles.
- Device identifiers are determined implicitly from the number of devices
present in a system, which is obtained by using the device-numbering functions: auxGetNumDevs, joyGetNumDevs, midiInGetNumDevs, midiOutGetNumDevs, mixerGetNumDevs, waveInGetNumDevs, and waveOutGetNumDevs. There is a one-to-one correspondence between a device identifier and the
physical device it represents.
- Device handles are returned when device drivers are opened by using the
device-opening functions: midiInOpen, midiOutOpen, mixerOpen, waveInOpen, and waveOutOpen. There may be more than one for a device. You can think of a device instance
as a logical copy of the physical device.
- The device-capabilities and volume functions can take either a device
identifier or a device handle. These functions are midiInGetDevCaps, midiOutGetDevCaps, midiOutGetVolume, midiOutSetVolume, waveInGetDevCaps, waveOutGetDevCaps, waveOutGetVolume, waveOutSetVolume. All other functions take device handles.
There are no functions for opening and closing auxiliary audio devices.
Auxiliary audio devices don't need to be opened and closed like MIDI and waveform
devices because there is no continuous data transfer associated with them. All
auxiliary audio functions take device identifiers to identify devices.
| 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
|
