TI Automation in Ableton Live

[kcinsu]

Ok,

So my understanding is that you have the main TI plugin strip. Then, for any additional MIDI channels you want, you need to make a MIDI strip in Live, and route it to the appropriate channel in the TI.

So, as far as I can tell, the only TI automation that shows up (filter cutoff for instance) happens only on the main TI plugin strip... for all the other channels, you have to assign a parameter to a MIDI cc, and then automate that CC in Live.

Is this right? There is no way to view all the automation parameters any other way?

Not very TOTALLY integrated?

[7G]

Originally Posted by kcinsu

There is no way to view all the automation parameters any other way?

I use Live 8 and just hit the "+" button...

Cheers!

[kcinsu]

Im using live 8 as well...

what + button? I dont see one on the TI track...

[kcinsu]

you're messing with me right? I searched the manual pdf, and there is no "+" button for adding tracks.

[Splat!]

I think he means the '+' button in the Arrangement View of Live which unveils the Automation lanes. I haven't tried this, so can't really comment on whether it works.

It'll be cool if it works. I've been bouncing every damned pattern out.
________
marijuana indica

[gtrance]

it is right that you can only view the automation lanes on the one channel that the virus plugin is on. However, you can still view automation for all 16 parts on this one channel.

So you have two options

1) Do all your automation for all parts on the virus track

or

2) Use midi cc's to automate enabling you to have automation for each part on its own track.

I started using the virus track for all automation, then I switched to using midi cc's. But now I've switched back to using the main virus automation. The midi cc's for me got too messy and you cant have midi automation in the arrangement lanes, only as clip envelopes which can get awkward.

Dont forget on virus control, to "right click - add to automation", for that parameter to appear in the automation menu.

[ehunter]

Say you setup an automation lane for whatever parameter, aside from drawing it in how can you record your automation when tweaking the knobs

[Doc Jones]

Originally Posted by ehunter

Say you setup an automation lane for whatever parameter, aside from drawing it in how can you record your automation when tweaking the knobs

you can also record the knob tweaks in realtime as you turn them.

[kcinsu]

Originally Posted by gtrance

it is right that you can only view the automation lanes on the one channel that the virus plugin is on. However, you can still view automation for all 16 parts on this one channel.

So you have two options

1) Do all your automation for all parts on the virus track

or

2) Use midi cc's to automate enabling you to have automation for each part on its own track.

I started using the virus track for all automation, then I switched to using midi cc's. But now I've switched back to using the main virus automation. The midi cc's for me got too messy and you cant have midi automation in the arrangement lanes, only as clip envelopes which can get awkward.

Dont forget on virus control, to "right click - add to automation", for that parameter to appear in the automation menu.

Thanks for your response!

This is too bad... life would be so much easier if this weren't so...

ah well...

back to assigning MIDI CCs...

[tranqui]

that's one of my biggest gripes... I'd love to see a closer collaboration with ableton on this. at least giving one MIDI track access to the parameters of a VST that's on another track (without any MIDI CC workarounds) would be a huge improvement of the workflow. there are times when I simply don't have a choice but to record audio clips, which kinda defeats the purpose of having such a beautifully capable synth...

one would think that saving all the automated parameters on one clip/track would work, but that's for people who trigger scenes and prefer more of less fixed arrangements. I've grown fond of using clips to keep the performance dynamic, and sometimes two hands simply aren't enough. let's hope there will be a solution for this in the future.