<< ... my hope is that more people try RB and it may help them as I find it easier to use than BIAB where i have to dig around for functionality that is easy to see in RB." >>

That's a good goal Bob, but in this thread the OP is familiar with RealBand and aware that it's available for use and will record audio. However, although not a deal breaker to offer RealBand as an option, the OP said he prefers to record in BIAB and thus posted in BIAB for Windows Forum.

I'm also a proponent of RealBand, use it when it's beneficial to do so and support your attempt to recommend it whenever such opportunity arises. While RealBand is functional for your recording needs, there is quite a few functions that don't carry over from BIAB to RealBand or the DAW Plug-in.

You mentioned a lot of features and functions that are easy in RealBand but didn't explain how you accomplish a single advanced feature task of BIAB that is unavailable in RealBand, the DAW Plug-in or any DAW. That's a great topic for another thread in the future because there's a lot of potential in BIAB for complex arrangements that alleviate much of the manual editing users have to do in RealBand or a DAW that reduces and diminishes the time to complete a project where moving tracks to RealBand or a DAW is done without losing the complexity or quality of the arrangement, number of instruments and tracks.

That said, the focus of this thread is helping answer the original question and resolve the issue in BIAB. This appears to be a technical glitch or setting problem and should be quickly solvable for John F.

BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.