Deleting one MIDI CC event in list edit deletes two

Anyone knows what is going on here ? Often the MPC seems to consider MIDI CC events as pairs - but also often not. This drives me crazy...

there's always an initial value (@ 0.0.0) and then the real value @ the time you inserted it

wavejockey wrote:there's always an initial value (@ 0.0.0) and then the real value @ the time you inserted it

In that case, how do the other values in this example exist alone ?

as wavejockey said - 001:01:000 is usually treated as initial or "undefined" value, that's why most often the time of that event is greyed out. The first "real" event is always coupled with initial value. Just press "nudge" on the initial value, move it back and forth one tick to decouple it from the next "real" event down the track.

Thanks, I think I understand. Initialization values at 001:01:000, in practice undefined, can exist as singletons - whereas values further down the sequence, with actual effect, cannot exist if an initialization value for it doesn't exist.

And I think I understand the reason why that is shown to the user: it symbolizes that, between the beginning of the sequence and the first user-set value, the variable has a value but it is unknowable before runtime.

Well, all that seems true most of the time... But here I have one parameter that only exists as an initialization value - and modifying it does effect the targeted instrument. So, my hypothesis is that at least one actual value must be paired with an initialization value, and the others can exist with no initialization value... But I haven't yet thoroughly tested to be sure - the effect of deletion in particular.

Anyway, for the sake of neatness I used the thousands of second to group my beginning-of-sequence burst of parameters - at 001:01:001, 001:01:002, 001:01:003 etc. and, when playing, I see the cursor fly by along the List Edit and the values produce the intended effect on the instrument. Nice.

I had a hard time spotting those CC fly past in the MIDI Monitor among the bloody useless clock packets lines - not a comfy debugging environment... Akai, let us filter the MIDI Monitor's log dammit !

(Sundry MIDI puzzlement deleted - I had forgotten to set a couple of input channels)

FYI : MIDIox (windows) or SHOWMIDI (cross platform) enable you to filter out MIDI (real) timing events

but i agree AKAI should enable a filter in the MIDI page too
(the MPC4k has it)

A quick experimental proof: single MIDI CC events placed at the track's very beginning in the List Edit screen are perfectly functional although they have no no sibling. I had to verify - but it doesn't contradict the theories mentioned here so far: it is just a special case, where initialization value and actual value are defined at the same instant, and the List Edit collapses them into a single entry.

Maybe this is all obvious to seasoned MPCists, but experimental verification helps my understanding - and maybe someone else shall benefit !

of course that works (too) because that's how it works on every other sequencer / and should work according to the MIDI protocol