Skip to content

StreamLive Overview โ€‹

Updated

StreamLive is a service that receives a live origin, processes the video / audio, and sends it to the specified destination. Multiple resolution outputs can be created from a single origin, and this guide delivers the HLS output to StreamPackage.

Role of each console menu and the task order โ€‹

Console menuItems configured hereNext step connected
Security GroupAllowed list of push public IPsSelected when creating an input
InputInput protocol, origin address or push address, authentication, A/B inputsConnected as the input of a channel
ChannelInputs to connect, output groups, transcoding, start / stop, monitoringOutput to StreamPackage / SRT listener / COS, etc.
Asset โ†’ WatermarkWatermark assets to useReferenced in the video transcoding settings of the channel
Asset โ†’ Graphic OverlayGraphic assets used for screen compositingUsed in the graphic overlay configuration of the channel
Usage StatisticsUsage by periodUsage review based on channel execution / output configuration

Transcoding templates and output groups are not independent video delivery menus, but items connected within the channel configuration. In the basic exercise, proceed in the order security group โ†’ input โ†’ channel โ†’ output group โ†’ per-resolution output.

Choosing the input protocol โ€‹

Origin connection methodType to selectWhat to prepare
RTMP push from an encoderRTMP_PUSH / RTMPS_PUSHInput security group, application name, stream name, required authentication
Pull from an RTMP originRTMP_PULLAccessible origin URL and required authentication
Pull from an HLS originHLS_PULLOrigin playlist URL and access policy
File originMP4_PULLAccessible MP4 origin URL
RTSP originRTSP_PULLOrigin RTSP address
SRT receiveSRT_PUSH / SRT_PULLAddress and SRT settings matching the push / receive role
RTP / UDP equipmentRTP_PUSH / UDP_PUSH / RTP-FEC_PUSHMatching transport method of the equipment and the input, network allowance

The input fields differ for each type. Check the creation form and the push address connection in input configuration.

Processing flow โ€‹

1080p and 720p outputs are each configured from the 1080p 30fps input. The player selects an output according to the provided quality list and the playback environment.

From one origin to two resolutions

Components โ€‹

ComponentRole
Security GroupAllows the push IPs that can connect to PUSH inputs
InputReceives external video signals or pulls the origin
ChannelExecution unit that bundles inputs / processing settings / outputs
AV TemplateDefines video / audio encoding parameters
OutputTemplate to use and individual output settings
Output GroupOutput type and destination configuration

Input access policy and processing configuration

Security groups are used for the input access policy, and templates are used for the encoding settings of channel outputs.

Relationship between channels and outputs โ€‹

Internal channel configuration

When creating 1080p and 720p, add two outputs and specify the shared video / audio template of the corresponding quality for each. If multiple audio tracks are needed, consider configuring separate audio / video templates.

Choosing the output type โ€‹

Output group typeDestination and purpose
HLS / DASHDelivered to the specified destination with HTTP PUT
HLS_STREAM_PACKAGE / DASH_STREAM_PACKAGEDelivered to a StreamPackage channel in the same account
HLS_ARCHIVE / DASH_ARCHIVESaves the live output to COS
M2TSSent to the destination with the SRT protocol
FRAME CAPTUREOutputs frame images at regular intervals

SRT is a transport protocol, and M2TS is the output group type of this configuration.

Basic configuration order โ€‹

  1. Prepare the destination StreamPackage channel.
  2. Create a security group that allows the push IP and an input.
  3. Connect the input to the channel.
  4. Specify the StreamPackage destination in the output group.
  5. Set the per-resolution outputs and transcoding parameters.
  6. Start the channel and push the origin.
  7. Check the input / output status and the final video / audio playback.

Execution status and check criteria โ€‹

IDLE is the standby state and RUNNING is the running state. Check the input metrics / output status / playback list / actual playback together.

Editing a running channel requires stopping it. Stopping a production channel affects the service, so keep it separate from test channels and schedule a maintenance window.

Next steps โ€‹

Official documentation โ€‹

Built with VitePress ยท Deployed on Tencent EdgeOne Pages