Why Twice the Buffer Size?

[Horst Sergio]

The receptor seems like a gift from the heavens in my quest for low-latency, live signal-processing (with sequencing + automation).
Alas, the minimum buffer setting of twice that of the host machine shatters my hopes of breaking the latency barrier once again. (My goal is 10ms or less total).

Can you explain why I cannot go with a lower setting when using the unit via UniWire with a host machine?

Thanks,

H.S.

[Horst Sergio]

Does nobody know the answer to this?

The minimum buffer setting when using the Receptor via Uniwire with a host computer is twice that of the host's plugin-buffer. Why??

[looneytunes]

Hi Horst,

I thought I knew the answer, but then double checked with the developers. Here is a quote of the explanation:

One buffer allows UniWire to act as an accelerator. Without this buffer your DAW would have to wait for Receptor to process the current buffer before playing it. Your CPU load would not be reduced.

The second buffer is to cover the overhead of the network transmission. Otherwise, the network overhead would limit how much of Receptor's CPU you can use. If the network took 10% of a buffer, then you could only use 90% of Receptor's CPU without dropping buffers.

The reason that the latency is in whole buffers is that you have to have entire buffers back to play them.

I hope this explanation gets added to the Uniwire supplement, as it does justify the latency Receptor adds.

Regards,
Kevin L