Ok a couple of IMPORTANT pieces of information I have just discovered in my testing. This all goes along with my theory that the CASIO PXS5000 keyboard does not play nice with BIAB 2024.
FIRST, the Casio transmits High Resolution Velocity MIDI data. High Resolution MIDI Velocity CC#88 was adopted by the MMA around 2010, giving controllers and instruments a velocity range of 0-16,000+, instead of the basic MIDI 0-127. (Pianoteq is one of the few software instruments that respond to it.). These are the CC # 88 picked up in the BIAB MIDI Monitor but apparently BIAB 2024 does not know how to respond to these. This is most likely causing the recording to stop abruptly with some of the MIDI data being transmitted by the Casio BIAB just doesn't know what to do with it and translates it into the wrong command and stops the recording.

SECOND: I am able to DISABLE the high resolution MIDI velocity data transmission in the Casio and when I do that, BIAB responds better, but not perfect. The MIDI Monitor no longer picks up any strange data, the only thing listed is Note on clean data (see attached screen shot). BIAB seems to do well with this UNLESS, I play too fast or strike the same note repeatedly and very fast. These two actions will cause the recording to STOP abruptly.

So I'm getting closer, but I can't play too fast because as soon as I do or repeat a single note fast in succession, it triggers the recording to stop - and that is with high velocity resolution turned off. So it seems that BIAB is having a problem with the rapid playing. Also, I wonder if BIAB programming can implement the High resolution Velocity MIDI data reception into its programming.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
Clean-MIDI-Events.png (187.74 KB, 128 downloads)