August 14, 2017

Setting UDT in Nimble Streamer

UDP-based Data Transfer Protocol (UDT) is a high-performance data transfer protocol designed for transferring large amounts of data over high-speed wide area networks.

UDT is designed for extremely high speed networks and it has been used to support global data transfer of terabyte sized data sets. Concurrent UDT flows can share the available bandwidth fairly, while UDT also leaves enough bandwidth for TCP.

Nimble Streamer has full support for UDT:
  • Both Push and Listen delivery modes are supported.
  • Both Listen and Pull receive modes can be used to get UDT streams for further processing.
  • Rendezvous mode for sending and receiving is supported.
  • Multiple streams can be sent via single UDT channel.
  • Mux rate can be set correctly - Nimble Streamer has 100% PCR accuracy, 0ns PCR drift and PCR interval <20 ms according to StreamGuru. This is typically used for precise testing of channel throughput.
Using Nimble Streamer transmuxing engine, you may create any supported live protocol output from UDT and receive any of them to create UDT.

Let's see how UDT can be enabled and used in Nimble Streamer.

August 8, 2017

Use SLDP player latency tolerance against environment glitches

Our company keeps improving new real-time low latency protocol called SLDP. It provides quick start and sub-second delay for live streaming delivery. You can find protocol overview in this page and some basic setup and usage described in this article.

One of the features of SLDP is an ability to keep up with live stream without delays regardless of environment glitches. Let's take a look at this capability more closely.

August 4, 2017

Using offset to decrease start time in SLDP player

Recently we introduced new real-time low latency protocol called SLDP. It provides sub-second delay for live streaming delivery for the cases when it's truly important. Some basic usage of SLDP protocol is described in this article.

One of the key features of SLDP is a quick start of a stream on a client side. Typically the best way to reduce start time is to set GOP size to 1 second or less. This can be done with any transcoder, e.g. Nimble Live Transcoder. This will increase bandwidth however so you need to reach some balance between start time and traffic consumption.

So if you cannot make that GOP size reduction, SLDP has an offset player parameter which allows affecting the start-up behavior. The following description shows how you can use it for your use cases.

Typically, a playback starts with a key frame of each GOP (group of pictures) as the player cannot start decoding and processing without the key frame information. This means a delay between the start of connection and the start of the playback and it may be several seconds, depending on the encoding settings - all this time a viewer will see a black screen waiting for a picture. This is what needs to be avoided, let's see how this can be avoided.

July 27, 2017

VP8 and VP9 support in SLDP HTML5 player

Our customers keep adding our new real-time low latency protocol SLDP into their streaming workflows as it allows sub-second delay for live streaming delivery. Some basic usage of SLDP protocol is described in this article which describes typical usage scenarios.

People ask us about adding new capabilities into SLDP technology. One of them is adding VP8 and VP9 codecs - those are open and royalty free video coding formats developed by Google. Nimble Streamer Live Transcoder now supports these protocols transcoding in addition to already supported VP8/VP9 transmuxing feature set.

SLDP is codec-agnostic protocol so in order to have full support for VP8/VP9 from source to the viewer,  we only needed to add it into our HTML5 player.

So today we'd like to announce that VP8 and VP9 support was added into SLDP HTML5 web player. This type of playback fully depends on platform support, so it can be currently played in Chrome, Firefox and Opera and possibly in Microsoft browsers over time.

You can use SLDP for streaming in various bitrate modes. First you can stream single-bitrate VP8/VP9 if you know your target audience can play it.

Another option is to create ABR group to include streams encoded with both H.264 and VP8/VP9. In this case our SLDP HTML5 player will choose stream with H.264 codec if target browser or platform doesn't support VP8/VP9 playback. That would give you capabilities for flexible delivery of your content to multiple platforms.

We'll be adding other codecs support per our customers' requests so please contact us to get help or suggest new features.

July 24, 2017

Publishing stream to Periscope

RTMP republishing is widely used by Nimble Streamer users to deliver live streams to various types of destinations, including other media servers, CDNs, YouTube or Twitch.

Periscope live streaming platform also takes RTMP streams as input so our customers use that as a target too. As Periscope requires some additional stream setup, we've created a dialog in our UI to cover that use case.

As a source for your stream you can use any delivery method supported by Nimble Streamer.


Once the input stream is taken by Nimble, you can perform a setup for publishing it to Periscope.

July 18, 2017

Transcoding VP8 and VP9 in Nimble Streamer

VP8 and VP9 are open and royalty free video coding formats developed by Google. Nimble Streamer Live Transcoder now supports these protocols transcoding in addition to already supported VP8/VP9 transmuxing feature set.

Live Transcoder allows performing both decoding and encoding.

To receive VP8 and VP9 for transcoding, Nimble Streamer allows processing RTSP from published and pulled sources. The result stream can be delivered using RTSP protocol as well.