Preset Banks seem to offer a huge opportunity for FX automation within BiaB (and RB for that matter, though it's probably less useful). From a modest amount of research into the VST implementation I've got an idea how things work with preset banks.

Both the VST and VST host have an opportunity to save and load preset bank files. Obviously the VST gets first dibs since the host has no idea what preset bank file you are going to load until it's loaded.

Since we can manually load a preset bank it's also clear the host can load a bank after the VST has done it's thing. So if BiaB were to save the preset bank files for each slot with the song file, as it does for the plain presets, then we could have a user defined preset bank for any song we want.

That's good as far as it goes. By having a preset bank load with a song file the user could easily change the presets for a given track. That might be nice from the point of view of changing the sound of a track while the song is open but I think it can go much further.

If we embed a user defined midi event in a track, or under the bar change menu, there seems to be no reason why BiaB couldn't change the preset during playback. I would envision something like this. Send a command 200 which BiaB could interpert as slot 2, bypass. 404 would mean slot 4, preset 4 etc.

Now you would have to allow a ms or two for the VST to change preset or disable itself but I think this would make a great unique feature for BiaB.

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