EDIT
Ignore/delete this, I didn't turn Automation Read mode. It literally says this a few pages down in the guide.
Automation doesn't work at all in Tracktion 6 [DELETE/IGNORE]
-
- KVRer
- 8 posts since 26 Nov, 2017
I'm learning Tracktion 6 through Bill Edstrom's guide and I wanted to try out automation in Tracktion. Unfortunately, after creating automation for volume, it seems to not work at all, whatever I do; adding points and shaping the curve doesn't work, neither does just moving the line without any points; the volume doesn't change no matter what I do. Tracktion even crashed a couple of times while I was trying to do this: once while adding the automation (by dragging and dropping the 'A' icon) and once after I believe trying out automation steps. Any help would be appreciated.
EDIT
Ignore/delete this, I didn't turn Automation Read mode. It literally says this a few pages down in the guide.
EDIT
Ignore/delete this, I didn't turn Automation Read mode. It literally says this a few pages down in the guide.
-
- KVRist
- 320 posts since 9 Sep, 2017
Ok, I see,
if it is allowed to add some caveats:
Generally it works for me, but some details are not stable.
(It may depend on the particular plugin also.)
Automation in racks:
There may be a difficulty to maintain the connection of the displayed curve on my screen with the respective plugin, especially when the same plugin exists in the rack more than once (start with multiple volume faders).
This is also the case with the default parameter fader. (That thing you select yourself, shown on the surface of the plugin symbol, to point to some parameter deeper down.)
If you have duplicate names, it will find the first plugin instance only, if you want to automate.
I tried to create a default parameter for a whole rack, but it seems difficult. If the rack is used as a switchboard, to connect several tracks (side chaining; send effects _with_ latency correction), by inserting the same rack multiple times, we might get lost with attempts of complex automation in such a construct.
Automation tracks, that you create with [+].
If you select the curve, and then pull some changes in the bottom window (Displace Curve, Scale Curve), it may not find the backtrack to the real parameter and crash.
A workaround for me seems, that I create a new point in the curve, and delete it immediately, and only then use these dragging scale controls. Creating a point seems to realign the connection.
It is similar with parameters that are hidden down in a rack. But they seem even less stable.
After some experience to get an instinct about the crashes, I was able to create quite complex mixes with a lot of sidechaining and automation.
For some problems, as an approximate solution, it might help to route a particular complex signal through an extra "normal" track, and use its volume fader for the automation, or also some ersatz-EQ or plugin there, if some sound component does not automate deeper down in my rack networks.
if it is allowed to add some caveats:
Generally it works for me, but some details are not stable.
(It may depend on the particular plugin also.)
Automation in racks:
There may be a difficulty to maintain the connection of the displayed curve on my screen with the respective plugin, especially when the same plugin exists in the rack more than once (start with multiple volume faders).
This is also the case with the default parameter fader. (That thing you select yourself, shown on the surface of the plugin symbol, to point to some parameter deeper down.)
If you have duplicate names, it will find the first plugin instance only, if you want to automate.
I tried to create a default parameter for a whole rack, but it seems difficult. If the rack is used as a switchboard, to connect several tracks (side chaining; send effects _with_ latency correction), by inserting the same rack multiple times, we might get lost with attempts of complex automation in such a construct.
Automation tracks, that you create with [+].
If you select the curve, and then pull some changes in the bottom window (Displace Curve, Scale Curve), it may not find the backtrack to the real parameter and crash.
A workaround for me seems, that I create a new point in the curve, and delete it immediately, and only then use these dragging scale controls. Creating a point seems to realign the connection.
It is similar with parameters that are hidden down in a rack. But they seem even less stable.
After some experience to get an instinct about the crashes, I was able to create quite complex mixes with a lot of sidechaining and automation.
For some problems, as an approximate solution, it might help to route a particular complex signal through an extra "normal" track, and use its volume fader for the automation, or also some ersatz-EQ or plugin there, if some sound component does not automate deeper down in my rack networks.