Container — QuickTime
One H.264 elementary stream wrapped in QuickTime. Every file in this group was produced from the SAME encode with a stream copy, so the compressed video bytes are identical and the container is genuinely the only difference. Apple's container, and the direct ancestor of MP4 — the two share the same atom structure, which is why remuxing between them is nearly free.
Rendered preview of the mov file (23.1 KB). Download above for the original.
Specifications
- Resolution
- 480x270
- Fps
- 24
- Duration
- 1s
- Container
- QuickTime
- Codec
- H.264 (libx264) — identical across this group
- Remux
- stream copy — video bytes are unchanged
- Audio
- none
Testing contract
Reference control- Scenario
- Demux the video stream out of the container and compare the extracted elementary stream against the one from any other member of this group.
- Expected result
- The container is QuickTime and the video is H.264 (libx264) — identical across this group. Every member of this group was produced by a stream copy, so the encoded video bytes are unchanged across all seven - the extracted elementary streams must be identical, and only the container framing differs. 480x270 at 24 fps, 1s, no audio.
What is a .mov file?
MOV is Apple's QuickTime container, introduced in 1991 and the direct ancestor of MP4. ISO adopted its box structure as the basis of ISOBMFF, so the two are close relatives rather than rivals. Beyond video and audio it carries timecode tracks, edit lists, and reference movies: files of a few kilobytes that play only where the media they point at still lives. It also carries codecs MP4 does not, notably ProRes and Animation with a true alpha channel, which keeps it the working format of professional editing.
How to use this file
Use an example MOV to test QuickTime box parsing, timecode and edit-list handling, and MOV-to-MP4 remuxing, confirming that a stream copy is chosen when the codecs allow it, that an alpha channel survives where the target supports one, and that a reference movie is not mistaken for self-contained media.
How to use this file for testing
“Container — QuickTime” is a deterministic Novus Examples fixture for Video codecs, Conversion testing, Video QA. One source encoded as H.264, HEVC, AV1, VP9, MJPEG, and a ProRes-compatible mezzanine, across 8/10/12-bit and 4:2:0/4:2:2/4:4:4, for testing decoder support, transcode pipelines, and container remuxing.
Documented properties for this file: 1s · 24 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="mov.mov"></video>Related files
- webmAlpha Channel — Opaque VP9 TwinThe same codec and container with NO alpha plane, as the control for the alpha clip in this group. Useful for checking that alpha detection reads the pixel format rather than assuming every WebM is transparent — and for confirming a compositing bug is in the alpha handling rather than in the player.
- webmAlpha Channel — VP9 in WebMVideo with a real per-pixel alpha channel: VP9 yuva420p in WebM, the one alpha path browsers decode natively. Composite it over a page background and the transparency is genuine, not a chroma key. Roughly 90% of each frame is fully transparent. Two traps this file exists to expose. First, auto-alt-ref must be disabled at encode time or libvpx silently drops the alpha plane, producing a valid file with no transparency and no error. Second, WebM stores VP9 alpha in BlockAdditional and signals it with AlphaMode=1, so FFmpeg's NATIVE vp9 decoder reports pix_fmt yuv420p and decodes fully opaque — you must force `-c:v libvpx-vp9` to see the alpha at all. Probing this file with default settings and concluding it has no alpha is the expected mistake.
- mp4Bitstream — All-Intra (Every Frame a Keyframe)Every frame is an I-frame, so any frame is an independent cut point. Much larger, and the shape editing and frame-accurate seeking want. Same picture and same codec as every other clip in this group — only the GOP and frame-type structure differ, so the effect on size and seekability is directly attributable.
- mp4Bitstream — Heavy B-Frames (8 Consecutive)Eight consecutive B-frames with a B-pyramid, so decode order and display order diverge sharply and DTS runs well behind PTS. The case that breaks naive timestamp handling and any code that assumes frames arrive in display order. Same picture and same codec as every other clip in this group — only the GOP and frame-type structure differ, so the effect on size and seekability is directly attributable.
- mp4Bitstream — Long GOP (24 Frames, One Per Second)One keyframe per second — the delivery default, and the setting that determines HLS/DASH segment boundaries, since a segment must start on a keyframe. Same picture and same codec as every other clip in this group — only the GOP and frame-type structure differ, so the effect on size and seekability is directly attributable.
- mp4Bitstream — No B-FramesI and P frames only. Required by some low-latency and legacy decoders, and it removes the reordering that makes decode order differ from display order. Same picture and same codec as every other clip in this group — only the GOP and frame-type structure differ, so the effect on size and seekability is directly attributable.
Generated by generation/video_codecs_wave.py. Free for any use, no attribution required, license.