MIDI CC strange behaviour SOLVED

Hi! I have a strange behaviour when using MIDI CC. I’ll try to explain it as clearly as I can, not a native speaker.

So I first tried defining Trigger 7, 8 and 9 as seperate MIDI CC Messages for the same CC on the same Channel with different Value like in the following:
7. Was CC 59 with Value 01,
8. Was CC59 with Value 02 and
9. Was CC59 with Value 03
All three on Channel 01
I then made a sequence with these and the DT only sends the CC at the first pass of the sequence, every other “loop” doesn’t change the state of the receiving device it simply stays stuck on the last step.

If I do the same thing more logically with just one track and PL on the Value it works without a problem. Now I was wondering why it does that above?

By Trigger 7,8,9 do you mean Track 7,8,9? Trigs are the steps of the sequences, tracks are the 8 sequences that make up a pattern.

Don’t have a DT but it sounds like it’s behaving like Octatrack where as a way of minimizing midi bandwidth and avoid some other issues it will only send a CC value if it is different than the last value sent from that track for that CC…

To me this would make sense why it wouldn’t work on multiple tracks but would work on one signal track…

2 Likes

That makes perfectly sense! Thank you! It cost me some time to realize I was doing it way too complicated with the first method and the second method is way better, but still I thought it was odd that the first didn’t work. Cheers to you!

1 Like