Thumbnail Track — Sprite Sheet
A 6x2 sprite sheet of 160x90 scrub-preview thumbnails in a single JPEG. Players fetch one image rather than 12 separate requests, then crop each tile with a media fragment — which is why the WebVTT index in this group is the load-bearing half of the pair. Useless on its own; that is the point of shipping them together.
Specifications
- Grid
- 6x2
- Tile Size
- 160x90
- Tiles
- 12
- Sheet Size
- 960x180
- Format
- JPEG q82
- Indexed By
- thumbnails.vtt in this group
Testing contract
Expected to pass- Scenario
- Load the sprite sheet and crop the tile addressed by any cue in the companion WebVTT file.
- Expected result
- A 960x180 JPEG (quality 82) holding 12 tiles in a 6x2 grid, each 160x90. Every crop must land exactly on a tile boundary: 6x2 at 160x90 accounts for the full 960x180 with no padding, so an off-by-one in the x/y arithmetic shows up as a visible sliver of the neighbouring tile rather than as an error.
What is a .jpg file?
JPG is the common extension for JPEG, a lossy raster format that uses discrete cosine transform compression tuned for photographic images. It is 8-bit truecolor with no alpha channel, and quality is traded against file size via a compression factor. It is ubiquitous for photos on the web and from cameras.
How to use this file
Use an example JPG to test decoders, EXIF/metadata parsers, re-encoding quality, and orientation handling, or to confirm converters and image pipelines process baseline and progressive scans correctly.
How to use this file for testing
“Thumbnail Track — Sprite Sheet” is a deterministic Novus Examples fixture for Streaming manifests, Video QA. HLS playlists and DASH MPDs covering multi-bitrate ladders, byte-range addressing, and segment templates. Served inline with permissive CORS under /files/stream/, so a player can load them from any origin without re-hosting.
Documented properties for this file: JPEG q82. 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
<img src="sprite.jpg" alt="Example image" width="640" loading="lazy">Related files
- mpdDASH — Dynamic (Live) Manifest With a Time-Shift BufferA live DASH manifest: type is dynamic, there is no total duration, and the client must compute which segment is currently available from availabilityStartTime, the wall clock, and the segment duration. Declares a one-minute time-shift buffer and an eight-second presentation delay. The timestamps are fixed so the fixture stays deterministic — a real client will compute a segment number far in the future, which is itself a useful edge case to handle gracefully.
- mpdDASH — Explicit SegmentList AddressingThe same content addressed with an explicit SegmentList — every segment URL enumerated rather than derived from a template. Verbose, but it is what older packagers emit and it permits non-uniform segment naming. A DASH client must support both this and SegmentTemplate; the paired template manifest in this group is the direct contrast.
- mpdDASH — Intentionally Corrupt: Malformed ISO 8601 DurationAn intentionally corrupt DASH manifest whose mediaPresentationDuration is the bare number 14.0 instead of the ISO 8601 form PT14.0S. The XML is well-formed, so it parses cleanly and only fails at schema validation — which most players skip. The usual result is a duration of zero or NaN and a seek bar that never populates, with no error anywhere.
- mpdDASH — Multi-Period Manifest With a Mid-Roll BreakThree DASH periods — content, an ad break, then content again — each with its own initialisation segment. Period boundaries are where players most often break: the decoder must be reset, the buffer cannot span the discontinuity, and rendition selection restarts. Pairs with the VMAP and SCTE-35 fixtures, which describe the same break from the ad-signalling side.
- mpdDASH — Static MPD With a Segment TemplateA DASH manifest with separate video and audio adaptation sets, three video representations, and $RepresentationID$/$Number$ segment-template addressing — the standard VOD packaging shape. Served inline as application/dash+xml with permissive CORS, so dash.js can load it cross-origin. A manifest-parsing fixture: it describes segment URLs rather than shipping the segments.
- m4sDASH VOD — Init Segment (init-stream0.m4s)A DASH initialisation segment carrying codec configuration for one representation. Named by the manifest's $RepresentationID$ template, so this file also exercises whether a client resolves template variables correctly rather than pattern-matching filenames.
Generated by generation/video_streaming_wave.py. Free for any use, no attribution required, license.