Yes, that's as I explained pretty much how it works in Sonar, and it seems very effective.Lunch Money wrote:The ONLY way to make clip-based automation work in a non-broken way is to have each instance of the plug-in associate with each clip. As soon as a clip overlaps, an identical copy is made on each of the overlappers. Move to another track? No problem, Tracktion makes a copy of each of the plug-ins on the track so that there are 2 distinct sets that can be automated.
This is perhaps how Mackie could implement the more flexible freeze that has been mooted. Basically, if there was a "Clip Freeze" function which released filters on clips, it would then be possible to move, copy, trim and paste those clips at will. Also, this would not affect Track based filters, so it would still be possible to use volume and pan filters to mix tracks, and full Track Automation for any filters dropped onto tracks (although filters placed in clip bins would of course be inaccessible when frozen). I think it could be a powerful way to implement both features in one integrated wayIt's the only reasonable solution, and it's a CPU pig. I'd be willing to put up with it if it meant keeping everything in its proper place, and intuitive. But I suspect that people are going to go, "Oh, MAN... that's a LOT of CPU consumption."
Yes, not sure how that would fit into this approach...Then there's the problem of moving clips that feed racks... clips that feed submixes...