Seenfromspace,

You can send Program Change per pattern, but the bad thing is that it seems that you can’t choose which program change each OT’s Pattern will send.

Because of this, pattern a1 will send 1, a2:2 and then. One of the problems comes when you reach pattern i1. when you play pattern i1 on OT the A4 will also play pattern a1. So it seems you can’t use OT’s patterns after h16 with the A4 unless:

— I usually use for a song on my live several OT patterns and just a few A4, sometimes just one, but is good to use at least two with twins Kits, so I can reload the A4 kit remotely from the OT (very useful after improvising too much :P)

So If I have a song that uses more than 8 OT let’ say for example 12 patterns there will be placed like this

a1, a2, a3, a4, a5, a6, a7, a8, and i1, i2, i3, i4,

In this way OT a1 and i1 will share the same A4 pattern, OT a2 and i2… and go on.

I know it seems a bad idea to stay jumping between banks on the same song. For me is ok because I use the Arranger to group, organise, automate mutes, flow control.etc., then I can for example make a loop between a1 and i1 to keep playing till I decide to start with another group/pattern.

— The other method you can use is to send Program change by Part using the OT MIDI tracks. In this way you can have 64 A4 patterns linked to the OT parts, the good thing is that you can choose manually, the bad thing is that you have to use an extra part just to change a pattern on the A4. So this depends on how you are using Parts.

I think that program change should be per pattern and the user should choose the PGM value to send, Elektron should put it on PATTERN X## SETTINGS’s menu (Function+Edit while not recording)