move objects AND automation curves TOGETHER

[stupid usa]

Hi.
Does anybody know if it is possible to move track objects TOGETHER WITH the automation curves?

I only can only grab some track objects at the same time but the keyframes on the aut.curve are not affected when these objects are moved to another position.

[aldi]

it isn't possible at the moment. but you can copy and paste automation. but i think it will be possible someday.

[stupid usa]

Thank you for the quick answer. I ask myself why such an important move is not yet possible..

[pHz]

because the CURRENT tracktion structure means that clips and automation are entirely seperate (which is why you can usefully view ANY automation curve on ANY track) ... this is in fact a very logical way to think of automation ... since any automation actually affects a plugin / filter parameter and NOT the data in the clip why SHOULD they be linked ???

... however ...

... there have been many discussions on ways to keep this current functionality while also introducing some form of per-clip automation or a way to lock automation curves to the clips they affect ... as aldi says - its almost certain that a future version of tracktion will feature this ... dont know when though ...

slainte rob

[clueless]

then wouldn't it make sense for automation data to be handled as clips too?

[semiquaver]

I'm with clueless - automation clips.

[Graeme]

... this is in fact a very logical way to think of automation ... since any automation actually affects a plugin / filter parameter and NOT the data in the clip why SHOULD they be linked ???

I don't follow this argument at all.

The automation may act directly on the clip (as, say, volume or pan) or it may act on the functions of a plug-in through which the clip is being run. Either way, if you move audio/midi driving that plug-in, then it would make sense for the automation to follow it (at least by default - there could be an argument for being able to unlink the two when required).

[pHz]

The automation may act directly on the clip (as, say, volume or pan) or it may act on the functions of a plug-in through which the clip is being run.

vol / pan automation DOESNT act on directly on the clip ... it acts on a vol / pan filter ...

... BTW not saying i actually agree with the way T does it ... just trying to explain WHY automation and clips are (currently) seperate under the T paradigm ...

... personally id like to see the current automation system stay but maybe just have an added right-click option on clips along the lines of 'lock automation to this clip' that would then allow you to select a 'live' automation track whose breakpoints would then shift if you moved the clip ... obviously you could lock more than one automation track to any given clip ...

slainte rob

[rpc9943]

another vote for automation clips.

[Todd24]

I think both optins, to lock or not, makes the most since. Clips could solve that IF, a glue clips tool was added.

[Mr. Tingle]

why not have the copy/paste function copy both the clip to be moved AND the automation where that clip is located at the same time?

That way automation is still linked to filter but it makes it dead quick to move stuff around.

No extra functions required.

[semiquaver]

T doesn't associate automation with clips! - what if you have two overlapping clips on a track feeding a filter which is being automated. What should happen when you move one of the clips but not the other?

[pHz]

T doesn't associate automation with clips! - what if you have two overlapping clips on a track feeding a filter which is being automated. What should happen when you move one of the clips but not the other?

thanks ... not JUST me then ???

slainte rob

[SaviorNeeded]

Might be time for some glowing red ovals and arrows!

Tom

[pHz]

Might be time for some glowing red ovals and arrows!
Tom

heehee ...

... i doubt that even the mighty power of the red hot ellipses can bring clip automation to T without the intervention of st jules the municipal ...

slainte rob