Search found 8 matches
- Thu Jan 25, 2018 1:52 am
- Forum: OptiTrack Data Streaming
- Topic: Timestamps in SDK 3.0
- Replies: 5
- Views: 5229
Re: Timestamps in SDK 3.0
The high resolution timestamps are available through direct depacketization, which is the process any Linux application would need to follow in order to receive the tracking data. The PacketClient and PythonClient both demonstrate the depacketization process. Specifically, you can find information ...
- Wed Jan 24, 2018 1:55 am
- Forum: OptiTrack Data Streaming
- Topic: Timestamps in SDK 3.0
- Replies: 5
- Views: 5229
Re: Timestamps in SDK 3.0
Because the goal is to calculate things like "Software Latency" on a per frame basis, it does not really matter when the timer (clock ticks) started, only the difference between the values. I don't fully agree on this. For example, how can I calculate what you define as "Client Laten...
- Tue Jan 23, 2018 5:06 am
- Forum: OptiTrack Data Streaming
- Topic: Timestamps in SDK 3.0
- Replies: 5
- Views: 5229
Timestamps in SDK 3.0
Hello, from the documentation, it is a little unclear which is the "reference" (time 0) for the timestamp values introduced with the last version of the streaming engine (NatNet 3.0), more specifically * CameraMidExposureTimestamp * CameraDataReceivedTimestamp * TransmitTimestamp While for...
- Mon Jan 22, 2018 3:45 am
- Forum: Motive
- Topic: SDK 3.0 mocap frame data format
- Replies: 2
- Views: 3322
Re: SDK 3.0 mocap frame data format
I think I found the problem, line 116-117 in NatNetClinet.py :
by removing this the code seems to work. Can you confirm that the mentioned padding block has been removed ?
Code: Select all
# Skip padding inserted by the server
offset += 4
- Thu Jan 18, 2018 5:19 am
- Forum: Motive
- Topic: SDK 3.0 mocap frame data format
- Replies: 2
- Views: 3322
SDK 3.0 mocap frame data format
Hello, we recently switched to motive 2.0 and thus SDK 3.0. Trying to run the python client in the sample folder of the SDK, however, I get strange results: * parsing error leading to application crash: File "/home/dario/Downloads/NatNetSDK/Samples/PythonClient/NatNetClient.py", line 233, ...
- Fri Nov 10, 2017 9:30 am
- Forum: Motive
- Topic: Rigid body marker labels
- Replies: 1
- Views: 1837
Rigid body marker labels
Hello, The question could sound extremely naive, but I really didn't find any information about this ... Is it possible to manually change the label for markers constituting a rigid body ? By default, the labels for "RigidBody1" will be "RigidBody1:Marker0", "RigidBody1:Mark...
- Wed Aug 16, 2017 8:45 am
- Forum: OptiTrack Data Streaming
- Topic: Timecode Decoding on Linux
- Replies: 1
- Views: 2606
Timecode Decoding on Linux
Hello, I am writing a OptiTrack client application on Ubuntu linux using python. I would need to decode the timecode stamps provided within the streamed Mocap frame. It seems to me that the SDK package provides only windows libraries (regardless the fact that they are for c++). Is there any tool tha...
- Tue Aug 08, 2017 10:40 am
- Forum: OptiTrack Data Streaming
- Topic: Skeleton bone position
- Replies: 1
- Views: 2448
Skeleton bone position
In the data streamed by Motive, the position of the bone to which exact point makes reference ? The geometric centre ? one of the extremities ? It seems like a stupid question, but I could not find an answer to this question in the documentation. For generic rigid bodies the position makes reference...