Originally Posted By: Funkifized
So, that clearly begs the question: what's the workflow that one should use to avoid going back and forth between BIAB and RB?


In my opinion, for accompaniment users, there's little if any benefit to move a project to RB. A very complex arrangement consisting of dozens of instruments mixed, panned and audio leveled can be programmed and rendered taking little time to complete. Constructing a song in BIAB by programming the arrangement similar to how one contructs the song form and chord progression into the Chord Chart yields a professional quality render that the BIAB algorithm has anticipated instrument changes such as solo intro's and endings, instrument mutes and return to normal status, the same as the Chord Chart anticipates and reacts to shots, holds, rests, drum fills, Part Markers and chord changes. The result is that BIAB selects part appropriate audio or midi and provides smooth transitions, avoids abrupt beginnings and cut off's and also many other automated actions and create nice, complex arrangements that normally don't require any post editing.

The same is true of composing except users have developed a workflow that prompts them into thinking they have to have a high degree of individual instrument manual control.



Originally Posted By: Funkifized
How does one make up for the fact that RB doesn't do anything with Multistyles and won't import frozen tracks?


Complete those actions in BIAB and export the audio out to RB.


Last edited by Charlie Fogle; 01/11/21 01:27 PM.
BIAB Ultra Pak+ 2024:RB 2024, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.