fileformats:c3d
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungNächste ÜberarbeitungBeide Seiten der Revision | ||
fileformats:c3d [2018/01/04 14:29] – oliver | fileformats:c3d [2018/01/04 14:37] – oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
+ | ===== Vicon c3d file format ===== | ||
+ | |||
+ | **Mime Type:** application/ | ||
+ | |||
+ | **File Suffix:** .c3d | ||
+ | |||
The C3D file format ([[http:// | The C3D file format ([[http:// | ||
The usage of the c3d format is not recommended due to its restrictions and the manifold of unspecified workarounds to overcome them. | The usage of the c3d format is not recommended due to its restrictions and the manifold of unspecified workarounds to overcome them. | ||
- | Some examples: | + | **Some examples:** |
* Vicon stores Events in a prprietary way in the parameter section. But this allows to store only 127/255 events. | * Vicon stores Events in a prprietary way in the parameter section. But this allows to store only 127/255 events. | ||
* The count of timeseries is saved in one byte. This results that it also needs a workaround if you want to save more e.g as the CLEVE model do. To mange this additional parameters are defined: DESCRIPTIONS2, | * The count of timeseries is saved in one byte. This results that it also needs a workaround if you want to save more e.g as the CLEVE model do. To mange this additional parameters are defined: DESCRIPTIONS2, | ||
* The length of the timeseries is restricted due to the fact that it is saved as INT16 or UINT16 | * The length of the timeseries is restricted due to the fact that it is saved as INT16 or UINT16 |
fileformats/c3d.txt · Zuletzt geändert: 2018/01/04 14:59 von oliver