This won’t help your current issue - but as info:

The MIDI "Output drivers," determines where to route/send RealBand MIDI data to EXTERNAL MIDI devices, which includes (paradoxically) things like "MIDI yoke," LoopBe2 (free by the way) or LoopBe30 or other virtual port devices.

So as far as getting ST 3 or any plug-in to work within Real Band the "MIDI Output Drivers" (all, one, or none) are immaterial. For the purists, yes we can MAKE them matter if we start using software re-routers like LoopBe2, Loopbe30, MIDI yoke to send MIDI data to ST3 standalone - but that is NOT the way to troubleshoot this problem or even work in general)

The MIDI "Output drivers" are in play: (again without confusing the bigger topic with "MIDI Thru" settings) If you don’t have "Re-Route MIDI playback to default Dxi/VSTi Synth" checked. In this case, MIDI data in Real Band, during playback, will go out to the "outside world" devices (external hardware synths or to software re-routers or even the MS GS wavetable essentially the same thing as CoyoteWT).

If you DO HAVE "Re-Route MIDI playback to default Dxi/VSTi Synth" CHECKED then ALL MIDI data (EXCEPT possibly MIDI thru) is sent to the user selected VSTi's within Real Band (either the default VSTi or the individual track(s) set VSTi's - they can all be different.

Again I suggest you CALL PG they can walk you through in real time and ask follow ups, that are hard and time consuming for you, to make sure you have everything set correctly including (if required for this problem) your WINDOWS audio "stuff"



Larry

Win10Pro,i9,64GB,2TBSSD+20TBHDDs,1080TI,BIAB'24,Scarlett18i8,Montage7,Fusion 8HD,QS8,Integra7,XV5080,QSR,SC-8850,SPLAT,FL21&others,Komp.14,IK suite&others, just a guitar player-AXE FX III &FM9T, FishmanTP, MIDIGuitar2, GK2/3'sw/GI20