Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 210 of 221; 24 results per page.
Markdown creator brief for the conference highlight video kit 25; it fixes scope, local-input rules, deliverables, and the edge-case review. Stable P8 artifact p8-video-kit-25-creator-brief.
Download-only JSON control for video workflow 25; it removes the source timebase and publishes the only acceptable 12 fps fallback. Stable P8 artifact p8-video-kit-25-edge-case.
JSON evaluation contract for conference highlight kit 25; it publishes readability, timing, comparison, and edge-report assertions. Stable P8 artifact p8-video-kit-25-evaluation-contract.
H.264 expected-output clip for video workflow 25, with a moving marker and embedded frame labels for deterministic edit comparison. Stable P8 artifact p8-video-kit-25-expected-output.
H.264 input-media clip for video workflow 25, with a moving marker and embedded frame labels for deterministic edit comparison. Stable P8 artifact p8-video-kit-25-input-media.
Vendor-neutral YAML plan for conference highlight kit 25, with four stable actions and three machine-checkable local-execution conditions. Stable P8 artifact p8-video-kit-25-prompt-plan.
Short VQA question/answer pairs referencing library images — a fixture for VQA loaders and eval scripts.
A VMAP playlist scheduling three linear ad breaks — pre-roll at start, mid-roll at eight seconds, and post-roll at end — each pointing at a VAST tag. VMAP describes WHEN breaks occur while VAST describes WHAT plays in them. The mid-roll offset lines up with the period boundary in the multi-period DASH manifest, so the two can be tested together.
A one-page fillable PDF twin of the volunteer application HTML form. Its canonical AcroForm field tree, widgets, values, and appearance streams are generator-validated.
Machine-readable field names, labels, types, required states, choices, and input hints for the volunteer application family.
A nonprofit volunteer application for testing applicant imports, role choices, availability, contact autofill, free-text skills, and consent handling. This standalone HTML reference works offline, uses explicit labels and native validation, and submits nowhere.
A one-row UTF-8 CSV export of the fictional volunteer application response with columns in the same order as the field manifest.
Fictional submitted values for every documented volunteer application field, suitable for request parsing, mapping, and round-trip tests.
A WebVTT file used as a chapter track rather than captions: cue text is a chapter title and the cues tile the timeline with no gaps. Players surface these as seek-bar markers, so it exercises a different code path from subtitle rendering despite being the same file format.
An intentionally corrupt WebVTT file with timestamps that are not zero-padded — 00:00:3.000 and 00:1:03.000 where the grammar requires two digits. The third cue is well-formed. A strict parser drops the two bad cues; a lenient one accepts them; a regex-based one may match partially and produce a time that is wrong rather than rejected, which is the worst outcome of the three.
An intentionally corrupt WebVTT file with the mandatory WEBVTT signature removed from the first line. The cues themselves are perfectly valid. The spec requires strict rejection, so a browser refuses it outright while many lenient parsers accept it — a useful disagreement to be able to reproduce.
A WebVTT metadata track whose cue payloads are JSON objects rather than text for display. This is how timed analysis output — scene changes, detections, speech segments — is carried alongside a video and read from JavaScript via the cue change event. Nothing here should ever be rendered on screen.
WebVTT with multi-line and single-line NOTE comment blocks, runs of up to five blank lines between cues, and trailing blank lines at end of file. All legal — the spec treats blank lines as separators, not as structure. Parsers that count blank lines to find cue boundaries, or that treat NOTE as a cue identifier, produce phantom cues or drop real ones.
WebVTT cues carrying the full positioning grammar — line, position, align and size — plus named cue identifiers instead of numbers. Captions are placed at four different points in the frame, which is what real subtitles do to avoid covering burned-in text. Parsers that treat everything after the timestamp as cue text will fold these settings into the visible caption.
Companion VTT for the soft-sub MP4 — same SAMPLE cue timings.
WebVTT exercising the parts of the format beyond plain text: a STYLE block with ::cue selectors, a named REGION, voice spans, cue classes, and inline bold/italic/underline/ruby markup. A parser that handles only timestamps and text will render the tag names as visible characters.
WebVTT with a byte-order mark ahead of the mandatory WEBVTT signature. The spec explicitly allows this, and browsers accept it — but a naive check that the file literally starts with the six bytes 'WEBVTT' rejects a perfectly valid file. The mirror image of the missing-header corrupt fixture: one is valid and often refused, the other is invalid and often accepted.
Video QC companion SAMPLE (desync-caption.vtt) for Wave G suites.
Video QC companion SAMPLE (bars-caption.vtt) for Wave G suites.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
