Quote:

I'm going to chime in here . I hope I have this right. Paul's tool is sort of like a wrapper for a HW synth. If you insert it as the chosen VSTi say for the BASS track, and assume Bass is on channel 2 still, it's only going to pass channel 2 info out to the midi port.



That's correct. My midi redirector will pass any midi data it receives from BiaB (the host). If it's inserted in the bass slot it will only pass channel 2 data (assuming that's what BiaB passes to it, and I've no reason to doubt that).

Quote:

Now being that you CAN use a soft synth in the default slot and on individual tracks try rethinking the application. Use Paul's tool as the DEFAULT synth. This will now pass all of the info out the the midi port.Set your HW synths/harmony units to the appropriate channel. Now if you want a soft synth on say the bass insert it as a track specific VSTi.



That's an interesting idea. One I certainly didn't think of.

In theory that should work. I wish we had a map of BiaBs internel midi (and audio) routing. Then we'd know for sure what data will be passed. I also wish I knew more about the function of Sysex data. That might be the key to getting VW to function. I will be looking into this more as I find time.

Getting back to your suggestion, I'll give it a try ASAP.

BiaB 2013 b366, RB 2013 b4, WinXP Pro SP3, Toshiba M70, 1.8GHz 2GB RAM 100GB HD. Focusrite Saffire 6 USB, Ketron SD2.BiaB Wiki