Lately I’m trying to slave the a4 to the octa and access the a4 performance macros per Midi cc on the octatrack - pretty dope 
I p-locked specific cc values on the octa on the first note of the pattern to get the a4 the way I want it to sound, However it’s not 100% reliable, sometimes it doesn’t update the perf macros to the right values.
Until I go in and change the stuck cc trigs value a Little, then they update Again. Seems like the octa is only sending the values when they changed.
So my question is, is there a way or trick to force the octa to resend all cc data on the beginning of a track?
Thanks !
I noticed that Ot doesn’t send similar event too.
Workaround : use a different value just before intended value.
1 Like
Jeah i tried this , it works, but with parameters which affect the pitch for example this will get audible 
Has this been confirmed as a bug or by design. I’m having an issue where I try to engage/disengage Analog Drive (cc80) while switching parts with OT midi sequencer.
The Midi trig seems to be ignored by OT unless I move the knob or double-stop the sequencer. I’ve had to use the “two trig micro timed trick” to get around it.
I’m genuinely confused why that would be by design though. I have a different value plocked on a different pattern/part and it ignores it until it reads yet another cc?
Just to be clear:
Pattern 1/part 1, track 7, cc80, value 10-plocked
Switch to
Pattern 2/part 2, track 7, cc80, value 64-plocked…
Nothing happens
Only when a second trig on the new pattern/part (Technically the 3rd trig in this whole deal) is passed does anything happen… what’s the reason for that? The first trig on the new pattern is totally useless, taking up space and effectively causes a delayed cc change (albeit only one microtimed unit).
I just don’t understand.
The suppression of sending a CC with the same value as before is by design (what this thread was about). What you describe (now in detail) seems to be a different problem. Switching parts is - in some regards - buggy.
Okay. This might actually be an issue with my Analog Drive pedal after more testing. Seems like it’s misbehaving with other CCs too but rebooting it, they go away.
