tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
Tencent Real-Time Communication
    Documentation

    Stream Mixing and Recording

    Last updated: 2022-09-26 16:47:34

      1. Mixtranscoding

      

      How do I know whether the new MCU stream mixing scheme or legacy on-cloud stream mixing scheme is used?

      If the following conditions are met and mcumix = 1 is printed in the client log, the new MCU stream mixing scheme is used:
      The application is created on or after January 9, 2020.
      The version of the TRTC SDK is v6.9 or above.
      

      What should I do if the stream mixing API fail to work?

      1. Make sure you have enabled relayed push in the TRTC console.
      2. Listen for onSetMixTranscodingConfig() and make modifications based on the error message returned.
      3. If a relayed stream ID is specified through an SDK API, the legacy on-cloud stream mixing scheme will fail.
      4. If the onSetMixTranscodingConfig() callback indicates that stream mixing is successful, but no mixed stream can be pulled via CDN, it may be caused by failure to set a playback domain name. Please check the configuration of your playback domain name.

      2. On-Cloud Recording

      

      How do I record users’ streams separately?

      Select Global Auto-Recording in the console, and each user’s stream in a room will be recorded automatically during publishing. For details, see Scheme 1: global auto-recording.
      Select Specified User Recording in the console and specify the userDefineRecordId parameter in TRTCParams during room entry. For details, see Scheme 2: user specified recording (SDK API).
      If you do not want to use global auto-recording and your platform does not support the APIs of the TRTC SDK, you can also use the Live Recording feature of CSS to record the streams of specified users.
      

      How do I record mixed streams?

      If Global Auto-Recording is selected in the console, mixed streams will be recorded automatically.
      If Specified User Recording is selected in the console, and a RESTful API is used to initiate stream mixing, you can record the mixed stream by specifying the OutputParams.RecordId parameter when calling the API. For details, see OutputParams.
      If Specified User Recording is selected in the console, and an SDK API is used to initiate stream mixing, you can record the mixed stream by letting the anchor specify the userDefineRecordId parameter in TRTCParams during room entry. For details, see Scheme 2: user specified recording (SDK API).
      

      When does recording start?

      Separate stream recording: a few seconds (network latency and keyframe waiting time) after publishing starts
      Mixed stream recording: a few seconds (network latency and keyframe waiting time) after stream mixing starts
      

      When does recording end?

      Separate stream recording ends after a stream stops. If a resumption timeout period is specified, the recording ends after the timeout period elapses.
      If the SDK API setMixTranscodingConfig() is used to initiate stream mixing, the recording ends after the anchor leaves or after setMixTranscodingConfig() is called again with null passed in.
      If the RESTful API StartMCUMixTranscode is used to initiate stream mixing, the recording ends after all users in the room leave or after StopMCUMixTranscode is called to stop stream mixing.
      

      When are recording files and callbacks generated?

      A recording file is saved to the VOD platform and recording callback triggered 5 minutes after recording finishes.
      If a resumption timeout period is specified, the time to wait will be 5 minutes plus the timeout period. Before the timeout period elapses, recording will not end even if the stream is interrupted. No recording file or callback will be generated either.
      There is an upper limit (which can be configured in the console) to the duration of recording files in MP4, FLV, or AAC format. Whenever this limit is exceeded, a recording file and callback will be generated, and the recording will continue.
      

      How do I obtain recording files?

      You can search for recording files in the VOD console or via a RESTful API of VOD. For detailed directions, see Searching for Recording Files.
      You can get the download URLs for recording files in recording callbacks. For details, see Receiving Recording File.
      

      What should I do if no recording files are generated?

      If a call is not set up successfully or publishing continues for a too short period (preferably longer than 30 seconds), a recording file may not be generated. You can check whether your upstream data is normal in the dashboard.
      If Specified User Recording is selected in the console, and userDefineRecordId in TRTCParams is not specified during room entry, the streams in a room will not be recorded.
      If Specified User Recording is selected in the console and a RESTful API is used to initiate stream mixing, but OutputParams.RecordId is not specified when the API is called, the mixed stream will not be recorded.
      If Specified User Recording is selected in the console and an SDK API is used to initiate stream mixing, but userDefineRecordId is not specified when the anchor calls the API, the mixed stream will not be recorded.
      

      What should I do if I don’t receive recording callbacks?

      Check in the console if recording files are generated. If not, refer to the previous question. For how to search for recording files, see Searching for Recording Files.
      If recording files are generated, check whether you have configured the callback correctly. For more information about callback configuration, see Receiving Recording File.
      If you have configured the callback correctly, check whether the server can handle callbacks properly, for example, by using curl to simulate callback requests.
      

      Why are so many recording files generated?

      If Global Auto-Recording is selected in the console, each stream in a room will be recorded into a separate file.
      If you haven’t configured a resumption timeout period, a recording file will be generated each time a stream is interrupted.
      There is an upper limit to the duration of recording files in MP4, FLV, or AAC format. Whenever the limit is exceeded, a recording file and callback will be generated, and the recording will continue.
      Multiple recording files may be generated if stream mixing is initiated multiple times in a room.
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy