Expanded Clip Effects?

[Cheesehead]

Wouldn't it be great to be able to stack non destructive third party FX on to a clip?

I know it's been asked for for a while, but we've done pretty well over the last few years finally getting some of the things we've asked for for a long time, so I thought I'd mention it again.
(Please, nobody mention folders in the clip list in this thread, I won't)

The existing Clip FX workflow is great and I use it a lot where you just need a static EQ for a particular clip or section. Surely it should be possible with our powerful computers these days to expand this out to host other plugins as clip FX like reverb or delay etc in a non destructive way.

Baking everything in with Audiosuite seems pretty old fashioned these days and Reaper and even Final Cut have had these workflows for years.
It would be really useful in both music and post production, so a total win for everyone!

[JingleDjango]

I would love an EQ module that didn't feel so clumsy to dial in. That's about the only thing I use ClipFX for (usually tone-matching DX).

[noiseboyuk]

Originally Posted by Cheesehead

Wouldn't it be great to be able to stack non destructive third party FX on to a clip?

It would. But I suspect that there's a problem here. Imagine if you had 100 different clips with 100 different plugins, all hidden but in use. It might prove am intolerable resource burden.

But I'd hope that just as they are partnering with Celemony and iZotope that a limited number of 3rd party plugins might be allowed.

[JingleDjango]

Originally Posted by noiseboyuk

It would. But I suspect that there's a problem here. Imagine if you had 100 different clips with 100 different plugins, all hidden but in use. It might prove am intolerable resource burden.

But I'd hope that just as they are partnering with Celemony and iZotope that a limited number of 3rd party plugins might be allowed.

A good point. Ableton sessions can become really sluggish and unwieldy if you aren't diligent–there are so many opportunities for nesting (drum racks, fx racks, etc). Creatively it's freeing but it can get away from you.

I would love a pared back Pro-Q that lived in ClipFX but I get the impression FF would rather stay DAW agnostic.

[smurfyou]

I'm pretty sure I remember Avid saying clip effects would be expanded to other uses when it was first introduced.... Wonder what happened there.

Although I agree I'd be scared of resource usage getting out of hand in large sessions.

I don't think it's ever a bad time to ask about folders in the bin

[BScout]

Imagine the issues with delay comp!
If other plugins were allowed, it'd have to be limited to "no look ahead" plugins and very low-latency plugins. (No linear eqs, for instance)

I'd imagine the confusion for developers and users alone is preventing that.

[Cheesehead]

It would. But I suspect that there's a problem here. Imagine if you had 100 different clips with 100 different plugins, all hidden but in use. It might prove am intolerable resource burden.

I agree it could become a massive resource hog, but to be honest I imagined it might use some kind of hidden rendering process rather than all the plugins remaining 'live', since we're talking about a static effect on a clip rather than an evolving one.

I can see the potential issues with delay compensation too, but a hidden 'freeze' would solve that.

Even an Audiosuite that allowed you to step back through renders web browser style to get back to the original would be an improvement. Especially for some of these new machine learning plugins that have too much latency to work in real time.

[noiseboyuk]

Interesting thought Cheesehead - I thiiiink it's not rendered, it's a live effect on a clip, but someone here will know for sure.

Were it rendered then that's entirely different of course.

[BScout]

Originally Posted by Cheesehead

I agree it could become a massive resource hog, but to be honest I imagined it might use some kind of hidden rendering process rather than all the plugins remaining 'live', since we're talking about a static effect on a clip rather than an evolving one.

I can see the potential issues with delay compensation too, but a hidden 'freeze' would solve that.

Even an Audiosuite that allowed you to step back through renders web browser style to get back to the original would be an improvement. Especially for some of these new machine learning plugins that have too much latency to work in real time.

I imagine this is handled like clip effects are handled in Media Composer. They are rendered. If they opened this up to everyone, it would probably have to work just like Media Composer (where there's a rendering buffer/time) which is much like how X-form works now when making adjustments.

[smurfyou]

From what I understand its like a render cache usually. I'd probably rather have Audiosuite history like Cheesehead mentioned.