Efficient tools to build your streaming infrastructure

Nimble Streamer WebRTC Capabilities

WebRTC is supported in Nimble Streamer with WHIP signaling

Highlights for Nimble Streamer and WebRTC

WebRTC

Nimble Streamer is a powerful streaming solution that provides capabilities for easy ingestion of WebRTC live streams. The Nimble Streamer software uses the WebRTC-HTTP ingestion protocol (WHIP) for signaling and Pion implementation of WebRTC API. Nimble allows for the ingest of H.264, VP8, VP9 video, and Opus audio input, as well as H.265/HEVC video from Apple devices. A JavaScript publisher library is available for adding streaming capabilities to web pages. WebRTC input is processed and can be delivered to end users via multiple protocols such as HLS, Apple Low Latency HLS, MPEG-DASH, RTMP, SLDP, RTSP, Icecast, and MPEG-TS (UDP and TCP), along with re-publishing where applicable. WebRTC ingestion can be transcoded into NDI output with ultra-low latency or transmuxed directly into MPEG-TS UDP multicast with low latency and no need to transcode.

Specifications and Details Regarding WebRTC and Nimble Streamer

Nimble Streamer has the following capabilities.

  • Ingest of WebRTC live stream into Nimble Streamer.
  • WHIP is used for signaling.
  • H.264, VP8, VP9 video and Opus audio input.
  • H.265/HEVC video from Apple devices.
  • JavaScript publisher library allows adding streaming capabilities to your web pages.
  • Publisher demo page with sample client is also available.

Signaling is an important part of the WebRTC stack because it defines how a client connects to the host or to another client.
Nimble Streamer uses WebRTC-HTTP ingestion protocol (WHIP) for signaling. It is a standard with Internet Draft status and it's already used by various WebRTC products.

Nimble Streamer uses Pion implementation of WebRTC API.
Softvelum extends a special thanks to Sean DuBois and all Pion contributors.

Setup and Usage

To start using WebRTC in Nimble Streamer, you need to do the following:

  1. Sign up for WMSPanel account or log in.
  2. Install Nimble Streamer or upgrade it to latest version.
  3. If your source content differs from your viewers, e.g. you ingest Opus while your viewers need AAC, or you ingest VP8 while you need H.264 output, then you need to use Live Transcoder.
    • Subscribe for WMSPanel account. Currently the price starts from 30 USD per month.
    • Create Live Transcoder license and subscribe for it. This currently costs 50 USD per month per server.
    • Install Live Transcoder package and register the license on the server with Nimble Streamer instance.
  4. Follow full WebRTC setup instructions.
  5. Try our demo publisher page to test the ingest.
  6. Use WebRTC JavaScript library to add publishing with WHIP to Nimble Streamer.

Once WebRTC input is processed, it can be delivered to end users via multiple protocols:

Larix Broadcaster supports WebRTC output:

  • Video is encoded with H.264, audio is encoded with Opus.
  • WHIP signaling is used for communication.
  • User can stream via multiple simultaneous connections with any combination of WebRTC, SRT, RTMP, RTSP and RIST.

Please take a look at some WebRTC transformation and delivery scenarios below.

WebRTC ingest is transcoded into NDI output with ultra-low latency:

WebRTC is transmuxed directly into MPEG-TS UDP multicast with low latency and no need to transcode:

Ingesting WebRTC from Larix Broadcaster into Nimble Streamer from iPhone and pass through Opus audio via SLDP

We keep working on improving WebRTC feature set and new features are coming out later on.

Please contact our team if you have any questions or suggestions regarding WebRTC functionality.



Install Nimble Streamer now
Install now
Free trial of WMSPanel included