Logic MIDI routing


Mar 27, 2007
Brighton, UK
Hey there,

I picked up a Yamaha MJC8 for next to nothing the other day and quickly set about integrating it into my bedroom studio;

Yamaha MG12/4 mixer

15" MacBook Pro 2Ghz 2Gb Ram running Logic, Bidule mainly
Echo AudioFire 4
M-Audio Uno 1x1 USB MIDI interface

3.2 Ghz PC too, running Bidule only as VST host and for other patches
EMU 1820
Korg ER1 MkII
Behringer Truth B2031A
CME UF6 Controller Keyboard

Basically I have all MIDI outs going to the ins on the MJC8 and then the MIDI thrus ont he MJC8 lead to the ins of the interfaces and Korg.

The unit works great and appears to send midi data where I want it.

Now, here's where I'm a bit confused in Logic. Say I want the Korg to act as a hardware sequencer for a AU instrument (Battery, EXS24 etc..) but at the same time I want to enter notes with the CME on a second AU, say a synth.

I have routed the MJC8 to send the CME to the Uno interface and the Korg to the AudiFire's Midi in. How do I route it in Logic so that when I select a synth in the arrange window to play notes with the CME, the data being sent from the Korg stays where I want it and doesn't start playing the synth?

I kind of understand the Environment window but not realy, have managed to get logic to send midi out to my pc on different channels but am not sure how to address the above problem!

Also am interested in getting in touch with a Bidule community to help develop my skills

Any help greatly appreciated



Well-Known Member
Mar 19, 2003
Kirkland WA
Make sure that you select the audio instrument you want to trigger from the arrange page, in the view menu make sure parameters are enabled.

There are two dropdown menus activated by the white triangles, from there you get midi control options for that audio instrument.

I'm not sure what you are trying to do, but you could be getting in trouble if you have an external sequencer activated, while trying to trigger the instrument with another midi device.

Double check to see if you are creating a midi loop, could be as simple as turning off local control on external midi devices.

Word of advice, if you have sequence data in multiple devices it can get complex. Keep all midi data in one place.

Record all midi data into Logic then edit to you heart's delight.

I recently cleaned up a clients workflow, he had drum sequences in multiple drum machines, and multiple keyboards for each song.

I had him use his Sequencer (Sonar) as the master first to capture all midi data.

Use the sequencer triggering the midi gear, use the midi hardware as sound modules only. Do your editing after the capture. Then capture the audio from the external gear. Turn the external gear off, continue working the audio.



Mar 27, 2007
Brighton, UK
Cheers for the advice!

I see what you say about keeping midi data together, I usually have everything running from logic.

My problem is that sometimes I just want to be able to press a button to hear what a certain midi sequence will sound like with a specific instrument whilst playing another - I feel maybe Logic is not the best for this and I should just route my ER1's midi out to the EMU and use other VSTs for on the fly rhythm.

Thanks for your help!