View Issue Details
|0000491: Slaving to a master automation track/sequence
|It would be nice to slave multiple instances of plugins to one automation track/sequence. There are often times when I want to create identical automations in multiple instances of the same plugin. It would be a big time saver to be able to use one automation track for the plugins.
It would also be nice to move between the different automation keys within the plugin config dialog. It there were buttons for navagating between the keys that looked something like:
[<] Key# [>]
It would be easier to tweek the automated values from within the plugin config rather than trying to use the automation track. (That automation track can be cumbersome for fine adjustments)
|No tags attached.
i don't totally understand the second part of your comment.
we plan to put automation "bar controllers" into the track control area of the automation tracks. not sure when.
The second part refers to the keys that are created in the automation track. It might be more useful than "bar controllers" in automation tracks because it would allow changing any automation track associated with a particular plugin.
Here's an example of how such an implementation might be used:
I have a track using "Plugin-X". Plugin-X has two values that can be automated: A and B. In this track both of the values are changed twice, the first changes are independent and the second change occure at the same time. e.g. At frame 100 A is changed, at frame 200 B is changed, at frame 300 both A and B are changed.
In the plugins settings dialog, there are two buttons: one for previous key, and one for next key. In between the two is a number listing the current key selected. It is blank because the playback head is at frame 0. I hit the "Next Key" button and the play head is moved to frame 100 where the first key is, the text between the two buttons now reads "1". The values shown in the dialog show the values of key number one. The Value of "A" is highlighted because that value has a key at this point. If I change the value of A at this point the value for the key in the automation track for A changes corrispondingly.
I click the Next Button to go to key two and the play head is moved to frame 200. Now the value of B is highlighted. I don't want to change B. The value of A shows what it's value at this time is. At frame 100 A is set to 10 and at frame 300 A is set to 20. Since the playhead is at frame 200 the value shown for A is 15. I decide I want the value for A at this point to be 17 instead of 15. I change the value in A to 17. Now A is highlighted because a key has been added at frame 200.
I click the Next Button to go to the 3rd key. The play head is moved to frame 300, both A and B values are highlighted.... etc. etc.
Does this make more sense?
makes perfect sense.
we call them "control points" rather than "keys", hence my confusion :)
the long term plan, btw, calls for exposing the "object status" of automation curves so that they can be used like audio playlists (shared between tracks, etc).
definitely post-1.0, though.
|Still an outstanding issue ?
|Note Added: 0000880
|urgent => low
|new => acknowledged
|Note Added: 0000881
|Note Added: 0000884
|Note Added: 0008585