I read somewhere that this is true. My earlier tests on the MPC confirmed it. The last bank is for user patches
Doing this by pattern change while OT is playing btw (not stop/start)
Pattern 1: Plays P102
Pattern 2: Plays P103
back to pattern 1: plays P002
Pattern 2, plays P103
and continues the same, P002, P103 etc So if it is already in Bank 2, pattern 1 seems to start playing the patch from that bank. Then when it comes back to pattern 1 after pattern 2, it plays from bank 1. In other words, it wants to start from the last bank it played?
If you donāt send appropriate Bank+Pc messages, it stays in last selected bank, thatās normal.
What surprises me is that with the settings I gave it should be P001 for pattern 1 and P102 for pattern 2.
The first program is P001?
That might be just because OT value 0= Pulse2 program 1?
and cc# 32 value 0 =bank1, cc32 value 1 = bank 2?
If we set program values to 0 and 1 we get your expected programs
2 Likes
OT PC =1 is the lowest value. Did you use that value?
No- the lowest PC value is 0. When I used 0 and 1, rather than 1 and 2, I got your expected programs on the Pulse
1 Like
Ok, my bad. Depending on manufacturers, lowest PC can be 0 or 1. I was pretty sure it was 1 for OT.
So it seems normal.
We have definitely confirmed that program changes work between parts ( I think this was already known).
So I am left with 2 questions:
1- why are we microtiming here in this experiment?
2- if cc#32 changes banks on the Pulse2 , does cc#0 change program? If I send a cc#32 (say on step 4) message then a cc#0 on step 5, shouldnāt I be able to trigger different patches within a pattern? ( I would turn PC OFF in the midi set up page).
In order to send the CC32 message before the PC, which is required.
2- CC0 wonāt change any bank or PC, btw I couldnāt find CC0 or CC32 in Pulse 2 CC list. Any link about bank changes update?
You need to send PC anyway.
Not 100% sure, but you also need to send PC to make a bank change effective. Maybe you can tryā¦
With a midi processor, just mapping CC0* to CC32 would simplify all this. Midi Setup settings would suffice.
*OT bank message is CC0.
1 Like
Oh- now I get the microtiming! The PC message is effectively sent āon gridā while the cc message gets sent just before.
Iām not sure where @PeterHanes found the cc#32 but itās obviously right! (Itās the same on the MPC so I guess itās standard).
So Program Change messages are different completely from cc messages? At least I know that now 
I guess the feature request for Elektron is to enable p-lock of the program change message?
I have emailed Waldorf asking for an updated list of programs and banks for their presets- the old list misses alot of the new programs and doesnāt tell you what banks they are in.
Thanks so much- I think we gave it a good shot!
1 Like
Maybe here. Iād like an official Warldorf sourceā¦
Midi messages you can send with OT (correct me if Iām wrong!) :
Note On*
Control Changes**
Program Changes
Pitchbend (MSB only)
Channel Aftertouch
Transport (Start / Stop)
Midi Clock
ā¦?
*OT Note Off are actually Note On with value 0, like many facturers, but some others use Note Off, which is a different message.
**Bank message is actually a CC0 Control Change.
1 Like
Something @ericd should know if you havenāt figured it out already is that the OT only sends the midi tracks PC when a pattern linked to a new part becomes active. It wonāt send it just by muting/unmuting tracks. It will also send out the midi tracks ccās and pcāc when you double stop. I donāt have my OT for testing but maybe if the tracks are muted the pc wonāt be sent, so thatās why whatever track is unmuted upon double stop thatās what the pulse playsā¦ Also as sezare said the OT doesnāt send a cc unless itās different than the last one sent on that track, to conserve bandwidthā¦
I donāt know if it will send pcās just by changing part in a pattern, no OT handy for testingā¦ Might workā¦
Edit: I guess you figured it outā¦ Oh well, just recappingā¦ 
3 Likes
Yes, mostly (painfully) figured all that out!
What I still donāt understand is why the OT canāt send a new program change message from a second (or third or eighth) track, even if you send a bank change cc before it!! It can only send a PC message on one track per pattern/part- why? I also donāt quite get why this does become possible by using a midi event processor, but it might dawn on me eventually 
It can send send 9 PCās per partā¦ One for the sync menu option if itās activated, and one for each midi track. They all have to be on different channels, if you have multiple midi tracks on one channel sending PC, the device on that channel will only respond to one of themā¦
1 Like
With a midi processor you can convert cc to pc and send them on any step of any trackā¦
Think of the patches on midi devices and the machine/sample of audio tracks as a group of 16 sounds/voices.
When a pattern linked to a new part becomes active the midi track PCās basically just load 8 patches to devices from midi tracks just like the audio tracks load 8 machines/samples.
Itās still very useful if not per step just to be able to recall the correct patches of 8 midi devices that go with your 8 audio tracksā¦
1 Like
This is what confuses me. With the MPC2000XL as the controller, one midi device (i.e. the Pulse 2) will respond to program changes on each track. I can effectively have 16 sounds from the Pulse2 in a sequence (pattern)- so I donāt understand why the OT canāt manage 8.
Itās because the OT sends them at the same time, only when a pattern linked to new part becomes activeā¦ If you send a device two or three PCās at once your only gonna end up on one of themā¦
The 2000xl must behave differently, sending them when tracks are unmuted perhapsā¦
I guess I donāt understand why the OT is designed that way. Why isnāt it possible to send PC messages on each step, or at least a seperate PC on each track? What advantage is there to it being limited in this way?
I donāt know- I didnāt have to do anything too tricky (muting/unmuting etc) on the MPC2000XL, just send a cc#32 and a program number on a step. The MPC does seem to send the cc message and PC messages in a consecutive order (even though they are on the same step) and you can set this order- so the cc#32 has to be first then the PC change. Each track can be used to trigger a different sound on the Pulse.
EDIT_ In fact I just tested something and it goes further. The MPC can send a new PC on each STEP and the Pusle will respond with the corresponding sound- giving an almost unlimited potential.
1 Like
Per step is even better than upon track launch/unmutingā¦ Some other Elektrons can do per step PC, OT can not. I tried to explain a theoretical concept of the OT midi track PC paradigm a few posts up. There is no advantage to this over per stepā¦
Just to be clear though itās not just one track PC, if you have 8 different midi devices set to different channels and 8 OT midi tracks on those channels set to send PC, all 8 will switch patch when the pattern/part becomes activeā¦
This is just how it isā¦
2 Likes