![]() |
#5
|
|||
|
|||
For now, I think I have found the problem! It explains why I had the issue with the motion tracker on or off. The cause was not the tracker itself but the way the function which was writing the output was implemented. It was messing up the sampling, slowing it down, since the output file had to be opened, data saved and written each time.
Now that I am only saving data at each timepoint and writing it only once at the very end, the issue seems to be gone. |
Tags |
motion tracking, polhemus, timing |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Motion Builder + Vizard Objects | ForeverBound | Vizard | 1 | 04-01-2015 03:49 AM |
Unusual tracker sensor setup with Vizard | Zhi | Vizard | 2 | 06-12-2012 09:52 AM |
Vizard tech tip: Using the Python Imaging Library (PIL) | Jeff | Vizard | 0 | 03-23-2009 11:13 AM |
problem in using xsens motion trackers in Vizard | bharatbhushan | Vizard | 3 | 01-26-2009 05:51 PM |
Can Vizard interact with the Arrington eye tracker? | Deltcho | Vizard | 1 | 09-18-2007 02:38 PM |