Strange behavior when sending midi from the DAW

[kortezzzz]

Hi.

I get some strange results with my synth when playing a midi keyboard\MIDI track on some DAWs.
For example, when I use "Studio one" DAW, any time i press a note on my hardware keyboard, "Studio one"'s cpu indicator rises to a very high rates, then falls to normal rates while the signal sustains and rises again after release for 1-2 seconds before it "dies".
The strange thing is that it doesn't happens when i play with my "built-in the synth" virtual keyboard; the cpu stays
at normal grades during the whole MIDI event.
When using my synth on "Reaper", "Reaper"'s cpu indicator acts very normal without any dramtic rises and falls (shows 0.7% cpu use), with both virtual keyboard and MIDI track massages.
Under cubase 5's midi, the "rises" and the "falls" are not as dramatic as at "Studio one", but they appear and the whole "rise" and "fall" situation happens in milliseconds and even turns "Cubase"'s overload indicator led up.

So, it makes me wonder how FS deals with MIDI tracks\hardware keyboard midi massages and why there is such a difference between one DAW to another. And the most important thing: how to get rid of these cpu "rises" and "falls"?

Thanks.

[kortezzzz]

Problem solved, but not completely. The problem occurs because of the MIDI wireless output primitive on my synth's general stage, which should send the CC info to my knobs for the "learn"\"forget" feature.
It seem like the knobs got any of the MIDI data that has been sent by this wireless output so actually,
my knobs were "playing" every time i press a note on my hardware keyboard or connect my synth to a DAW's MIDI
channel

So, i'v built a small module that filters the CC data only, before it sends anything to the MIDI wireless output.
also optimized my knobs and put there 3 selectors that pass the MIDI data to the "cc learn" system, only
when the "learn" possibility is chosen. other than that, it is off by default.

Tested my synth on these 3 daws again and here are the results:

Studio one- no more dramatic cpu "rises". the cpu usage is about 70-80% less
cubase- same thing as "studio one". no more "overload indicator" led flashes.
reaper- best resaults: only 0.3% cpu usage.

but the problem hasn't solved completely. results could be even better than that if i could filter the "note on"\"Note off" safely and send it to the "midi to poly", as my virtual built-in keyboard does. but the virtual keyboard plays only one note each time and it can not handle few notes pressed simultaneously (its there for sound testing testing purpose).so... there is no safe way to filter "note on"\"note off" massages from the midi data and send it to the "midi to poly". as i try to filter it using "status" connectors in the "midi event" primitive, the synth crashes after few minutes of playing a keyboard with both hands.
seem like the "green" is not fast enough to handle large amount of midi data in short time...

anyway, hope that information helps to anybody. if someone has a solution (maybe Ruby?) please share.

cheers!