Skip to content

Quick start ​

This page walks the whole flow in one pass: sign in → create a project → upload → Data → Diagnose → Clean → Review → export. If you only read one thing, read this: you must create a project before you can upload (step 2).

The one-line mental model ​

Post cleans motion-capture takes. A take is one recorded performance: one file, one shot, one or more performers. 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 version, named Clean v1, then Clean v2, and so on.

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, which is the Data screen.

2. Create a project: do this first ​

A project is the folder your takes live in. 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. A shoot day is the group of takes you captured on one day. The supported formats are FBX, C3D, BVH, TRC, TAK and VDF, and the format and the tags are detected for you. Confirm the project, then click Upload N files. New takes are grouped by the day they are uploaded, and you can move a take to another shoot day from the Projects screen.

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

4. Data: takes diagnose themselves ​

Each take is diagnosed automatically. A diagnosis is a read-only pass over the file: Post finds the gaps, swaps, merges and jitter in it, and changes nothing. Watch the take row. It shows Diagnosing…, and then it shows two things.

A quality badge, which is about how cleanly Post expects to fix the take. It is one of OK, Review or Manual, with a score from 1 to 99, and it says predicted until the take is cleaned. Beside it, a plain chip says where the take is, such as Raw or Cleaned v2.

A Cleanup forecast, which is about how much work the take is. It is one of four words, called bands: OK, Review (predicted), Significant effort or Manual. A take that has not been cleaned yet shows only its predicted quality badge on its row, because the two would use the same words for different things. The forecast is on the row of a cleaned take, and above the list you get one line per shoot day, such as Shoot day · Aug 21 · 80% OK · 10% Review (predicted) · 10% Manual. That line 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.

Each take row ends with an actions menu, the ⋯ button. It holds Clean again (or Clean for a take that has no clean version yet), Diagnose again and Delete. An action that cannot be used right now stays in the menu with a sentence saying why. Delete asks you to confirm in a dialog that names the take, and removes the raw file and every clean version of it. A deleted take cannot be restored.

Archived projects are listed apart, under Archived at the foot of the project list, with how many there are. Select the heading to show them.

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 Diagnose again button in its panel, under the reason the diagnosis failed. Every take has that one diagnose action, in its panel and in its actions menu. It reads Diagnose while the take has no diagnosis yet. To read what a diagnosis found, select the take and open the Diagnose screen.

5. Diagnose: the predicted map ​

Open Diagnose to see what was found before anything is changed. You get a 3D viewer and a heat timeline, the regions the diagnosis found, and a triage list split into the takes To clean and the takes that are good as captured. A region is one span of frames on one marker. There are three views to choose from: Regions, Curves and Takes. Nothing is modified on this screen.

6. Clean: Auto or Assisted, with the Cleanup Plan ​

Open Clean. There are two modes.

  • Auto cleans every take in To clean unattended, with the standard fix order.
  • Assisted lets you tune the work per take. You can set the frame range, which error types to fix and which markers to touch. Cut and refill jitter applies to the whole run and is on by default. Marker names in the output also applies to the whole run. It is set to Keep as in the file by default, and you can choose Add the performer name instead. See Performer names on marker labels. Jitter sensitivity, which decides how small a jitter has to be before Post leaves it alone, is set per take. You can also tick already-cleaned takes to re-clean them.

Post sets the error types for every ticked take from that take's own diagnosis, whether or not you open its options. A type the diagnosis found is switched on. A type it did not find is switched off and greyed out, because there is nothing for it to repair. Only you can switch off a type that was found. Above the switches, the options for a take say in one sentence what the run will repair in it. Clean N files waits until Post has read the diagnosis of every ticked take, so each take always launches with the options its panel shows.

In Assisted a third column appears. It is the Cleanup Plan for the take you have selected: the steps Post will take on 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, and you can leave the screen while it runs.

7. Review: the measured result ​

