I would add that I have tried very hard to get my ASIO drivers working well in BIAB on two different computers with two different high quality manufacturers' ASIO drivers, RME and Echo Audio, and also with the well regarded ASIO4All ASIO driver ... and have given up. I'm either using MME drivers on Windows or direct midi to sound module.

I also note that I have never had these problems in any other audio software package I own, which includes to latest updates Cubase5, Ableton6, AcidPro6, Reaper3 and many other applets ... or stand alone synths like NI FM8.

The very fact that, as you describe, it works sometimes and doesn't others suggests a basic problem with BIAB's ASIO implimentation. That was my experience as well. Further, everytime, on both PCs, I have changed the VST/ DXi host the program has crashed ... although with the MME drivers is properly loaded on boot up.

If you search this forum for "ASIO," you will find all kinds of threads noting these or similar ASIO problems ... as well as comments in many of the threads from some folks who report they have never experienced these problems.

Now, while it is true that proper GM patch selection sync issues will affect the sound that you get (the patch that plays) from your VSTi, it has absolutely nothing to do with latency ... other than in the very odd case that the patch that responded just happened to be some pad with an extraordinary long attack time.

I, as I believe others, have simply learned to compose/ arrange in BIAB and then drag the song's converted midi file to your sequencer of choice ... where easier patch and instument selection is available ... with the expected low latency of ASIO other things being equal, i.e., you have enought CPU and RAM to set a low buffer in your ASIO audio device. That would be my choice and recommendation for recording midi or audio to a song you created in BIAB.

Prado