Menu
What's new
By:
Filters

VEPro's Buffer, Cubase and Negative Track Delay

C

chizfreak

New Member
Hello, I was finishing my orchestral template (finally) but I stumbled upon the realization that I actually need to up the VEPro plugin's Buffer Size to not have cracks in the audio when many tracks are playing at the same time. I'm using VEPro 6.5 (latest version before 7).

My question is as follows: I have already finished up setting up all my Negative Track Delays for each track so they sound ''on the grid''. If I change the Buffer of VEPro's plugin, it says it adds a bit more latency (as expected), but does that mean that I also have to add the difference in latency to the Negative Track Delay in all my MIDI tracks? For example, if one more VEPro buffer adds 5ms, does that mean I have to add 5ms to all my current Negative Track Delays? Or is it compensated automatically by the DAW (Cubase 13 in my case)?

Another thing: the latency reported by VEPro in the plug-in UI is added to the latency reported by the DAW itself? Or that's the total final latency because it already took the DAW's latency into account?

Maybe @Ben knows?
Click to read more...
 
Can't remember how VST2 handled these things, but with VST3 the DAW will compensate for the reportet latency, and VEP reports the correct latency based on what you insert back to the DAW. At least VEP7 does, can't remember what 6 did.
 
Ben said:
Can't remember how VST2 handled these things, but with VST3 the DAW will compensate for the reportet latency, and VEP reports the correct latency based on what you insert back to the DAW. At least VEP7 does, can't remember what 6 did.
Click to expand...
I see, thanks @Ben . One thing: I'm a bit confused what you mean with ''latency based on what you insert back to the DAW''.

Let me re-phrase the question (assuming VEPro 7 which is the behavior you are familiar with):
Right now Cubase itself reports an output latency of 5ms. If the VEPro plugin reports 10ms round-trip latency (2 buffers), then is 10ms the FINAL latency to hear the sound after a signal is sent, or do I have to sum the 5ms from Cubase too for a total 15ms?
 
Like most VST3 plugins VEP7 will report its latency to your DAW. If you insert a plugin or virtual instrument into VEP that has delay VEP will also consider this and update the delay reported to your DAW.
 
The negative delay setting in the track inspector is not for reported latency. Its for the various articulations/patches within a vsti/sampler that have for example
a) a script that needs thinking time before it will trigger the sample
b) the sample has extra audio at the beginning that isnt considered part of the down beat
ie to get the full start of a not pick or bowing where the real down beat may be a little later.

These cases arent reported to the DAW and need "manual" adjustment. Hence why we are all calling for track delay in Cubendo expression maps

That my understanding anyway.
 
Latency: the delay between striking a note on your keyboard and your computer registering the MIDI
Negative track delay: compensation for the sample itself. So a sample might have some silence in it for a few miliseconds, or the examples like Bcslaam gave.
 
You must log in or register to reply here.
Top Bottom