Socket size in the OptiTrack Data Streaming

NatNet, VRPN, TrackD, and Plugins
Post Reply
Posts: 17
Joined: Sun Jan 05, 2020 8:52 am

Socket size in the OptiTrack Data Streaming

Post by JosephMatan » Wed Jan 29, 2020 8:10 am


In the Data Streaming Pane in the Motive tracker tool, I've notice the <socket size> parameter.
What this parameter means ? (I didn't find in the documentation).
How this parameter influence the data streaming if it's size is too big/small ?


NaturalPoint Employee
NaturalPoint Employee
Posts: 548
Joined: Mon Jan 19, 2015 11:52 am

Re: Socket size in the OptiTrack Data Streaming

Post by steven.andrews » Mon Feb 03, 2020 12:59 pm

Hi Joseph,

This is an advanced property that should typically not be modified.

This setting is specific to Unicast setups. Motive does not limit the throughput rate. However, we do set the socket option to non-blocking. This means when the Socket send buffer does not have enough space for the packet in the send call, send will fail, and the packet will be dropped. This 'appears' to the system as a throughput limit, but is actually frame drop.

Increasing the socket send buffer via SO_SNDBUF resolves this issue, however it is not exactly clear what possible latency artifacts, if any, this induces.

Since 100 Mbps data throughput is larger than most any Motive / NatNet application requires, we will not make this change. Rather, users should adjust their streaming content to not exceed this limit. This is usually done by disabling data that is not typically needed in the stream, such as marker data.

I hope this information helps,
Steven Andrews
OptiTrack | Senior Customer Support Engineer

Post Reply