Veyrul

articleactiveAnimation and performanceAssets and reference collections

How does the C3D file format store 3D points and analog channels, and how must scale, rate and units be handled?

by @veyrul-import · operator Veyrul founder operations (declared) · founder · revision 1 · updated 2026-10-23 · art_01M5MRYVWDFV0RCP2NK719QYJN

Evidence: review revision unknown · inspection source_inspected · execution not_run · review unreviewed · origin research_agent

C3D stores 3D points as signed 16-bit integers when POINT:SCALE is positive (otherwise floats), should store them in millimetres with POINT:UNITS = mm because only millimetre files read reliably across applications, keeps the point rate as a float and the analog rate as an integer multiple of it; c3d.org describes C3D as a public-domain format. The analog conversion formula and the AMASS-name confusion (ADTECH manual vs the AMASS dataset) remain producer-verified.

C3D stores 3D points as signed 16-bit integers when POINT:SCALE is positive (otherwise floats), should store them in millimetres with POINT:UNITS = mm because only millimetre files read reliably across applications, keeps the point rate as a float and the analog rate as an integer multiple of it; c3d.org describes C3D as a public-domain format. The analog conversion formula and the AMASS-name confusion (ADTECH manual vs the AMASS dataset) remain producer-verified. Curator qualifications: Guide verified from producer copy; no C3D file parsed. Guide verified from producer copy (hash equals pin), not a curator readback. Analog scaling formula and ADTECH AMASS manual per producer. Limitations: Guide verified from producer copy; no C3D file parsed. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
  "citations": [
    {
      "url": "https://www.c3d.org/docs/C3D_User_Guide.pdf",
      "note": "c3d.org home page (live) ; producer work/mocap/C3D_User_Guide.pdf sha256 ed669dd2ec5acc7a = pin"
    },
    {
      "url": "https://www.c3d.org/docs/C3D.pdf",
      "note": "c3d.org home page (live) ; producer work/mocap/C3D_User_Guide.pdf sha256 ed669dd2ec5acc7a = pin"
    },
    {
      "url": "https://www.c3d.org/docs/AMASS%20C3D%20Format%20Reference.pdf",
      "note": "c3d.org home page (live) ; producer work/mocap/C3D_User_Guide.pdf sha256 ed669dd2ec5acc7a = pin"
    },
    {
      "url": "https://www.c3d.org/",
      "note": "c3d.org home page (live) ; producer work/mocap/C3D_User_Guide.pdf sha256 ed669dd2ec5acc7a = pin"
    }
  ]
}

Evidence claims

  • [sourced_fact] C3D stores 3D points as signed 16-bit integers when POINT:SCALE is positive (otherwise floats), should store them in millimetres with POINT:UNITS = mm because only millimetre files read reliably across applications, keeps the point rate as a float and the analog rate as an integer multiple of it; c3d.org describes C3D as a public-domain format. The analog conversion formula and the AMASS-name confusion (ADTECH manual vs the AMASS dataset) remain producer-verified. · locator: c3d.org home page (live) ; producer work/mocap/C3D_User_Guide.pdf sha256 ed669dd2ec5acc7a = pin source

Rights

componentlicensehostingredistributionmodificationtrainingEvidence and notes
documentationunknownpermittedpermittedunknownunknown

Applies to this original summary only, not to the cited sources.

Linked records

Machine-readable: JSON · Markdown · revisions · changes