MOTUnation.com

Is it possible to delete all automation lanes in a DP sequence editor track? I can only see how to do one lane at a time (i.e., range select the entire top layer of the track and delete, next layer comes to the top, repeat... it can get pretty tedious...)

Thanks-

Gary

Sorrry... "'DOH!" moment- make new take, copy and past audio from previous take!

Here is one simple way:
In the view filter window (cmd - F), hide the soundbites.
Select all tracks (cmd -A) and delete, automation is gone
Back to view filter and show the soundbites.

David

+1

altho the i beam tool will delete all automation - and if that the only area with that automation the lanes will disappear..

it's good to get to know the view filter - so u dont have that brown trouser moment when u inevitable think there is a bug cos all soubites disappear yet u can still hear them

( that was my first ever post I think )

That's a new one... A brown trouser moment he he...

Grigri wrote:Here is one simple way:
In the view filter window (cmd - F), hide the soundbites.
Select all tracks (cmd -A) and delete, automation is gone
Back to view filter and show the soundbites.

David

Good tip, David, I hadn't thought of that; of course if I want to kill it in just one or two tracks I can hide the others before command-all.

ghobish wrote:

Grigri wrote:Here is one simple way:
In the view filter window (cmd - F), hide the soundbites.
Select all tracks (cmd -A) and delete, automation is gone
Back to view filter and show the soundbites.

David

Good tip, David, I hadn't thought of that; of course if I want to kill it in just one or two tracks I can hide the others before command-all.

Or just draw in the automation you need instead of hitting the automation record and recording every parameters controller data in the plug when it's only one knob your turning.

newrigel wrote:Or just draw in the automation *you need* instead of hitting the automation record and recording every parameters controller data in the plug when it's only one knob your turning.

That's quite an assumption, newrigel; I don't do that.

In mastering an album of multiple songs on one track, one will often have multiple plugs with multiple parameters changing on every song (sometimes within a song). One plug I use often has over 40 parameters controllable and believe me I don't automate any more of them than necessary (usually "only" 20 or so). Between the multiple plugs, I sometimes have as many as 35 or 40 parameters that need to be changed over the course of the album.

Alternatively I use the "one song, one track" method in which very little automation is used, the trade off being many multiple instantiations of some very heavy CPU plugs (which need to be run in real time to avoid some minor glitching).

The reason this came up is because opening some older (5.13) sessions in DP 6 & 7 lost some automation turnover points, resulting in the automation lanes becoming horribly disfigured with all sorts of ramps that shouldn't have been there- Easier to erase the existing automation and lay it back in (using the presets that I saved for every plug for every song).