Ok, before I go too far down the rabbit-hole...

My normal setup for this sort of software involves using ASIO4ALL to output through the onboard audio support. Upon starting BiaB, I tried to use that driver, only to find that the ASIO outputs are disabled, presumably because BiaB (via the MS Wavetable GS synth) is already using the audio device.

No problem, I would certainly prefer to use a DXi/VSTi substitute, starting with either the VSC3 or the Cakewalk TTS1 (similar Roland-based GM2 synth). I got that to work, but apparently BiaB still has the MS synth active, because the ASIO outputs are aren't available. (It's playing the TTS1, but apparently through the MME driver.)

What's worse (or, more to the point, completely unacceptable), this condition persists after BiaB exits: my other DAWs/VST hosts can't use the ASIO interface until I reboot.

I need to get BiaB to:
1. completely ignore the MS Wavetable synth,
2. send its MIDI output to the DXI/VST I specify,
3. send the DXI/VST output through the (low-latency) ASIO4ALL driver, and
4. leave everything in a usable state when it exits.

Suggestions?