(OT) MIDI CC not changing on trig

Hi gang,

Struggling with something this morning that I’ve not hit up against before, unsure what I could have done wrong.

I have a MIDI channel added on the OT (1), with CC1 linked to 104. It’s activated and turning the corresponding knob changes the parameter on the external synth as expected, but setting a value on a trig does nothing. I’ve tried both regular trigs and triggless trigs, I’ve tried various note lengths and shifting the timing etc. Whatever I do I can’t get the trig to fire the CC value, only turning the knob manually does it.

Any thoughts?

track mute ?

1 Like

The track isn’t muted.

When using a normal trig I can perform a note change without issue - it only seems to have an issue with the CC value…

I’d be wary of MIDI sequencing on 1 given the potential conflicts wrt audio track ‘blocking’ - this is a well known thing i’m not explaining well

but in your case maybe see if you can swap channel on your device to get clear of potential routing conflicts- it may be nothing, just thinking about steps - i’d also check with a different cc on your device to see if it’s cc specific and whether it’s ot related

maybe when turning it’s happening on a different channel (not sure if OT is even like this wrt later devices which allow setting output as track channel or auto channel

i would always just start with a fresh pattern and take minimal steps - if it’s a parameter on your device which is modulatable after initiation then that should work for you, but some devices only initiate certain key settings at note on - it may be about the order of events

dig out a computer midi monitor too if you want to be thorough etc

Just tried on CC5 and the same issue.

Yea it’s a weird one tbh - I’d understand if the synth wasn’t responding at all (could be many issues), but the fact that it responds to the knob but not a value on a trig seems strange to me…

I can try on a fresh project but that doesn’t help too much as I need the midi interaction on an existing project anyway :expressionless:

Can you use a midi monitor to see what’s being sent when you turn the knob vs how it looks when you assign a cc event to the trig? That might tell you if it’s looking for a second value or it may give you some other hint.

1 Like

AFAIK shared channels block audio tracks midi send or midi tracks receive.
It doesn’t block midi tracks send nor audio tracks receive and allows midi loopback.

@natehorn possible conflicts with midi tracks sharing the same channel and CC. Upper one have priority IIRC.

A classic : a soloed track?

1 Like

This led to the solution indeed!

The problem appeared to be that Audio channel 1 was (as per the default) assigned to MIDI track 1 - which was causing some kind of conflict. Having turned off the audio track midi channel assignments things are now working as expected :muscle:

Thanks folks!

Actually I take it back, still not working :sweat_smile: Not sure what I managed to do but still having the same issue. Have even tried on a fresh project and same problem - knob works to change value, any kind of trig does nothing.

Will have to see if I can set up some midi monitoring but will be a faff.

Edit: Assigning an LFO to that CC also gives the desired result. So LFO works fine, turning the knob works fine, but any kind of trig wont. Makes no sense to me.

Can you set all audio tracks to off (no midi channel) and under midi -> control “audio note out” and “audio cc out” to “int”?
This is not necessary, but let’s disable everything potentially coming from audio tracks.

Then place two trigs on that midi track and p-lock the midi cc to 1 on the first trig and to 126 on the other (or any value you want).
Lfo’s all to zero, arp off.

1 Like

Yes, better for tests as same values aren’t sent more than once. Elektron machines behavior that SHOULD BE OPTIONAL.

(Audio tracks with same channel don’t block midi send, I used it this way a hundred times for midi loopback without problems)

Ok something new is happening now, which is interesting.

The first trigless trig now seems to be working, but the second one isn’t. They’re space 8 trigs apart.

If I copy the first trig to the 4th trig, and set a new value, it also works. The 7th trig… nothing.

So it must be something to do with timing… which is equally unusual as turning the knob freely works and so does the LFO, but it seems certain trigs won’t trigger the change.

It’s not correlating with the note triggering on the synth itself, as it’s a polymeter (subharmonicon) - it seems fairly random which trigs will work and which ones won’t.

Any clues as to what’s happening? Feels like we’re narrowing in one something at least :sweat_smile:

Edit: Actually after playing some more this is far from consistent too… I really need to monitor the midi and see what’s going down.

You can use a free midi monitor software. Some daws even have them built in. We really have to see what OT actually sends out.

The manual states

1 Like

It doesn’t state midi tracks can’t send midi if channels are the same. :wink:
(I never had an issue with that, even using midi lfos as envelope for the crossfader.)

:thinking: Waiting for midi monitor results…

1 Like

Sure, just wanted to clarify what the manual says. Prioritizing audio channels to receive and midi to send makes sense with the OT and I’ve also never had problems.
The reason I said to disable audio tracks note and cc out was just for sake of troubleshooting. It shouldn’t make a difference, but you know…ghost in the machine.

1 Like

Sorry I’m away from home right now but I will report back when I get the chance and have the patience to troubleshoot :sweat_smile:

Come back home immediately!
We have to know. :wink:

1 Like