Strat,

I've discovered that if you want to use both RB and BiaB to develop a song project it is better to do minimal work in BiaB and transfer the project to RB. The reason I say that is that many of the settings you make in BiaB are not read by RB.

When I want to use both programs on a song project I divide the project into two phases where BiaB is used to build the song structure and RB is used to develop instrument tracks.

In BiaB I concentrate on selecting the song key signature, tempo, swing or even feel, primary style, main instruments, basic chords and number of verses. I don't try "fancy" things like using F5, instrument patch changes, or using repeats because they don't always translate well to RB so they either waste my time or mess up in RB.

When I move to RB the first thing I do is (if the import has midi tracks) raise the file resolution to a higher setting then save the import in RB's native file format which is SEQ. That way future saves take less time and I always have the original BiaB SGU or MGU file as a fallback or safety.

Now I am in RB and can import other styles, try different instruments, use the multi-riff feature, modify the chord chart and do any other "trick" I can think of to create great instrument sounds.

Hope this helps.

Jim Fogle - 2025 BiaB (Build 1128) RB (Build 5) - Ultra+ PAK
DAWs: Cakewalk Sonar - Standalone: Zoom MRS-8
Laptop: i3 Win 10, 8GB ram 500GB HDD
Desktop: i7 Win 11, 12GB ram 256GB SSD, 4 TB HDD
Music at: https://fogle622.wix.com/fogle622-audio-home