Ahh well, thanks for these explanations. That does all make sense, and I do hope the developers will contact me for more details and fix my issue. I found that I was able to message Stalker directly and did do that, so thanks for pointing out that messaging exists here.
I did indeed file a bug/support issue on this website within an hour or so of my first post on this forum (a week ago or a bit more).
I have a thought. In Step mode there is the Poly view and the Mono view. Some sequencers have a Mono/Poly setting per track (or instrument/channel for sequencers that define those). I don’t see that on the Pyramid. Is there any such thing that I’ve simply missed or forgotten about? Are there any other settings that would affect the treatment over overlapping notes?
There is a funny thing about polyphonic sequencing. Overlapping notes with the same note numbers do have legitimate musical uses. But because stuck notes are a problem for sequencers in general, it is possibly a reasonable defensive measure to send NOTE_OFF(x) before NOTE_ON(y) when x==y. After all, most controllers cannot send NOTE_ON(x) NOTE_ON(x) NOTE_OFF(x) NOTE_OFF(x).
So I wonder how much of this kind of processing Pyramid does. I’ll check this behavior in detail as well as the pads thing, because it may have some bearing on the behaviors we’ve been seeing.