How do you mute automation? Delete automation?
- KVRian
- 1385 posts since 12 Oct, 2012
Hi,
So i created 2 automation lanes, each is assigned to a different parameter, but when i deleted one of them (using the "-" button), the knob it was tweaking was still reacting as if the automation was still there. How do i completely delete an automation?
Additionaly, is the a way to temporarily mute an individual automation lane?
Thank you
So i created 2 automation lanes, each is assigned to a different parameter, but when i deleted one of them (using the "-" button), the knob it was tweaking was still reacting as if the automation was still there. How do i completely delete an automation?
Additionaly, is the a way to temporarily mute an individual automation lane?
Thank you
-
- KVRist
- 358 posts since 3 Dec, 2004
The minus thing just hides the automation track, so the automation is still active.
To completely delete it you just need to delete all the points on the line. You can do this by clicking the line and the selecting the option for delete all point in the properties menu. Or you can shift click the first and last nodes to select them all and hit delete. At this point your line is just based on how you have the setting set in the plugin.
I don't know if there's a way to disable an automation line temporarily. I might just be missing it, but what I would do is duplicate the plugin, bypass one, automate what I wanted on one of them, then switch between the two. Highlight them both and use the 'bypass plugin' key-command for instant comparisons. Sounds convoluted, but only takes a second really.
That would definitely be worthy as an option, or at least macro or key command, if it isn't already.
To completely delete it you just need to delete all the points on the line. You can do this by clicking the line and the selecting the option for delete all point in the properties menu. Or you can shift click the first and last nodes to select them all and hit delete. At this point your line is just based on how you have the setting set in the plugin.
I don't know if there's a way to disable an automation line temporarily. I might just be missing it, but what I would do is duplicate the plugin, bypass one, automate what I wanted on one of them, then switch between the two. Highlight them both and use the 'bypass plugin' key-command for instant comparisons. Sounds convoluted, but only takes a second really.
That would definitely be worthy as an option, or at least macro or key command, if it isn't already.
- KVRian
- Topic Starter
- 1385 posts since 12 Oct, 2012
What a bummer, it's like for every nice thing workflow-wise Tracktion has given me and i have enjoyed, it takes away with missing on some basic functionalities.
Thanks
Thanks
-
- KVRian
- 524 posts since 16 Mar, 2017
Not quite accurate.Kang wrote: Wed May 19, 2021 7:06 am The minus thing just hides the automation track, so the automation is still active.
In Waveform, the automation "track" is just a window through which the automation data for a particular parameter is viewed. The actual automation data is not stored in the track. You can create two automation tracks and select the same parameter of the same plugin into them, and they will display the same data, constantly in sync - edits to one are reflected on the other - because they are two windows displaying the same underlying data. If you have one automation track, you can change the parameter whose data is displayed and the one previously displayed keeps the data even though it is not currently visible.
The "-" button actually does delete the track, but the track is just a view of the data - deleting the track has no effect on the actual automation data itself.
If you click on the automation curve where there is not an automation point, the properties area in the expanded toolbar along the bottom of the Waveform window will show data for the "Automation Curve" - there is a big red button there to "Delete Points from Curve" - clicking that and selecting "Delete all points from the curve" will in effect reset the automation data for the parameter being viewed.
Unfortunately I don't know of a way either to disable the use of automation data for an individual parameter (only to globally disable all of them using the button in the transport section). That would be a nice addition.
-
- KVRist
- 358 posts since 3 Dec, 2004
Uhhh... that's what I said...fde101 wrote: Wed May 19, 2021 11:28 amNot quite accurate.Kang wrote: Wed May 19, 2021 7:06 am The minus thing just hides the automation track, so the automation is still active.
In Waveform, the automation "track" is just a window through which the automation data for a particular parameter is viewed. The actual automation data is not stored in the track. You can create two automation tracks and select the same parameter of the same plugin into them, and they will display the same data, constantly in sync - edits to one are reflected on the other - because they are two windows displaying the same underlying data. If you have one automation track, you can change the parameter whose data is displayed and the one previously displayed keeps the data even though it is not currently visible.
The "-" button actually does delete the track, but the track is just a view of the data - deleting the track has no effect on the actual automation data itself.
If you click on the automation curve where there is not an automation point, the properties area in the expanded toolbar along the bottom of the Waveform window will show data for the "Automation Curve" - there is a big red button there to "Delete Points from Curve" - clicking that and selecting "Delete all points from the curve" will in effect reset the automation data for the parameter being viewed.
Unfortunately I don't know of a way either to disable the use of automation data for an individual parameter (only to globally disable all of them using the button in the transport section). That would be a nice addition.
-
spoontechnique spoontechnique https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418750
- KVRist
- 492 posts since 7 May, 2018
I've often wished Waveform had a clip system for automation, to normalize it with the rest of Waveform. Automation could benefit greatly from all the features available to regular tracks/clips, like mute/solo, copy/paste/delete, etc.
Linux version?
-
- KVRAF
- 1601 posts since 9 Jan, 2018
Agreed, as it would be ideal to copy and paste pitch bends or mod wheels, especially for plugins that interpret those as specialized control functions. Would be a huge time saver. You could put a fade out clip on a track, or if you wish, drag it to a master track and fade the whole song. Stretch or squeeze the clip to lengthen or shorten its duration. I could see myself building a small library of presets, too.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRist
- 52 posts since 6 Mar, 2010
Automation is one of the quirkiest aspects in waveform, but the functionality is there.
To understand it, first you need to realize that plugin parameters are handled by automation tracks, whereas standard midi messages are handled within midi clips, in the "controller" lanes.
So, when it comes to midi, it's entirely possible to have a separate midi track with clips dedicated to automation. However, editing could benefit from the vector points system existent in automation tracks (the controller editor is a bit rough). Ctrl+c/v works within the controller window too.
As for, plugin parameters handled by automation tracks, the vector point system is great, but copy/paste can only be accesssed in the properties panel below, in conjuntion with markers.
I can see why midi controller data should be stored in clips rather than the track, as it will apply to any other midi track you desire to move your clips. The same will not happen with specific plugin parameters, specific to the ones assigned to each particular track. This behavior makes perfect sense to me.
And I do agree it would be a substantial improvement to make the behavior of the two uniform, with the ability to draw lines from vector points, and a more coherent copy/paste behavior.
To understand it, first you need to realize that plugin parameters are handled by automation tracks, whereas standard midi messages are handled within midi clips, in the "controller" lanes.
So, when it comes to midi, it's entirely possible to have a separate midi track with clips dedicated to automation. However, editing could benefit from the vector points system existent in automation tracks (the controller editor is a bit rough). Ctrl+c/v works within the controller window too.
As for, plugin parameters handled by automation tracks, the vector point system is great, but copy/paste can only be accesssed in the properties panel below, in conjuntion with markers.
I can see why midi controller data should be stored in clips rather than the track, as it will apply to any other midi track you desire to move your clips. The same will not happen with specific plugin parameters, specific to the ones assigned to each particular track. This behavior makes perfect sense to me.
And I do agree it would be a substantial improvement to make the behavior of the two uniform, with the ability to draw lines from vector points, and a more coherent copy/paste behavior.
-
spoontechnique spoontechnique https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418750
- KVRist
- 492 posts since 7 May, 2018
The controller editor was, for me, miserable to use. I stopped using pitch bends entirely until I found a synth that allowed automation for pitch bending. Vector points would be a huge improvement.
But that undersells how useful applying the clip system to automation would be. For example, automation tracks could have a destination parameter in a dropdown menu. An automation lane going to "pitch bend" could be instantly switched to controlling "Macro 1" with no need to copy/paste.
But that undersells how useful applying the clip system to automation would be. For example, automation tracks could have a destination parameter in a dropdown menu. An automation lane going to "pitch bend" could be instantly switched to controlling "Macro 1" with no need to copy/paste.
Linux version?
- KVRian
- 528 posts since 10 Nov, 2018
-
- KVRAF
- 1601 posts since 9 Jan, 2018
I haven't found any substantive changes to automation in v12.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
