pdtGraceSeconds

How long, in seconds, to wait for the stream's EXT-X-PROGRAM-DATE-TIME on a wallclock-timebase session before concluding the stream carries none.

A session is normally started before the content player has loaded its source, so the scheduler's first ticks see no PDT even on a stream that does carry it. Those ticks make no scheduling decision, rather than matching breaks against the system clock — which runs ahead of the live playhead by the stream's latency and would fire a break early (PLAYG-360).

This is a backstop, not a fixed delay. The SDK stops waiting at whichever comes first: content has been playing for ~1s and still exposes no PDT (direct evidence about the stream — DA-PDT-MISSING is emitted once and the clock takes over immediately, so a join-in-progress break is not delayed below the tune-in minimum), or this window elapses (the backstop for a player that never starts).

Set 0.0 to fall back to the system clock immediately. Has no effect on pts-timebase manifests. Mirrors the web pdtGraceSeconds.