Originally Posted By: rharv
In RB
First, maybe try the Make All BB tracks regular tracks option (right-click - Track option)
When they change, they will not have Blue track names anymore, if they did.
Then it behaves like RB instead of BiaB. Some RB functions only happen on regular RB tracks, as I mentioned; the Blue BiaB tracks continue to try to emulate a more BiaB behavior.

If you opened a BiaB file in RB, the tracks may be acting like BiaB tracks and not as expected like with other RB files.
After changing them to regular tracks, use Save As (to a SEQ file format) to preserve your original BiaB file.
Then work with the resulting SEQ file in RB.

After that, how exactly are you loading the plugin?
I'd normally right click the track and assign to a different VSTi port, then assign the desired synth to that port in the resulting popup.


Thanks Rharv,

TBH, I have only uses RB in the past for the multi-riff function, and was just trying it now to see if I have the same issue with MIDI VSTs as I did in BiaB.

I've been loading plugins w/o issue since I originally purchased the program in 2014 and 2015. In fact I made a couple of YT videos on organizing and loading up your plugins in BiaB, and how to identify the proper file paths for 32 bit vs 64, as well as a video about using Minihost Modular as a plugin, so I'm pretty sure I have the basics down. This is a bug of some sort.

Band-in-a-Box 2024. Custom Build Desktop PC W/ Windows 10 Home 64-bit. CPU: Intel Core i5-9600k @ 3.7GHz (6 core x 6 threads) RAM: 16GB DDR4. Storage 238GB SSD + 2.7 TB HDD. GPU: ZOTAC NVIDIA GeForce GTX 1050 Ti 4GB