I want to be able to automate some parameters on a plugin and 'attach' them to clips, but it doesn't seem to be possible to do this if you put the automation on a track other than the one you are automating.
For instance, if I have a synth being played by a two bar midi clip and want to automate the cutoff over one bar on a separate track (for ease of moving the automation around), the automation envelope refuses to lock to the empty midi clip I create in that track. If I move the synth to this second track and make the first track's midi feed into this track, the automation will lock to the clip without problem. However, if I then want a third track to automate the resonance, I cannot get the automation to lock to a midi clip anymore and there doesn't appear to be a way round it...or is there?
I realise that it is possible to copy/paste the automation envelopes, but I tend to prefer working with clip based automation and to be able to see all the automation at once, making it easier if I choose to rearrange things later on. Does anyone have any way of doing the above?
Automation clips...any way to do this?
-
- KVRAF
- 16154 posts since 2 Dec, 2003 from Nashville, TN
This is because Tracktion's automation currently locks onto a clip. It's actually still track based, but is made to lock to a clip that is underneath it. I might be wrong, but do other hosts let you do what you are wanting to do? There might be, but I've never tried.
So really, it won't work the way you are wanting it to right now. Not until something other then track based automation is added, or the current functionality is expanded.
I like the idea though. So maybe it will be something that Mackie will look into.
Brent
So really, it won't work the way you are wanting it to right now. Not until something other then track based automation is added, or the current functionality is expanded.
I like the idea though. So maybe it will be something that Mackie will look into.
Brent
My host is better than your host
-
- KVRist
- Topic Starter
- 457 posts since 14 Aug, 2001
Thanks for the response, Brent. I was hoping that when I created a midi clip on the automation track, that the automation would lock to it, which it does, but only when it is on the same track as the synth or effect that you are wanting to automate.
There are a few hosts that let you do that: Project5 and XT2 do...I think you can do it with FLStudio and Podium too.
There are a few hosts that let you do that: Project5 and XT2 do...I think you can do it with FLStudio and Podium too.
-
- KVRist
- 451 posts since 8 May, 2008
Any progress on this one? Clip-based automation is the deal-breaker for me. And currently only FL Studio does it. Guess what's my go-to DAW: FL Studio. Not to mention the excellent feature of linked clip copies which basically means if you change any one of the linked clips all the other clips will be updated automatically. Basically the way this works in FL Studio is perfect, so I recommend taking a look at the demo for inspiration.
-
lay it prodctions lay it prodctions https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=210819
- KVRian
- 544 posts since 6 Jul, 2009 from Washington D.C
Maybe I am getting this wrong but, you can add any automation from any track to another but remember you are looking at or using the automation of that track you have selected, you can also have as many automation tracks as you like. If you select the small A on the right of all tracks in the edit page select it and you will see all the visual options and you see the + automation button use this to create automation tracks, you can also use a blank track to add automation curves for copy and paste purposes or to see what your last curve is doing. You can not send automation thru a track only midi clips and step clips can send midi thru tracks so if you automate a track and try to send it to another track it won't work that, all track automation must be created on there track first and then you can call it up on any track and if you change the automation it will change the automation to the track it is assigned to not the Track it is visible on.
-
- KVRAF
- 2464 posts since 9 Oct, 2008 from UK
Also, to get the same automation to apply to multiple tracks, you can create a folder track, put the others in it, and apply automation to the folder track.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.
-
- KVRist
- 451 posts since 8 May, 2008
That's all great and well but IMO it's not as convenient as the way FL Studio does it, and believe me I also use track-based automation. Even FL Studio is not perfect in this regard, but it's much closer to perfect.
What I'm talking about is automation clips, where automation lives within a container that can be manipulated in the same way MIDI and audio clips. If MIDI were track-based (no clips, just notes in a track, it would be very hard to re-arrange parts of the song. This is exactly how practically all DAWs but a few handle automation and it's not very good.
What I'm talking about is automation clips, where automation lives within a container that can be manipulated in the same way MIDI and audio clips. If MIDI were track-based (no clips, just notes in a track, it would be very hard to re-arrange parts of the song. This is exactly how practically all DAWs but a few handle automation and it's not very good.