I am confused why RealBand and BIAB work differently with regard to re-routing MIDI data to a DXi/VSTi synth. In RealBand when I select to re-rout MIDI data to DXi/VSTi (Forte) I don't have to select any of the MIDI output driver(s). I have available "Microsoft MIDI Mapper" and "Microsoft GS Wavetable Synth" but neither are selected. It plays MIDI out to Forte and works fine. In BIAB when I try to do the same I get yellow error messages, silence, and sometime crashes. BIAB gives me 3 choices "No MIDI/Sound Output", "Microsoft MIDI Mapper", or "Microsoft GS Wavetable Synth" and always one is selected even when the box is checked to re-rout to DXi/VSTi. No matter which of the 3 is selected by mouse click a box pops up telling me they won't be used because I have DXi/VSTi selected. Ok fine, that is exactly the way I want it. Then when I try to play a song a yellow error message pops up telling me that the Microsoft GS Wavetable Synth is in use by another program. It doesn't matter which of the 3 choices are selected because I always get the "Microsoft GS Wavetable Synth is in use by another program" error message. I thought both RealBand and BIAB ignore the MIDI output driver(s) when re-routing to DXi/VSTi correct? Normally this is never a problem for me because I almost always use a MIDI Sport and a Ketron SD2 but sometimes I am mobile and just want to use my notebook PC audio chipset. Dave

Microsoft Surface Pro, Thunderbolt 4, Windows 11, Scarlett Audio Interface, 2025 BIAB & RB, FL Studio Producer, Studio One Producer, Melodyne Editor, Ozone Advanced.