While I understand that there may be reasons why modulators do not directly work with external instruments, I fail to understand why they don’t work with VSTi plugins controlling external instruments, like I tried e.g. with Soundtowers PlugSE for my Prophet 6.
Any explanation from Steinberg staff?
An external synth is actually an audio channel. Do they work on audio channels? If yes do you have it inserted there? I don’t gave 14 yet so I can’t try
The VST control surface is for writing Midi to a track to be played back triggering the external synth, including automation. At the same time it passes audio to the Prophet 6 or Voyager Bus within my UAD Apollo.
So whenever a midi track for the Prophet or the Moog is finished, I can create an audio track for the instrument and record the midi to it (connected to the Prophet or Voyager audio bus).
As the control surfaces work as VST connections, I would have expected Cubase 14 modulators to work fine with them.
Not sure if I can post link to another forum herebut if it works… this guy seems to have it working with soundtower
Those only seem to work for true registered VST parameters.
It’d be up to the VSTi plugin to register those and convert them to the CCs and/or SYSEX that the hardware synth needs.
In hopes that ‘device panel’ controls register as usable VST parameters in Cubase…I tried it with the old-school ‘device panels’ too. I made a simple panel for CC91 and CC93. While the controls work and I can automate them in Cubase…
The new modulator system isn’t recognizing these ‘MIDI device automation’ tracks/lanes.
For external hardware modulation is typically done with CC events (Expression, Mod Wheel, Etc.), so the older Auto LFO MIDI insert still works and will accomplish the same thing. You can manipulate the settings of this (toggle it on/off, change settings, etc.) with automation lanes.
You can also drag a line down in the inspector that makes it possible to record/freeze what the LFO MIDI insert is doing on a MIDI part. If you want that to live in an automation lane instead, extract the CCs from the MIDI menu.
Until those ‘device panels’ are recognized somehow…For Sysex Modulation, it seems like we’re out of luck unless some third party VSTi ‘host inside a host’ stuff gets into the mix (Maybe your synth comes with a plugin that converts VST paramters to sysex, or stuff where you can build it and link it to a registered VST paramter like…bidule/bluecat/KushView/Ctrlr/etc.)
Yes, I’d like the new Modulation system to work with CCs and MIDI Device Panels too. Hopefully this gets fixed/added soon.
Not sure he really got it working and already asked back.
But thanks for the link!
Hi, I’m writing this here as well (just wrote the same on that other forum): I noticed the modulators don’t work (they don’t even move) if the “Suspend VST3 plug-in processing when no audio is received” option is turned on in Cubase preferences.
This makes sense to me, because we are talking about an editor/controller for a piece of hardware, so there’s no audio involved inside the plugin.
Thanks for the hint!
I have put my question to you up in the other forum to avoid double threads.
