Skip to content
Novus Examples
mp49.5 KB

Segmentation Input — Trimap (Foreground / Unknown / Background)

A three-level trimap derived from the instance masks: definite foreground, definite background, and a nine-pixel unknown band around every boundary. This is the input interactive matting and rotoscoping tools actually take, and the band is where all the difficulty lives — a matte is only as good as its handling of that region.

Browser-playable test video · 2 seconds

Specifications

Resolution
640x360
Fps
24
Encoding
255 = definite foreground, 128 = unknown band, 0 = definite background
Band Width
9 px morphological dilate/erode
Role
trimap input
Reference
vid-segmentation-solids-gt
Crf
19
Base Plate
solids

Testing contract

Reference control
Scenario
Feed the trimap to a matting or refinement model together with the scene clip from this group.
Expected result
Three regions are encoded by value: 255 = definite foreground, 128 = unknown band, 0 = definite background. The unknown band is 9 px morphological dilate/erode, derived from the ground-truth mask, so the band's width is known exactly and a model's output can be scored only inside it - which is the standard trimap protocol and impossible to apply without a documented band width.

What is a .mp4 file?

MP4 (MPEG-4 Part 14) is the dominant container for digital video, holding video, audio, subtitle, and metadata tracks in a tree of typed boxes. `ftyp` declares the brand, `moov` carries the sample tables that make seeking possible, and `mdat` holds the media; when an encoder writes `moov` last, playback cannot begin until the file has fully downloaded, which a faststart remux fixes. It derives from Apple's QuickTime format, generalized by ISO into the ISOBMFF base that MOV, 3GP, and HEIF share.

How to use this file

Use an example MP4 to test box parsing and track detection, seeking, range-request streaming, and transcode or thumbnail pipelines: verifying that a file with a trailing `moov` box is still handled, and that codec support is checked per track rather than inferred from the extension.

How to use this file for testing

“Segmentation Input — Trimap (Foreground / Unknown / Background)” is a deterministic Novus Examples fixture for Video segmentation, Video matting, Video QA. Hard-edged and anti-aliased subjects in motion, each shipped with the exact per-frame mask used to create it, for scoring video object segmentation and rotoscoping frame by frame instead of spot-checking.

Documented properties for this file: trimap input · 24 fps · 255 = definite foreground, 128 = unknown band, 0 = definite background. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Media fixtures are short and synthetic by design. Prefer waveform or transcript ground truth in the same group when measuring ASR, trim, upscale, or sync tools; do not assume broadcast-quality masters.

Code examples

<video controls preload="metadata" width="640" src="trimap.mp4"></video>

Generated by generation/video_ai_suites.py. Free for any use, no attribution required, license.