Totally. You were one of the ones who said “go set a channel” that’s a paraphrase not a quote, but don’t feel like deleting. It just got lost in so much nonsense.
The answer is, set a channel under prog send or receive, set the same channel on the sending or receiving device. Done. I can’t believe we are at 40 posts on this. Maybe because all my devices are elektron. I dunno. But glad I love Elektron then. Begrudgingly. Even the OT. Lol
Another thing interesting to know IMHO (not in the manual), is that crossfader and scenes midi CC are sent on the same channel as “AUTO”.
1 Like
No, that’s not what it does on the DN and DT. When you set PROGRAM CHG IN CH and/or PROGRAM CHG OUT CH to AUTO on the DN and DT it really means “use the AUTO CHANNEL” of the DN/DT.
It’s only the OT where the implementation is that weird (I guess they learned that it’s too confusing to do it this way).
2 Likes
I read that, that still means if it has to search up to 16 to find one, it should still work, maybe not optimized, but still should, turns out it would have had to listen up to 9, because 9 was where dt, using auto, was sending from.
I just reread what he posted. But digitakt was sending it. So it is “auto channel” but only if the channel is open for audio and not doing anything with midi? Ok im now with you because aside from program change, no midi was being used for audio, and therefore not available for “auto channel” to find?
AUTO CHANNEL is independent from audio tracks / midi tracks settings.
Ugh. Im so confused by this. One extremely knowledgeable person who knew exactly what page to send me to is saying it doesnt even mean auto channel at all. And the manual says auto channel but only if the audio track is available and not in use for midi. But in practice, just tell it what channel and it will work. So in the sync settings, the thing that says prog ch chnl: auto that i changed to the actual channel, what does it mean if not that?
Already answered:
Its sort of moot now that I know what it needs and how to fix it. But I’d like to fully understand it.
Answered but not understood because repasting the same thing into the feed, to me looks like the same thing I didn’t get the first time. Its AUTO under these conditions except not really? I’ll just not understand and move on. It works and its easy to fix for when the next confused person or 10 ask this same thing. I can tell them its AUTO but no it isn’t. Just go here and pick a channel. That will have to be good enough.
AUTO (in MIDI > SYNC page > PROG CH) doesn’t correspond to AUTO CHANNEL (MIDI > CHANNELS).
AUTO corresponds to the lowest midi channel used by audio tracks (MIDI > CHANNELS), and not shared by a midi track. If audio channels are all off or shared, SYNC page program changes are not sent. It is safer to choose a specific midi channel in the SYNC page.
AUTO CHANNEL let you control an audio or midi active track. It is set in MIDI > CHANNELS, and doesn’t depend on other settings.
This is specific to Octatrack. AUTO setting corresponds to AUTO CHANNEL on other Elektron devices.
3 Likes
Thanks man. That makes it make more sense. I’m just happy my Digitakt can tell my Octatrack when to Clap. 
1 Like
I don’t think OT’s AUTO setting really makes sense! 
1 Like
It was a way to close the topic, just agree with your explanation. But I agree with this one more.
I don’t get how to be 100% sure that correct PCs are sent to my synth when I load a pattern.
I know how to send PCs to select programs on my synths, from the 'MIDI NOTE SETUP" menu. However, here’s an example :
- Set up a pattern that selects a PGM on a synth.
- load another pattern
- change the PGM on the synth, FROM the synth.
- load the pattern (the one that sets the PGM)
- RESULT : it doesn’t select the PGM back.
Any help/explanation f what triggers the PC messages ?
It requires a part change. I’m not sure if it also requires a trig…
IIRC an identical PC isn’t sent again. You have to set a different PC in another part (and pattern) to be sure to send the PC again (or see below*).
I highly recommend a midi monitor to check what happens…
*You can send again current pattern midi tracks PCs with DOUBLE STOP, or by changing PC to another value, then select again the right value…
@PeterHanes, The Program Change passionate specialist may chime in…
1 Like
Thanks a lot.
I need to make more tests, but my conclusions so far are :
- it doesn’t need a trig. Even with the sequencer stopped it’s sent.
- the PC is not sent if it didn’t change. (which means you cannot “reload” a PGM to revert its saved state. Shame!)
- CC values are not sent unless changed. Which means you can’t recall a PGM with some changes, like for instance recall a PGM but with closed filter.
True for all Elektron midi messages, except notes, clock…
Annoying. With OT, a workaround is to use a square lfo, mode ONE, which send 2 values. That way you’re sure to send the one you want.
Interesting ! I’ll dig into it. one issue I could foresee is that it will reset the value at each pattern pass. But maybe doable with one shot trigs, if there is no trig on the first step, or maybe with a spare MIDI track…
I’ll figure out what’s the easiest solution.
Thanks !
EDIT : it seems to work ok ! It doesn’t reset the value since the LFO action is relative to the parameter. Great tip !
1 Like
I’d rather use a First trig condition…
1 Like