AUDIO MIDI SETTINGS DRIVER
Open the BIAB Audio Settings dialog with the menu 'Opt|Preferences', then click the 'Audio' button, then click the 'Audio Drivers' button when ASIO is selected as your Audio Driver type. You can also run the ASIO control panel in the BIAB Audio Settings dialog. Often the ASIO control panel can be found in Windows' 'Start|Settings|Control Panel' menu item.
You can run the soundcard's ASIO control panel by launching it when BIAB is not running. Any time you change the soundcard's ASIO latency, BIAB will auto-adjust to use the driver's new latency setting. BIAB uses whatever latency is preferred by your ASIO driver. ASIO:ĪSIO latency is user-adjusted by running your ASIO soundcard driver's control panel. Higher latency might be necessary on a slow computer, but dropouts could also happen if you have a fast computer loaded down with many 'bloatware' softwares running in the background. But if your computer is struggling to keep up, and you hear clicks or dropouts, increase the latency until playback is smooth. If you hear no dropouts, use the minimum 100 mS. With MME, you can manually adjust Audio Latency in the range of 100 mS to 2000 mS. If the Audio latency is 100 mS, then we know that sound will come out the speakers about 100 mS after a MIDI Note is played, so it is a good bet that 100 mS is also the proper MIDI 'Driver Latency'.Īudio Settings dialog - 'Audio Latency in mS'Īudio Latency determines how long it takes for audio tracks (or DXi/VSTi rendered sound) to come out of the speakers after the computer program sends audio to the soundcard. In MOST CASES the DXi/VSTi playback latency will be identical to the Audio Driver's latency. If you type in a different value, BIAB will ignore it. Using DXi or VSTi synths, 'Driver Latency' is automatically set to the audio latency of your soundcard driver. If on-screen notes are hilighting AFTER you hear the notes, DECREASE 'Driver Latency'. If on-screen notes are hilighting BEFORE you hear the notes, INCREASE 'Driver Latency'. So this MIDI Driver Latency must be experimentally adjusted 'by eye and ear' to get a 'perfect' match. It is impossible for BIAB to always accurately estimate the exact latency of standalone softsynths and any possible video latency on each computer. To make the notation or pianoroll notes 'light up' at the same time you hear the sound, the screen display must be delayed. In other words, if driving the Microsoft synth, BIAB plays a MIDI note, and then some time later the sound comes out of your soundcard. On XP SP2, we find that the Microsoft GS Wavetable softsynth needs a latency in the ballpark of 100 mS, and the standalone Roland VSC-3 usually needs a latency in the ballpark of 300 mS. This latency will vary among different softsynths, and as they run on different computers.
If connecting to a standalone softsynth such as the Microsoft GS softsynth or the standalone VSC softsynth, the screen display must be delayed by the audio latency of the softsynth. For most hardware synths, 'Driver Latency' can be set to zero for good screen sync with the sounds. If connecting a MIDI cable to a hardware synthesizer, most hardware synths have latency in the ballpark of 3 to 20 mS. Screen display includes scrolling/hilighting the ChordSheet, Notation, and Piano Roll windows, and lighting-up the on-screen piano notes. The purpose of 'Driver Latency' is to sync the playback screen display to the MIDI sounds. MIDI Driver Setup dialog - 'Driver Latency'
0 kommentar(er)
