Fills, seams and holes

What happens to a gap, what happens at the edges of a repair, and what happens when Post decides not to fill something.

Fills

A gap is filled from the data around it. Which step does it depends on how long the gap is — the Cleanup Plan shows Fill small gaps, Fill medium gaps and Fill long gaps as separate rows, because they are different pieces of work with different prerequisites.

The join matches the speed, not just the position

A fill that only meets the captured frames at the right place still pops, because it arrives at the wrong speed. Post matches the motion at both edges as well as the position, so the repaired trajectory leaves and re-enters the captured data without a step. Where only one side of the gap has data, the fill carries that side's motion into the hole for a short band and then tapers, rather than snapping to a dead hold.

A flickering marker is filled as one stretch

A marker that keeps dropping out and returning used to be filled gap by gap, which left a small step at every boundary. Where the surrounding capture supports it, that whole run is now filled as one continuous stretch. Where it does not, the gaps are still filled separately.

Filling a run as one stretch means a few frames your raw take still shows get replaced along with the gaps — the little islands between the drop-outs, which are reacquisition wobble and are a worse thing to anchor on than nothing at all.

Where to see the frames a fill replaced

The region card on After says it on the face of the card:

Includes 111 measured frames replaced during filling (flickering signal)

Expand it and each stretch is listed: the frames, the check that consumed it, and how far the fill ended up from the samples it replaced —

f962–f1072 · 111 frames · temporal — acceleration spike · fill 0.42 cm from measured

with one line for the worst of them:

Fill landed up to 1.2 cm from the samples it replaced.

Some deviation is expected: those samples were consumed precisely because they were noisy. The number is there so a fill that went somewhere the measurement never did is visible.

A card that says nothing about this is a fill that replaced no measured frames.

Seams

A seam is the join at the edge of a run of frames Post wrote — and it is a seam whatever is on the other side of it: captured data, another repair, or the end of the take.

The Smooth joins step, counted in joins, judges each of those boundaries and conditions the ones that need it. The joins it could not land are reported rather than smoothed over. The inside of a repair is checked separately, so every frame Post wrote is judged exactly once.

A join is where a fill is most likely to give itself away, which is why it is its own step and its own check rather than a side effect of filling.

Holes left open

Post repairs occlusions. It does not invent frames that were never recorded. So a cleaned take can still show holes, and re-cleaning will not fill them — which is the thing worth knowing, because the instinct is to run it again.

The After screen names them. A note above the region list reads:

8 windows · 88 frames · 0.7s not repaired

and then says what each of them is. There are three kinds, and Post tells them apart rather than calling everything the same thing:

Kind	What it is
Out-of-volume window	The performer had left the capture volume. Motion that was never seen cannot be recovered.
Capture dropout	The capture system recorded nothing across those frames — nobody went anywhere. There was nothing to repair from. A window that takes more than one performer down at exactly the same frames is this, not an exit.
Not assessed	Detection did not complete on that layer, so nothing there was cleaned either.

The note ends with the sentence that stops a futile re-run:

Cleanup repairs occlusions; it does not invent frames that were never recorded, so re-cleaning will not fill these.

and says where they are — At 00:00:12, 00:01:44 and 2 more. — so a hole on screen can be matched to the note.

Open frames inside a repair

Separately from the three above, a repair itself can leave frames open. Post would rather leave a gap you can see than ship a fill it cannot stand behind.

• A region card reading Nothing filled shipped no value for that span, and says why in plain words — for example the fill moved the marker faster than this marker can move, or the fill did not line up with the captured frames beside it. That card carries no model attribution and no score, because nothing was fixed.
• A repair that shipped part of its span keeps its model and states both halves: the frames that landed, and the frames still open.
• The Cleanup Plan block counts what the whole delivered file still has open, once: 4 frames ship open. That number is measured from the delivered file. Where nothing measured it, the panel says plan ran — open frames not recorded rather than working one out.
• The region list header counts the same thing per region: 168 regions repaired · 59 regions still need work · 1 reverted to raw.

Revert

Every region card on After has a Revert button. One click and that region is excluded from the Clean version — the card reads Reverted to raw capture · excluded from Clean v1 — and Undo puts it back. A reverted region counts as work still to do, because the file you would hand over has the original problem in it.

On export, a revert is an exact restore of your original capture over those frames — nothing is recomputed, and the rest of the clean stands. The export dialog says which state it is in:

• 2 reverted regions — the export restores your original capture over those spans (nothing is recomputed; the rest of the clean stands).
• Preparing the reverted export — a file downloaded right now still contains every AI fill for the 2 reverted regions. This usually takes a few seconds.

and, after the export, what the file you just got actually contains: 2 reverted regions restored to your original capture in this file.

A cut that Post measured and then put back has nothing to revert, so it has no button — the frames in the file are already yours.

What this page does not cover

• Which model filled a gap. The region card names it; the full model id is in its tooltip.
• Why a step did not run at all. That is a plan question — see Step states.
• Spikes. A spike is cut and refilled rather than filled — see Jitter.

What to do next

Open a cleaned take on After, read the note above the region list first, then switch the region list from By frame to By confidence to put the shakiest repairs at the top. Revert what you disagree with before you export.

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.