Further on, I have some more realizations about these problems in this Folder "X:\bb\MIDI SuperTracks - Demos". The SampleTank2 Hi-Q Polyphony for the Hi-Q-Piano is set too small. That is it is set to 32 voices, I have reset it to 64 voices. I discovered that the SampleTank2 piano bites off notes at 32 voice polyphony in some of the faster, denser playing styles. I just re-saved the SampleTank-Hi-Q-Preset with 64 voices over the original BiaB preset. Now all the notes come out with out being "stolen" by the next note.

I have not auditioned all the Demo folders, (I have BiaB Audiophile 2016) but so far it appears that there is no other folder of BiaB that has these issues. I thought that they were software-code issues or Super-MIDI-Tracks issues, but it turns out that they were only badly-set Demo.SGU issues. The problem was that the piano suddenly morphed into a xylophone and later into a saxophone. This would happen on the first bar of the second chorus and the ending respectively. This was only due to an (invisible) Bar-Setting. When I go to the first bar of the the Demo-Song, press<F5> then press "Reset Bar" the Demo-Song no longer morphs the piano into a xylophone at the beginning of Chorus-2. So this is a Bar-Setting Issue. But strangely it is NOT visible in the Bar-Settings GUI.

The "Attenzione Part3: INSTRUMENT NOT FOUND" was solved by deliberately setting the Piano-Part-Preset to the correct Hi-Q Piano Preset in the BiaB GUI.

I have noticed that I must NOT have the VSTi-Plugin-Settings Popup Window open when I save any change to a Song. This sometimes generates the memory issues and usually crashes BiaB. For that matter any other BiaB-Pop-Up-Window tends to do the same. And additionally, saving any change to a Song, while the song is playing, also tends to give these memory insufficiency errors which usually crash BiaB. At least this is the situation on my machine. I do not have a top-of-the-line killer computer, but I do not have a shabby one either. I use a Toshiba Qosmio X775 with 2.2Gz i7 with 8GB Ram and it seems to handle anything I throw at it. Getting such errors is not normal for any other software that I have installed. I had thought that these memory-insufficiency-error were due to the "Attenzione Part3: INSTRUMENT NOT FOUND" popup-boxes, but I am still getting the memory-insufficiency errors and I no longer have the IKM-popup popping up. This does seem to be a software issue.

Last edited by ChandraSwami; 05/18/16 06:47 AM.