Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Localhost vs Slave latency
Last post Thu, Dec 26 2019 by nspaas_13658, 5 replies.
Options
Go to last post
Posted on Fri, Oct 27 2017 18:50
by Synetos
Joined on Mon, Jun 22 2015, USA, Posts 121

Can anyone tell me if the math is correct? What is the "real" latency? How can I test it?

The reason I am asking is two fold. One, I want to know if those are real latency numbers, or just a formula? It seems even when they are quite high, I don't sense the delay when playing a VST. Secondly, my Slave crackles and pops like crazy and my localhost just chugs along. CPU, RAM, and NIC all have tons of capacity on both systems based on Task manager/Performance Monitor.

First, here is my config: 

RayDat 48k sample rate buffer set to 64. 

The RayDAT latency in Cubase reads 1.375ms for Input and 2.063ms for Output

Rack instrument VEPro with two buffers of latency connected to instance on local host. It reads 128(2.7ms)

Rack instrument VEPro with two buffers of latency connected to instance on slave PC. It reads 192(4.0ms)

EDIT: Actually...what I am getting on the slave is a stutter. Not the normal clicks and pops of a drained audio buffer. Performance monitor shows notches on the network inferface, every time this happens. It is random, but at least once evey 10-20 seconds.  Machines are connected via cat5 into a switch. 

Posted on Thu, Nov 09 2017 16:06
by Synetos
Joined on Mon, Jun 22 2015, USA, Posts 121

UPDATE: While I did solve the problem with the connection (network issue), I am still interested in how one determines the real latency of VEP? 

Posted on Thu, Dec 26 2019 19:44
by nspaas_13658
Joined on Wed, Apr 13 2005, Posts 7

Slightly off topic, but I am curious as to how you solved your network problem, as I have a similar issue.

I upgraded a slave from win7 to win10 and am experiencing symptoms as you describe.

I would appreciate your experience and solution.

Thanks.

Posted on Thu, Dec 26 2019 19:57
by Synetos
Joined on Mon, Jun 22 2015, USA, Posts 121

I think this issue was a bad switch, or outdated NIC driver. Too far back for me to recall.

Check out what your Network card is, go to manufacture and get the latest driver. Same for all your hardware. I dont rely on Windows 10 to have it right. In my case, I went straight to Intel.

Posted on Thu, Dec 26 2019 20:26
by nspaas_13658
Joined on Wed, Apr 13 2005, Posts 7

Thank you for the reply.  

Windows 10 does indeed report latest drivers.  (Intel NICs).  I will follow your advice and go straight to intel.

Thanks again.

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.