I love the new feature in BiaB to copy/move midi tracks to the standard BiaB tracks. It makes it really easy to create convincing covers of popular songs to play along with. There are, however, a couple of things to be aware of when doing this.

Make sure you do any deleting or copying of bars while the midi file is still intact on the melody track. Once you move any parts to BiaB standard rracks you cannot do this easily (I made a wishlist request to fix this issue).

Move any midi data you want to assign to a BiaB track to the soloist first. This way you can remove any midi patches and other control commands using the event editor. Once you move the data to a BiaB track your only option will be the piano roll window and some things are harder to do that way.

Watch out for duplicate channel assignments. If a bass part in the midi is assigned to a channel other than 2 (the BiaB bass assignment) it opens up the possibility that conflicts might occur. Rechannel any midi assigned to the same channel as the BiaB track (note; this shouldn't be necessary but I did have a couple of issues and this cleared it up).

I hope these tips help you make the best use of this great new BiaB feature.

This isn't working for me (build 366). (Others have reported the same.) The data appear to move from the melody to the target track. They can be seen in the notation and in the sequencer for the target track (non-melody or soloist), and the track freezes. But the track doesn't *play* and there's no midi transmitted to the midi monitor. I know the data are there, because I can actually move them to the soloist where they *do* play. It's as if everything works as advertised, but the routine for actually transporting the midi out of the track to the sound source is busted.

There is the following in the help file:

"The track to Copy/Move selected channels to -> can be Melody or Soloist (since these are the only tracks that are editable in Band-in-a-Box)."

But the new features manual for 2013 indicates the target track can be *any* track. So I've assumed the above quote is mistakenly carried over from 2012.5. No?

I notified support. But am I missing something?

-Ron

@pwarren

Thanks, those are valuable tips.

Stan

Quote:

---

This isn't working for me (build 366). (Others have reported the same.) The data appear to move from the melody to the target track. They can be seen in the notation and in the sequencer for the target track (non-melody or soloist), and the track freezes. But the track doesn't *play* and there's no midi transmitted to the midi monitor. I know the data are there, because I can actually move them to the soloist where they *do* play. It's as if everything works as advertised, but the routine for actually transporting the midi out of the track to the sound source is busted.........

---

Thanks to Rob in support, I now know what was going on here:

> When you use the File -> Open Midi file -> The midi file imports
> onto the
> melody track and the style is turned off. I have found that in my
> testing
> because the style is turned off that any midi data copied to one of
> the
> style supported tracks we are discussing it rendered in operable. If
> you
> enable the style the transferred midi should play.


So (to add my own tip), bottom line is to make sure the style is enabled when using this feature. Hope it helps someone, -Ron