Thursday, October 05, 2006

Control Surfaces MIDI Monitor

Sometimes it's useful to be able to see what MIDI data is coming in to Logic, if you're troubleshooting, or transforming MIDI messages to do useful things, and experienced users will place MIDI Monitor, MIDI keyboard and other environment objects in the path between the Physical Input and the Sequencer Thru objects to see incoming MIDI data, as well as watching the MIDI monitor in the transport window.

The one problem with this method though is that Logic's controller support, and Logic's controller learn assignments "steal" assigned MIDI messages *before* they arrive at the Physical Input.

So if you learn plugin parameters to your MIDI keyboard's knobs, or you use Automation Quick Access on your mod wheel, or you have a control surfaces such as a Mackie Control - any MIDI messages assigned to these functions, or coming in from a control surface *will not* be displayed via the Physical Input - they effectively don't exist in the sequencer part of Logic, as the controller assignments reroute them internally to control whatever you've assigned them to.

However, Logic does have an extra MIDI Monitor window, which will display *all* incoming MIDI data, including control surface data, and it's called the Control Surfaces MIDI Monitor window - you'll need to assign it to a key command to open it.

The Control Surfaces MIDI monitor will show you *all* MIDI data going in and out of Logic, including the data intercepted by the controller assignments and control surfaces functions.

The "View" local menu gives you a number of options for customising what you want to see or ignore.

It's a handy one for troubleshooting those pesky MIDI messages.


At 6:14 AM, Anonymous RockBottom said...

This one simply doesn't show in my KC window, whatever the keyword I type: what is the command title again?

At 6:21 AM, Anonymous Anonymous said...

That's because you're still running 7.2.1: when were those two extra commands added? I think it would be fair to the reader if you did mention version requirements along with the tips.

At 6:26 AM, Anonymous Anonymous said...

In my Key commands no Open midi monitor option ?

At 7:58 AM, Blogger Bee Jay said...

I am running 7.1.1.

The screenshot of the key commands window in the tip shows you exactly where you can find it and what it's called.

I have no knowledge of whether this has been removed in 7.2 but it seems unlikely(!). If someone can categorically tell me that this feature is not in 7.2, then I will amend the tip accordingly. So gimme me a screenshot, chaps!

I get what you say about versions, but really, we are talking about Logic 7 here, and if there's a specific feature that was only added in 7.1 or 7.2 then I will try to note that, but those will be in the vast minority.

From what I know, the control surfaces MIDI monitor has been in Logic 7 from the start, and it's not in Logic 6.

(Note: Unfortunately, I'm stuck on 7.1.1 and Panther at the moment due to Waves upgrade policies - I don't see why I should have to pay them more money just to continue to use the same plugins I already own, so if I upgrade to Tiger, I'll lose them. Plus the fact that they are now dongle only, when one of the reasons I bought them in the first place was because they supported disk authorisations.)

At 12:36 PM, Anonymous RockBottom said...

I can confirm there's no such command in 7.2.1

At 12:39 PM, Anonymous RockBottom said...

How do we send you screenshots? With href tags inserted in the comment form?

At 1:21 PM, Blogger Bee Jay said...

RB, just gimme the url of the pic in a comment, its the easiest way.

I'm really surprised though...(!)

At 11:00 AM, Anonymous RockBottom said...

Sorry, look at this:

At 6:59 PM, Blogger Bee Jay said...

Yeah, it definitely looks missing.

If you give me a little while, I'll upload a Logic song with the monitor window open - can you try it and see if the window opens for you?

It could be that the key command is gone, but the function is still there (like the track automation folder key command)

At 9:56 AM, Anonymous RockBottom said...

Or maybe the environment monitor object doesn't filter out the hijacked events any longer? Oh no! I just checked: they do not show, either...


Post a Comment

<< Home