(Bad) Datas resampling when export from Motive
Posted: Mon Dec 14, 2015 8:40 am
Dear all,
I experience a real problem when I try to export tracked datas from Motive. Datas are tracked and labelled, and after a right click>export on the take, I create a c3d or csv file. Unfortunately, the exported datas does not correspond with the recording ones.
More exactly, it seems that a resampling is operated by Motive (in my case, resample at 120/100 Hz), even if the export parameters remain correct. Moreover, the exported sampling frequency (specified in c3d header) is not corrected.
For instance, if my recording is 1 second at 120Hz (with V120 trio), in the exported files my datas are sampled at 144hz (an event at frame 60 in motive will appear at frame 72 in the exported file), but the sampling frequency written in the header of .c3d files remain 120Hz. More, I only have 120 sample in the exported file, datas are trunckated. In the export parameters, if I asked for 144 samples, the full recorded second is exported (I have 144 samples at 144Hz). This phenomenon appears with release from 1.7 to 1.9 (I did not test the other one).
Does anyone else experience this problem? Is there a bug to fix here?
Thanks
Etienne
I experience a real problem when I try to export tracked datas from Motive. Datas are tracked and labelled, and after a right click>export on the take, I create a c3d or csv file. Unfortunately, the exported datas does not correspond with the recording ones.
More exactly, it seems that a resampling is operated by Motive (in my case, resample at 120/100 Hz), even if the export parameters remain correct. Moreover, the exported sampling frequency (specified in c3d header) is not corrected.
For instance, if my recording is 1 second at 120Hz (with V120 trio), in the exported files my datas are sampled at 144hz (an event at frame 60 in motive will appear at frame 72 in the exported file), but the sampling frequency written in the header of .c3d files remain 120Hz. More, I only have 120 sample in the exported file, datas are trunckated. In the export parameters, if I asked for 144 samples, the full recorded second is exported (I have 144 samples at 144Hz). This phenomenon appears with release from 1.7 to 1.9 (I did not test the other one).
Does anyone else experience this problem? Is there a bug to fix here?
Thanks
Etienne