Interpolation Input — orbit-solid, Motion-Blurred Decimation
Halved frame rate where each output frame is the AVERAGE of the two it replaces, rather than one of them — what a long shutter angle actually produces. Substantially harder than clean decimation, because the interpolator must undo motion blur as well as invent the missing instants, and no input frame matches any ground-truth frame exactly.
Browser-playable test video · 2 seconds
Specifications
- Resolution
- 640x360
- Fps
- 12
- Frames
- 24
- Decimation
- pairs averaged, not sampled
- Role
- interpolation input
- Reference
- vid-interp-orbit-solid-gt
- Crf
- 19
- Base Plate
- orbit-solid
Testing contract
Expected to pass- Scenario
- Interpolate the clip back to the ground truth's frame rate and score each synthesised frame against its counterpart.
- Expected result
- The input runs at 12 fps with 24 frames (pairs averaged, not sampled), taken from the orbit-solid plate at 640x360. The decimation here is not sampling but averaging - pairs averaged, not sampled - so no input frame equals any ground-truth frame, and a model that scores well on the sampled members of this group by copying the nearest input frame cannot do so here.
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
“Interpolation Input — orbit-solid, Motion-Blurred Decimation” is a deterministic Novus Examples fixture for Frame interpolation, Video deblur, Video QA. Clips with frames removed on a known pattern, paired with the full-rate source, for scoring frame-interpolation and slow-motion tooling against a real reference.
Documented properties for this file: interpolation input · 12 fps. 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="orbit-solid-blended.mp4"></video>Related files
- mp4Interpolation Input — depth-layers, Motion-Blurred DecimationHalved frame rate where each output frame is the AVERAGE of the two it replaces, rather than one of them — what a long shutter angle actually produces. Substantially harder than clean decimation, because the interpolator must undo motion blur as well as invent the missing instants, and no input frame matches any ground-truth frame exactly.
- mp4Interpolation Input — pan-city, Motion-Blurred DecimationHalved frame rate where each output frame is the AVERAGE of the two it replaces, rather than one of them — what a long shutter angle actually produces. Substantially harder than clean decimation, because the interpolator must undo motion blur as well as invent the missing instants, and no input frame matches any ground-truth frame exactly.
- mp4Interpolation Ground Truth — depth-layers at 24 fpsThe full-rate 24 fps reference for the depth-layers interpolation set. The decimated clips in this group drop frames from exactly this sequence, so every frame an interpolator is asked to synthesise has a true original to be scored against — which is the only way to tell invention from reconstruction.
- mp4Interpolation Ground Truth — pan-city at 24 fpsThe full-rate 24 fps reference for the pan-city interpolation set. The decimated clips in this group drop frames from exactly this sequence, so every frame an interpolator is asked to synthesise has a true original to be scored against — which is the only way to tell invention from reconstruction.
- mp4Interpolation Input — depth-layers at 12 fpsThe depth-layers plate decimated to 12 fps by keeping every 2th frame, so 24 of the original 48 frames are missing. Interpolate back to 24 fps and each synthesised frame has an exact counterpart in the ground truth. Larger gaps need genuine motion understanding rather than blending.
- mp4Interpolation Input — depth-layers at 6 fpsThe depth-layers plate decimated to 6 fps by keeping every 4th frame, so 36 of the original 48 frames are missing. Interpolate back to 24 fps and each synthesised frame has an exact counterpart in the ground truth. Larger gaps need genuine motion understanding rather than blending.
Generated by generation/video_ai_suites.py. Free for any use, no attribution required, license.