Hey there!
I have been trying for a while to get the Program Change message sent from the Octatrack to switch patterns on the Norand Mono MK1.
The goal is to have each part linked to a different pattern on the Norand Mono, so when I switch parts, I want the associated pattern to change too. I would like to use the Mono’s sequencer with the stored patterns.

I have tried various settings but none seem to work.
The most sensible settings seem to me:

Octatrack Midi Out --> Norand Mono Midi In
Octratrack settings: Transport Send, Clock Send, Program Change Send Channel 1, Midi Setup Channel 1, Bank Off, Prog 0-12 (for testing purpose), SBank off.
Norand Mono settings: Midi Channel 1, Midi Clock Receive.

I feel like I’m missing something since the transport works fine and also Midi notes entered into the Octatrack Sequencer get interpreted by the Mono. I can assign CCs for example for the filter as well and they work. This is why I think the Midi Channels are set up correctly. The program change message that changes patterns on the Mono however is not. I think that the PC-message only gets sent when I change patterns on the Octatrack so I did that, but it doesn’t work. I feel that maybe I need to set up the “Bank” and “Sbank” parameters in the Octatrack in a specific way, but so far, everythink I’ve tried failed to work.

So, long story short: Does anyone use the Norand Mono with pattern change from the Octatrack and maybe help me troubleshoot?

You’re probably right with that. Does the manual of the mono say anything about it?

well it says that the mono changes pattern with external program change messages:
Mono supports program change to switch pattern, send a program change between 0 and 63 to set the current pattern. Note that play mode will affect the behavior just as it would if you switch pattern manually.

Does setting ‘Bank 0’ and ‘Prog 1’ on the midi note Page of the OT do anything?
If not try:
‘SBNK 0’ and ‘Prog 1’

Depending on weither or not the Mono listens to MSB or LSB, either one should work.

Otherwise I have no idea, since I don’t know the Mono.

Update:
The problem was a bug introduced somewhere between firmware 1.xxx and 2.0
Since I have installed firmware 2.1.0 the problem went away and the settings in my post above for the Octatrack are correct.

I did read the patchnotes but this bug was not mentioned so I figured it must be something else…

2 Likes