Logic Users Group - Forums - LUG - Thread #69731: [GEN] Assign Modulation Cotrol to PlugIn Parameters

Hi there, I would like my modwheel to become a kind of general controller that I can very easily change to control the value I'm working on at the moment. Example: I just inserted an EQ in an audio channel and now I would like the Modwheel to control the cutoff of that EQ. I know how to build an environment object, then cable it to that channel and then find out to what information the plugin reacts (by recording the movement with the mouse and then checking the list editor) and insert a transformer. Now, these are a couple of steps and take a while and I was just wondering, if there is a faster way of doing this. I know Logic now has the automation quick access, however in there I only seem to be able to control the volume of the current track (which is already a pretty darn good thing!) I once built an environment object where I could switch between different transformers via a Menu, but of course I can't cable anything to a plugin. especially if that plug in is not used yet ;-) Cheers Hans Sytem: Logic 6.0.0 G4 Dual 533Mhz / 1 GB RAM OS 9 OS X (10.2.5) MOTU 2408mk2 Unitor8

On a fine day, 02-05-2003, Hans Hafner wrote: >I would like my modwheel to become a kind of general controller that >I can very easily change to control the value I'm working on at the >moment. Example: I just inserted an EQ in an audio channel and now I >would like the Modwheel to control the cutoff of that EQ. I know how >to build an environment object, then cable it to that channel and >then find out to what information the plugin reacts (by recording the >movement with the mouse and then checking the list editor) and insert >a transformer. OK, so I'll suppose you know how to deal with a transformer set to "Track Autoamtion Splitter" in order to transform incoming CC to fader events, so you can record track autoamtion. If not, check my autodemo set of tutorials (Logic section of my website -- see sig). >Now, these are a couple of steps and take a while and I was just >wondering, if there is a faster way of doing this. I know Logic now >has the automation quick access, however in there I only seem to be >able to control the volume of the current track (which is already a >pretty darn good thing!) > >I once built an environment object where I could switch between >different transformers via a Menu, but of course I can't cable >anything to a plugin. especially if that plug in is not used yet ;-) Have a Channel Splitter transformer between Physical Input and To Sequencer. Set it to 'split' CC1 (modwheel), so CC1 comes out of the 1st outlet and all the rest comes out of the 2nd outlet. Cable the 2nd outlet into the To Sequencer object. The 1st outlet goes into a transformer that 'fixes' the channel, which in turn goes to a transformer that 'fixes' the -1- value. Cable a meta-127 text-fader into the channel-transformer, set range to 0-15, and enter the text "channel strip, insert 1, insert 2, ... insert 15" in the fader. Cable another meta-127 text fader into the -1- transformer. Enter the 128 parameter names of parameters you want to be able to change, in any order you like -- like "Fat EQ band 1 freq, St.Delay L-feedback, ...". Now suppose the 1st text fader is set to 'insert 2', and the 2nd is set to "Fat EQ band 1 freq.". This means the modwheel will be transformed, in 2 steps, to a controller on channel 3 (=insert 2), CC#=0 (since FatEQ... is the 1st entry in your 'parameters' text fader). Clearly you now want this CC0, ch3 message to affect the Fat EQ band1 freq (which might be Fader Event 28, or whatever). You therefore have to make a mapping from the 2nd textfader to the appropriate event type. So figure out which fader event belongs to Fat EQ band 1 freq by attaching a Monitor to a channel strip, inserting a Fat EQ and moving the relevant knob. Let's say you find a Fader event 28. Now create another transformer, set to "Use Map" for parameter -1-. Set the 1st entry of the map (entry 0, corresponding to the CC0) to 28. Set the 2nd entry (no.1) to the fader event for "St.Delay L-feedback" (following the example I gave above -- of course you should use the actual 128 parameters you're interested in here). This is a lot of work, but only needs to be done once (as long as 128 different parameters suffices, that is... :-) Then cable this transformer into a Cable switcher. Each output of the Cable Switcher goes to a transformer set to Track Automation Splitter, converting CC to Fader events (Operations Status = Fader -- leave the rest alone). Every such transformer finally runs into one channel strip. To top it off: cable a text fader into the Cable Switcher and have it control the switch position. Enter descriptive names, corresponding to the connected channel strips, into the fader. Summing it up, you have: * Physical Input into * Channel Splitter (2nd outlet goes to To Sequencer), 1st outlet to * Transformer-A (controlled by 1st meta-127 textfader) fixes channel, into * Transformer-B (controlled by 2nd meta-127 textfader) fixes -1-, into * Transformer-C, set to -1-: Use Map (mapping 2nd textfader entries to proper events), into * Cable Switcher (controlled by textfader), into * multiple copies of Track Automation Splitter, each running into * Channel strip. I guess you can combine transf A and C into one -- so the order would be B -> A&C. Would save one transformer... With this setup you pick the proper insert slot from the 1st textfader, pick the parameter you want to control from the 2nd textfader, and pick the appropriate channel strip from the switch-controlling 3rd textfader. Note: It's annoying that you have to use multiple Track Automation Splitters. In an ideal world, you would have Transformer-C --> Track Autom. Spl --> Cable Switcher --> channel strip thus only needing _one_ TA splitter. Last time I tried this doesn't work unfortunately -- it seems there may be no objects between the TA splitter and the channel strips. Even a simple Cable Switcher will stop the patch from working. Is the above a bit clear, or am I talking Chinese here? :-) -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.omega-art.com/