Logic Pro 9 Setting up a single macro to control multiple plugin automation

[scottmach]

Hi Guys
I have audio on a track that lasts 1 bar running through various fx.. During the course of this one bar I want to automate the multiple fx on the channel as one "mega effect" (filter sweep, distortion, reverb all move together) I go and assign all the parameters from different plugins I want to automate to single knob on my midi controller essentially creating a macro. I record this automation and each individual parameter that was assigned to the knob gets its own automation lane. This is fine but if I want to edit the automation later I have to go into each automation lane and do it individually. I am wondering if there is a way to have a single automation lane representing the knob on my midi controller, and this one lane will control the multiple parameters.

If you have used NI massive what I am trying to do is the same as its macro controllers and how they work in logic. With massive I can assign multiple parameters in the synth to be controlled by one of its macros, say macro 1. If I want to automate all these parameters together I can simply draw automation in logic for Massive macro 1 and all the parameters in massive assigned to that macro will move as one, but are controlled by a single automation lane. So say if filter cutoff and reverb size are assigned to macro 1 and I record automation with it I just see 1 automation lane for macro 1 as opposed to two separate lanes for filter cutoff and reverb.

So basically I am trying to achieve this same functionality using different plugins. I believe this is fairly easy to do in abelton live but not sure how to best do it on logic.

Any advice is appreciated
Thanks

 

[Tangra]

I am wondering if there is a way to have a single automation lane representing the knob on my midi controller, and this one lane will control the multiple parameters.

Yes there is a way...
Here is a short step by step description:
1. Create a new fader in the environment and name it "Master Auto". Select the newly created fader object and set its input definition to match the CC# you use in your external controller. By default the IN/OUT fader control definitions are set to CC#7, so you can change them to say CC13 if your external controller knob is set to CC#13 etc.
2. Create a track in the Arrange for the "Master Auto" fader.
3. Create a new Standard Instrument object in the Environment, select it and set its midi port to the IAC bus. If you have not enabled the IAC, do that in the Mac Audio Midi Setup ...
4. Cable the "Master Auto" environment fader to the IAC Instrument object.
5. Start to "Learn" the plugin parameters as you do usually using the Controller Assignments dialog and your external controller. NOTE - instead of tweaking the external controller you have to mouse tweak the "Master Auto" environment fader during the learning process !
6. After the learning select the "Master Auto" track in the arrange, hit Record in the Logic transport and tweak your external controller fader.
The incoming midi will be recorded as regular midi Controller data (say CC#13) and the "Master Auto" fader will correspond to that master control data.
7. After the single CC# recording you can easily tweak the Hyper Draw view via the Autodefine keycommand and edit the Controller data in hyper draw view (as nodes) directly in the arrange.

BTW: Delete all previous Controller assignment for the CC# you have been used with your external controller or use another CC# with your external controller. I say that cause if you use a previously learned CC# with Logic CA then that number will be filtered by the Logic Physical Input and can not pass to the Environment etc

I guess you will need some parameter scaling cause all parameters will follow your external fader using ratio 1:1. This can be done in the CA dialog or by patching multiple transformers between the "Master Auto" fader and the IAC instrument, so you can set custom value scales for the different parameters you want to control.
If you have any questions, be welcome!
Regards,
A.G

 

[Atlas]

Providing that you could set all your plugins parameters to respond to the same CC (CC#13 for example), what you need to do is to move the already recorded MIDI CC#13 data from the region to the track (yes, automation could either reside inside a region as MIDI data and/or pertain to a track independantly of the regions of that track. Once your automation moved to the desired track(s) you can edit it at will.