+1000
soundpeaks_net:
In many cases if all you want is a single MIDI driven LFO, you can right click the thing you want to automate in the plugin and assign it a CC, then use the autolfo MIDI insert right away. You won’t really need to bother with the whole Remote Map thing unless you’ve got a plugin that can’t ‘learn’ whatever CC you want the autolfo insert to modulate, or if you’re also wanting to control one of the autolfo parameters with another autolfo track.
I don’t understand what do you mean here.
[snipped image]
[snipped image]
So I still has no idea what to to with AutoLFO and what its purpose. To me it’s useless. I need some automated automation to be able modulate VSTi parameters outside of plugin possibilities.
For example I want modulate pitch of OSC 1 in NI Massive but not with help of Massive’s built in LFO.
But because Cubase automation is not vector, all “parabolas” has sharp edges and sounds wrong. That’s another issue. Meh… Maybe I don’t understand something though.
OK,
If this were using something like HALion that also has a built in duplicate of this plugin inside HALion itself, I’d use the built in effect instead of putting it in a Mixer insert of the DAW. That way you could drive it with any CC you like. If a VSTi plugin has internal effects, those are far easier to automate via MIDI without doing anything fancy.
In this case you are trying to automate a VST insert plugin rather than a VSTi, so there’s no ‘midi’ connection to the plugin…thus, you can’t use the autolfo MIDI insert ‘directly’; however, you can use it indirectly. You’d need to put it on a MIDi track, and drive the VST via Generic Remote map.
In the device setup menu go to Remote Maps and add a new one of type “Generic Controller”. Make sure the plugins you wish to remote control are loaded in your instrument rack or mixer insert(s).
Create a new Generic Remote Device and link controllers to specific items you wish to Automate in the DAW.
Set your Virtual MIDI Port as the input for the Generic Remote Track.
Create an empty MIDI Track, and enable the autolfo MIDI insert and set it up to LFO the CC that you linked up in your Remote Device Map.
Set the input port of the track to whatever fader’s/knobs/etc. you’ll be using.
Set the MIDI output to the same Virtual MIDI port you assigned for the Remote Map, and set the MIDI channel to “Any”.
Arm the track for recording.
Move the slider(s) you’ve assigned to various VST controls, and they should work as long as this MIDI track is armed for recording or monitoring.
In the case of MIDI insert effects, if you want those to become actual MIDI events in a part on your MIDI track, then you’ll need to freeze the track to incorporate inspector/live mod output, or set it up the insert so its effects get recorded on the track during the pass.
You can record your movements in the MIDI track if you like, and they’ll play back. You could also freeze them into actual VST automation lanes later if you like (set the ‘write’ buttons for all the plugins you want to freeze and play the DAW for a pass), or extract the MIDI part to CC lanes in the track and ‘copy paste’ them to VST lanes. If you do ‘freeze’ things, be sure to mute/disconnect/clean out, or get rid of the MIDI track since you don’t really want a doubled set of automation controls.
Hi there,
I appreciate these steps but they do not work
Compared to a well working LFO automation this has about 100 steps to hook up
a) there is a midi delay
Consider wanting to mix a track, and solo it
In cubase this means all your automation turns off when you solo the mixer track
So no it can not be done ( in Cubase ) and the amount of these steps shows only the beginning of a steep hill with plenty issues not even mentioned in the above posts
I tried these methods and
~ Midi delay ( that changes for every track if you change buffers )
Is too much to consider this a working workaround for anyone who is used to
Ableton/Bitwig/FL Studio :
~ Sample accurate LFO Automation of all parameters in any synth
Cubase has none of that
And the workarounds ( as much effort and intelligence they require ) do not work
In real context of making music there is no workaround to make anything similar happen in Cubase that is built in to other Systems
Cubase is great in many ways but behind 20 years in terms of studio tech
Only the devs can help on this one