RTMP/RTMPS with OBS, vMix and encoders
Set up OpenRTMP ingest, enter server and key in OBS, use RTMPS, and understand legacy vs. Enhanced RTMP.
Enhanced RTMP (E-RTMP): HEVC, AV1 and modern codecs
Short answer: Enhanced RTMP – or E-RTMP extends classic RTMP/FLV with modern codecs and signaling. The current E-RTMP v2 specification includes HEVC/H.265, AV1, VP9, modern audio codecs, HDR and multitrack features. That does not mean every RTMP server or destination automatically supports them: sender, relay and receiver must all understand the feature being used.
Why did RTMP need an extension?
Legacy RTMP and classic FLV come from an era where H.264/AVC and AAC became the typical modern streaming codecs. Newer codecs such as HEVC and AV1 could not simply be represented cleanly by the old codec identifiers.
E-RTMP therefore extends media packets and uses mechanisms including FourCC signaling for additional codecs and metadata without replacing the entire existing RTMP ecosystem.
What does E-RTMP v2 add?
- Modern video codecs: including HEVC/H.265, AV1, VP9 and other specified codecs
- Modern audio codecs: including Opus, FLAC, AC-3 and E-AC-3
- HDR and expanded metadata
- Audio and video multitrack for concurrent tracks
- Reconnect Request for more modern reconnection workflows
- FourCC signaling for modern and selected existing codecs
Can I simply send HEVC to Twitch or Kick?
Not automatically. E-RTMP specifies how modern codecs can be signaled and carried over RTMP. A real end-to-end workflow depends on every hop:
- The encoder must generate the codec and publish it using E-RTMP.
- The ingest/relay must accept the E-RTMP variant and process it correctly.
- Any forwarding stage must preserve compatible signaling.
- The destination platform must accept that specific codec on its ingest.
Check compatibility first: “The server supports E-RTMP” does not automatically mean “every platform accepts HEVC/AV1.” Test the full path before a production stream.
How does OpenRTMP fit in?
IRL.com.de uses OpenRTMP / librtmp2-server for RTMP/RTMPS. That lets the platform follow modern RTMP development directly and integrate E-RTMP capabilities where they are useful and compatible in a real streaming path.
Classic H.264 workflows remain important: legacy RTMP continues to be a major compatibility mode.
E-RTMP vs. RTMPS
The names sound similar, but they solve completely different problems:
| E-RTMP | RTMPS | |
|---|---|---|
| Purpose | Extend RTMP/FLV functionality | Encrypt the RTMP connection with TLS |
| HEVC / AV1 | Can provide signaling | No codec extension |
| Encryption | Not the primary purpose | Yes |
For transport encryption, see RTMP vs. RTMPS.