Quote:

Somewhere in the program there is something wrong... but I can't figure it out.... I'm not a newbie... I have had BIAB since version 1, but as I said in my first post...I'm stumped.

I can confirm that in build 303, before ever hitting "play", my external controller plays the loaded DXi, TTS-1 in my case (albeit with significant latency, which is not an issue for me since I don't do real time external control with this configuration.) FWIW, the audio driver is ASIO4All, "ASIO always on is enabled", "route midi thru to midi driver" is unchecked, the three midi thru options in the midi options window are enabled, and I'm running under Win7x64.

The problem you describe has occurred here intermittently over the years. I've always gotten it to go away, but can't recall exactly how. FWIW, some thoughts:

1) Ensure "asio always on" is enabled.

2) I don't think you said which VST/Dxi you've loaded. Try triggering it from its own interface to make sure it plays. One thing I've found with the TTS-1 is that if it receives bank controllers not within its midi implementation, the voice on that channel can get "stuck" in limbo. It won't play, and it won't respond to further patch/bank changes. I've found I can unstick it by manually resetting it to a valid patch from within the TTS-1 interface itself. Perhaps something like this has happened?

3) Use the midi monitor to make sure the output from your controller is actually reaching BB, and that the channel/patch data etc. have the desired values. (In the display filter for the monitor, don't forget to enable computer midi input.)

4) If using ASIO, ensure that there's no other app making a demand on it (even if ASIO always on is enabled.)

Post back if issue remains. If no further insight on the forum, a support call might be in order.

Good luck. -Ron

EDIT - Understood from your OP, you've already tried some of these approaches. Sorry, just wanted to put all thoughts in one place.

Last edited by rkl122; 07/12/10 10:21 AM.