Are you tired of struggling with complicated setups and technical jargon when trying to create a public internet WHIP service for OBS? Look no further! In this comprehensive guide, we will walk you through the process of effortlessly building your own WHIP service using the Oryx, all with just a single click. Say goodbye to the complexities of security, authentication, and WebRTC, and embrace the future of sub-second live streaming and seamless OBS-RTC room connections.
HEVC, or H.265, can reduce bandwidth usage by about 50% compared to the widely used H.264 codec, which has the best compatibility. Over the past 10 years, HEVC has grown slowly because a new codec needs an ecosystem to support it, including decoders and device hardware. Now, both RTMP and FLV support HEVC in OBS and FFmpeg, which are the standard tools in the live streaming industry.
OBS now features WHIP support, with the patch having been recently merged. This enables various new functions and possibilities with OBS WHIP, as the latency drops from 1 second to 200 milliseconds.
Without OBS WHIP, you can employ RTMP+WebRTC for live streaming, which results in a latency of approximately 500ms. However, by using OBS WHIP, you can achieve low-latency live streaming with a latency of around 200ms.
Written by Winlin, chundonglinlin
OBS 29.1 supports HEVC via RTMP, so you can do HEVC live stream by OBS and SRS now.
There is a new specification for HEVC via RTMP, please see Enhanced RTMP.
This specification defines a new codec ID for HEVC, which uses fourCC hvc1,
both OBS and SRS support it.