Draft:Enhanced RTMP

{{AFC submission|d|adv|u=Wozloz|ns=118|decliner=Caleb Stanford|declinets=20250328013532|ts=20250314175734}}

{{AFC submission|d|npov|u=Wozloz|ns=118|decliner=Caleb Stanford|declinets=20250312224446|small=yes|ts=20250311232659}}

{{AFC submission|d|reason|Please add a lead section. Please add inline citations to every sentence in the article.|u=Wozloz|ns=118|decliner=Caleb Stanford|declinets=20250310073347|small=yes|ts=20250304220725}}

{{AFC comment|1=Just renaming "The specification includes several key advancements" to "The specification outlines" does not mean you have addressed the suggestion. The article needs a more careful rewrite and the text needs to be organized into sections. Some of the text in the lead could go under a "History" section for example. All the features use the same primary source [1] (the documentation) and it might be easiest to just cut them. Please rewrite the article to focus on what is covered about the topic in independent, reliable sources. Caleb Stanford (talk) 01:35, 28 March 2025 (UTC)}}

{{AFC comment|1=Please add inline citations to every sentence in the article that is not cited. E.g., "Multichannel Audio Configurations: Support for multichannel audio to enhance auditory experiences without compromising existing setups," "Multitrack Capabilities", etc.

Please fix minor formatting errors: capitalization should generally not occur mid-sentence, as in "Adaptive Bitrate Streaming" and should not occur in section headings like "Licensing and Availability". A space should not occur prior to a citation, there are spaces before citations [1], [2], and [3][4].

Please rewrite the article to ensure it is written in a neutral tone, without promotional language. Some examples: "RTMP continues to be widely used for live-streaming ingestion and remains a standard protocol for broadcasters." (to replace: show, don't tell!) "The specification includes several key advancements:" This part is purely WP:PROMO, the encyclopedia article exists to introduce the topic, not to sell its key advances or features, so it should be a balanced summary of the aspects (including both features and drawbacks) as covered in reliable, independent sources. Caleb Stanford (talk) 22:44, 12 March 2025 (UTC)}}

----

{{Short description|E-RTMP extends RTMP with new features}}

{{Draft topics|internet-culture|software|computing|technology}}

{{AfC topic|stem}}

{{Draft article}}

Enhanced Real-Time Messaging Protocol (E-RTMP) is an open-source streaming protocol that extends Real-Time Messaging Protocol (RTMP) and Flash Video (FLV) while maintaining full backward compatibility.{{Cite web

|url=https://veovera.org/docs/enhanced/enhanced-rtmp-v2

|title=Enhanced RTMP (V2)

|last=Lozben

|first=Slavik

|publisher=Veovera Software Organization

|date=21 January 2025

|access-date=1 March 2025

}} E-RTMP introduces support for additional codecs, multichannel audio, multitrack streaming, expanded metadata support, and nanosecond timestamp precision.

RTMP was originally developed as part of Adobe Flash to enable real-time streaming of audio, video, and data over the internet. While Adobe Flash Player reached its end of life in December 2020, RTMP continues to be used for live-streaming ingestion and remains a standard protocol for broadcasters.{{Cite web

|url=https://www.adobe.com/products/flashplayer/end-of-life-alternative.html

|title=Adobe Flash Player EOL General Information

|publisher=Adobe

|date=13 January 2021

|access-date=3 March 2025

}}

Veovera Software Organization (VSO), a non-profit organization, published the E-RTMP specification as an extension of RTMP while maintaining backward compatibility.{{Cite web |title=Veovera Software Organization (VSO) |url=https://veovera.org/ |access-date=3 March 2025 |publisher=Veovera Software Organization}} VSO worked with industry stakeholders to create E-RTMP, incorporating features designed to support current streaming technologies. The specification outlines:

• Additional audio codecs: Introduction of codecs such as AC-3, E-AC-3, Opus, and FLAC, expanding the range of audio formats compatible with the protocol.
• Multichannel audio: Support for multichannel audio while maintaining compatibility with existing setups.
• Additional video codecs: Introduction of codecs such as VP8, VP9, HEVC and AV1, including support for HDR.
• Video metadata: Introduction of {{code|VideoPacketType.Metadata}} to accommodate a broader range of metadata types.
• FourCC signaling: Introduction of FourCC signaling for the additional codecs mentioned above, as well as legacy codecs such as AVC, AAC, and MP3.
• Multitrack streaming: Support for audio and video multitrack functionality, enabling concurrent management and processing of multiple media streams, including:
• Adaptive bitrate streaming (ABR)
• Multi-language audio within a single FLV container
• Simultaneous camera angles for events and live broadcasts
• Multi-codec publishing, allowing encoding in multiple formats within a single stream and selecting codecs based on platform compatibility
• Timestamp precision: Nanosecond precision offsets for synchronization and compatibility across formats such as MP4, M2TS, and Safari's Media Source Extensions, while preserving RTMP’s original timestamp structure.

E-RTMP has been implemented by streaming platforms and has received contributions from technology companies.{{Cite web |last=Hu |first=Roger |date=17 September 2024 |title=Enhancing RTMP: The Journey to Modernize a Decade-Old Streaming Protocol |url=https://www.linkedin.com/pulse/enhancing-rtmp-journey-modernize-decade-old-streaming-roger-hu-yp7sc/ |access-date=2 March 2025}}