WebRTC capabilities

Ingest WebRTC into Nimble Streamer

WebRTC is a big stack of technologies solving problems related to live streaming in various use cases and scenarios.

Nimble Streamer provides capabilities for easy ingest of live streams from any browser for further trasformation and delivery.

WebRTC in 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 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's a standard with Internet Draft status and it's already used by various WebRTC products.

Nimble Streamer uses Pion implementation of WebRTC API.
Special thanks to Sean DuBois and all Pion contributors.

Setup and usage

Currently WebRTC is available in Nimble Streamer only on Linux.

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

  1. Sign up for WMSPanel account or log in if you have it.
  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, the price starts from 30 USD per month.
    • Create Live Transcoder license and subscribe for it. It 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 to make it work.
  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:

Take a look at some of 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:

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

Easy installation and upgrade

Nimble Streamer can be installed in a couple of small steps and upgraded to the latest version by running two or three simple commands in console.

Let us know if you need any help and search through our documentation to find more information.

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.