Audible latency with VE pro audio input

[[email protected]]

Hey guys, I'm sending some tracks from PT12 into VEP and bringing them back into PT.

There's audible latency in the tracks coming back into PT. I have ADC on in PT, but still latency.

I tried bypassing all plugs in VEP so that the audio goes through VEP and comes back into PT12 untouched.

Any ideas?

[Tim Ripley]

Is this a new problem? If yes, what changed? What is your buffer setting? How are you bringing VE back into Pro Tools?

[MusoPro]

Check the buffer settings on the plugin on your insert on your PT track.
Should be set to none(zero)

Best
Mitch

[[email protected]]

Bring it back into PT via aux track with its input set to (plugin) in 5/6.
VE buffer in PT is set to 2 buffers. should that be set to zero? That usually causes VE to click and pop. Could I set negative compensation to that track?

[StudioRhythm]

I'm new to VE Pro myself but ran into the same delay compensation issues when testing it out. It turns out that when you increase the number of buffers on the VE Pro plugin, the audio will actually come back early by the amount reported in that window (it gives a readout of how many samples it's adding in that window somewhere, I'm not in front of my studio computer at the moment.) So I guess it must be over-reporting the actual delay to the delay compensation engine.

The easy fix for this is to put a Time Adjuster plugin on the track that your VE Pro audio comes in on, and set that to the number of samples that you're seeing on the VE Pro Plugin for that instance. If you're routing audio into VE Pro and then back out, you can test it with a simple setup by bypassing your plugins in VE Pro, reversing phase in the Time Adjuster plugin and adjusting levels as needed to cancel out the original signal. That's working well for me here, although it'd be nice if it were done automatically so you don't have to change your value if you change buffer sizes...etc.

[vudoo]

Originally Posted by [email protected]

Hey guys, I'm sending some tracks from PT12 into VEP and bringing them back into PT.

There's audible latency in the tracks coming back into PT. I have ADC on in PT, but still latency.

I tried bypassing all plugs in VEP so that the audio goes through VEP and comes back into PT12 untouched.

Any ideas?

The buffer multiplier setting on the VEP plug ins inside PT adds to your host's delay. So if PT buffer is set to 128 samples and VEP's buffer multiplier set to 1x, you have 256 ms latency total, if it's set to 2x, you have 384 samples....etc

Technically you can set it to 0 but most likely you will encounter CPU overload (pops and crackles) even with a super powerful computer.

Finding the best setting on your DAW and slave computers will depend on many factors such as CPU, ram, number patches you want on line at all time on the slave (VEP).

Are your VEP local or over ethernet ? What's your CPU and ram ?

For a start, try setting your DAW's buffer to 128 samples and the VEP's buffer multiplier to 2xbuffer. Start one instance of VEP server 64 bit and instantiate Kontakt, Play or any synth plug-ins, return 16 outputs from VEP back into PT.

[[email protected]]

Not really working for me...
I'm sending a tone into VE, then bringing it back into PT. Phase flipped on return. (also monitoring original signal) Seems that the return needs to be negatively compensated. But still won't cancel out completely. Anyone??

Originally Posted by StudioRhythm

I'm new to VE Pro myself but ran into the same delay compensation issues when testing it out. It turns out that when you increase the number of buffers on the VE Pro plugin, the audio will actually come back early by the amount reported in that window (it gives a readout of how many samples it's adding in that window somewhere, I'm not in front of my studio computer at the moment.) So I guess it must be over-reporting the actual delay to the delay compensation engine.

The easy fix for this is to put a Time Adjuster plugin on the track that your VE Pro audio comes in on, and set that to the number of samples that you're seeing on the VE Pro Plugin for that instance. If you're routing audio into VE Pro and then back out, you can test it with a simple setup by bypassing your plugins in VE Pro, reversing phase in the Time Adjuster plugin and adjusting levels as needed to cancel out the original signal. That's working well for me here, although it'd be nice if it were done automatically so you don't have to change your value if you change buffer sizes...etc.

[StudioRhythm]

Hmm, delay compensation seems to be strange with the VE Pro and Pro Tools combination....

The way I'm doing it works when you're sending and returning audio on the same aux track in Pro Tools -- i.e. placing the VE Pro Audio Input plugin first on your aux track, followed by the VE Pro plugin returning audio from Outputs 1-2 for that instance (so it's acting essentially like any other native plugin on an aux track would). If you put a TimeAdjuster after that set to the number of samples reported by the plugin it generally seems to work correctly and null outs 100%. (To make this work I'm using a separate instance of VE Pro for each send/return, since there's no "VE Pro Audio Output" plugin.)

I'm setting up a new mix template, not using any VIs -- I'm running my mix bus processing and a bunch of send/return FX through VE Pro. This method seems to work correctly so far for what I'm using it for.

I haven't figured out how to get the delay compensation to work correctly if you're not doing routing like above though. I just did a quick test, and when I send audio to VE Pro and return on a separate aux track, I'm getting the VE Pro audio coming in late like you.

[[email protected]]

That's why it wasn't working for me. I was using a VE audio input return to PT. (track input-->plugin-->VE 5/6) I'll give this a try...

Originally Posted by StudioRhythm

Hmm, delay compensation seems to be strange with the VE Pro and Pro Tools combination....

The way I'm doing it works when you're sending and returning audio on the same aux track in Pro Tools -- i.e. placing the VE Pro Audio Input plugin first on your aux track, followed by the VE Pro plugin returning audio from Outputs 1-2 for that instance (so it's acting essentially like any other native plugin on an aux track would). If you put a TimeAdjuster after that set to the number of samples reported by the plugin it generally seems to work correctly and null outs 100%. (To make this work I'm using a separate instance of VE Pro for each send/return, since there's no "VE Pro Audio Output" plugin.)

I'm setting up a new mix template, not using any VIs -- I'm running my mix bus processing and a bunch of send/return FX through VE Pro. This method seems to work correctly so far for what I'm using it for.

I haven't figured out how to get the delay compensation to work correctly if you're not doing routing like above though. I just did a quick test, and when I send audio to VE Pro and return on a separate aux track, I'm getting the VE Pro audio coming in late like you.

[[email protected]]

Originally Posted by StudioRhythm

Hmm, delay compensation seems to be strange with the VE Pro and Pro Tools combination....

The way I'm doing it works when you're sending and returning audio on the same aux track in Pro Tools -- i.e. placing the VE Pro Audio Input plugin first on your aux track, followed by the VE Pro plugin returning audio from Outputs 1-2 for that instance (so it's acting essentially like any other native plugin on an aux track would). If you put a TimeAdjuster after that set to the number of samples reported by the plugin it generally seems to work correctly and null outs 100%. (To make this work I'm using a separate instance of VE Pro for each send/return, since there's no "VE Pro Audio Output" plugin.)

I'm setting up a new mix template, not using any VIs -- I'm running my mix bus processing and a bunch of send/return FX through VE Pro. This method seems to work correctly so far for what I'm using it for.

I haven't figured out how to get the delay compensation to work correctly if you're not doing routing like above though. I just did a quick test, and when I send audio to VE Pro and return on a separate aux track, I'm getting the VE Pro audio coming in late like you.

I'm trying your method and am a bit confused- (could you please clarify)
Have to first create a VE server in order to have the input into VE created and put on the Aux... SO then when I want to put a VE server AFTER that, that's a new server, not the one I was sending the input to... Explain?