The Util tracks are in RAM until saved, so if you regen a section of the Util tracks it's still in RAM, so it looks like it should be able to do the same with regular BB tracks this way.
I generated all the regular & Util tracks before saving and Biab was using 1.5 GIG of RAM for 96 bars @ 120bpm. For it to work it would just need to save the track data for all generated tracks rather that saving to wav, but any imported, recorded or destructively edited tracks would need to save to wav (unless it uses non destructive editing then the track could be saved as reference data).
I don't know how it would all go if we ever get more than 255 bars that are all in RAM and the time it would take to generate first to RAM rather than direct play ???
The BBPlugin needs direct play before Biab.
If the BBPlugin can get away from BBW4 to do this all the better.

Last edited by Pipeline; 09/08/21 10:57 AM.