When saving as an ."*.sgu/*.mgu" in RB and then opening in BIAB, the Utility Tracks don't contain the corresponding patch information in the event list for each track and don't automatically set the corresponding MIDI channel number for each track.

Am I missing something here?

Thanks!

Hi Thunderthud,

I'll have a look at this later today. I'm not sure what Realband's relationship to BIAB is now that Utility tracks are in BIAB. In the past, Realband only recognised the original eight BIAB tracks. This is still found under "Edit >> Track >> Make first 8 tracks BB tracks".

Regards,
--Noel

We are talking about the File/Save As option, which saves as a ?.SGU/?.MGU File.

The option to includes the Utility Tracks has existed for the last few versions, although, they didn't really work until this version (as I remember). It does create a file that opens in BIAB, but doesn't include event/patches for instruments or levels and effects. And it doesn't carry through and set the corresponding channel number on the Utility Track.

Thanks

I always treat BIAB to RB as a one way street. Everything I can do in BIAB then over to RB for final tweaking. Can't think of anything I'd need to go back to BIAB for that can't be done in RB but I agree the two programs should work seamlessly together and you should be able to go back. But to get BIAB to its current state of capability, with so many added features, it must be quite complicated to go back from RB.

Hi again, Thunderthud.

I've been playing around a bit with taking songs created in RB into BIAB, and I see what you mean. Like Bob, I've always gone from BIAB to RB to my DAW and I've never used the RB to BIAB path until now.

When I generated a MIDI Supertrack on one of the non-BIAB tracks in RB, saved the file and then opened the file in BIAB, the MIDI notes were there, but the patch was a default synth sound (in my case it was brass). The information about the track being a Supertrack was not present. Also, when I generated RTs on some higher-number RB tracks, saved the file as SGU/MGU and opened the file in BIAB, the RTs were imported as audio and the information that they were RTs was lost.

While there is compatibility in creating an MGU/SGU in RB and taking it into BIAB, the BIAB-specific track information looks like it is still only present on the first 8 tracks of RB. The remaining RB tracks seem to be treated as DAW tracks. I'll pass this information on to the development team, and reference this thread, just in case there is something obvious that I've overlooked. My discoveries seem to be similar to yours.

Regards,
--Noel

Thanks Noel, I would appreciate it!

FWIW, these programs behave differently for reasons .. otherwise there would be a need for just one of them.
They do seem to be getting more and more cross-merged and integrated, but sometimes RB does what it does because that is the functionality most users expect and want. First thing I do when opening a BiaB file in RB is 'Make all BB tracks regular tracks'. If I went the other way I would expect some caveats .. RB handles tracks, routing, etc. much differently that BiaB

I personally cannot see why anyone would want to go the other way, and thus I assume it is a small group that would .. so I'm biased.
It would feel like I went backwards.
A couple others have mentioned the same (BB -> RB -> DAW workflow) so I'm not alone here.

I move to RB because I find most things apart from basic track generation much easier than in BIAB. But if you tell us why you are going into RB there are two ways we might be able to help. If you tell us what you want to do we can probably tell you how to do it in RB. Or gurus Jim and Charlie Fogle can most likely tell you how to do it in BIAB so you don't need RB.