One last, sort of off-topic, comment here because the OP's request for multiple midi patches on a single track and BIAB's solution is such a clear demonstration of why converting BIAB into a DAW isn't as good an it's thought to be.


< JOAM: in rb i can work mostly in tracks view.
and would like the same for bb new fab tracks view...
in summary bb tracks view becomes 'work central' with the same protocol as rb and some daws. (so its familiar to new bb users.) >

< JOAM: in summary the op's need re midi would be a breeze given the above scenario. >

< BOB CALVER: And forgive me for a point of view expressed many times, changing the midi instrument is dead easy in RB where you can see lots of separate tracks and copy one track to another, cut bits you don't want and use the existing midi info to drive different instruments.

But I know switching to RB is not a route people want to follow. >


Yes, the solution to placing multiple midi patches on a single track is easy in RealBand. but it involves rendering multiple tracks of multiple instruments and copy and pasting between tracks.

In BIAB the solution to changing multiple midi patches on a single track is selecting another Style and setting Part Markers.
Or, with a sound source like Coyote, use Bar Settings.

What's being missed from the DAW proponent's perspective is BIAB is driven by the Chord Sheet and the Chord Sheet and all the associated features and tools are non-linear. RealBand and all DAW's are linear.

I've attached screen shots of a BIAB constructed song SGU demo with seven Styles, each with two style variations. It's 128 bars of 14 styles composed of at least six different instrument changes to show the difference this makes between BIAB and a DAW creating the same song. To accentuate the drastic difference between non-linear and linear, there's a screen shot of bar settings that by adding just on chorus, allows for the second chorus to be change each Part Marker, instrument and add even more styles. BIAB can have ten more styles for this arrangement.

Open the demo in BIAB, and the song is very dynamic and interesting because it's constructed in non-linear manner using 14 Style variations and six soloist instruments.

Open the demo in RealBand with it's linear design, there are only two substyle in the song. All of the dynamics are missing becasuse the a/b styles don't feature any soloists. These would have to be input manually.

Even if the song is rendered in BIAB and the tracks exported and imported RealBand, to edit the tracks so the dynamics, style variations and soloists are the same as the single render MultiStyle done in BIAB, they have to be rendered individually for each instrument, style variation and edited manually.



Audition the demo to hear the comparison. If I were giving a BIAB demonstration to a potential new user, regardless their DAW experience or not, I think the BIAB demo render to be much more impressive than the RB demo render.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
Demo Opened in BIAB.jpg (151.24 KB, 52 downloads)
Demo opened in RealBand.jpg (187.03 KB, 52 downloads)
SubStyles.jpg (87.86 KB, 52 downloads)
Bar Settings and multiple Chorses to edit Part Markers.jpg (257.13 KB, 52 downloads)
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.