SBV — YouTube Timing Without Cue Indices
SubViewer/SBV as YouTube exports it: no cue indices, a comma rather than an arrow between start and end, and single-digit hours. Superficially similar enough to SubRip that format detection by eye fails, which makes it a good test of sniffing logic — a parser that guesses SubRip from the timestamps then trips on the missing index.
0:00:01.000,0:00:03.000
SBV has no cue numbers at all
0:00:03.500,0:00:06.000
Times use a comma separator, not an arrow
0:00:06.500,0:00:09.000
Single-digit hours, three-decimal seconds
0:00:09.500,0:00:12.000
[Sound effects use square brackets too]
Specifications
- Cues
- 4
- Separator
- comma between start and end
- Indices
- none
- Hour Format
- single digit
- Origin
- YouTube caption export
Testing contract
Expected to pass- Scenario
- Parse the file as SBV (YouTube caption export) and read its timings.
- Expected result
- 4 cues using a comma between start and end rather than an arrow, no cue indices at all, and single-digit hours. Every one of those differs from SubRip, so a parser that dispatches on extension and hands `.sbv` to an SRT reader finds zero cues rather than erroring.
What is a .sbv file?
SBV (.sbv) is the simple caption format used by YouTube's Studio. Each cue is a start,end timestamp line (H:MM:SS.mmm) followed by the caption text, with a blank line between cues. It has no styling, just timings and text.
How to use this file
Use an example .sbv file to test caption parsers, YouTube caption import, and conversion between SBV, SRT, and VTT.
How to use this file for testing
“SBV — YouTube Timing Without Cue Indices” is a deterministic Novus Examples fixture for Subtitle parsing, Video QA. The same captions written out across SubRip, WebVTT, ASS/SSA, SBV, TTML and a synced LRC lyric file, with known timings, for exercising subtitle parsers, format converters and burn-in tools against every serialisation.
Documented properties for this file: 4 cues. 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.
Parse the cues and check timings against the documented count; the same captions ship across subtitle formats so you can diff a converter against a known target.
Code examples
<video controls src="clip.mp4">
<track kind="captions" srclang="en" label="English" src="frame-timecode.sbv" default>
</video>Related files
- csvCSV — Cue Timing ReportPer-cue timings and text metrics for the shared cue list, as a caption QC tool would export them: start, end, duration, line count and character count. Useful as the expected output when testing a caption analyser, and as a quick way to check reading-rate calculations against known values.
- dfxpDFXP — TTML Under Its Other ExtensionTimed text as DFXP — byte-for-byte a TTML document, just under the extension Netflix, Adobe and older captioning tool-chains still use. Same tt root, same head/body/div/p structure, same styling and region attributes. It exists to check that a caption parser dispatches on document content rather than on the file extension: a parser that accepts .ttml but rejects an identical .dfxp is exactly the bug this catches.
- jsonJSON — Caption Cue ListThe same five cues as a plain JSON array with float second timings — the shape most caption pipelines use internally between parsing one format and writing another. Handy as the expected intermediate when testing a converter, since it removes timestamp-formatting differences from the comparison.
- jsonJSON — Timed-Text Suite IndexA machine-readable index of all 67 timed-text, streaming-manifest and ad-signalling fixtures in this wave, with id, format, path and byte size for each. Useful as a work-list when running a parser across the whole suite, and as a manifest to diff against after regenerating.
- webmMulti-Track Subtitles — Embedded WebVTT (WebM)WebVTT muxed inside a WebM container, which the Matroska specification allows and almost nothing consumes. No browser surfaces an embedded WebVTT track through the HTML TextTrack API — the web platform expects a separate <track> element pointing at a sidecar file — so this is the fixture for the gap between what a container is permitted to hold and what a player will actually give you. One caveat about this file specifically. Every other fixture in this phase carries byte-identical H.264 video, but the WebM muxer accepts only VP8, VP9 or AV1 video and WebVTT subtitles — that restriction is the container's definition, not a limitation of the tooling — so the picture here is re-encoded to VP9 from the same source frames. Same content, different bytes.
- mkvMulti-Track Subtitles — Forced Narrative (MKV)Two English subtitle tracks in one file: the full dialogue track, and a forced-narrative track that carries only the two moments where on-screen text needs translating. The second track sets the `forced` disposition, which tells a player to display it even when the viewer has subtitles switched off. The forced track is deliberately two cues, not eight. A forced track that repeats the full dialogue is the most common way this feature is got wrong in the wild, and a fixture that reproduced that mistake could not be used to detect it. Useful for checking that a player reads the flag rather than the track order, and that a transcoder preserves it — many drop the disposition silently and the file still looks fine until a viewer turns subtitles off.
Generated by generation/video_timedtext.py. Free for any use, no attribution required, license.