Without the Midi synth in the VST every midi track needs to be routed to the DAW for use with an individual VST in order to hear the sounds. That means one for the drums, one for the guitar, one for the horn, one for the piano and on and on. The alternative would be to have a GM synth in you DAW, but that would still require routing of everything. If the VST had the GM synth, which is what Adar is proposing, then you only need to route those tracks which you need/want over in the DAW. I know you are a big midi user, so am I, but don't you use any audio RTs from BIAB in your DAW? I use both. I reserve the midi for those tracks which I want to customize both content and sound source. RTs do the rest of the fill.

The midi in BIAB that I want, I move directly to the DAW and set it up with my Sounds Sources, but I don't want to set up every midi track just so I can hear it. Would be much more convienent and faster to compose and construct the midi in the BIAB-VST with an internal Synth in the BIAB-VST and than when I get it right, move it via drag and drop or via routing to the DAW.

I know that are lots of ways to skin this cat, but what Adar is offering is something very new and very practical for the BIAB-VST. So I will lobby as hard as I can.

Thanks
Dan



BIAB – 2025, Reaper (current), i7-12700F Processor, 32GB DDR4-3200MHz RAM, 1TB WD Black NVMe SSD, 2TB WDC Blue SSD, 1TB WD Blue, 2 TB SK NVMe, 6 TB External, Motu Audio Express 6x6