Hi,

There is a manual in the download section under MyVSL. Just make sure to set the filter to Software manuals.

If you want to use the plugins from within your DAW, you can purchase them here:
https://www.vsl.co.at/en/Vienna_Software_Package/Vienna_Suite_PRO

Best, Ben

I should have been more clear... I want to use my plugins, not VSL plugins, in VE Pro and see them show up as sends and/or inserts that I can choose in Cubase. So far I have not seen anything show up in my sends in Cubase.

I need specifics... details.... how to.... is there a video tutorial on doing that specifically? I haven't found one.

Thanks.

Thanks.

I found this which explains it as well... https://www.youtube.com/watch?v=NvQzjy0_V_k

My issue now is latency for the send effect. The VE Pro plugin shows some 1000+ latency, but the manual claims zero latency. What am I missing?

Thanks.

I had a thought... I was playing live with the effect send on, which has the latency. If I create an audio track, then assign a send on that audio track to the VE Pro effect, I get no latency.

So I guess I cannot play live with an effect send to VE Pro and get zero (or close) latency for that effect return. Is that correct? If I put the effect on an effects track in Cubase (no VE Pro involved) there is no latency.

Thanks!

The VE Pro instrument has very low latency. The VE Pro send effect has latency when playing live.

For example, I put a reverb with a mix control in VE Pro and connect to it as an effect send, and turn the mix all the way dry, the sound gets doubled. Alternatively, if that reverb is put on a local effects channel there is no doubling, no noticable latency with the effect.

Sending recorded material to the VE Pro effect works normally (latency compensation).

Originally Posted by: Synetos

I created an FX instance, purely for this purpose. I can run with a zero buffer, and still not get any artifacts. 

Thanks Synetos. You are running VE Pro on your Daw computer, I presume?

So if you put a reverb, for example, on VE Pro and connect to it via a send in your DAW, and turn the mix on the reverb all the way dry, do you get no delay to speak of? What does the VE Pro plugin show for the latency in that situation?

Thanks.

Originally Posted by: Synetos

That is correct. I am running VEP on my DAW, local host mode. VST and FX are all on the DAW and accessed via VEP rack instruments. 

Thanks for that Synetos.

What I am trying to do is use VE Pro as an "Effects Server". I have a send effect on my DAW instrument track that uses an effect hosted in VE Pro. Here is what I have discovered so far...

In Cubase I opend the VEP Plugin and look at the latency number. Buffer is set to none in the plugin. If I highlight the VEP audio track in Cubase the plugin shows 192(4.0ms). If I highlight the local VST Instrument track the VEP plugin shows latency of 1088(22.7ms).   Why does the latency change?

Scenarios:

1) Instrument hosted in DAW, Send Effect hosted in VEP - Delay

2) Instrument hosted in VEP, Send Effect hosted in VEP - No Delay (Now I'm thinking this may not be correct)

3) Record a MIDI part and play it back - Same as above for the MIDI data. Bounce it to audio and this audio track with the send to the VEP effect plays with no delay (latency value increases in the VEP plugin).

Now here is the strange bit...

I bounce the VSTi to an audio track which also sends to the VEP hosted effect (same as the VSTi track)..

1) Now, if I select this new audio track and press Play in Cubase it will play with the VEP hosted effect without issue (plugin latency shows 22.7ms). Ok. Fine and dandy.

2) If I select the VEP track which has the VEP plugin on it the latency shows 4.0ms, and I get crackling, no matter how I set the VEP buffers. Setting my audio interface buffer high helps that, but that's beside the point. The strange thing is that if I enable monitoring on the VSTi track from which I bounced to get audio  the crackling goes away, and the plugin still shows latency of 4.0ms. To quote that Kevin Bacon character on Tremors, "I mean just what the hell is going on!!??"

===>  Anyway, what I take away from this is that I cannot resonably use a VEP hosted effect or processing for VST instruments, via sends or inserts in Cubase, without issue unless both the instrument and the processing/effect are hosted in VEP. 

Thoughts?

Thanks!

What is your Audio interface? I am running a complete Waves Soundgrid setup.

If you are using a USB interface, you will have latency from USB alone.

My PC is 6950x running at stock clock speed. I have 128gb ram, but never use more than 50% of it. I have my Windows 10 OS tuned as well. There are links all over the place on how to do that. One thing for sure, disable windows defender. I run ESET, which is much more efficent. 

Drop your DAW buffer to 64, and you will cut your latency. But again, it has much to do with your overall signal/rig chain. 

Ok. More discoveries about the delay on effect plugins. I am finding that there is a delay between different instances, whether using a VE Pro on the DAW computer or on another server.

Here is a short test. I am using Cubase 10.0.4.....

1) Set up an effect in one instance of VE Pro, and connect to it in the DAW as an FX Channel. 

2) Set up an instrument on another instance of the same VE Pro session, and connect to it in the DAW as an instrument track..

3) in the DAW make a send on the instrument track to the effect.

4) Play the instrument. See if there is a delay on the effect (there is for me).

5) Set the instrument track to monitor mode (so it will still sound if another track is selected), and then select the VE Pro effect track, and play the instrument. Did the delay go away?

Please let me know. Thanks very much.

Originally Posted by: Synetos

I already basically did that, and I do not experience the latency you are running into. Your latency is most likely your audio interface. I dont think you can duplicate what I am doing with a USB interface.

That's right, but I do not get latency if I select the track of the VE Pro instance that has the effect on it, so I would like to understand what is going on. Why does the selection of track affect the latency?

It's very odd.