Stream ingest over RTS

This topic describes how to implement stream ingest over Real-Time Streaming (RTS).

How it works

Push SDK supports stream ingest over RTS (Real-Time Streaming), a protocol that uses real-time communication (RTC) to maintain stable stream ingest under poor network conditions. RTS is an alternative to Real-Time Messaging Protocol (RTMP)-based ingest.

After ingesting a stream over RTS, you can play it back using RTMP, Flash Video (FLV), or HTTP Live Streaming (HLS). ApsaraVideo Real-time Communication (ARTC) also supports RTS-based playback. For a comparison of RTS and RTMP ingest, see RTS vs. standard live streaming.

Important

The billing of RTS differs from standard streaming billing. For details, see Billing of RTS.

Prerequisites

Before you begin, complete the required setup in the ApsaraVideo Live console or via the ApsaraVideo Live API, including adding domain names, configuring CNAME records, and associating the domain names. For details, see Get started with ApsaraVideo Live.

Limits

RTS stream ingest has the following limitations:

Only mono audio is supported.
Only Low Complexity (LC) audio encoding is supported.
The audio sampling rate must be 48 kHz.
Automatic image ingest under poor network conditions is not supported.
Audio-only and video-only stream ingest is not supported.

Ingest a stream over RTS

Enable the RTS feature. For details, see Enable RTS.
Generate an ingest URL. For details, see Generate ingest and streaming URLs.
Pass the ingest URL to Push SDK. The URL must use the artc:// scheme.
```
mAlivcLivePusher.startPush(mPushUrl);
```