One issue with using JABB in BIAB is how it deals with dynamics.

Instead of using note velocity, it uses CC1 or CC11 events.

I'm really new to biab, but so far I've been using bidule to 'snoop' all MIDI events coming into ARIA and insert a CC1 event in real time that is equal to the the note's on velocity (value 2).

Another perk to setting bidule as the default vsti synth, is that I can easily get my VST3 plugins into the game too.

Yet another bonus is the ability to manipulate the velocity curves of drum kits before they hit their respective plugin(s). I.E. Garritan JABB drum kits need more 'velocity' to cut through the mix. Cranking up the 'volume' for the kit isn't always enough.

As far as BIAB knows, it's talking to a single instance of the Bidule plugin. Inside bidule, I have a party going on, where I can mix and match sounds from any plugin I like.

Here I've got an instance hosting:
Synthfont64 (VST2),
Roland Sound Canvas Plugin (VST2),
Two instances of HALion 7 (VST3),
Groove Agent 5 (VST3),
MIDI output to a hardware Fantom XR (MIDI output),
Garritan/Plogue ARIA (For JABB3) with Velcoity to CC1 injection (VST2),
Roland Zynology (VST3),
East West Play (VST3)

I can easily route any channel to the plugin/channel of my choice using a special matrix, that can also save remote controllable presets.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
bbb01.png (81.6 KB, 67 downloads)
bbb02.png (108.18 KB, 67 downloads)
bbb03.png (79.41 KB, 63 downloads)
Last edited by Brian Roland; 11/27/23 12:22 PM.
Windows 11, OmniPak