Originally Posted By: Pipeline
I wonder if setting bb\bbw4.exe to Run As Administrator would help or does the vst run it in admin mode already ?


Not sure if this was a coincidence, a Win10 issue, a BIAB issue or a Reaper issue, but after I set the bbw4 and the bbw64 exe's to Run As Admin, Reaper was able to load the plugin, as it should.

Prior to that, I was getting the BIABVSTi GUI coming up without the transport BIABVSTi issue

I was able to load a demo song/style from my BIAB-HDD, Generate tracks and save it as a user preset.
Now when I call up my BIAB Project Template in Reaper, the user preset comes up including the generated tracks, all within a matter of seconds and my latency within Reaper does not change (64 spls @ 48K).

I then changed the permissions back by unchecking Run As Admin, and it all worked. Repeated this several times last evening. Had my computer off over-night and when I fired it up this morning, it all worked!

I no longer need to use SAVIHost.

So thanks to Pipeline for suggesting the Run As Admin step. In the end, this is what got things working for me in Reaper.

I did not change anything else in my system, including updates nor did I disable my AV.

It also may have had something to do with the fact that I kept BIAB 2016 installed with it's library on an internal drive "G drive". The 2019 BIAB is being run off the BIAB-HDD library.

Prior to this, it seemed like each time I loaded the BIABVSTi in Reaper, I had to set the Preferences to the "R drive". That is no longer the case - the Preferences now shows the correct R drive path.

The Drag/Drop into separate tracks took only seconds.

And because my latency didn't change using the current method the BIABVSTi uses, I am very happy with the way things are now running.

It took awhile, but it was worth it.