microKorg XL+, M-Audio UNO usb-MIDI adapter, arpeggiator

[cpcohen]

OK -- into the Twilight Zone . . .

I want to use my microKorg XL+, running into an M-Audio "Uno" MIDI-to-USB adapter, connected to my computer. [That's to avoid ground loop noise, so you don't say "Why not use the USB connector on the MicroKorg ?"]

When I first tried this, I was plagued by missing "note-off" MIDI messages, several times per minute of playing. This didn't sound nice!

I found a post suggesting that the problem could be fixed by setting the microKorg's MIDI Clock to "External MIDI". And by golly, it worked! The microKorg and Uno were playing nicely together.

But then, a problem:

. . . The microKorg's arpeggiator didn't work, on the
. . . microKorg's own patches.

So I have a choice:

. . . Use the Uno, and lose the arpeggiator;
. . . Use the arpeggiator, and not use the Uno;
. . . Change the MIDI Clock setting, depending on what I'm doing
. . . . . . [NOT a good idea for me!]

I have three questions:

1. Can somebody explain what's happening? I have a good background in electronics (but not in digital music), and I'll try to understand.

2. Is there a way to get around this?

3. Is there a way to get the microKorg [XL+] to send its arpeggiator patterns over MIDI Out ?

Thanks -0-

. Charles

[OpAmp]

Hi,

1. I don't understand exactly what's going on when note-off messages are missed. The fact that it is gone when switching to 'external MIDI' and the ARP no longer working, makes me think about a MIDI loop. Sent out events (notes + clock) by the board are again looped back (echoed) by your USB-MIDI interface for some reason and this seems to cause some overload and results in lost looped back MIDI IN messages.

When the arpegiator is not working when switched to external clock points to the fact that the board does not get an external clock on its MIDI IN via the USB-MIDI interface. When no clock is received, the arpeggiator can not know the tempo.

2. It would help to explain more exactly what you want to achieve. Options you can try:
* make sure that the SW on your PC sends a MIDI clock to let the arpeggiator run again
* still use the internal clock but disable the loopback of your sequencer software
* switch OFF the LOCAL option of the XL (MIDI parameters page). This makes that keyboard event are only sent out over MIDI OUT and not to the sound engine of the synth. The loop back should then echo back the events to the board to the board to trigger the sound engine. (When local is on and if a loopback is enabled, notes may be played twice at the same time.) (Note that when local is off and there is no loopback, or the MIDI cables are not connected at all, the synth may seem dead - not responding to key hits)

3. Choost POST KBD as POSITION in the global parameters section. MIDI OUT is taken after the arpeggiator in that case. In the other setting (PRE TG) MIDI OUT is taken after the keyboard, but before the arpeggiator.

Succes.

[cpcohen]

Sorry for the delay -- thank you for the reply!

I'll try some of this out in the next few days.

. Charles

[tommymandel]

Those USB-Midi cable adaptors often go bad, and an intermittent connection can cause stuck notes. Maybe you've already considered this.