I'm eager to hear experts' opinions on the most efficient workflow with BiaB.
Vector vs Scalar
The most important part of core technology in BiaB is the vector generation. Vectors are location addresses pointing to the source material (RealTracks & RealDrums), aka the green colored style tracks. Because each vector track is just a collection of link addresses, it is light-weighted, fast processing, and can be regenerated easily, most ideally to work with.
On the other side, once BiaB is rendered and exported as an audio file, such as WAV, WMA, MP3, it becomes a scalar track, which can not be relinked to the source material or regenerated anymore.
BiaB VST DAW Plugin
It's just a lite version of BiaB with less features. When you drag tracks from the plugin to the DAW, all tracks become scalar tracks (rendered audio tracks). BBPlugin doesn't seem to offer much of value.
RealBand
RealBand is supposed to be the best DAW to work with BiaB, and I don't know why there are not many people using it. It's true while compare to BiaB, RealBand is lack of features. But within RealBand, without the need of BBPlugin, RealBand itself can read chord sheet, generate vector tracks, of which can be regenerated as wish. Why RealBand hasn't become the most popular DAW in the BiaB community?
Cockos Reaper
Why Reaper seems to be the most popular DAW in the BiaB community? Does it have any advantages over other DAWs such as Ableton, Cubase, Studio One, etc?
BiaB Track Injector
It is a genius idea to utilize the vector technology of BiaB. But it's currently in beta and there're bugs and may not work for all users.
BiaB vs RealBand
Since RealBand can do exactly what BiaB is doing, generate vector tracks from a built-in chord sheet, plus RealBand has the visual sequencer view like a DAW, why does everyone seem to work with BiaB and export to DAW, completely skip and ignore the existence of RealBand?
* Vector = Address Data File, Contains Data Linking/Pointing to Source Soundbank
* Scalar = Rendered Audio File