Key Studio Pro

How to pull a matte from motion blur

A moving hand is half background for most of its width. Clip that to a hard edge and it reads as a cutout instantly.

6 min readUpdated

Freeze a frame of someone clapping in front of a green screen. The hand is not a hand. It is a smear thirty pixels wide, and most of those pixels are more screen than skin. That smear is what motion looks like at 24 frames a second with a 180 degree shutter, and the audience’s eye expects it. Take it away and the motion turns into strobing, which is why keyed action so often feels like a video game.

The blur is not damage to be cleaned up. It is picture information, and the key has to carry it.

Why mattes turn hands into paddles

A blurred edge is a gradient of mixed pixels: 10 percent hand, then 30, then 60, then 90. A chroma keyer maps that gradient through its transparency slope, and with the slope tuned to protect the rest of the frame, the gradient mostly lands in the kill zone. The blur trail vanishes and the hand gets a hard, jittering outline. Choke and blur the matte and you have not restored the blur, you have smeared a wrong answer.

Binary AI mattes are worse here for the same reason they fail on hair: in-or-out per pixel. A 30 percent pixel becomes 0 or 100, and either way it is wrong by a mile on a blurred edge.

The honest options

Shoot around it. A faster shutter reduces blur at the cost of choppier motion; some action work does exactly that on purpose. If the look allows it and you have not shot yet, it is the free fix.

Key sharp, re-blur in comp. The traditional rescue: pull the crispest matte you can, then apply synthetic motion blur from motion vectors. It can work, and it is real labor per shot, and synthetic blur over a hard cut edge never quite matches the optical thing, because the color inside the trail is still missing.

Unmix the trail. The blur trail is mixed pixels, and mixed pixels are precisely what a neural unmixing keyer is trained on. Key Studio Pro predicts the foreground color and a linear alpha for every pixel in the smear, so a 30 percent pixel comes back as skin tone at 0.3 alpha. The trail composites over the new background the way the lens originally drew it.

Doing it

  1. Run the shot through Key Studio Pro and open the Comp preview on the fastest frame in the move.
  2. Look at the trail edge. It should fade over the checkerboard, not cut.
  3. Composite with the Matte and FG passes, or the premultiplied Processed pass, in linear. Blur math only works in linear light.

Being realistic about the trail

The reconstruction is only as deep as the exposure. When a whole limb crosses the frame in one frame, the middle of that trail is nearly all screen, and the recovered foreground there is faint because it genuinely was faint. Comped over a similar-brightness background, faint is exactly right. Comped over something radically brighter or darker than the screen was, extreme trails can need help from the comp, and no keyer changes that: transparency composites carry the photometric assumptions of the plate.

Common questions

Should I denoise before keying?

Heavy sensor noise lives in the same soft-gradient territory as blur, so aggressive denoising can eat trail detail. If you denoise, keep it gentle and compare the matte both ways on the fastest frame.

Does frame rate matter?

Higher frame rates mean shorter exposures and shorter trails, which are easier for every method. The 24fps cinematic look is the hard case, and the one this page assumes.

The blur keys fine but the edges are still green.

That is spill living inside the trail. Despill handles it: the spill guide covers where to apply it.

Is this the same reason hair keys badly?

Same physics, different scale: hair is spatial mixing, blur is temporal mixing, and both produce pixels that are partially foreground. The hair guide goes deeper on the matte mechanics.

Keep reading

All guides