Virtual MIDI keyboard problem (solved)

I just purchased this Chirp virtual MIDI keyboard to use on my laptop. It uses LoopBe30 for routing.

The keyboard works fine with DimPro and Rapture in stand alone mode, but I'm having problems using it within X2a.

As soon as I click anywhere on Chirp's window (not just a key), X2's audio engine turns off. If I then click on the keys I see MIDI activity for the note on's and note off's on the MIDI meter of my MIDI track, but nothing sounds since the audio engine is off.

However, if I arm my track to record, and start record on the transport, everything works fine. The audio engine doesn't stop, I hear the notes and they're properly recorded.

Any ideas as to what is going on ? I've gone over all the settings and I'm stumped.

Thanks scook, it was already checked.

It turns out that things also work fine during playback. So with things moving, either record or playback (even with nothing to play back, no clips) the audio engine keeps going and my virtual keyboard works as expected.

The track's input echo button works as expected during playback and record.

But with things stopped, I see midi activity but the audio engine is stopped, so no sound.
Input echo turns the midi activity on and off.

I can turn the audio engine back on, and it'll work ok for PRV, but the minute I touch the virtual keyboard window the engine shuts down. The keyboard notes activity continues to be reflected in the PRV keyboard.

I guess it was a little ambiguous. When the "Share Drivers With Other Programs" feature is enabled (checkbox selected), as SONAR looses focus it also looses the audio driver (i.e. it shares the driver with another program). By disabling the feature (checkbox empty), SONAR keeps the audio driver when it looses focus to the virtual keyboard.

Glad you got it going, have a great holiday.