Messy session after automated Reconform

[soundworx]

Hi,

Just did a 3-reel reconform with Conformalizer. With all these extra edits and inserts, is there a "smart" way of getting rid of all the unwanted automation breakpoints? (erase breakpoints where there's no audio region or something)

It's really messy to look at and I can't imagine it being helpfull for the responiveness of the session.

[Frank Kruse]

Select over break-points then hit X (only works on the automation parameter currently selected)

Other option: Select, then write to all enabled automation with a static setting.


Frank.

[Reckless Erik]

You could also try Control X which will glide all parameters in the selection and as a result clean up the look or,
Control delete which will delete all automation in the selection or,
Thin all, a new command in 8.0.4 which will thin all automation in the selection.
Be careful that you don't delete something that you shouldn't!!

Regards Nick

[jimlongo]

Command-option-/ will write a static set of all automation across a selection.

[Ray JB]

option-apple-T (thin automation) works well to vape non-useful automation points

[The Cargo Cult]

I've often thought about adding an optional "automation cleanup" routine at the end of a conform run to tidy up that breakpoint debris.

if I did, which command would you guys prefer for it to call?
write to all?
clear all auto?
glide ?


cheers,
justin

[bad jitter]

I would always like to keep my existing automation after conform. "Problems" are all those new useless automation breakpoints, which don't actually affect automation at all. But IMO, it's not a big problem. Also, I think that it's Pro Tools that should have the "delete useless automation breakpoints" command after all.

[Frank Kruse]

Originally Posted by bad jitter

I would always like to keep my existing automation after conform. "Problems" are all those new useless automation breakpoints, which don't actually affect automation at all. But IMO, it's not a big problem. Also, I think that it's Pro Tools that should have the "delete useless automation breakpoints" command after all.

I also pretty much ignore those break-points. I never noticed that they made the session slower. For me it´s only been more a "cosmetic" than a real issue since nothing is playing there anyway.

frank.

[soundworx]

Originally Posted by Frank Kruse

I also pretty much ignore those break-points. I never noticed that they made the session slower. For me it´s only been more a "cosmetic" than a real issue since nothing is playing there anyway.

frank.

It is a cosmetic thing, I agree, haven't noticed any issues with performance yet, but I use a HD2 pretty much maxed out, so I have to be very organized to make that work. (low budget feature). And besides that, I hate faders clunking all over the place for no reason.

Speaking of faders; Anyone for a no preamps, 16/24 fader, Eucon enabled, integrated keyboard Digi Controlsurface? Where's the good news ;-)?

[The Cargo Cult]

the problem I have with leftover automation in those gap areas is that at some point I'm gonna fill the gap with audio and depending on how I do that, the automation in that area might get left behind. and it's usually a snap up to zero dB which I may not notice right away.

the other issue is that plugin automation breakpoints are only accurate to within a couple of frames so you might find your atmos EQ setting kicks in 2 frames after the scene starts simply because there's a chunk of "nothing" preceding it.

justin