Playback Settings

The <PlaybackSettings> block defines how streams can be played back within an application, including allowed connection types (harnesses), viewer limits, and buffer configuration.

Available in: mono, origin, transcode, edge

Sample Configuration

PlaybackSettings block

xml

<PlaybackSettings>
    <AllowedHarnesses>
        <Harness type="storm-hls"/>
        <Harness type="storm-mse"/>
        <Harness type="generic-hls"/>
        <Harness type="rtmp"/>
    </AllowedHarnesses>
    <TotalViewerLimit>3500</TotalViewerLimit>
    <StreamViewerLimit>1000</StreamViewerLimit>
    <FrameBufferSize>0</FrameBufferSize>
</PlaybackSettings>

Parameters

Parameter	Description	Default
`<AllowedHarnesses>`	List of allowed connection types (harnesses) that are permitted to connect to this application.	all
`<TotalViewerLimit>`	Maximum number of total viewers allowed across all streams in the application. Leave empty for no limit.	—
`<StreamViewerLimit>`	Maximum number of viewers per individual stream. Leave empty for no limit.	—
`<FrameBufferSize>`	Minimum server frame buffer size used during video reception.	`0`

Harness Types

Harnesses define the types of end-point connections that are allowed for stream playback. Each harness type corresponds to a different protocol or delivery method.

Harness Type	Description
`storm-mse`	WebSocket / Media Source Extension connection used by Storm Player Core and Storm Player UI. Provides the lowest latency playback.
`storm-hls`	HLS connection generated by Storm Player Core and Storm Player UI.
`generic-hls`	Standard HLS connection compatible with any HLS-capable player (e.g. FlowPlayer, JW Player, Video.js, native mobile players).
`rtmp`	RTMP protocol connection for legacy player support.

Security Tip

If you use Stream Security Settings (Token Protection or Domain Access Rights), keep in mind that these apply only to storm-mse and storm-hls harnesses. To restrict access via generic-hls or rtmp, remove those harness types from the <AllowedHarnesses> list.

Environment Variables

All parameters support environment variables using the ${EV:VARIABLE_NAME} syntax. Fields locked by environment variables cannot be modified via the REST API.

Support Needed?

If you have any questions or need assistance, please create a support ticket and our team will help you.