[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-09 (世界標準時間)。"],[],[],null,["# Best practices for the Live Stream API\n\nThis page contains a summary of best practices for the Live Stream API. If you\nare just starting out with the Live Stream API, refer to one of the\n[Quickstarts](/livestream/docs/quickstarts).\n\nUse the SRT protocol if possible\n--------------------------------\n\nWhen creating the input endpoint, there are two options for the source stream\nprotocol:\n[`RTMP_PUSH` and `SRT_PUSH`](/livestream/docs/reference/rest/v1/projects.locations.inputs#type).\nThe SRT protocol is preferred over RTMP because SRT is more advanced and\nprovides additional features such as the following:\n\n- Packet drop recovery\n- Forward error correction\n- Support for multiple audio elementary streams\n- Higher bandwidth\n\nThe choice of streaming protocol requires a proper encoder/transcoder that\nprovides that feature. Most professional-grade encoders support SRT.\n\nRecommended bitrates\n--------------------\n\nUse the following bitrates depending on the source resolution and framerate.\nHigher bitrates directly correlate to higher quality.\n\nFor the output channel resolution and bitrate, depending on the input\nresolution/frame rate (60 FPS), add the higher frame rate step for 60 FPS if it\napplies. Note that adding additional steps requires more computing power. The\nfollowing is the recommended ladder:\n\nFor audio, the recommendations are based on the number of channels:"]]
