jazzmammal, yea it definitely sounds like the drive went bad. Did support say they had some sort of replacement program for such cases? Maybe you can get a replacement for the cost of the drive plus shipping, or something like that.

Quote:

silvertones
#2 I've tried and I get a message" can't generate a midi track on an audio track that has data."
# 3 can't reproduce
#1 can't reproduce. I originally had all of my songs in BIAB. When RB came out I loaded them into RB and all the bar settings stayed the same.



For #2, make sure to first select the RT with a left-mouse click, then use a right-click to bring up the context menu for the MIDI track. Also, I think the RT type should match the MIDI type of track. For instance, left-click on the bass RT. Then right-click on an empty MIDI track and choose to generate the bass track. In my case, the RT will now be converted to a MIDI track with MIDI data.

For #3, I suspect what I was seeing was a symptom of #1. I have BiaB set to 0 count in bars, but RB was set to a bar offset of -2. Maybe this mismatch added to the problem (I think RB should account for differences in offsets when importing). Also, I believe I deleted a few bars in RB that was before some of the bars that contained bar settings (you modify bar settings by selecting a measure in the Chords view and pressing F5). Those bar settings were muting some instruments. So what happens is that the MIDI data is generated on the track, but areas that have been muted in the bar settings were muting the MIDI data (which is the expected behavior I guess). I would probably have caught this except that due to the fact that RB got the bar settings mixed up and applied it to the wrong bars. For instance, a bar setting might be set to mute the piano on bar 10, but internally RB applied this to bar 8 (for example) and at that point the MIDI notes will be muted/unmuted at the wrong locations. So what you see visually and what you hear doesn't match up.