While we wait for the new feature…I’ve just built a macro to clone a new copy of the selected track(s) and mute the old one(s). Another macro launches a Project Logic Editor that stashes selected tracks into a ‘versions’ folder out of the way.
It’s also possible to automate the entire DAW and all of his hosted plugins via MIDI tracks and MIDI Events (MIDI Track --> virtual loop-back port --> Generic Remote Device). One cool thing about this approach is that one could set a section of music on loop, hit play, and automatically do a different version each time it loops. (Info on Virtual Ports for PC, and for Mac)
Once things are done freeze the take into real VST/i automation lanes. Some can actually be copied and pasted directly once extracted to a track’s CC automation lanes…for those that can’t, just toggle write on all the plugins automation lanes and play a pass.
Why bother with such a 1990s style work-around? Because MIDI recording in Cubase has quite a few options on how it handles recording cycles (Start a new track, or a new version, or a new part on the same track, or merged in the same part, or overwriting the part, etc.). You’ve also got ‘introspective’ MIDI recording as well, so even if you didn’t have an automation track armed for recording at the time you did something interesting, you can paste the MIDI buffer contents right into a track and save that impromptu inspiration. MIDI recording also gives more flexibility on manipulating punch points on the fly (which can also be automated via the Generic Remote Maps).
Another advantage to keeping automation in MIDI parts is that the MIDI Logic Editors really come in handy! Drawing in new stuff at your chosen resolution, and editing in general is a good deal more intuitive and powerful in the Key Editor than anything we get in the VST automation lanes.
One can also take advantage of various MIDI insert plugins such as Auto LFO.