Originally Posted By: cwiggins999
I took the latest plugin (3.3.5) for a quick spin this morning, and still ran into some things that are showstoppers for me. Here some observations:

1. I started with a song that I had put together in the app, all RealTracks. It took the app 7 seconds to generate. The plugin took 40 seconds - regardless of whether using standalone plugin or inside Cakewalk. I'm guessing the VST is single threaded, whereas I think multithreading has been implemented in the app. (I'm running with an 8 core processor.)



Have to agree with much of what you have said. I can only add based on working with the VST for over two years that the BIAB-VST can indeed be stubborn and demanding regarding workflow. Whereas BIAB is known for having multiple ways to do the same thing, the BIAB-VST can only do things its way. So you have to adjust your workflow or be willing to jump back and forth between the standalone and VST.

However, your item 1 does not sound like a correct assumption. I am seeing much quick regens in the VST then you report. I get times which are comparable to the Standalone , especially with V3 which is now much quicker than V2. I imagine it is dependent on the number of RTs and number of bars. I generally will only have a handful for short sections. In addition, the standalong has historically had a unique algorithm where it will start playing a tune prior to completion of the generation. In RB and now the VST the generation has to be fully completed before it will play.

Otherwise, the VST just another tool to use.

DAn

BIAB – 2025, Reaper (current), i7-12700F Processor, 32GB DDR4-3200MHz RAM, 1TB WD Black NVMe SSD, 2TB WDC Blue SSD, 1TB WD Blue, 2 TB SK NVMe, 6 TB External, Motu Audio Express 6x6