Skip to content

FAQ ​

These are the questions artists and pipeline leads actually ask us. Throughout, a take is one recorded motion-capture performance, and a region is one span of frames on one marker inside a take.

What does "Did not land" mean? ​

It means Post attempted that step and shipped nothing. It is not a crash, and it is not a step that was skipped. The step looked at its windows and put no value in the delivered file, so what it stood for is in your take as holes for an artist to finish. Running the take again will usually decline the same work the same way, and the Cleanup Plan says so when that is the case. The Cleanup Plan is the per-take list of steps Post will take, and it is where the words "Did not land" appear. See Step states.

Why is the jitter cut the last step? ​

Because a cut takes frames out and has to rejoin the trajectory on both sides, and next to an unfilled hole there is nothing to rejoin to. So the cut runs after the fills of its own pass, once the surrounding data exists. That is also why there are two cut passes: filling a gap can expose a peak that was not visible in the raw. Your raw take is the file you uploaded, which Post never modifies. See Why the jitter cut comes after the fills.

Why is there still a hole in my take? ​

There are two possible reasons. Either the frames were never recorded, which happens when the performer had left the capture volume or the capture system dropped out. Or a repair was rejected because it would have moved the marker faster than that marker can move. The Review screen, which is where you read a finished run, names which of the two it was, with counts and with where to find them. Re-cleaning will not fill the first kind, because Post repairs occlusions and does not invent capture. See Holes left open.

Where do I find the frames Post replaced? ​

They are on the Review screen, in the section headed What the AI changed · per region. A card whose fill replaced measured frames says so on the face of the card, in the words Includes 111 measured frames replaced during filling (flickering signal). Expand that card and it lists each stretch with its frames, the check that consumed it, and how far the fill ended up from the samples it replaced. A fill is the motion Post writes into a gap. See Fills.

My upload does nothing: the button is inactive ​

Create or select a project first. A project is the folder your takes live in. Uploads attach to a project, so a brand-new workspace has nowhere to put files until one exists, and the upload button stays inactive until then. Add a project from the + next to Projects in the left rail (or from the prompt in the upload dialog), select it, and upload again. See step 2 of the quick start.

I re-cleaned the same file and nothing changed ​

That is expected. Cleanup is deterministic per (raw, options, model), which means the same raw file with the same options and the same model produces the same result every time. To get a different result, change the frame range or the options, or upload a new raw file. Running Auto again over an unchanged take will not move it. Auto is the run mode that cleans every take in To clean without asking you anything.

Why is a clean marked "unverified"? ​

Because Kapnetix will not show a fake score. When a result cannot be measured, the Review screen labels it unverified rather than inventing a confidence number. This is deliberate. Confidence is a real, measured figure on the Review screen, and a result that cannot be verified is reported as such instead of dressed up. See confidence is fixability.

Can I convert formats on export? ​

Not yet, and it is still to come. For now use Keep original. Every supported format, TAK and VDF included, comes back in the format you uploaded. See Supported formats.

What happens to TAK and VDF files? ​

They come back as TAK and VDF. Both are proprietary containers with no public specification, so Kapnetix does not author one from scratch. It patches the cleaned animation into a byte-preserving copy of the file you uploaded, leaving your header, calibration, cameras and processing metadata exactly as they were. We validated this by opening the results in MotionBuilder, Maya and Shōgun.

A solved-skeleton FBX is the one exception. It comes back as a fresh build rather than a patch, because a solve goes stale once markers move. See Supported formats.

Does cleanup ever overwrite my raw capture? ​

Never. Raw capture is immutable. Every cleanup lands beside it as a new named version, called Clean v1, then Clean v2, and so on, and the version history is never collapsed. You can compare any version against the raw and revert individual regions. See Raw is immutable.

What does a confidence score actually mean? ​

It says how cleanly Kapnetix can fix the take or the region. It does not say how broken that take or region is. You see the figure twice. On Diagnose it is predicted, so you can plan your review. On Review it is measured, so you can verify the result. It is never an error meter. See core concepts.

How long does diagnosis take? ​

Most takes take from seconds to minutes. A diagnosis is the read-only pass Post makes over a take when you upload it. Long, multi-performer takes take longer, so diagnosis and cleanup each get up to two hours and a large file runs to the end instead of being cut off. Watch the take row on the Data screen, which is the screen that lists your projects and their takes. The row shows Diagnosing… and then resolves to a status and a Cleanup forecast, which is a one-word rating of how much work the take will be.

What this page is not ​

This page is not a reference. It answers the questions people actually ask us. For how the cleanup itself works, read how Post cleans a take. For the release history, see what's new.

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.