Skip to content
Novus Examples
srt37.9 KB

SRT — 500-Cue Throughput File

Five hundred short sequential cues over four minutes. Small in bytes but long enough to expose quadratic parsing, per-cue DOM churn, and UI that re-renders the whole caption list on every cue change.

Preview — first 50 linessrt
1
00:00:00,000 --> 00:00:00,400
Cue 1 of 500 — parser throughput check

2
00:00:00,500 --> 00:00:00,900
Cue 2 of 500 — parser throughput check

3
00:00:01,000 --> 00:00:01,400
Cue 3 of 500 — parser throughput check

4
00:00:01,500 --> 00:00:01,900
Cue 4 of 500 — parser throughput check

5
00:00:02,000 --> 00:00:02,400
Cue 5 of 500 — parser throughput check

6
00:00:02,500 --> 00:00:02,900
Cue 6 of 500 — parser throughput check

7
00:00:03,000 --> 00:00:03,400
Cue 7 of 500 — parser throughput check

8
00:00:03,500 --> 00:00:03,900
Cue 8 of 500 — parser throughput check

9
00:00:04,000 --> 00:00:04,400
Cue 9 of 500 — parser throughput check

10
00:00:04,500 --> 00:00:04,900
Cue 10 of 500 — parser throughput check

11
00:00:05,000 --> 00:00:05,400
Cue 11 of 500 — parser throughput check

12
00:00:05,500 --> 00:00:05,900
Cue 12 of 500 — parser throughput check

13
00:00:06,000 --> 00:00:06,400
2000 lines total — download for the full file.

Specifications

Cues
500
Duration
250s
Cadence
one cue every 0.5s
Pattern
sequential, non-overlapping

What is a .srt file?

SRT (SubRip) is a plain-text subtitle format listing numbered cues, each with a start and end timecode and one or more lines of text. It is simple, human-readable, and extremely widely supported by players. It carries no styling metadata beyond basic inline tags.

How to use this file

Use an example SRT to test subtitle parsing, timecode handling, and converters that translate between SRT and WebVTT or other caption formats.

How to use this file for testing

“SRT — 500-Cue Throughput File” is a deterministic Novus Examples fixture for Subtitle parsing, Video QA. The same captions across SubRip, WebVTT, ASS/SSA, SBV, and TTML, plus a synced LRC lyric file — for testing subtitle parsers, players, burn-in tools, and format converters against known timings.

Documented properties for this file: 500 cues · 250s. 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="stress-500.srt" default>
</video>

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