Skip to content
Novus Examples
mp418.6 KB

60 fps Clip (MP4)

A 60 frames-per-second clip with a smoothly sweeping marker — double the usual frame rate. A fixture for testing high-frame-rate playback, frame-rate detection, and fps conversion (60→30 decimation).

Browser-playable test video · 3 seconds

Specifications

Resolution
480x270
Fps
60
Duration
3s
Audio
none
Codec
H.264

Testing contract

Expected to pass
Scenario
Decode the clip and confirm its geometry and the event the fixture is named for.
Expected result
480x270 at 60 fps, 3s, H.264 in MP4. The clip runs at 60 fps with no audio stream - double the house rate, so any code that hard-codes 24 or 30 fps, or that derives duration from a frame count and an assumed rate, gets the wrong answer 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

“60 fps Clip (MP4)” is a deterministic Novus Examples fixture for Conversion testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.

Documented properties for this file: 3s · 60 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="60fps.mp4"></video>

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