You have non destructive volume automation in RealBand because it was suggested, before that users had to destroy audio that can't be undestroyed as was stated in clearly in the video above, where as volume automation can be changed anytime, the same has now been implemented in Biab, that is the extent, the others are destructive and destruction will cause wav files to be written and attached to the SGU.
The examples show in the forum from years back with Biab having more tracks that gave rise to Utility tracks used NDE in the "OLD" multitrack VSTs so no wav files were created.
If I import wav files into Utility tracks it will make hard copies of them and attach to the SGU. A thousand BIAB projects with wav files attached would be an issue.
The future can't be anything else but NDE for Biab as this is how most DAW's work, now including Audacity.
It all comes back to generate time, that's why you are starting to see DAW features added to Biab because RealBand and the BiabVST are too slow to make changes or regen the whole song, the idea is great but they fall short in practicality, SO they don't want to go back n forth and want to do it all in Biab because of the gen speed, that's it !
How can you make RealBand and the BiabVST/standalone faster, or even Biab faster ????? can you give feedback on how PG can do that, or have we come to the end of development progress because of old users with old hardware ?

Attached Files (Click to download or enlarge) (Only available when you are logged in)
BB-Destructive-Editing.png (31.81 KB, 140 downloads)