I’m not intentionally sending any noteOff messages anywhere yet. I traced the noteOff event to MidiList::createDefaultPlaybackMidiSequence() which ends up making the call: addToSequence (destSequence, clip, note, channelNumber, useNoteUp, grooveTemplate); and the useNoteUp parameter is true. That seems to be where the noteOff event comes from. It seems this is replaceable by subclassing the EngineBehaviour class but it would change the logic for the entire app in that case.
The ‘all notes off’ from the last few messages on my other thread could also be an issue, potentially but I’ll settle for getting rid of the explicit note off first. ( See: Adding / removing MidiNotes from a playing MidiSequence in a MidiClip without restarting playback - #29 by dave96 )
This is what the midi messages look like:
|10:10:47.035|To IAC Driver Bus 1|Note On|1|E3|64|
|---|---|---|---|---|---|
|10:10:47.043|To IAC Driver Bus 1|Note Off|1|E3|0| <- seems to be from MidiList::addToSequence()
|10:10:47.043|To IAC Driver Bus 1|Control|1|All Notes Off|0| <- these last two are a known issue from the other ticket, I just haven't gotten around to working on the fix suggested by dave96 in that ticket yet
|10:10:47.043|To IAC Driver Bus 1|Control|1|Reset All Controllers|0|