How does LVB recording work?

When you enable the recording for an LVB 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 URL 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 using the RecordInterval parameter.

Why is LVB recording not available?

LVB recording and playback is built on Tencent Cloud's VOD service. To use this feature, you need to activate VOD in the Tencent Cloud console.

How soon will the recording file be ready after the live streaming is over?

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.

After LVB recording is completed, how do I get the recording files?

The generated recording files are automatically stored in the VOD system. After you have activated VOD, you can get the recording files in the following ways:

• VOD Console
• Recording event notification
• VOD APIs

Can I migrate an LVB video?

You can use the download address of the video to migrate it.

How do I set the video storage period?

LVB currently has no limit on the video storage period. You can manage video files through the console and RSETful APIs.

How many recording files are generated in an LVB recording process?

• Recording a file in MP4, FLV or AAC format: the maximum recording length of a single file ranges from 5 to 20 minutes. You can specify a shorter segment using the RecordIntervall parameter of the CreateLiveRecordTemplate API.

• If the duration of a live stream is too short (for example, shorter than 1 second), no recording file is generated.

• If the duration of a live stream is not long (shorter than RecordInterval), and the push is not interrupted during the live stream, only one recording file is generated.

• If the duration of a live stream is very long (longer than 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.

• If the push is interrupted during a live stream (SDK will re-push later), a new segment will be generated every time the interruption occurs.

• Recording a file in HLS format: there is no upper limit. If a file exceeds the recording resumption timeout period, a new file will be created to continue recording. You can set the recording resumption timeout period to 0-1800 seconds.

How do I splice segments?

You can splice segments by using the TencentCloud APIs.

How do I troubleshoot when only one recording template is set but two recording streams exist?

In general, this might be because there are two recording tasks under the current push domain name. We recommend troubleshooting in the following ways:

1. Check the recording configuration in the console. Make sure that only one format is selected as the recording file type.
   • If you use the new console, go to Domain Management, click Manage on the right of the desired push domain name, select Template Configuration, and view the "Recording Format" of the associated template in the Recording Configuration tab.
2. You can use one of the following methods to record: create a recording task or create a recording template. If you create both recording templates and recording tasks for the same live stream, it will be recorded repeatedly. Check whether a recording task has been enabled in the console and another recording task has been enabled by CreateLiveRecord (API v3.0) or Live_Tape_Start (API v2.0) at the same time.

Note：

If the problem persists, please submit a ticket.