[Ardour-Dev] rfc: proposed feature to prevent accidental overwriting of automation

Thomas Vecchione seablaede at gmail.com
Wed Sep 8 13:40:54 PDT 2010

Very much like this idea, you have no idea how often I want to write
automate an entire AU plugin for instance which can have 20-30
different controls, then have it playback after I am done.


On Wed, Sep 8, 2010 at 3:48 PM, Paul Davis <paul at linuxaudiosystems.com> wrote:

> There are broader plans for a tree-like heirarchy of automation
> control. Ben Loftis has described this to me, and it seems like an
> obvious and *relatively* simple idea. Each thing that can be automated
> has an "automation parent" that can disable or change its automation
> state. So, for example, each plugin parameter has the plugin as the
> automation parent. The plugin has the track/bus as its automation
> parent. The track/bus might have  a track group as its parent. Each
> track group and/or track/bus has the Session as its automation parent.
> This allows you to enable/disable automation state for the entire
> session in one place, or more finely at various different levels.

More information about the Ardour-Dev mailing list