You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/API.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1903,6 +1903,7 @@ data will be passed on all media requests (manifests, playlists, a/v segments, t
1903
1903
- `interval`: For the time-interval event, the reporting cadence in seconds. Defaults to `30`.
1904
1904
- `batchSize`: The number of events to batch before sending a report. Defaults to `1` (send each event immediately).
1905
1905
- `includeKeys`: An optional array of CMCD keys that overrides the top-level `includeKeys` for this target.
1906
+
- `rtpSafetyFactor`: A multiplier applied to the segment bitrate to compute the `rtp` (requested throughput) field. The spec defines `rtp` as the maximum throughput the client considers sufficient, which should include headroom above the encoded bitrate to absorb network jitter and avoid rebuffering. Defaults to `5` (5× the segment bitrate). Only used when `version:2`.
1906
1907
- `loader`: An optional async function `(request) =>Promise<{ status }>` used to deliver CMCD v2 event reports. When omitted, event reports are delivered via `fetch` (honoring the Hls `xhrSetup`/`fetchSetup` hooks). Only used when `eventTargets` is configured.
1907
1908
- `reporterCallback`: An optional `(reporter:CmcdCustomReporter) =>void` callback. Called once per `MANIFEST_LOADING`, before the reporter starts. Use it to seed custom CMCD keys or store the reference for firing custom events at runtime. Always use the most recently received reference, since a new source load yields a new instance.
0 commit comments