monohusche

this is probably the easiest question, but I can't wrap my head how to implement this with list management.

I want to build a M4L device which filters out the note-off messages from my push2 in such a way that the first note-on triggers the note while an additional note-on sends a note-off. Basically locking notes into sustain mode, but being able to stop playing notes selectively by triggering them again.

Most of the inbuilt midi commands (stripnote, flush, sustain) manage note off's holistically. In this case, it seems I would have to keep track of the notes being triggered before, and if a note is being triggered again (comparing lists), a note-off message would have to be triggered.

managing-note-off

This is an abstraction that does it. I made it back when I was even more of a beginner than I am now, so it's probably incredibly convoluted and could be done far more simply. But hey - IIRC it works. Its main ingredients are stripnote and table. Please let me know if you come up with something better. :-)

thanks so much. works like a charm. was thinking more aling the lines of using lists and zl to store the currently sounding notes, but why worry about it if it works?

managing note-off