> i.e I send cc 75 and the oddity responds > to cc 11!I have been told there is an offset produced by logic 4.7 > Is this true and more importantly is there a workaround to this > problem? Here's what happens: Logic 4.x and earlier provide access to controls in plugin slots via CC messages. But the first 64 CCs (0-63) are reserved for controls ON the fader strip (volume, pan, sends, etc). Then CCs 64-127 are passed through to the first 4 plugin slots, 16 CCs per slot. So sending CC75 will control the 11th control in slot 1, as you have found. If you need access to more than 16 controls in any slot, don't put a plugin in the next slot. That will give you 32 controls in the first slot. Similarly, if you only have a plugin in the first slot, and no plugins in slots 2, 3 and 4, all 64 CCs will go to the first plugin. It's a pretty annoying and limiting system, and there is no workaround in Logic 4.x or earlier. In Logic 5+, which uses new "Fader" events to control most stuff, you _can_ set a preference to pass all CCs through to the Audio Instrument plugin (not to an effect plugin). Except for CC7 and CC10, which still control the channelstrip volume/pan (dumb, huh?). So you can either cope with it, or upgrade to Logic 5. John Pitcairn ------------------------------------------------------------- Logic Control emulation for generic midi controllers: LC Xmu demo: http://www.opuslocus.com/lcxmu/ -------------------------------------------------------------