SRT bonding and libsrt 1.5 in Nimble Streamer

Nimble Streamer has a wide SRT feature set which covers multiple capabilities. Our team has been an active contributor and a platinum member of SRT Alliance so we follow up closely with all updates.

At the moment Nimble uses libsrt version 1.4.4 by default when you install SRT package, however we continuously monitor new versions and features. So we wanted to give a try to the latest update.

libsrt 1.5

Now Nimble allows using libsrt 1.5 as an option.

If you want to try it with the latest Nimble build, use SRT package installation procedure with this command to install SRT package:

sudo apt-get install nimble-srt-1.5

You can always install "nimble-srt" package to get libsrt 1.4.4.

Bonding

With version 1.5.0, libsrt provide a new major feature set for Connection bonding.

Nimble Streamer allows enabling SRT bonding as provided by libsrt.

This capability is enabled by adding "srt-bonding-enabled" parameter with "true" in MPEGTS In setting for incoming SRT connection:

With this rule Nimble streamer will listen for incoming SRT stream 'in bond' on all the machine’s available interfaces “0.0.0.0” on the defined port “2022” (UDP).

If you’d like to specify the interfaces to bind additionally to the one defined in 'Local IP' and 'Local port' main input fields, please use the srt-group-nodes parameter.

Parameter syntax is “srt-group-nodes” with value like “ip1:port1, ip2:port2, ip3:port3” etc.
Example of value: "192.168.1.2:1101, 10.0.0.2:1100, 172.16.0.2:1100"

See the screenshot below

If any of our customers have SRT sender software or hardware capable of bonding, please feel free to try it with Nimble Streamer and let us know how it works, your real-life feedback is always valuable for us.

Learn more about SRT features of Nimble Streamer and SRT capabilities of other Softvelum products.

Follow us in social media to get updates about our new features and products: YouTube, Twitter, Facebook, LinkedIn, Reddit, Telegram