Originally Posted By: Bob Calver
maybe you could do it another way. if you have the drag and drop facility, drag the master button to the wav drop section, wait for it to turn green then drag te wav files into RB.

that's available in the recent programs but not sure if its supported in your versions
Thanks very much for your suggestion.

After some experimentation and research I found that your method works to a degree.

I determined that I don't have a "master button" but I found that the "combo" button in my version of BIAB apparently does the same thing. It also looks like individual instruments listed next to the "combo" button can be separately dropped into RB by dragging them individually! That is a huge step forward toward a successful workaround!

The problem that I'm finding is that no matter what *audio* (non-midi) instrument I drop into RB whether via the "combo" button or by the instrument button alone, the program inserts the music "wav file" at bar #16. The test file I'm using only has four bars total including the ending. This appears to be happening for all *audio* based tracks or instruments. I achieve the same response no matter if I select the track in RB to be audio or leave it at the default midi designation, or if I drop the instrument on the track control area on the left (where the label and midi/audio badge is located) or if I drop into the track itself at position -1 (or any other position). Additionally if I try to drop a second audio instrument into a new previously unused track in RB, the instrument always is inserted into track #1 at bar 16 overriding whatever was in there previously.

The above occurs also when I drag the instruments or "combo" to the "drop" button and drop it into RB after the button turns green.

Midi based instruments drop in and play perfectly!

If I can get the audio based instruments to drop into a separate track at the beginning position and not at bar 16, along with the midi tracks to drop in individually as they are now doing, I'd be very happy with this workaround.

Thanks again, I think we're close to a good workaround solution. I hope.