[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-21。"],[],[],null,["# Overview of the Live Stream API\n\nThis page provides an overview of the Live Stream API. The Live Stream API\ntranscodes mezzanine live signals into direct-to-consumer streaming formats,\nincluding Dynamic Adaptive Streaming over HTTP (DASH/MPEG-DASH), and HTTP Live\nStreaming (HLS), for multiple device platforms.\n\nYou first create an input endpoint, then create a channel resource that\ntranscodes the live SRT or RTMP input signal into an HLS or DASH output stream.\nOutput streams created by the Live Stream API are saved to Cloud Storage\nbuckets. You can then configure a Cloud Storage bucket as a backend for\nMedia CDN.\n\nFeatures\n--------\n\nThe Live Stream API includes support for the following features:\n\n- Automatic infrastructure provisioning\n\n- Integration with Cloud Storage, Cloud Audit Logs, and Google Cloud\n infrastructure\n\n- Configuration of a backup input stream for redundancy\n\n- Live to video on demand (VOD)\n\n- Content encryption\n\n- Slates (image and video)\n\n### Supported inputs and outputs\n\nThe following tables show the supported input and output formats for the\nLive Stream API.\n\nSee the\n[supported configurations for content encryption](/livestream/docs/how-to/encrypt-content#supported-configurations).\n\nAccess control\n--------------\n\nThe Live Stream API access control model is based on\n[Identity and Access Management (IAM)](/iam/docs). IAM's fine-grained\npermissions give you control over what can be done with media data, and by whom.\n\nConcepts and terminology\n------------------------\n\nThis section provides a glossary of useful terms for working with the\nLive Stream API.\n\n### Channels\n\nA channel is a resource that ingests the input stream through an input endpoint,\ntranscodes the input stream into multiple renditions, and publishes output live\nstreams in certain formats in the specified location. You can include a primary\nand backup input stream in the same channel.\n\n### Channel events\n\nA channel event is a sub-resource of a channel that executes operations on a\nchannel resource without needing to stop the channel. The following channel\nevents are supported:\n\n- Create ad break markers\n- Mute/unmute the live stream\n- Insert a slate into the live stream\n- Return to program (live stream)\n- Switch the channel input\n\n### Encoder\n\nAn encoder is a program used to send input streams, such as `ffmpeg`.\n\n### Input endpoints\n\nAn input endpoint is an endpoint to which your encoder sends your input stream.\nYou can use the input endpoint to specify configurations for your stream, such\nas input resolution, input type, and video cropping.\n\nAn input endpoint consists of either an RTMP or SRT URI that looks like the\nfollowing: \n\n```\nrtmp://192.0.2.1/live/STREAM_ID\n``` \n\n```\nsrt://192.0.2.1:4201?streamid=STREAM_ID\n```\n\nwhere \u003cvar translate=\"no\"\u003e\u003ccode translate=\"no\" dir=\"ltr\"\u003eSTREAM_ID\u003c/code\u003e\u003c/var\u003e is a string such as\n`b8ebdd94-c8d9-4d88-a16e-b963c43a953b`."]]
