I've been getting back to playing with the DAW vst lately and have run across a rather serious problem which started with build 612 and later builds. If I use a style with one or more midi tracks, the midi tracks will not generate either one at a time or as part of the master track. The generation goes to about 90% completion and then locks up the vst. Sometimes a rather large file(multi-gigabyte) is created if I wait long enough. Task manager is needed to shut down. This occurs both stand-alone and vst's added in the DAW. Examining the SavedTracks directory show a BBInstrumentName.TRK files for each midi track, a BBInput.txt file and a VBA.BIN file. No .wav, or .midi file. The window task manager shows that a bbw4.exe is the process hanging and must be ended to get out of the lock-up. Midi files generated as expected with a midi and a .wav file with build 611, although there were tempo or sync problems with the tracks when played within the vst DAW. Once dragged into my daw (Reaper) they were in sync.

My system is a follows:
Windows 7, Biab UltraPack 2019. Reaper Daw, Halion Sonic/Halion 6 vst synths,
yamaha/steinberg ur22 interface.

Biab and even RealBand are working fairly well with the above now although there are
a number of relatively minor issues with the on screen interface with need to be addressed. (especially with two monitors.)

With the VST DAW styles containing all Real Tracks generate fine as do Multi Riffs, it's just the problems with midi tracks within styles causing problems.

Any of you experts have any ideas??

A related question is: Build 611 created a .wav file from the midi track. Where did the audio come from? If I drag/drop a midi track within the main BiaB progrem it creates audio from whatever vsti instrument I am using. Same with generating an audio file from a midi track in RealBand.