Hi, Patanjali. I’ve been researching this for a while.
VEP Pro will not work for FX, even with its Audio Insert, due to a known issue with how it returns the audio back from the slave.
You will end up with the FX out of sync.
It works fine with Virtual Instruments (that don’t use the VEP Audio Insert), of course.
It can work acceptably with simple FX use-cases that can work asynchronously, like basic reverb.
The issue is that the host DAW can’t do its PDC on the channel, because the VEP Audio Insert does not return on the channel, it returns somewhere else. That is to say, the PDC the DAW does do, ends up being wrong in most cases.
Very simple setups, without cascading busses and with other inserts in the project that are either zero latency or where the latency masks the issue, may not initially show the issue.
But for any kind of a serious project, the issue will eventually present itself.
There is no workaround.
VSL has admitted to the limitation and had revealed that they are working on a special “Remote FX Rack” product to address the need. No date was given (and this was about a year ago).
Here’s my saga. Way too TL;DR, but it does eventually have an official response from VSL finally ending the long debate I had with someone claiming it would work (but just not understanding why it wouldn’t).
The other solution is Reaper’s “ReaMote.”
It’s tricky. You have to use its ASIO component (ReaRoute) to expose virtual audio cables, use Cubase’s External FX insert, run Reaper on the same machine and then use its Reamote to another machine running the Reamote slave.
It works. but is not optimized and you’ll only get about 4 channels over a non aggregated gigabit Ethernet. Depending on what you’re doing it may be enough.
It also has latency / sync issues that are a huge PITA, but can kinda be worked around by inserting a bunch of Voxengo sound delay plugins and fiddling with the values. It’s a nightmare though and changes each time you relaunch everything.
Then there’s Audiante Via.
But it’s not out quite yet, but will be later this year. It will create a virual audio interface between networked computers. In theory, you could then use the External FX insert. Or use VST System Link (built into Cubase) to sync with another instance of Cubase on the slave. Use Dropbox to sync the project files.
That’s what I’m waiting for.
The other solution is to use VST System Link with a MADI interface or the new MOTU AVB networking interfaces (which are about half the cost), but it’s still not cheap.
Here are some audio interfaces to drool over that would work. This is the real solution if money were not object, as it’s less fiddly.
(I’ll save you the trouble of thinking the new MOTU UltraLite AVB product, which is almost affordable, can do 128 channels out and 128 channels in, like its big brothers, it can’t. They artificially hobbled it to 8 channels out and 16 channels in. What a shame.)
The RME RayDAT may be the way I end up going. It’s bullet proof. Not cheap, but cheaper than its closest hardware alternative.
I already have two Focusrite Saffire Pro 40’s that can be joined in dual mode and therefore have 16 optical channels. So I’d only have to get the RayDAT on another machine to matrix 8 stereo pairs between them.