Ad Player Demo
Idle
Docs →
0:00
AD Ad break
Event Log
Waiting for events…
SDK Config
Session

SGAI only. DAR keeps the historical resume (skips the replaced window only when a break sets resumeOffset); DAI resumes content at the exact pre-break position. Resume-seek applies on the pts (VOD) timebase. Ignored in SSAI mode.

SGAI only (NFL Channel/Network streams). Resolves pts-timebase breaks via in-stream Anvato ID3/emsg cues (type=cue&pts=…) instead of the raw manifest PTS; a break stays pending until its cue is seen.

wallclock timebase only. How long to wait for the stream's EXT-X-PROGRAM-DATE-TIME before deciding the stream carries none. A session starts before the player has loaded its source, so the first ticks see no PDT: in that gap the SDK schedules nothing rather than matching breaks against the system clock, which runs ahead of the live playhead and would fire a break early. It is a backstop, not a fixed delay — once content is playing with still no PDT (~1s) you immediately get one DA-PDT-MISSING (visible in the log and in Export/Analyze) and clock-based matching, so a PDT-less stream is never delayed. This window only applies when playback never starts. Blank = default 5; 0 = fall back immediately (the pre-PLAYG-360 behaviour — watch a live wallclock break fire early).

In SGAI this is the stream the player loads. In SSAI the SDK plays the stitched master instead — this URL just seeds the Stitcher Origin URL below.

Off — the backend break manifest is used as-is.

Org ID, Channel ID, Custom Asset Key, Content URL and Ad Tag Parameters are remembered in this browser. Reset to defaults

SSAI Stitcher (dev)

The content the stitcher fetches server-side (it follows redirects and resolves relative variant/segment URIs against the final URL). Defaults to the Content URL but may differ — some operators ingest a separate origin for SSAI. Left blank → falls back to the Content URL.

Caps rendition bitrate via max_bitrate; the stitcher drops higher variants from the master playlist.

Spawns a local @dolby-ads/stitcher dev server (via the Vite middleware) using the Org ID, Channel ID, GAM Network Code and the Stitcher Origin URL above as a single channel. The SDK only loads the stitched master.

Stitcher not running.
AI Troubleshooting

Capture a redacted diagnostic report and run the same analysis the @dolby-ads/mcp troubleshooting agent uses — fully client-side. No secrets leave the page.