Live event timeline

    Follow

    A live event in the Screen9 platform follows a defined timeline consisting of four checkpoints, namely event register, start, end and recording available (as seen in the graphics below). Each checkpoint causes the live event to enter a new state which will be one of preview, live, copy and on-demand.

    These four checkpoints have the following properties:

    1. Registered
      • The event was just registered and will enter preview state between 1-8 hours (the so called preview lead time) before the event is scheduled to start.
      • Embed codes for the event are available to be embedded on a website.
      • External players will show a splash screen with the title of the event, a poster image and a count down to the start time.
      • At this point, preview lead time, start time and end time of the event can still be changed.
    2. Preview
      • The preview state starts 1-8 hours before the scheduled start of the event and no eariler than about 3 minutes after registering the event.
      • At this point a preview player shows up that displays the live stream as it is being sent to the streaming encoders.
      • Encoders can now connect to the ingest instances and start sending the video stream.
      • At this point, start time and end time of the event can still be changed.
      • Pressing "Preview now" will force the event into preview state for 30 minutes, but afterwards it will go back to the first state and wait for start time and preview lead time.
    3. Live
      • The event enters the Live state which is triggered by scheduled start time or by clicking “Start now” button.
      • Externally embedded players now start to display the stream.
      • Recording starts (if event is configured to be recorded).
      • At this point, the scheduled end time of the event can still be changed.
    4. Copy
      • Live event has ended (triggered by scheduled end time or by clicking “Stop now” button)
      • External player will stop playing the video and, if recorded, event enters copy state.
      • Recording stops (if event is configured to be recorded).
      • System sanity checks recorded video and copies to streaming servers.
      • If the event was recorded, the player will display a message that the event will be available in recorded version soon.
    5. On-demand (optional)
      • The player now behaves as a normal on-demand player and the recorded stream is available. The event is in on-demand state.
      • Optionally, a publish until time can be set at which the video will no longer be available.
    Was this article helpful?
    0 out of 0 found this helpful

    Comments