Overview

Live Stream Replay (DVR) allows a player to rewind and play past segments of a live audio stream (HLS or ICY).


This feature works by:

  • Recording a rolling window of the live stream (up to 24 hours)
  • Exposing past playback positions via a metadata API
  • Allowing the player to reconnect to a previous point in time

Replay sessions behave like normal live playback sessions and require no special handling once initiated.


Requirements

Before implementing Live Stream Replay:

  • DVR must be enabled in DAS configuration (publisher required to stream using DAS)
  • You must control your own player or mobile app
  • Feature is intended for talk/non-music stations only (see Licensing below)
  • Player-side development is required (this is not plug-and-play)
  • Player must be able to receive metadata through a second metadata connection API


Licensing Restrictions

Important: Live Stream Replay can only be used for talk/non-music content.

This feature is not available for music stations without legal review.


Enablement

Contact Support@soundstack.com to enable Live Stream Replay for your talk/non-music content.


Playerside Development

The player must be able to:

  • Call metadata API
  • Display or interpret available rewind positions
  • Reconnect using startFrom
  • Handle session changes

Optional functionality:

  • “Back to Live” button: Reconnect without startFrom
  • Pause/Resume: Store and reuse last position
  • Timeline/seek UI: Based on metadata positions

Player Configuration

Retrieve Past Metadata

The player retrieves available replay positions using the second metadata connection API.


Request

> GET /mount_name/all_metadata&type=json HTTP/1.1
> Host: 192.168.68.220:8080
> User-Agent: insomnia/8.5.0
> Accept: text/event-stream

Example

http://192.168.68.220:8080/<mount_name>/all_metadata?type=json

Response

{
"metadata-list": [
{
"start": "105633",
"media_sequence": "123",
"metadata": "title=\"celine dion - im alive remix\",url=\"&artist=celine%20dion&title=im%20alive%20remix&album=&duration=186645&songtype=S&overlay=NO&buycd=&website=&picture=\""
},
{
"start": "115644",
"media_sequence": "142",
"metadata": "title=\"dj_fire_ - _corona_vs_la_bouche_megamix\",url=\"&artist=dj_fire_&title=_corona_vs_la_bouche_megamix&album=&duration=1224150&songtype=S&overlay=NO&buycd=&website=&picture=\""
},
{
"start": "1337652",
"media_sequence": "200",
"metadata": "title=\"Madonna Feat. Nicki Minaj & M.I.A. - Give Me All Your Luvin\",url=\"&artist=Madonna%20Feat.%20Nicki%20Minaj%20%26%20M.I.A.&title=Give%20Me%20All%20Your%20Luvin&album=M.D.N.A.&duration=204722&songtype=S&overlay=NO&buycd=&website=&picture=\""
}
]
}
  • First entry = earliest available replay position
  • Last entry = most recent (near-live) position

Fields

  • start: timestamp (metadata start time)
  • media_sequence: use this for seeking
  • metadata: rack/content info

Seek to a Past Position

To replay from a previous point, reconnect to the stream using:

Option A: URL Parameter

?<...>&startFrom=<media_sequence>

Option B: Header

X-DAS-StartFrom: <media_sequence>

Rules

  • Must be within available range between the earliest and latest positions
  • Use media_sequence, not start

Playback Behavior

  • Replay sessions behave like normal live playback
  • A new session is created when reconnecting
  • There will be no visual difference unless it is implemented in the player

Returning to Live

To return to the live stream:

  • Reconnect to the stream without the startFrom parameter

This should be exposed as a “Live” or “Go Live” button in the player.

Ads & Monetization Considerations

Replay affects ad delivery and must be handled carefully:

  • Each reconnection may trigger new ad opportunities
  • Rewinding can increase ad impressions artificially

Recommendations

  • Use ad capping in your SSP to limit frequency
  • Be mindful of:
    • Pre-roll replay behavior
    • Mid-roll duplication during rewind

Replay sessions still support standard ad delivery via DAS.

Common Pitfalls

  • Using start instead of media_sequence
  • Not handling session restart on seek
  • Ignoring ad duplication risk
  • Assuming player support without custom development
  • Not using port 8080 for the second metadata connector calls

Questions? Need additional help? Contact Support@soundstack.com