If you set the midi array in onCallback() you must not clear the array in the following onProcess() but in the call of onProcess() after that (so the midi array remains set for a whole bloc). It seems that during a given bloc processing period, onCallback() is called just before onProcess(), since the method I have described is totally reliable.
If you are setting the midi array in onCallback(), bear in mind that you can get several onCallback() during a bloc, and if this happens you have to not clear the midi array, and may have to add the new midi message as a second entry in the array, etc.
This sounds a bit complicated but the way I do it is this:
At the start of onCallback() this code:
if (! hadCallback) {
sdkSetEvtSize(midiArrayEvent, 0);
hadCallback = true;
}
At the start of onProcess() have this code:
if (hadCallback) {
hadCallback = false;
}
else {
sdkSetEvtSize(midiArrayEvent, 0);
}
Then to send a midi message from onProcess() or onCallback() use this:
int size = sdkGetEvtSize(midiArrayEvent);
if (size < 0) size = 0;
sdkSetEvtSize(midiArrayEvent, size + 1);
sdkSetEvtArrayMidi(midiArrayEvent, size, code);
All this could have been hidden behind some stuff in the SDK I suppose.
Similarly if you want to send a trigger output, you can do the same sort of thing to make sure it stays
set for one bloc.
Simon.Statistics: Posted by sm_jamieson — 21 Aug 2017, 20:55
]]>