[EDIT] With more JS pratice, I now think that this issue was due to something like:
http://forum.cockos.com/showthread.php?t=50634
OP:
______
"LOST" EVENTS ISSUE:
I'm doing some classical processing on midi events sent by an e-drum: something like "while (midirecv(ts,msg1,msg23)[...]".
It most cases, it works fine BUT when the events rate becomes higher (e.g. roll on the drums) most of those events are "lost" !! After some debug + monitor at the output of my JS, I've seen that the events are not really "lost", in fact there're not processed at all, they pass thru
(and it's not a programming error).
I didn't find any thread dealing with that issue: is it a known issue ?
... and the most important question: HOW CAN I FIX IT ?
For the moment, I use this work around: copy/paste of the faulty JS (events missed by the 1st instance are processed by the 2nd one) but, it's really complex: processing started in the 1st instance / finished in the 2nd one, variables sharing, etc...
Remarks:
- not a PC perf issue (monster !)
- MIDI ROUTING: events are received form a track where a 1st (very simple) JS midi filter applies. No issue with this one, all events are correctly processed !
Then those events are routed to another tracker with the faulty JS
Elapsed time beween midi events:
Can someone provide a code sample or help me to compute the elapsed time between 2 midi events ?
I'd a look a schwa's humanize JS, but it didn't helped me...
Thanks!