The MIDIpal settings would be the following:

• inp = 1 (the whole “stack” will handle all notes played on channel 1)
• mod = pol (true 3 voices note stealing)
• out = 2

As a result, notes played on channel 1 are dispatched on either channel 2, 3 or 4.

The connections would be the following:
Interface OUT -> MIDIpal IN
Midipal OUT -> Stage II IN
Stage II THRU or OUT -> Tribute IN
Tribute THRU or OUT -> SEM IN

The synth MIDI reception settings would be:

• Stage II MIDI channel: 2
• Tribute MIDI channel: 3
• SEM MIDI channel: 4

As a result, if you play a C E G chord, the C will be dispatched by the MIDIpal to channel 2 and will be played by the Stage II ; the E will go the Tribute (channel 3) ; and the G will go to the SEM (channel 4). If you release the C and play a B (Em inversion), the B will go to the Stage II.

Dear Pichenettes,

Thank you for your reply. Your instructions for how to make the connections were exactly as I thought. The settings for the MIDIpal now make more sense.

I just tried the following test on my Mac (running Cubase 4.5.2) just in case:

MIDI track 1: Channel 11
MIDI track 2: Channel 12
MIDI track 3: Channel 13

<naturally, these Channels all correspond to the same MIDI output on the interface that communicates with the rig in question>

The Stage II is set to receive on Channel 11 and send on Channel 12
The Tribute is set to receive on Channel 12 and send on Channel 13
The SEM is set to receive on Channel 13 <end of MIDI chain>

(the above synths do not send/receive on an omni channel)

Then, I added a C# to MIDI track 1… an E to MIDI track 2… and a G# to MIDI track 3… altogether comprising a C# minor chord. I pressed play on the transport and the triad was played perfectly.

So, if I understand Dispatcher correctly, the latter will essentially do the distribution for you, right? (I’m a firefighter, so bare with me… we’re not the smartest guys on Earth you know?) Once the MIDIpal is installed in my setup, I go:

MOTU MIDI interface ——-> MIDIpal ——-> Stage II ——-> Tribute ——-> SEM... right?

Then, I assign a MIDI track set to output on Channel 10, tell the MIDIpal to receive the note stack on Channel 10, then it distributes notes (in order of appearance) to Channels 11, 12, and 13.

*Does that sound like a proper interpretation of your instructions?

• Does the MIDIpal introduce significant or noticeable MIDI latency?

*In this sort of setup, the main benefit of the Dispatcher function is that you can use just one MIDI track to enter intervals and chords, rather than having to use multiple MIDI tracks for each note you wish to enter in a “polyphonic” array, since the Dispatcher does that division of notes for you (e.g. instead of you having to do the division yourself by setting up a note per track). Am I right?

• The Dispatcher also works extremely well when you have some sort of MIDI controller triggering these synths without a computer laying somewhere between the controller, MIDIpal, and modules. If I were to have:

MOTU Interface ——-> MIDI controller (assuming it has what Moog calls “MIDI Merge” ——-> MIDIpal ——-> Stage II ——-> Tribute ——-> SEM

... then that would be the best of both worlds, since the controller would receive MIDI info from the computer when needed, pass it along to the MIDIpal do perform the above stated functions, and such a chain would allow you to shut off the computer and simply play your mono synths from the controller as it sends out notes to the MIDIpal for distribution to the rest of the synth array. Am I right?

*Again, thank you for your explanation. And in the event that I test the MIDIpal in my setup and I deem that I would prefer to work another way, what is your return policy?

Kind regards,

Xia

The dispatcher is fun to use with a multitimbral synth as well I’ve noticed. Use a copy of the same patch on a few channels and tweak each version slightly (pan, cutoff, detune etc), or why not different drumkits on each channel. Variations ahoy!

tb323, you just blew my mind. man I just laughed thinking, “what an awesome idea!”

If you play a chord note by note, the first note will go to channel 11, the second note to channel 12, the third note to channel 13. That’s because you might have dialed on each synth a sound with a long release, and the MIDIpal prefers spreading the notes so that the releases of each note can overlap with the others (sending the 3 notes to channel 11 would make the second note “cut” the first one). However, if you play the same note repeatedly, it gets retriggered on the same synth. This is the behavior of any keyboard instrument – play an arpeggio on a piano with the sustain pedal on, and 3 different sets of strings will resonate ; but play C C C C with the sustain pedal on, it’s always the same set of strings that resonate and each new note “re-triggers” the same set of strings.

I think you’re worrying it too much about the details. I’m reassuring you, it’ll “feel right” musically.

Bonjour Pichenettes,

You’re right, I am worrying about it a bit too much and I’m sure the MIDIpal will integrate with this array just fine. I have spent a long while trying to get this right before I found your website that I am thinking, “is this gadget too good to be true?” Apparently not, and it looks like your invention is exactly what the doctor ordered. Well done! =)

Thanks for your help, for answering all my questions, and for taking the time to write back so soon. I sincerely appreciate your effort and look forward to finally having the polyphonic setup I have always wanted.

Merci beaucoup. =)

Kind regards,

Xia

@pichenettes: Just noticed a bug I think (firmware 1.1).
I’ve set inp=13, mod=cyc, out=13, num=3.
When I send notes on channel 1 they will go through as they should, but at the same time the dispatcher also starts sending notes to 13,14,15.

I’m using it with an Alesis qsr right now and the dispatcher is really nice with its drumkits. :)

Wow, that was fast. Thanks!

The .hex file is for flashing with an AVR ISP programmer. The .mid file is for loading into a sequencer ; the .syx file for a SysEx transfer utility.

Yep, check the “updating the MIDIpal firmware” section in the manual

Dear Pichenettes,

I have followed the link you posted with the new firmware midi file. I click on it, but it does not download (it opens with Quicktime for some reason as a sort of media file…<?>) Is there a way that I can download it is a midi file so that I can just play it through Cubase?

Thanks!

Xia

OK, I think I got it now. I had to <option> <click> on my Mac so that it downloads instead of trying to play it like a media file (weird). If I experience an issue, I’ll post again.

Thanks again.

Xia.

Browsers like to play MIDI files, people used to use them as background music at times.

I hate Apple mice, I have a Microsoft one attached to my Mac :)

@fcd72: For the internet I use an older MacBook, so right clicking is a bit of a pain (oh well).

All: So I received the MIDIpal a couple of days ago (very fast shipping by the way). The poly mode in Dispatcher does not seem to work right with my setup… I think it has to do with my setup, not the MP.

So, cycling mode works VERY well, though. Wow. It simply distributes the notes it receives in the order in which they arrive to the channels you specify. Well done Pichenettes! Your invention has made me very happy! Finally, analog polyphony of the sort I have always wanted.

Thanks buddy, and thanks for your excellent customer service.

Merci!

—Xia.