Tag: #rtmp

#rtmp, Learning, Mentor, Technology, Streaming, Software Development, Video Codecs, Internet Protocols

Adobe, YouTube, and Twitch Collaborate with Veovera Software to Modernize RTMP Protocol

Veovera Software, a dedicated not-for-profit organization, has taken the lead in the mission to revamp the Real-Time Messaging Protocol (RTMP), aligning its specification with state-of-the-art technology. Backed by industry giants Adobe, YouTube, and Twitch, Veovera aims to modernize and enhance the RTMP specification, ensuring its compatibility with the latest advancements. The organization’s efforts reflect a commitment to improving the streaming experience and addressing the challenges posed by an outdated protocol. (Link to specs here)

Originally developed by Macromedia, RTMP emerged as a TCP-based protocol for high-speed transmission of audio, video, and data between servers and Flash players. It quickly became the standard for web-based streaming video and played a vital role in delivering Flash Video. While the delivery aspect of RTMP has diminished, its significance in ingestion remains strong. Many broadcasting platforms continue to rely on RTMP due to its speed and reliability, particularly for first-mile delivery. However, RTMP has not received any updates in over a decade, rendering it incompatible with current technologies such as support for modern codecs and HDR. This leaves companies dependent on RTMP with a crucial decision to make—should they invest in a costly transition to a different protocol or work towards enhancing the existing RTMP specification? The latter option presents a more manageable task and avoids disruptive overhauls.

It is remarkable that RTMP retains its relevance even after twenty-one years since its introduction alongside Flash Video. Veovera has taken the first step by incorporating support for AV1, VP9, and HEVC, and now focuses on defining additional capabilities promptly. Their objective is to refine the RTMP specification continuously, ensuring backward compatibility without disrupting the internet or existing tools. The lack of an organization to lead this effort and formally align the protocol within the industry has kept RTMP untouched for an extended period. The challenges involved are not solely technical but also encompass logistical aspects. Veovera aims to:

  1. Prevent protocol bifurcation and maintain a unified definition of RTMP.
  2. Enhance and modernize the RTMP/FLV specification by introducing new functionality.
  3. Collaborate with organization members and third-party solution providers to deliver implementations supporting the enhanced RTMP specifications.
  4. Engage with the RTMP community to promote and encourage RTMP enhancements.

Veovera emphasizes that there is substantial demand for this initiative across the industry, with solution providers relying on RTMP eagerly anticipating these enhancements. Despite its longevity, RTMP has remained relevant, having been employed by numerous longstanding streaming services. Even today, major platforms and services such as Google, YouTube, Twitch, PlayStation, Meta, OBS, FFmpeg, VideoLAN, TikTok, and others incorporate RTMP into their workflows.

Veovera has already enhanced the RTMP specification by introducing popular video codecs like VP9, HEVC, and AV1. Looking ahead to their roadmap for 2023, Veovera plans to further enhance video codec updates by integrating widely-used audio codecs. Key contenders for integration include Opus, FLAC, AC-3, and E-AC-3. Additionally, Veovera aims to specify more features for RTMP, including support for a seamless reconnect command and other capabilities. These enhancements will likely result in lower latency and improved content quality. Consequently, RTMP is poised to remain relevant for many years to come, serving as a reliable foundation for streaming content.

Bandwidth, Best Practices, Career, Digital Platforms, Mentoring, Technology

Video Streaming Protocols: RTMP, RTSP, SRT, & NDI: How They are Consumed

RTMP, RTSP, SRT, and NDI are all different protocols used for streaming audio and video content over the internet. Each protocol has its own unique features and advantages. In this response, we’ll explore what each protocol is, how it works, and how it’s consumed.

RTMP (Real-Time Messaging Protocol) is a proprietary protocol developed by Adobe. It’s commonly used for streaming video content on platforms like YouTube and Twitch. To use RTMP, you need a video encoder, which captures the audio and video content and compresses it into a digital format. The encoded content is then sent to a streaming server, which distributes the content to the end-users. RTMP has been widely used in the past, but it’s gradually being replaced by more modern protocols like SRT and NDI.

RTSP (Real-Time Streaming Protocol) is an open-source protocol used for streaming audio and video content. It’s commonly used for security cameras and other surveillance systems. To use RTSP, you need an RTSP server, which stores the audio and video content and distributes it to the end-users. RTSP is widely used in the security industry because it supports real-time streaming and is compatible with a wide range of devices.

SRT (Secure Reliable Transport) is an open-source protocol that was designed to address some of the issues with RTMP. SRT is a low-latency protocol that’s optimized for live streaming. It’s designed to work over unreliable networks, which means that it can deliver high-quality audio and video content even in poor network conditions. To use SRT, you need an SRT encoder, which compresses the audio and video content and sends it to an SRT receiver, which decodes the content and distributes it to the end-users.

NDI (Network Device Interface) is a proprietary protocol developed by NewTek. It’s commonly used for streaming video content in the professional production industry. NDI allows you to add multiple video sources to a single network and stream them to multiple devices. To use NDI, you need an NDI-enabled device, such as a camera or a video encoder. The NDI-enabled device sends the audio and video content to an NDI receiver, which decodes the content and distributes it to the end-users.

In terms of consumption, each protocol can be consumed using a variety of devices, such as smartphones, tablets, laptops, and smart TVs. To consume RTMP content, you’ll need a media player that supports the protocol, such as Adobe Flash Player or VLC Media Player. To consume RTSP content, you’ll need an RTSP client, such as IP Camera Viewer or VLC Media Player. To consume SRT content, you’ll need an SRT player, such as Haivision Play or VLC Media Player. To consume NDI content, you’ll need an NDI-enabled device, such as an NDI-enabled camera or an NDI-enabled video encoder.

In conclusion, RTMP, RTSP, SRT, and NDI are all different protocols used for streaming audio and video content over the internet. Each protocol has its own unique features and advantages. The choice of protocol depends on the specific needs of the user, such as the type of content being streamed and the quality of the network connection.