Please add SRT (Secure Reliable Transport) support for ingress traffic. https://github.com/Haivision/srt
@darthclide gotcha.. so can you expand on your question better?
"I tried asking on belabox discord, but so far no bites on my request for a walkthrough on how to set up bonded SRT between a raspberry pi 4 and OBS Studio running on a Windows 10 computer."
Because from what I see here you are asking to use a Raspberry Pi 4 to bond SRT and send it to OBS Studio.. and the only way I know is to use SRTLA.. so I figured you were talking about audio/video.. my bad..
You can also use belabox with a phone if you plan to use more than 3 connections it has a built-in RTMP Server that you can use as a source to use with SRTLA to send to the cloud/hosted server.. (vs using IRL Pro)
Using your phone for streaming is going to suck the battery, you'll maybe get 1-2 hours depending on if you are using IRL Pro to bond connections or not.. so you're going to need some type of power source to extend past that timeframe.. unless you plan to stream for that short of a period.. then you'll be okay..
@b3ck Yes, your whole post is talking about encoding when all I want is a bonder running on an ARM device. Specifically with the hardware/software I mentioned in the previous post. Not everyone can afford a jetson nano (or any "cheaper" alternatives). And not everyone wants a cable to be plugged into their phone from the starting of the stream to the finish. (I assume unplugging things and plugging them back in does not go over well with srtla mid stream)
@darthclide A walkthrough? SRTLA is just apart of the belabox software, which runs on the Nvidia Jetson Nano and now more recently a few rk3588 boards, checkout: https://belabox.net/rk3588 for more info on that, the board has to be able to encode H.265 (HEVC), can the Raspberry Pi 4 do that?, there is also an Open-Source Github Repository for SRTLA which you can build a receiver from, check that out here: https://github.com/BELABOX/srtla.
I would assume that it won't work on the Raspberry Pi 4 otherwise Rational would've already made the belabox software for that board.
@b3ck Yes obviously srtla would not provide internet. Sadly this does not address my concerns of battery drain + requiring a cable to be constantly plugged into the phone.
I tried asking on belabox discord, but so far no bites on my request for a walkthrough on how to set up bonded SRT between a raspberry pi 4 and OBS Studio running on a Windows 10 computer.
@darthclide please keep in mind that SRTLA is an audio/video protocol, it allows you to wrap audio/video with pretty much any codec, not an "all traffic" bonding solution like "openmptcprouter".
RE:Not to mention the clunkiness of requiring a usb cable plugged into your phone 24/7; how will you charge your phone for those 24/7 streams?
Also you can have everything in a small hydration backpack.. or satchel, or fanny pack and use a 6FT USB Type-C Extension Cable, see example here; https://cdn.discordapp.com/attachments/583911490789310464/1150469582260281499/20230901_111045.jpg
Using the USB Hub like in the example above only adds on (1) Connection, without all of that you will still be able to use (2) Connections SIM and WiFi.
And yes I hear you it would be nice to be able to bond all carriers in the US on one device which would support all TCP and UDP traffic and provide (1) single hotspot that your phone could connect to.. but so far that device doesn't exist.. and that's why there is IRL Pro.. it's better than a single SIM phone stream.
@b3ck A decent solution yes, but I would be more excited to have 3 WiFi connections bonded because then you wouldn't have to worry about weird powered-usb-hub passthrough issues, as well as intense battery drain on your phone due to sim usage. Not to mention the clunkiness of requiring a usb cable plugged into your phone 24/7.
An even better solution would be someone getting SRTLA to work on any router/arm device. This way you could buy a router that allows 3+ usb ethernet connections, power it with a 12v portable battery, and never have to worry about power pass through problems ever again.
I look forward to the day I can replace openmptcprouter with a piece of software that does SRT bonding which can also be updated. (Many SRT options out there are often multiple versions behind. I want to be on the latest version released on github the second it releases)
Please, after 4 years....
If you're an Android IRL Streamer; use IRL Pro, you can bond 3 connections (SIM, Wi-Fi, USB/Ethernet using a hub with pass-through charging.. that means if you're in the USA you can have all of the major networks (TMO, ATT and VZN)..
And if you don't want to use OBS or a 3rd party cloud service you can even bond these connections "straight" to Twitch.. Technically it goes to IRLToolKit over SRTLA(H.265), then to Twitch via RTMP(H.264).
What is SRTLA? It stands for Secure Reliable Transport Link Aggregation;
SRT transport proxy with link aggregation for connection bonding.. It splits the audio/video feed over however many connections you have to a server which then combines them and sends it to its final destination whether it be an SRT server or create a custom route to an RTMP ingest.
Helpful IRL Streamer Links:
IRL Pro: https://irlpro.app
Stream Buddy: https://play.google.com/store/search?q=stream+buddy&c=apps
It's stupid Twitch still hasn't done anything about SRT (and AV1). For those who don't know SRT is probably the most reliable streaming protocol today. It can recover from 15% packet loss with the right configuration with no degradation in audio/video quality.
SRT is already widely used in the broadcast industry in OB Vans where internet signals (satellite/5G) can be spotty.
There's also a lot of people nowadays on Twitch streaming from their cellphones in all kinds of places where good internet connection is not a guarantee. SRT is literally made for these uses cases.
Plus it has encryption with no added latency.
I know Twitch can't stream SRT to viewers but this part is OK because Twitch has a massive reliable CDN behind them to take care of this, the important part is the Streamer->Twitch and RTMP just isn't reliable enough for IRL streamers.
SRT would make IRL streaming feasible for more people, and improve the viewer experience by having more reliable, higher quality streams. The implementation of SRT support is an important step in future-proofing Twitch, in particular in light of the more fierce competition. Also, H.265 ingest should be considered when implementing SRT support, as they complement each other.
This will help with multiple audio streams we want to do
To make IRL streaming more accessible (aka removing the requirement for a "streaming backpack" that has 4g bonding), Support the SRT protocol natively to counter packet loss for unstable networks such as 4g.
cant vote but please add srt support fot twitch, i have packet loss and i want to stream
Can't vote either, but I'm in support of this.
Agreed, this should be supported. Especially after Mixer closed down, there hasn't been another site with a low-latency protocol like this. It's why I gave up streaming after they shut down, instead of moving to Twitch, as Twitch's latency is atrocious, even in "low latency" mode.
Also, why the hell can't I vote for this? It's greyed out.