> On Jan 30, 2019, at 2:47 PM, Stéphane Letz <[email protected]> wrote:
>
> This standard MIDI handling code may drop some MIDI events. You can more a
> more robust path (using a queue of incoming events) that is used when dealing
> with MIDI synchronization messages (start, stop, clock…)
>
> You can « force » that MIDI sync path by explicitly adding an appropriate
> metata like in the following line:
>
> on = button("[midi:key 60][midi:clock]on »);
>
> Can you try that and report? If this solve your problem, then we may have to
> switch this more robust mode on by default…
Ah ok … so this is an issue of the time-resolution of UI events.
It makes sense that your suggestion would work, but alas,
I tried it & it didn't seem to change anything.
Faust is still dropping more than half the events.
My modified test program is below — can you double-check my syntax?
-m-
——————
declare author "Mykle Hansen";
declare name "short Midi note example";
declare options "[midi:on]";
import ("stdfaust.lib");
//on = button("[midi:key 112]on");
on = button("[midi:key 112][midi:clock]on"); // sletz suggestion:
count = +( on > on' ) ~ _ : hbargraph("# of button presses", 0, 10);
process = os.oscsin(440 + count ) * on;
_______________________________________________
Faudiostream-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/faudiostream-users
