Support for DVR configuration

[elv-gerald]

We will need to have a brain storm session on how we want to add support for DVR. This feature is already deployed to demo and I have been manually configuring streams to test this.

For now this ticket can serve as a general overview of DVR based on my testing

PR for qfab: https://github.com/qluvio/content-fabric/pull/2859#issue-2458103156

DVR is controlled using the following parameters in the "playout_config" of a stream config. Here are notes from my testing

• dvr_enabled: true or false (if not present, false is implied)
• dvr_start_time: ISO 8601 / RFC 3339 format of when the DVR start time (optional)
• dvr_max_duration: Amount of time in seconds the DVR sliding window will be open for (optional, this is bound by ttl. If longer than ttl nothing bad will happen, the sliding window will be controlled by ttl). Leaving this omitted or setting it to "0" means max dvr duration.

Examples

enable dvr on a stream with max duration

"playout_config": {
          "dvr_enabled": true,
          ...

enable dvr, start at 19:55 UTC time with max duration

"playout_config": {
          "dvr_enabled": true,
          "dvr_start_time": "2024-08-14T19:55:00Z",
          "dvr_max_duration": 0,
          ...

enable dvr, start at 13:30 PDT time and set the max duration to 1 hour

"playout_config": {
          "dvr_enabled": true,
          "dvr_start_time": "2024-08-30T13:30:00-07:00",
          "dvr_max_duration": 3600
          ...

enable dvr, start at 13:30 PDT time and max duration of 30 min

"playout_config": {
          "dvr_enabled": true,
          "dvr_max_duration": 1800
          ...

Additional notes

• With DVR enabled to fetch playlist with dvr simply add dvr=1 argument to playlist request. Same with embed URL.
• You can still fetch the non dvr playlist or embed url from a dvr enabled stream, just do not include dvr=1 in the requests.

Start time notes

• What happens if you request playout before start time? The playlist request will be empty, the embed player will also error out. Playout will work AFTER the start time.
• dvr_start_time will only work on playlist/embed urls with dvr=1, it will be ignored if you omit the argument from the urls.

[elv-serban]

For the Live Stream App

Playout Config

DVR

• Enabled - checkbox
  • Enable DVR playout - user can seek back in the live stream
• Start Time. - Date Time (default: not set)
  • Users can only seek back to this point in time. Useful for event streams. If not set, users can seek to the beginning of the stream
• Max Duration. - Time Duration (not sure how best to specify - maybe just in 'minutes')
  • Option: No Limit (default) 10 min 30 min 1 h 2h 4h
  • Users can only seek back only this many minutes. Useful for 24/7 streams and long events.

Recording Config

• Connection Timeout - Time Duration (not sure how best to specify - maybe in minutes)

  • Default 10 min
  • Options: 10 min (default) 30 min 1h 4h
  • The stream will remain active and wait for an input feed for this duration
  • metadata: recording_config.xc_params.connection_timeout

• Reconnection Timeout

  • Default 1 h
  • Options: No Reconnection (set to -1) 10 min 30 min 1h (default) 4h
  • If the input feed is disconnected, the stream will remain active and wait for a reconnection for this duration
  • metadata: recording_config.reconnect_timeout

[elv-gerald]

I found a bug.

dvr_start_time is optional. When I configured my stream to not include a start time I got an error

index-DOjALbTI.js:200 Unable to configure watermark TypeError: Cannot read properties of null (reading 'toISOString')
    at fEe.<anonymous> (index-DOjALbTI.js:254:162588)
    at Generator.next (<anonymous>)
    at gO (index-DOjALbTI.js:42:6173)
    at <unnamed flow> - runid: 830 - yield 3 (index-DOjALbTI.js:42:5992)
    at v (index-DOjALbTI.js:42:22998)

Here is how my form looked

Also happend if I want to disable dvr outright

[elv-zenia]

Fixed the above bug, plus the following:

• Make form subsections more discernible on the edit stream tab views
• Set connection timeout dropdown option to "Select connection timeout" when the current value doesn't match current options.

Updated prod-dev.

[elv-gerald]

I am testing on demo and I notice when I create/configure a new stream the reconnect_timeout is not being set in the config meta. I see it defaults to 1 hour in the form but it is not present in the config.

The path I am looking for the value resides in live_recording.recording_config.recording_params.reconnect_timeout

[elv-zenia]

Pushed a fix and updated demo and prod-dev.

[elv-gerald]

Today we also agreed to explicitly set reconnect_timeout and connection_timeout to 10 minutes (600 seconds) in the metadata for all created streams.