Transport layer, the server hostname is not strictly required to initiate theĬonnection however, it is required for authentication with our servers. The server that the ingestion URL specifies. Use your preferred socket library to create an SSL/TLS connection to port 443 at If you support dual ingestion, the backup address In the response, theįield specifies the RTMPS URL. If your encoder already uses the YouTube Live API, then the process for gettingĪn RTMPS ingestion URL is similar to the one for RTMP. The multimedia stream must be sent with RTMPS that is, using RTMP over an.The connection must be made to port 443 on the ingestion server.The path must be a valid YouTube Live RTMP application name.The server must be a valid YouTube RTMPS ingestion endpoint.Each part of the connection URL ( :///) must be.Sending RTMPS to YouTube Live has a few prerequisites: RTMPS is a good choice for most ordinary user content, especially if it requiresįor an overview of the different ingestion protocols that YouTube Live Streaming Vendors who want to add support for RTMPS to encoders that already support RTMP. RTMPS is a regular RTMP (RealTime Messaging Protocol) video stream This document explains how to use RTMPS to stream live data on YouTube from anĮncoder.
0 kommentar(er)
