Quick start

The whole flow in one pass: sign in → create a project → upload → Data → Run → After → export. If you only read one thing: you must create a project before you can upload (step 2).

The one-line mental model

Post cleans motion-capture takes. Confidence measures how cleanly we can fix a take, not how broken it is. Your raw capture is never modified — every cleanup is a new Clean v1, v2, ….

1. Sign in

Open the site and choose Continue with Google or enter your work email. Your first sign-in creates your own private workspace. You land on Projects & Data — the Data screen.

2. Create a project — do this first

Uploads attach to a project, so a new workspace needs one before anything can come in.

• Click the ＋ next to Projects in the left rail (or the prompt in the upload dialog) and name it.
• Select it in the left rail.

TIP

If you open Upload with no project yet, the upload button stays inactive until a project exists. Create one first.

3. Upload takes

Click Upload (top right). Drop files onto the dashed area, drop a whole shoot-day folder, or click to pick files. Supported: FBX · C3D · BVH · TRC · TAK · VDF — format and tags are detected for you. Confirm the project and shoot day, then Upload N files.

Large multi-take uploads run one after another with a per-file progress bar; you can leave the dialog open. See Supported formats for what comes back out.

4. Data — takes diagnose themselves

Each take is diagnosed automatically. Watch the take row: Diagnosing…, then two things.

A status, which is about how cleanly Post expects to fix it: Clean, High confidence, Low confidence, or Recommended manual cleanup.

A Cleanup forecast, which is about how much work it is: Clean, Light cleanup, Significant effort or Hard. Above the list, one line per shoot day — Shoot day · Aug 21 · 80% clean · 10% light · 10% hard. This is what you plan a day from. See Cleanup forecast.

The right panel shows the take's stats and its version stack (Raw capture → Clean vN). Takes are grouped by shoot day and sorted worst-first.

TIP

A take that cannot be cleaned says why in plain words rather than offering a retry that would fail the same way. A take whose diagnosis failed has a Re-diagnose button.

5. Before — the predicted map

Open Before to see what was found before anything is changed: a 3D viewer and heat timeline, per-frame flagged regions, and a triage list split into scheduled versus clean. Three views — Regions, Curves, Takes. Nothing is modified here.

6. Run — Auto or Assisted, with the Cleanup Plan

Open Run. Two modes:

• Auto — cleans every scheduled take unattended, with the standard fix order.
• Assisted — tune it per take: frame range, which error types to fix, which markers, and solve constraints. Run-wide, Cut and refill jitter (on by default); per take, Jitter sensitivity. You can also tick already-cleaned takes to re-clean.

In Assisted a third column appears: the Cleanup Plan for the take you have selected — what Post will do to it, in order, with what each step is waiting on. Change a file or an option and the plan is worked out again. You can launch without waiting for it. See The Cleanup Plan.

Launch with Clean N files. Progress is live and the plan lights up as steps finish; you can leave the screen.

7. After — the measured result

Open After:

• A verdict on the clean — Verified, Assessed with exclusions, Limited assessment, Not repairable or Not assessed — with the measured drivers underneath it. A result that could not be measured is never given a score to look like one.
• A before → after movement per take, and a Raw / Clean vN / Overlay viewer toggle.
• A note naming any frames the cleanup deliberately did not touch, and why re-cleaning will not fill them. See Holes left open.
• The Cleanup Plan, filled in with what each step actually did.
• What the AI changed · per region — one card per region with what changed, the model that produced it, a confidence, and Revert. A reverted region is excluded from the Clean version.

8. Export

From a cleaned take, choose Export:

• Format: Keep original — including TAK and VDF. Convert · soon is not wired yet.
• Contents: Cleaned only or Cleaned + original.
• Destination: Download · Shared storage · Pipeline.

If anything about the delivered file differs from what you uploaded, the dialog says what and why. See the export note.

Tips

• Start with one small take to see the whole loop, then try a large multi-performer one.
• Re-cleaning the same raw with the same options won't change the result — cleanup is deterministic. Change the frame range or the options, or upload a new raw.
• Changing Jitter sensitivity re-diagnoses the take first, because findings from two bands are not comparable.

Known limitations

• Convert-format export isn't wired yet — use Keep original.
• A solved-skeleton FBX is rebuilt on export rather than patched into your original file: a solve goes stale the moment markers move. Marker-based FBX, C3D, TAK and VDF are patched.
• BVH carries a solved skeleton and no marker cloud, so there is no marker cleanup to plan for it.

What to do next

Read how Post cleans a take — four short pages covering the plan, the forecast, jitter, and fills.

Ask us

Something looks wrong on a take? Write to support@kapnetix.ai and send the take id, or the take's name and the project it sits in.