The question "Why use a DAW when there is BIAB" literally depends on how BIAB is used in a workflow. I'm not speaking of the release year or program pak, but rather if one stays in BIAB as long as possible or if they rough out a song and render tracks and do the majority of arrangement and production in a DAW. The rendered output from each method yields dramatically different results.

Remaining in BIAB can take full advantage of the BIAB algorithm, multiple tools, techniques and features that are used to develop the structure, song form, instrument choice and arrangement, editing and effects.

Likewise, by quickly generating and rendering audio, the structure and song form are developed but most, if not all, of the more advanced programable or automatic tasks that are possible from using BIAB's tools, features and processes and allowing the BIAB algorithm to initiate commands and functions are lost to the user.

It's possible that in a single bar on a single track for the BIAB algorithm and settings to:
. Change from one RT instrument to another
. Alternately, have two or more instruments play simultaneously
. Change styles
. Change the sub-style
. Modulate the key
. Adjust the tempo
. Generate specific ending audio chosen for instrument 1
. Generate specific intro audio chosen for instrument 2
. Fade out the first instrument
. Fade in the second instrument
. Crossfade the two instruments
. Change the panning setting
. Change the volume level
. Repeatedly regenerate these actions and settings with the Generate and play icon.

In BIAB this is automatically initiated with a click of a button.

In a DAW, each step is done manually because most likely the two instruments are on separate tracks. In addition, RealTrack instrument changes or regenerations require going back to BIAB and requires additional rendered tracks for the different styles.

BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.