</div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>
QUOTE (Ott^ @ Mar 14 2004, 05:42 AM)</td></tr><tr><td id='QUOTE'> So - let me get this straight.
For one track of synth pad I have;
1. A midi track containing the note information.
2. A VST Instrument track for automating synth nobs etc.
3. A VST Effect track for every plugin on that instrument.
and each parameter shall have it's own dedicated track too.
[/quote:9b56ccab54]
Well actually no thats not straight
For one track of synth pad you would have:
- one MIDI channel containing the note (+cc + aftertouch + whatever) info
- one channel for that instruments output, with all channel parameters (volume, send levels, etc) and the channel's insert parameters (eg, ohmboyz D1 filt cut) available via a menu in that.
- one global "plugin automation" channel, with all plugin automation parameters for those plugins not attached to a channel (ie, master fx, send fx, and instruments) available via a menu in that. This would handle my V-Station FiltEnv Depth, but also my S1 NuendoReverb Predelay.
So, no, each parameter doesnt get its own track, you can flip between them in the menu on a single track if you want. I just have expanded them with the [+] to have a track each because i wanted to see multiple parameters against each other... so the track bloat is my fault. I could easily show only one track and use the menu, or indeed hide the automation altogether.