Open Review to read the finished cleanup. It gives you:

  • A verdict at the top of the panel on the right. Its first line says how many regions need your eyes, for example Needs your eyes · 12 regions, or Verified · nothing left to check when the clean was measured and nothing is left open, or Verified where measured · review the rest by eye when only part of it was measured, including a take assessed with exclusions. The line under it names the measurement, which is one of 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. The take's quality badge, such as Review 72 (measured), sits beside the verdict and matches the badge in the queue on the left.
  • An Audit block with the region counts, and a Details disclosure with the rest of what the cleanup reported.
  • For workspace owners and admins, a Details for support disclosure with the repair models, the cleaning worker build, the planner's own notes and the full list of steps. These are the details Kapnetix support asks for when you report a problem.
  • A before → after movement per take, and a Raw / Clean vN / Overlay viewer toggle. Raw is the file you uploaded, unchanged.
  • 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, with the outcome of the run for each performer.
  • A section headed What the AI changed · per region, with one card per region in three groups. Needs your eyes comes first, and each card in it ends with one line saying what to do. Where the card has one specific thing to look for, the line names it, such as Look for a kink where the repair joins the captured frames. Otherwise it reads Check this region by eye. A card whose repair was not used reads Not repaired. The original frames were kept. Repaired and verified is folded behind one line per error type, such as 120 gaps repaired · lowest score 33; choose Show all to see the cards. Left as captured comes last, and identical cards there are folded into one row, such as 50 one-frame jitter spans left as captured. By frame and By confidence order the cards inside each group. A card names the kind of repair in words, such as Solve · Gap fill or Rigid body, gives a confidence figure where one was measured, and has a Revert button. A reverted region is excluded from the Clean version and joins the regions that need eyes.
  • Tour regions that need eyes, under the queue, which steps through the needs-eyes group one region at a time: Region 3 of 12, with Back, Next and Stop. The [ and ] keys step the tour too, and Esc stops it.

8. Export ​

From a cleaned take, choose Export:

  • Format: choose Keep original, which includes TAK and VDF. Converting to another format is marked NEXT and is not available yet.
  • Contents: choose Cleaned only or Cleaned + original, which arrives as one zip file.
  • Destination: choose Download, Shared storage or Pipeline.

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

Versions, Keep raw and the export record ​

A take is its raw capture plus every Clean version a cleanup made, Clean v1, Clean v2 and so on. Nothing is ever deleted: a new clean is added on top, and the older ones stay in the take's version history on the Data screen. One version is the current one. It is the version you approve and export, and the version history marks it CURRENT. A new clean becomes the current version when it finishes.

When a clean scores lower than the raw capture, the Review screen says so in a red banner, for example "Clean v1 scored 94, lower than the raw capture (99)." The banner offers two actions. Compare raw and clean shows both in the viewer. Keep raw instead makes the raw capture the current version. The banner then reads "Raw is now the version to approve and export. Clean v1 stays in the version history." with an Undo button that makes the clean current again. That banner is a confirmation: it shows right after you press Keep raw instead and goes away after about 10 seconds, or when you open another take or another screen. To make another version current later, use Use this version on that version in the take's version history on the Data screen. A take whose raw capture is current also has Use Clean v1 again in its actions menu on Data and under the decision panel on Review. While the raw capture is current, the take reads Raw (kept) and shows the raw capture's predicted score. You cannot change the current version while a new clean of the take is being made.

The Export dialog opens on the current version and marks it Recommended. You can still choose the other version. A box headed Before you export lists what is worth knowing first, such as a clean that scored lower than the raw capture or regions that need your eyes. It never stops you from exporting.

  • File name: the dialog suggests {take name}_clean-v{N} with the format's extension for a clean, and the take's own name for the raw capture. You can type any name. Nothing is taken out of the take's name.
  • Cleaned + original arrives as one zip file named after the clean, holding the clean and the raw capture. One download means your browser does not ask whether Post may download several files.
  • Notes file: when regions of the clean are marked for a hand fix, a plain text file lists each one with its performer or prop, its marker, its frames and its seconds. With Cleaned + original it is inside the zip. With Cleaned only its link appears once the download starts.

Every export is recorded. The take then reads Exported with the date, such as Exported 30 Oct, and the Data screen lists each export under the version history with the version, the date and the file name. Exporting the same version again asks first, for example "You exported Clean v3 on 30 Oct. Export again?"

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 will not change the result, because 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 is not wired yet, so use Keep original.
  • A solved-skeleton FBX is rebuilt on export rather than patched into your original file, because 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. It is 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.