Automation data as Alias

[Vacheto]

Many people wish to use track automation as alias data to be able to edit only the original region automation. Unfortunately the track automation events are recorded in a separate Track Automation Folder which is not region based, so if try to make an alias of a given region which contains some automation data, you will find that the automation does not work when play the alias region. I offer some methods which solve the problem...

 

Scenario 1

 

Most of the track automation data uses so called Fader messages ( Logic behaviour messages type), that's why "Move Current Track Automation Data to Region" does not work with fader messages and it's hard to convert ( I'll describe how to in Scenario 2 ).

Let's try to draw some ES1 Cutoff automation and make it work in the alias regions.

Instead of drawing or record track automation ( which is a problem as I mentioned before ) I'll draw region automation.

1/ First you need to know the outgoing parameter Fader message number, its internal channel strip midi channel etc.. .

Example: Insert ES1 as Audio Instrument instance, go to the environment mixer layer, create Monitor object from "New" menu and patch/cable the ES1 channel strip to the Monitor object. Twist the ES1 cutoff and you will see F2 10 ... outgoing messages ( F=Fader message; 2=Midi ch.2; 10=Cutoff parameter number; ....=value ).

2/ Open Hyper Edit and create or modify some existing event definition of a hyper set and name "ES1 Cutoff"

• set the "Status" to "Fader" in the Inspector; check the Channel box and set it to midi ch.2; check the Number box and set it to 10; so the event definition will be customized to show ES1 Filter Cutoff only.

• create more hyper event definitions for other ES1 parameters and combine in a Hyper Set labeled as "ES1 Synth". You can create hyper sets for ES2, EVB etc...\

 

Using the above method you can create aliases of the original region with working automation.

 

Scenario 2

 

You have some existing Track Automation and you wish to convert it to region data to make it work in the alias objects.

1/ You can use "Move Current Track Automation Data to Region" which will work with continuous control events (CC#) like the channels strip level and pan faders, but "Fader" type plugin messages will be a problem yet...

2/ Hit Ctrl+Command+E to open the Track Automation Event List ( where you will find lots of F2 10 ... events ), draw empty midi region or select some if any, where the ES1 cutoff automation is. Open that region with Event List, so you will have two event list editors opened now ( Track Automation Event List and the Region Event List ). If there is some volume or pan CC automation on the same track just click the Controller Filter button of the event list to be able to see the Fader massages only.

Select all F2 10 .... events ( shift click to deselect the first message with position 1 1 1 1 ), copy and paste in the Region Event List in the same position.

3/ If have more than one automation parameters which are fader status based ( recorded in same or near event positions ), then it will be hard to filter and select them in the Track Automation Event List Editor, so try next example:

The ES1 Cutoff ( F2 10 ..) and Resonance ( F2 7 ...) are shown in messy order in the Track Automation Event List.

If like to select the ES1Cutoff ( F2 10 ... ) messages only, just select one message and go to Edit->Select Similar events, so this operation will select the Cutoff automation events only.

 

To edit the extracted track automation Fader massages for a certain region which must work as original for its aliases, use the Hyper Edit method described in Scenario 1 above !