When you enable the recording for a live stream, the audio/video data is relayed to the recording system. Every frame pushed from the host's mobile phone is written into the recording file by the recording system.
If an LVB push is interrupted, the access layer will immediately notify the recording server to record the file being written, store it into the VOD system, and generate an index. Then, you can find the new recording file in the VOD system. If you have configured recording event notification on a server, the recording system will send the index ID and online playback address to the server.
However, an error will occur in the processes of transferring and processing a large file on the cloud. To ensure success, the maximum recording length of a file is 120 minutes, and you can specify a shorter segment by using the
The playback feature of LVB recording relies on Tencent Cloud's VOD service. If you want to use this feature, you need to activate VOD first in the Tencent Cloud console.
You may get the recording file in about 5 minutes after the live streaming is over. An event callback will be triggered when the recording ends, which provides accurate recording completion time. For more information, please see Callback Configuration.
You can use the download address of the video to migrate it.
LVB currently has no limit on the video storage period. You can manage video files through the console and RESTful APIs.
Recoding in MP4, FLV, or AAC format: the recording length of a file can be 5–120 minutes. You can specify a shorter segment by using the
RecordInterval parameter of the CreateLiveRecordTemplate API.
RecordInterval), and the push is not interrupted during the live stream, only one recording file is generated.
RecordInterval), the video will be segmented based on the length of time specified by
RecordInterval, to avoid the time uncertainty of the flow of the file with a longer duration in a distributed system.
Recording in HLS format: there is no upper limit. After the resuming timeout period (which can be set to 0–1800s) elapses, a new file will be created to continue recording.
Actually, Tencent Cloud as PaaS does not know how you defined one live stream. If one of your live streams lasted for 20 minutes, during which a push interruption caused by network switching occurred, and the live stream was stopped and restarted once manually. For common mobile live streaming, we generally define the period between the two time points as shown below as one live stream.
Therefore, the time information sent from the application client is important. If you want to define that all the files recorded during this period belong to this live stream, you just need to retrieve the recording notification you received by using LVB codes and time information (each recording notification event comes with the stream ID, start time, and end time).
Tencent Cloud supports splicing video fragments with a TencentCloud API. For more information on how to use this API, please see Edit Media.
In general, this might be because there are two recording tasks under the current push domain name. We recommend you troubleshoot in the following ways: