Originally Posted by musocity
1) If bbw4_64.exe is now using the same engine as bbw64.exe you have the same operation but if it's not having to decompress the wma and write into ram, it's just data like midi data, quick, and then you will find you can go to bar 255 in the plugin and it will play right away before Biab has got to generating it into ram.
2) Partial Regeneration = Generate Selected Region (Plugin)
1) It is not keeping the backend in RAM. It loads the backend each time you do a generate for Instruction based generates. On my system it take ~ 4.5 second to load the backend and ~10 seconds to generate a typical style. This still makes it about 4X faster than 2024. BTW it also generates the Wave in the background so you can hear it quicker with the instruction tracks and still drag a wave at the same speed as it always took, which is equal to BBs speed of generating waves.
2) Partial Regeneration <> Generate Selected Region (Plugin)
Partial Gen is still on the to do list according to Adar. It currently generates just a section of the track leaving it blank audio before and after and is no faster than it was in the past.


Reply to the OP, it was disappointing that PGM did not hear the very loud cry from the customers asking for improved workflow. This cry was drowned out by the sound of AI last year and so they felt that they needed to react to it at a higher priority.
They will eventually get around to the workflow and reliability complaints.

Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).