RTMP or Real-Time Messaging Protocol is an old communication protocol made by Macromedia for Shockwave Flash Media Player (later bought by Adobe and named Flash Media Player). It's availability and reliability through the years has cemented it as the de-facto transport for live video, but it still has some drawbacks. It's main drawback is it's codec support, which is limited to H.264, Screen 1 & 2, VP6, and two different H.263 implementations. H.264 is the newest and best out of the bunch, with the others having their hay-day in the late '90s and early 2000s. This means that modern high-quality codecs, such as H.265 (HEVC), AV1, or VP9, are not supported. Another drawback is the fact that it was part of the Flash family, which was discontinued in 2020, this means that RTMP will never be updated to support the aforementioned modern codecs.
SRT or Secure Reliable Transport is a modern communication protocol made by Haivision. It's the new kid on the block, with ultra reliability and extensibility being it's main calls to fame. It's been adopted by several media giants such as Sky News and NBC Sports and has several attractive features. It's agnosticism, for one, means you can stream whatever codec you want using SRT (as long as the target supports it!). It can even be used on networks with high packet loss without needing to compromise on reliability. It also has high throughput, meaning that it can be used effectively with high bitrate video, which translates to higher quality and resolution.
Why does Brime not support WebRTC or FTL?
WebRTC is a fantastic low-latency protocol made by Google, and while it supports a myriad of codecs with more being added every year it's main drawback is the fact that it's designed for video chatting and not live-streaming. Since it's designed for communication it has some human-specific limitations, such as allowing video quality to suffer in order to help preserve audio transmission. It also by default only allows for lower bitrate video because it's designed for lower-power devices and unreliable mobile networks.
FTL was an experimental protocol made by Mixer for their live platform. It was designed to be super low latency but with that came a lot of reliability drawbacks. Namely, users with high packet loss couldn't use the protocol at all, and users with some packet loss would wind up with terrible video quality. It also only supported H.264 for video and Opus for audio (which is designed for the human voice and not desktop audio or music). The OBS project has also marked FTL as deprecated, with it planned being removed sometime in the future.
|Modern Codec Support||Actively Supported||Reliability|