Hi! I'm running VE Pro on my main machine locally (on the same machine is my daw), which is the following: DEll t5500 dual quadcore Xeon system at 2.66ghz, 24gb of ram, running W7 x64 and using Nuendo v5 32 bit. I'm currently using VE Pro to instance 64 bit versions of Kontakt 4 and be able to use them from Nuendo 32 bit. It's all connecting fine and I have 3 instances running of VE Pro. On all interfaces I've set buffer size to none. Unfortunately, I'm still getting significant latency despite my audio card's buffer (RME FF800) being set to 128. I would expect with buffer size set to none on all VE PRo plug-ins for there to be NO latency. But it feels like I'm getting 256 samples of latency if not more; there is a significant time between hitting a note and hearing a sound (when playing live). In addition, changing the buffer sizes on the VE Pro plug-ins seems to make no difference; I can't hear a difference between 2 buffers or zero... Is this a bug? I'm using the latest VE Pro version (6844) Cheers, Joe
-
[SOLVED] VE Pro local - buffer size has no effect?
-
Still bumping this, as I'm sure something very peculiar is going. Loaded one of my old sessions with 3 instances of VE Pro; 2 connecting locally and one another slave pc over the network. Even with a 2 buffer setting their latencies were incredibly low, and pretty much instantaneous... Any ideas what this might be? Cheers, Joe
-
thanks for your reply. Yes, I'm fully aware how latency compensation works. My point is that I have two different nuendo sessions (templates); a brand new one I just created, with around 3 instances of VE PRo running locally, and an old session that had 2 running locally and one over the network from another PC. In the new template the latency of vsti's running in VE Pro is significantly higher than in the old template. In the old template everything seemingly works the way it should. In the new one, some VSTi's running in VE PRo have incredible high latencies/response times; after checking again I would say much more than the reported buffer size; more like half a second. I'll recheck my session but so far the only main difference is that I'm using more audio channels from VE PRO (pretty much all 24 channels per VE PRO vst instance) and that I'm only running local servers. With buffer sizes set to zero, I would expect no latency whatsoever; but reaction times on some synths is incredibly slow, so something fishy is going on. Just a few quick questions: -does the number of audio channels used per VE PRo plug-in in the Daw affect latency? -is there any way to see the latency in the plug-in? -any reason why I would have such high latency? Many thanks, Joe
-
Joe, is it possible to try running the same template in both different setups, so that you know that there is no errant reverb plug (for example) somewhere in one of them?
I've always run VE pro locally, and am experiencing very little latency. Obviously your firewire (I think you have firewire) will add some latency above the reported buffer, but if that is a constant, it shouldn't be causing the problem you report.
Another thing to try is to switch latency compensation off and then on again. Sometimes Nuendo remembers something that was previously inserted and then removed.
-
so to recap, yes, I'm aware that it doesn't affect playback. However, there seems to be a huge difference in real-time playing of notes between the two sessions; in the old one it is pretty much instantaneous (i.e can barely 'feel' the latency when performing), in the other the amount of latency makes the vsti's unplayable. Which seems weird, as on the new session I'm only using a local Ve PRo server with buffersize set to 'none', which would make me think latency should be incredibly low, right? Cheers, Joe
-
Thanks for your response DG, I'll give that a go. There more I think about it, the surer I am something fishy is going on, as the amount of latency doesn't make any sense.
Firewire adds a small amount of latency, but with my new machine I've been running a buffer size of 128 on the RME's, so even double the buffer size on VE PRo seems to add little latency, timing wise.
The difference between the old and new session is large enough to cause me to think some plug-in somewhere is adding it!
CHeers,
Joris
-
*SOLVED*!!!!
Sorry for the false alarm, it has nothing to do with VE PRO! (I feel very silly now.....)
Turned out a few of the VE Pro channels had an EQ on them that was switched to 'Iinear phase', introducing at least 4096 samples of latency.
After turning those off timing is back to normal. Thank you for your patience, and glad to know it was pure operator error and had nothing to do with VE Pro.[:$]
Cheers,
Joe
