Real-time streaming

The rts plugin adds capability to consume Wowza Video Real-Time Streaming at Scale (RTS@S) streams, Wowza Video WebRTC streams, and Wowza Streaming Engine WebRTC streams.

Installation

Include the rts plugin next to the core player:

<script src="//cdn.flowplayer.com/releases/native/3/stable/flowplayer.min.js"></script>
<script src="//cdn.flowplayer.com/releases/native/3/stable/plugins/rts.min.js"></script>

Configuration

The RTS plugin is a Loader plugin which means it will add a special handler for the source types it handles.

Configuration depends on your stream type. See configuration examples from respective sections.

Wowza Video™ Real-Time Streaming at Scale

If you configure a src with type: "wowza/rts", the rts plugin will connect to Wowza RTS@S backend and consume the stream that you configure it to show. In addition to type you also need to configure streamName which you will get when you create the real-time stream in Wowza Video, either through the API or in the UI. subscriberToken is an optional parameter if you set a playback token in the Wowza Video configuration.

Example

flowplayer("#player", {
  src: {
    type: "wowza/rts",
    streamName: "<streamName>",
    subscriberToken: "<your playback token>"
   },
  token: "<your player token>"
})

Wowza Streaming Engine

If you configure a src with type: "wowza/webrtc", the rts plugin will connect to the Wowza Streaming Engine instance of your choice. You need to tell the player where your WSE instance is hosted and which stream to choose. You do that by configuring the following configuration properties:

• sdpUrl
• applicationName
• streamName

Example

flowplayer("#player", {
  src: {
    type: "wowza/webrtc",
    sdpUrl: "wss://zeezzrezrezr.streamlock.net/webrtc-session.json",
    applicationName: "webrtc",
    streamName: "myStream"
   },
  token: "<your player token>" 
})