M-AUDIO Delta RBUS - Manual (Page 53)

developing. As we add more tracks within our music software, we set
them to the next pair of Delta software outputs (1/2, then 3/4…), and
bring up the faders of those software inputs in the monitor mixer
(WavOut 1/2, WavOut 3/4…). We continually monitor from the Delta
analog outs, via the ‘Mon. Mixer’ setting as the monitor ‘source’ in the
Patchbay/Router page, and adjusting our mix of the software outputs
(and the way we monitor our guitar and vocal at the inputs) via the
Monitor Mixer settings.
Notice that if we continue to overdub past track 8, we run out of WavOut
devices to assign to. In this case, you may want to do some of your level
mixing within the software application if it supports it. Most applications
will allow you to assign more than one track to an output device and then
set the relative levels of the tracks within the software, letting the
software do the mixing. In this example you could have assigned all of
the playback tracks to "WavOut SP/ANA" and let the software handle
the mix, which, after you are through recording, may be your choice for
mixing tracks.
Troubleshooting
This section addresses potential problems that can occur in all operating
system environments, with emphasis on hardware troubleshooting.
Within the PC environment there are a limited number of hardware
resources (I/O addresses, IRQs, and DMA channels) available for use.
Since audio cards require many resources, most audio card installation
problems arise from unavailable or improperly set resources. This is
important enough to repeat:
IMPORTANT: Most sound card installation problems result
from attempting to use system resources (IRQs, address
locations) already in use by other hardware (or software
acting as “virtual” hardware) in the system.
The Delta R-BUS has been carefully designed to minimize the number of
resources consumed (it requires just one IRQ and does not require any
DMA channel resources). It is also capable of sharing an IRQ in some
cases. However, the possibility of resource conflicts still exists due to the
nature of the Windows environment. Many resource conflicts are
automatically recognized by Windows’ Plug-and-Play (PnP) system.
When a resource conflict is detected, it is displayed in the Windows
Device Manager. The Device Manager places a yellow exclamation point
on top of the icon associated with the problem device. For an example of
how the Device Manager should look when a Delta R-BUS is successfully
53