I encountered stuck notes recently with a simple sinewave instrument and poly/poly~. When single notes were released one after the other no problem, but when I released all notes at the same time, I was almost guaranteed a stuck note. So this might be a more general MIDI problem. I seem to recall several years ago encountering the same noteoff problem.
Well, here's a tidied up version which works. The ugly patching was mainly
to filter out note data from particular channels. I should have removed
I've tried a number of patch configurations. For example, using xnotein to
send a note off message, or the flush object. However, none of them
eliminate the stuck notes with the FM7 or Fm8. The only way I can get around
this at the moment is to send a global disable command to the vst if it gets
stuck and reinitialise it - not really practical in live situations, but the
best I can manage at the moment. I also tried overdrive mode - again, no
It is possible that this is a problem with certain Native Instruments
applications - I think someone over the summer reported this problem with
Absynth. This mighted be indicated by the fact that when a stuck notes occur
the flush object does not send out a note off message if banged. I take this
to mean that( as far as flush is concerned) the stuck note has already had
its note off. I've reported this to NI but I can't expect them to be
particularly MAX literate (they'll probably advise me to purchase Reaktor!).
I have not encountered this issue with other vst hosts.
>From: Mattijs Kneppers
>Subject: [maxmsp] Re: stuck notes with vst~
>Date: Mon, 18 Dec 2006 17:43:02 +0100
>Is there a way for you to make the patch a bit more tidy? It would make it
>a lot easier to find the problem..
>SmadSteck - http://www.smadsteck.nl
>Interactive audiovisual sampling soft- and hardware