AddLiveStreamTranscode
Calls AddLiveStreamTranscode to add transcoding configuration information.
Operation description
-
Using the live stream transcoding feature incurs transcoding fees, which are calculated based on the transcoding standard, resolution specification, and total transcoding length. For billing rules, see Live stream transcoding fees.
-
First obtain the user KMS master key ID through Key Management Service (KMS), and then invoke this operation to add default transcoding configuration information. Currently, this operation supports only two types of transcoding templates: standard quality templates and Narrowband HD™ transcoding templates.
-
Alibaba Cloud KMS provides default keys for server-side encryption of cloud services at no cost, and no instance purchase is required. However, if you need to build a custom application cryptographic solution, use the credential feature, or manage the key lifecycle, you must purchase a software or hardware key management instance. For billing details, see Billing.
QPS limit
The single-user QPS limit for this operation is 30 calls per second. If the limit is exceeded, API calls are throttled, which may affect your business. Invoke this operation appropriately.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
live:AddLiveStreamTranscode |
create |
*Domain
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
No |
The region ID. When using SDK 2.0, set this parameter to the region ID that corresponds to the service registration endpoint. When using SDK 1.0, ignore this parameter. |
cn-shanghai |
| Domain |
string |
Yes |
The streaming domain of the streamer. |
example.com |
| App |
string |
Yes |
The name of the application to which the stream belongs.
Note
If a transcoding template with App set to a single asterisk (*) is configured: when a user pulls a transcoded stream, the system first matches the transcoding template whose App value is the same as the AppName in the ingest URL. If no such template exists, the system matches the transcoding template with App set to a single asterisk (*). |
liveApp**** |
| Template |
string |
Yes |
The transcoding template. Valid values:
|
lsd |
| EncryptParameters |
string |
No |
The encryption configuration. JSON format. The fields are described as follows:
|
{"EncryptType": "aliyun", "KmsKeyID":"afce5722-81d2-43c3-9930-7601da11****","KmsKeyExpireInterval":"3600"} |
| Lazy |
string |
No |
Specifies whether to enable on-demand transcoding. Valid values:
|
yes |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The request ID. |
||
| RequestId |
string |
The request ID. |
16A96B9A-F203-4EC5-8E43-CB92E68F4CD8 |
Examples
Success response
JSON format
{
"RequestId": "16A96B9A-F203-4EC5-8E43-CB92E68F4CD8"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | InvalidParameters | %s Please check and try again later. | Exception parameter exists, please check and try again. |
| 400 | ConfigAlreadyExists | %s Please check and try again later. | Configuration already exists, please check and try again. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.