From: jimmy <wg...@ya...> - 2010-01-03 15:02:12
|
> Date: Fri, 1 Jan 2010 21:26:55 -0500 > From: "D. Michael McIntyre" <mic...@ro...> > > On Friday 01 January 2010, Abrolag wrote: > > > Hmmm. I've had a thought. Next time I'm doing some > intensive real > > keyboard work I'll also start up two instances of the > MIDI keyboard > > emulator, one on the same input channel and the other > on a different > > channel. I'll be able to see if when it dies it's just > the real keyboard > > that gets lost, that input channel or the whole MIDI > input. > > That sounds like a plan. I remember building a LEGO > Minstorms robot to try > hitting keys for hours on end or something to try to test > this last time, and > I could never reproduce it. You probably have to > really *play* the thing for > hours, which sadly, I can't do. > Maybe some shell scripts for "midish" (on Linux, probably also for BSD's not sure for other OS's) for generating midi events, maybe some random note generator in a loop of some sort. Try the speed of generated notes first to see if timing is the problem. If it takes thousands of notes, perhaps the segment runs out of room and can't grow, or memory allocation problem, or memory leak... Or the exception handling for such thread/process didn't handle it properly to print out appropriate error(s). Jimmy |