Thanks for the input Thomas and Len, I started this thread because I thought it was rather stupid that cc64 should control anything other than sustain pedal. The more I-ve been struggling with this _feature_ the last days, the more stupid I feel the whole issue is! This must have been programmed by someone not living in a musicians world. There are two cc numbers that are used all the time (modulation and sustain-pedal) . It should be a simple task to avoid theese numbers. And now I-m talking about those cc-s that is REALLY the most commonly used. Like most musicians I have a master-keyboard WITH a sustain-pedal. Sometimes I step at this even if I-ve selected an audio track. I know I shouldent by now, but it-s extreemely irritating that someone suddenly have designed a panel on my flor labeled _DANGER DONT TOUCH THIS_!! Hoping for a solution shortly!! ;-) Frode Fjellheim >>Hi Frode, >> >>> I realize there is a new feature allowing plug-ins to be automated. >>> So far so good but why why WHY with controller 64 (sustain-pedal). >> >>MIDI controllers are ubiquitous for *controlling* devices, including Logic's >>audio mixer. >> >>But there are issues, that often specialized controllers should only connect >>with certain specialized outputs. Synth knobs, sustain pedals, controller >>boxes... >> >>The Environment needs a way to treat these controller inputs as specialized, >>and restrict them so they only go 'thru' for appropriate instruments. >> >>Today, I am not exactly sure how to design this. Suggestions? >> >> >>Cheers, >>Thomas > >You can use transformers to capture and route these messages. Why >cc#64 was used for the first plug-in controller # is an unsolved >mystery (well actually it allows 64 contiguous controllers for >controlling plugins), but it makes the first parameter of a plug-in >instrument inaccessible. > >Len Frode Fjellheim http://home.sol.no/~frfjellh/ http://www.transjoik.com