Skip to content

CSRT tracking

Track an initialized object with correlation filters weighted by channel and spatial reliability.

Try it on your image ↓

VISUAL WALKTHROUGHMotion
REFERENCE INPUTTarget moves in the next frame

The previous position is a starting estimate, not the new target location.

RESULTUpdate the target box

Update position, scale and reliable appearance support.

STEP 03 / 03

Update position, scale and reliable appearance support.

Illustrative example. The stages explain the method; they are not a live OpenCV execution.

Try it on an image

YOUR IMAGE · REAL OPENCV

Experiment at pixel level

Open full lab ↗

Initialize a tracker on the input rectangle, then locate it in the second image. One update previews tracking; it cannot assess long-term drift.

The engine loads on your first run. Your images stay in this browser.

Input448 × 320
OutputWaiting for a result

Scroll over either image to zoom at the pointer. Use the scrollbars to pan both views over the same relative area. Zoom is relative to the input; pixel coordinates belong to each image. Warps can change scene correspondence.

Pixel inspector RGBA · native values · matched scale · 9 × 9 output pixels
Hover to inspect. Click to pin a pixel.
Input
Select a pixel

Output
Select a pixel

Sample models and licenses

When to use it

Follow a selected object when a more detailed CPU tracker is acceptable.

How it works

  1. 01Initialize a bounding box and appearance model.
  2. 02Correlate the learned filters with the next search region.
  3. 03Update position, scale and reliable appearance support.

initialized box → local search → model update

What to tune

Initialize on a clear frame. Search padding, feature channels and scale settings trade work against robustness.

Where it breaks down

Trackers can drift or lose an occluded object. A successful update should still be checked against application-specific confidence and geometry.

TypeScript API

Open an entry for its exact overloads, parameter descriptions, result ownership and pinned upstream source.

All of these calls execute on the CPU. Native objects need explicit disposal. See matrices and ownership and build compatibility.