In version 4.1.0 there seems to be an extra 4 bytes representing the length in bytes after the dataset type bytes. This was causing the lib to crash with a segmentation fault. In the Python client from optitrack the length doesn't seem to be used (yet?) so I just skip the bytes here.
That's great - thanks! I personally always switched to the closed-source backend since I didn't have time to investigate the source of the seg fault...
In version 4.1.0 there seems to be an extra 4 bytes representing the length in bytes after the dataset type bytes. This was causing the lib to crash with a segmentation fault. In the Python client from optitrack the length doesn't seem to be used (yet?) so I just skip the bytes here.