What We've Learned
After extensive experimentation with SRT, RTMP, FFmpeg, H.264 and H.265, our most dependable workflow has been SRT ingest followed by RTMP or RTMPS restreaming.
H.264 continues to provide the broadest compatibility in our testing. However, we've seen excellent H.265 results with compatible platforms such as GameChanger, sidelineHD and YouTube. We believe there is still considerable potential in HEVC.
Born From Real Streaming Challenges
streamHD began while broadcasting youth baseball, softball and flag football games. We needed to share one live event through several platforms without repeatedly configuring cameras or interrupting ongoing broadcasts.
Our equipment often consisted of a Mevo camera, an iPhone and a mobile hotspot. Unlike a studio connection, cellular bandwidth can change throughout an event.
We experimented with streaming protocols, codecs and media servers to find a practical way to deliver dependable video while keeping remote management simple.
Why SRT Ingest Works Best for Us
SRT, or Secure Reliable Transport, helps deliver video across unstable networks using configurable latency buffering and packet retransmission.
Cellular connections are particularly vulnerable to congestion, jitter and packet loss. SRT has performed well for us because it can recover certain lost packets without requiring the original camera to restart its broadcast.
SRT cannot overcome insufficient available bandwidth, but it has become our preferred protocol for sending video from the field to our server.
Our Preferred Streaming Architecture
SRT handles contribution streaming, while RTMP or RTMPS helps deliver broadcasts to compatible services.
We use FFmpeg passthrough forwarding whenever possible, avoiding unnecessary re-encoding. This conserves server processing resources and preserves the incoming video quality.
Stream copying still requires compatible codecs and enough outgoing bandwidth. It does not automatically convert H.265 into H.264.
H.264 vs H.265: Our Experience
We've tested both H.264 (AVC) and H.265 (HEVC) across different streaming configurations.
H.264 has proven more predictable across our mixed streaming and playback environments. Its broad compatibility makes it dependable when delivering to several destinations.
H.265 offers greater compression efficiency in suitable conditions, potentially preserving comparable picture quality at lower bitrates. This is especially interesting for sports streaming over mobile internet.
We've also found that established platforms such as GameChanger, sidelineHD and YouTube can deliver excellent H.265 experiences through their supported workflows.
We believe processing and delivery methods are an important part of that success. Platforms may repackage or transcode video for playback compatibility, although their exact internal processing is not always public. This remains our interpretation of our testing, not a claim about their proprietary systems.
Why We Continue Pursuing H.265
We refuse to let the quirks and nuances of streaming technology define what's possible. We continue experimenting with HEVC ingest, transport containers, LL-HLS and WebRTC playback.
Our objective is straightforward: keep the bandwidth efficiency of H.265 while achieving the reliability and smooth playback we've experienced with H.264.
We haven't perfected that combination, but each experiment brings us closer to understanding the limitations of different codecs, servers and playback implementations.
Streaming Destinations & Technical References
Different streaming services accept different protocols and codecs. We use official documentation alongside our own testing to understand these differences.
GameChanger
External-camera workflows and guidance for improving bandwidth and HEVC streaming quality.
Official documentation ↗sidelineHD
Supports H.264 and H.265/HEVC incoming streams with documented resolution and bitrate requirements.
Official documentation ↗YouTube Live
Documents H.264 with RTMP/RTMPS ingest and H.265 support through HLS ingest.
Official documentation ↗X (formerly Twitter)
Media Studio Producer provides encoder-based streaming with documented ingest requirements.
Official documentation ↗These independent services are not affiliated with or endorsing streamHD. Platform requirements may change over time.
Additional Technical Documentation
What Is streamHD?
streamHD is a subscription-based live restreaming service designed to simplify multi-platform broadcasting.
Subscribers can configure up to two incoming live sources and six outgoing destinations in total. OvenMediaEngine handles incoming streams and preview delivery, while FFmpeg handles compatible outgoing passthrough relays.
The dashboard includes a single OvenPlayer preview for selecting one source at a time using LL-HLS or WebRTC.
Our development is shaped by the same real-world broadcasting challenges that inspired the service.
Stream Once. Reach Everywhere.
Simple, affordable RTMP and SRT restreaming built from real experience.
Explore streamHD →