HLS Interstitials: Behaviour Overview and Limitations

General Behaviour

HLS interstitials follow the same API behaviour as client-side ad insertion. Scheduling is handled by the player.

Resume Offset Logic

When X-RESUME-OFFSET is not present, the resume offset is calculated with the following priority:

1. Playout limit
2. Sum of the duration of all assets in the asset list
3. Daterange tag attributes in this order:
   1. DURATION
   2. Duration derived from start and end timestamps
   3. PLANNED-DURATION

Limitations

Timeline Features

• Interstitials are always treated as ads.
• Timeline-related interstitial features such as X-TIMELINE-OCCUPIES are not supported.

Skip Control

• The skip duration (how long the ad remains skippable) is not considered or reported.
• Custom skip-until messages are not applied.
• Skip control properties defined only in the asset list JSON are not considered.
  Only skip control attributes on the daterange tag are processed.

Start/End Snapping

• The X-SNAP property is not considered.

Interstitial Content Type

• The content type is generally inferred from the interstitial URL.
• If inference is not possible, the interstitial is treated as an HLS stream.